Professional Documents
Culture Documents
Exchange 2013 Exam Notes
Exchange 2013 Exam Notes
12:02
General
Well-known ports
SMTP TCP 25
SMTP (MSA) TCP 587
SMTP (Encrypted) TCP 465 <-- No SMTP Extensibility
POP3 TCP 110
POP3S TCP 995
IMAP TCP 143
IMAPS TCP 993
CAS listens for SIP unsecured on TCP 5060
CAS listens for SIP secured (TLS) on TCP 5061
Mailbox server when UMStartupMode is set to Dual, listens for SIP unsecured on TCP 5065 and 5067
Mailbox server when UMStartupMode is set to Dual, listens for SIP secured (TLS) on TCP 5065 and 5067
Mailbox server when set to TCP (Default) or TLS, listens for SIP on TCP 5065 and 5066.
Various
EAC (web based Exchange Administration Center)
Set-ServerComponentState to take CAS or Mailbox offline
Cmdlet enhancements
Forefront Online Protection for Exchange (FOPE) --> Exchange Online Protection (EOP)
EAC Feature Panes info
Site mailboxes accessible through sharepoint and Outlook 2013, but don't appear in OWA
Hybrid Configuration Wizard (HCW)
What's New in Exchange 2013
Planning and deployment
The *-ServerMonitoringOverride and *-GlobalMonitoringOverride cmdlets enable administrators to set, remove, or view overrides.
Get-ServerHealth is used to retrieve the raw health data, while Get-HealthReport operates on the raw health data and provides a current snapshot of the health.
For DAG membership Server 2008 enterprise or Server 2012 Standard/Datacenter required
Prepare AD:
1) setup /PrepareSchema or setup /ps
2) setup /PrepareAD [/OrganizationName:<organization name>] or setup /p [/on:<organization name>]
3) setup /PrepareDomain:<FQDN of domain you want to prepare> to prepare a specific domain.
setup /PrepareAllDomains or setup /pad to prepare all domains in your organization.
New OU in the root domain called Microsoft Exchange Security Groups. This OU should contain the following new Exchange USGs:
Compliance Management
Delegated Setup
Discovery Management
Exchange Servers
Exchange Trusted Subsystem
Exchange Windows Permissions
ExchangeLegacyInterop
Help Desk
Hygiene Management
Organization Management
Public Folder Management
Recipient Management
Records Management
Server Management
UM Management
View-Only Organization Management
Exchange 2013 setup.exe parameters
DNS name configuration:
FQDN
Contoso.com
MX
Mail.contoso.com
Mail.contoso.com
172.16.10.11
Owa.contoso.com
172.16.10.11
Autodiscover.contoso.com A
172.16.10.11
Virtual directories:
Virtual directory
Autodiscover
ECP
https://mail.contoso.com/ecp
EWS
https://mail.contoso.com/EWS/Exchange.asmx
Microsoft-Server-ActiveSync https://mail.contoso.com/Microsoft-Server-ActiveSync
OAB
https://mail.contoso.com/OAB
OWA
https://mail.contoso.com/owa
PowerShell
http://mail.contoso.com/PowerShell
Permissions
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn
Get-RoleGroupMember "View-Only Organization Management"
Set-Mailbox Brian -RoleAssignmentPolicy "Unified Messaging Users"
Get-ManagementRole <role name> | Format-List
Get-ManagementRole "Mail Recipients" -Recurse
Get-ManagementRoleAssignment -Role <role name> -GetEffectiveUsers
Get-ManagementRole -Cmdlet <cmdlet>
Add-ManagementRoleEntry "Recipient Administrators \Set-Mailbox"
Get-ManagementRoleEntry <role name>\*
New-ManagementRoleAssignment -Name "Exchange Servers_SeattleAdmins" -SecurityGroup SeattleAdmins -Role "Exchange Servers"
Mail Flow
& $env:ExchangeInstallPath\Scripts\Disable-Antimalwarescanning.ps1
Set-MalwareFilteringServer -BypassFiltering $true
Anti-virus client on exchange server exclusions to configure includes important path locations
With routing groups and Routing Group connectors you can consolidate communication between servers by designating bridgehead servers that act as communication points between routing groups.
With routing groups and Routing Group connectors you can consolidate communication between servers by designating bridgehead servers that act as communication points between routing groups.
Modify NDR with New-SystemMessage
Message size limits and how to configure using powershell
Exchange Toolbox console MMC
Mail flow tools
Queue Viewer
Tracking log explorer
Configuration management tools
Eemote connectivity analyzer
Details Templates Editor
Pickup directory is %ExchangeInstallPath%TransportRoles\Pickup.
Replay directory is %ExchangeInstallPath%TransportRoles\Replay.
Edge Transport server not currently available in Microsoft Exchange Server 2013. Use 2007 or 2010 version.
Recipients
Mailbox
New-Mailbox -Alias pilarp -Name "Pilar Pinilla" -FirstName Pilar -LastName Pinilla -DisplayName "Pilar Pinilla" -UserPrincipalName pilarp@contoso.com -Password (ConvertToSecureString -String 'Pa$$word1' -AsPlainText -Force)
Set-Mailbox -Identity patc -DeliverToMailboxAndForward $true -ForwardingAddress sunilk@contoso.com
Get-Mailbox -OrganizationalUnit "Marketing" | Set-Mailbox -IssueWarningQuota 209715200 -ProhibitSendQuota 262144000 -ProhibitSendReceiveQuota 293601280 -UseDatabaseQuotaDefaults
$false
Get-Mailbox -Filter "Department -eq 'Customer Service'" | Set-Mailbox -MaxSendSize 2097152
Distributiongroup
New-DistributionGroup -Name "IT Administrators" -Alias itadmin -MemberJoinRestriction <open|closed|owner>
New-DistributionGroup -Name "All Administrators" -IgnoreNamingPolicy
New-DistributionGroup -Name "File Server Managers" -Alias fsadmin -Type security
Set-DistributionGroup -Identity "Goverment_Contracts_NWRegion" -Name "Government_ContractEstimates_NWRegion" -DisplayName "Government_ContractEstimates_NWRegion" -IgnoreNamingPolicy
Set-DistributionGroup "Seattle Employees" -EmailAddresses SMTP:sea.admins@contoso.com,smtp:admins@contoso.com
Dynamicdistributiongroup
New-DynamicDistributionGroup -IncludedRecipients MailboxUsers -Name "Mailbox Users DDG" -OrganizationalUnit Users
Get-DynamicDistributionGroup -ResultSize unlimited | Set-DynamicDistributionGroup -HiddenFromAddressListsEnabled $true -MaxReceiveSize 5MB -ModerationEnabled $true -ModeratedBy
administrator
Set-DynamicDistributionGroup -Identity "All Employees" -EmailAddresses SMTP:All.Employees@contoso.com, smtp:Seattle.Employees@contoso.com
Mailcontact
New-MailContact -Name "Debra Garcia" -ExternalEmailAddress dgarcia@tailspintoys.com -OrganizationalUnit Users
Enable-MailContact -Identity "Karen Toh" -ExternalEmailAddress ktoh@fourthcoffee.com
Use the Get-Contact and Set-Contact cmdlets to view and change organization and contact information properties.
Use the Get-MailContact and Set-MailContact cmdlets to view or change mail-related properties, such email addresses, the MailTip, custom attributes, and specify whether the contact is hidden from address lists.
Mailuser
Mail users are similar to mail contacts. Both external. Unlike a mail contact, a mail user has Active Directory logon credent ials and can access resources.
New-MailUser -Name "Jeffrey Zeng" -Alias jeffreyz -ExternalEmailAddress jzeng@tailspintoys.com -FirstName Jeffrey -LastName Zeng -UserPrincipalName jeffreyz@contoso.com -Password (ConvertToSecureString -String 'Pa$$word1' -AsPlainText -Force)
Room mailbox
New-Mailbox -Database "Mailbox Database 1" -Name ConfRoom1 -OrganizationalUnit "Conference Rooms" -DisplayName "Conference Room 1" -Room
Get-User and Set-User to view and set general properties such as location, department, and company names.
Get-Mailbox and Set-Mailbox to view and set mailbox properties, such as email addresses and the mailbox database.
Get-CalendarProcessing and Set-CalendarProcessing to view and set booking options and delegates.
Equipment mailbox
Similar to room mailboxes, but uses parameter -equipment instead of -room
New-Mailbox -Database "Mailbox Database 1" -Name MotorVehicle2 -OrganizationalUnit Equipment -DisplayName "Motor Vehicle 2" -Equipment
Collaboration
Site mailbox
Site mailbox picture explanation
The lifecycle of a site mailbox is managed through SharePoint. It is through SharePoint that you should perform all site mailbox tasks such as creating and removing site mailboxes. In addition, you can create a SharePoint Lifecycle policy to
manage the lifecycle of a site mailbox. For example, you can create a lifecycle policy in SharePoint that automatically closes all site mailboxes after 6 months. If the user still requires the use of the site mailbox, the user can reactivate the site
mailbox through SharePoint. We recommend that you use the Lifecycle application is in the farm. Manually deleting active site mailboxes from Exchange will result in orphaned site mailboxes. .
When the lifecycle application in SharePoint closes a site mailbox, the site mailbox is retained for the period stated in the lifecycle policy in the closed state. The mailbox can then be reactivated by an end -user or by an administrator
from SharePoint. After the retention period, the Exchange site mailbox that is housed in the mailbox database will have its n ame prepended with MDEL: to indicate that it has been marked for deletion. You will need to manually
remove these site mailboxes from the mailbox database in order to free storage space and the alias. If you dont have the Sha rePoint Lifecycle Policy enabled, youll lose the ability to determine which site mailboxes are marked for
deletion. Until the site mailbox has been removed by an administrator, the content of the mailbox is still recoverable.
You can use the following command to search for and remove site mailboxes that have been marked for deletion.
Public folders in Microsoft Exchange 2013 have been modernized to take advantage of the existing high availability and storag e technologies of the mailbox database. The public folder architecture uses specially designed
mailboxes to store both the hierarchy and the public folder content. This also means that theres no longer a public folder d atabase. Public folder replication now uses the continuous replication model. High availability for
the hierarchy and content mailboxes are provided by a database availability group (DAG).
The master hierarchy mailbox was the first one created in the organization and cannot be changed.
If the master hierarchy public folder mailbox goes down, the user can still view the public folders. However, they wont be able to write to the public folders. To help prevent the hierarchy from going down, we recommend
that your public folders are included in a database availability group (DAG).
Create a secondary public folder hierarchy mailbox for load balancing purposes
New-Mailbox -PublicFolder -name MasterHierarchy
New-Mailbox -PublicFolder -name Istanbul -Database DB01Istanbul
Shared mailboxes
Mailbox that multiple users can use to read and send email messages. Provides common calendar (schedule vacations, work shifts, etc)
New-Mailbox -Shared -Name "Sales Department" -DisplayName "Sales Department" -Alias Sales | Set-Mailbox -GrantSendOnBehalfTo MarketingSG | Add-MailboxPermission -User MarketingSG -AccessRights
Details templates
Details templates control the appearance of the object properties that are accessed by using address lists in an email client, such as Microsoft Outlook. For example, when a user opens an address list in Outlook, the
properties of the recipients in that address list are presented as defined by the details template that exists in your Exchange organization.
Details templates editor is in the exchange toolbox.
Restore a details template to the default:
Restore-DetailsTemplate -Identity "en-US\Contact"
%s = surname / lastname and %2g = first two letters of the given name.
New-EmailAddressPolicy -Name 'Execs' -EnabledEmailAddressTemplates 'SMTP:%2g%s@contoso.com' -RecipientFilter {((RecipientType -eq 'UserMailbox') -and (Title -like 'executive'))}
Set-EmailAddressPolicy -Identity "South East Offices" -ConditionalStateorProvince "Georgia","Alabama","Louisiana","Texas"
Hierarchical address books (HAB)
Graphical representation of Hierarchical Address Book
You can provide an additional level of hierarchical structure by using the SeniorityIndex parameter. When creating an HAB, use the SeniorityIndex parameter to rank individual recipients or organizational groups by seniority within
these organizational tiers. This ranking specifies the order in which the recipients or groups are displayed in the HAB. For example, in the preceding example, the SeniorityIndex parameter for the recipients in the Corporate Office
division is set to the following:
Detailed instructions for creating HABs are included in the topic Enable or Disable Hierarchical Address Books. The general steps are as follows:
1. Create a distribution group that will be used for the root organization (top-level tier). If desired, you can use an existing organizational unit in your Exchange forest for the distribution group.
2. Create distribution groups for the child tiers and designate them as members of the HAB. Modify the SeniorityIndex parameter of these groups so they're listed in the proper hierarchical order within the root organization.
3. Add organization members. Modify the SeniorityIndex parameter of the members so they're listed in the proper hierarchical order within the child tiers.
4. For accessibility purposes, you can use the PhoneticDisplayName parameter, which specifies a phonetic pronunciation of the DisplayName parameter.
Parameter
Set-OrganizationConfig HierarchicalAddressBookRoot
Set-Group
IsHierarchicalGroup
SeniorityIndex
PhoneticDisplayName
Set-User
SeniorityIndex
PhoneticDisplayName
Set-Contact
SeniorityIndex
PhoneticDisplayName
New-OfflineAddressBook -Name "OAB_Contoso" -AddressLists "\Default Global Address List" -Server SERVER01 -VirtualDirectories "SERVER01\OAB (Default Web Site)
Set-OfflineAddressBook -Identity "My OAB" -AddressLists AddressList1,AddressList2,AddressList3
Set-OfflineAddressBook -Identity "My OAB" -IsDefault $true
Set-OfflineAddressBook -Identity "My OAB" -Schedule "Sun.1:15 AM-Sun.1:30 AM"
Get-User -ResultSize Unlimited -Filter { Company -eq "Contoso" -and RecipientType -eq "UserMailbox" } | Where { $_.CountryOrRegion -eq "United States"} | Set-Mailbox -OfflineAddressBook "Contoso United
States
Set-OABVirtualDirectory "OAB (Default Web Site)" -ExternalUrl https://contoso.com/OAB
Sharing
Federation
Federated sharing:
A group of Exchange features that leverage a federation trust with the Microsoft Federation Gateway (free Microsoft cloud -based service) to work across Exchange organizations, including cross -premises Exchange
deployments. Together, these features are used to make authenticated requests between servers on behalf of users across multi ple Exchange organizations.
Federation example
Configure Federated Sharing
1. Create and configure a federation trust
2. Create an organization relationship
3. Create a sharing policy
4. Configure an Autodiscover public DNS record
Organization relationships
An organization relationship enables users in your Exchange organization to share calendar free/busy information as part of f ederated sharing with other federated Exchange organizations.
New-OrganizationRelationship -Name "Contoso" -DomainNames "contoso.com","northamerica.contoso.com","europe.contoso.com" -FreeBusyAccessEnabled $true -FreeBusyAccessLevel
LimitedDetails
Sharing policies
Sharing policies enable user-established, people-to-people sharing of both calendar and contact information with different types of external users.
Sharing polices are assigned to user mailboxes and allow your users to self-manage and share both their free/busy and contact information (including the Calendar and Contacts folders) with recipients in other external
federated organizations.
For recipients that aren't in an external federated organization or are in non-Exchange organizations, sharing policies allow people-to-people sharing of their calendar information with anonymous users through the use of
Internet Calendar Publishing.
New-SharingPolicy -Name "Contoso" -Domains contoso.com: CalendarSharingFreeBusyDetail, ContactsSharing
Get-Mailbox -Filter {Department -eq "Marketing"} | Set-Mailbox -SharingPolicy "Contoso Marketing"
Remote wipe
Device password policies
Minimum password length
Password complexity (minimum number of character sets, require alphanumeric password)
Enforce password history
Inactivity time before locking device
Wipe device after x failed attempts
After a remote device wipe has occurred, data recovery is very difficult. However, no data removal process leaves a mobile de vice as free from residual data as when it's new. Recovery of
data from a mobile device may still be possible using sophisticated tools.
Password recovery
Device encryption policies
Require encryption on device
Require encryption on storage cards
Other security policies
Allow Camera
Allow Wi-Fi
Allow unsigned applications
Unapproved InROM application list
Disable removable storage
Disable IrDA
Disable Bluetooth
Disable Desktop Sync
Block Remote Desktop
Block Internet Sharing
IRM enabled
POP3 and IMAP4
IMAP4 and POP3 clients have limited access to calendar information for Exchange.
By default, POP3 and IMAP4 are disabled in Microsoft Exchange Server 2013. To enable them, start the services
Microsoft Exchange POP3 service
Microsoft Exchange POP3 Backend service
Microsoft Exchange IMAP4
Microsoft Exchange IMAP4 Backend service
Enable POP3 and/or IMAP4 for users
Set-CASMailbox -Identity "John Smith" -POPEnabled $true -IMAPEnabled $true
Force Office Web Apps Server rendering before they can open them:
Set-OwaVirtualDirectory "Server01\owa (Default Web Site)" -ForceWacViewingFirstOnPublicComputers $true -ForceWacViewingFirstOnPrivateComputers $true
MailTips
MailTips are informative messages displayed to users while they're composing a message. Microsoft Exchange Server 2013 analyz es the message, including the list of recipients to which it's addressed, and if it detects a
potential problem, it notifies the user with MailTips prior to sending the message. With the help of the information provided by MailTips, senders can adjust the message they're composing to avoid undesirable situations
or non-delivery reports (NDRs).
MailTips are subject to the following restrictions:
MailTips aren't supported when working in offline mode in Outlook.
When a message is addressed to a distribution group, the MailTips for individual recipients that are members of that distribution group aren't evaluated. However, if any of the members is an external recipient, the External
Recipients MailTip is displayed, which shows the sender the number of external recipients in the distribution group.
If the message is addressed to more than 200 recipients, individual mailbox MailTips aren't evaluated due to performance reasons.
Custom MailTips are limited to 250 characters.
If the sender starts composing a message and leaves it open for an extended period of time, the Automatic Replies and Mailbox Full MailTips are evaluated every two hours.
Dial plan
For a single SIP dial plan, add all Client Access and Mailbox servers to the SIP dial plan. For multiple SIP dial plans, add all Client Access and Mailbox servers to each SIP dial
plan. This will make both servers trusted peers of Office Communications Server 2007 R2 or Lync Server. You must use the same certificate in your Office Communications
Server 2007 R2 or Lync Server deployment as you do on each Client Access and Mailbox server.
For a single SIP dial plan, add all Client Access and Mailbox servers to the SIP dial plan. For multiple SIP dial plans, add all Client Access and Mailbox servers to each SIP dial
plan. This will make both servers trusted peers of Office Communications Server 2007 R2 or Lync Server. If the certificates b eing used on the Client Access and Mailbox
servers are different, you must use the same certificate in your Office Communications Server 2007 R2 or Lync Server deployme nt as you do on each Client Access and
Mailbox server in your organization.
When you create a dial plan, you can configure the primary and secondary ways that callers can search for names to locate a user when they call an Outlook Voice Access number or a UM auto attendant that's
associated with the dial plan.
Set-UMDialPlan -Identity MyUMDialPlan -DialByNamePrimary <FirstLast|LastFirst|SMTPAddress>
Set-UMDialPlan
Set-UMDialPlan
Set-UMDialPlan
Set-UMDialPlan
Set-UMDialPlan
Set-UMDialPlan
-identity
-identity
-identity
-identity
-identity
-identity
MyUMDialPlan -LogonFailuresBeforeDisconnect 5
MyUMDialPlan -MaxCallDuration 10
MyUMDialPlan -MaxRecordingDuration 10
MyUMDialPlan -RecordingIdleTimeout 10
MyUMDialPlan -InputFailuresBeforeDisconnect 5
MySecureDialPlan -VoIPSecurity <Secured|SIPsecured|Unsecured>
UM IP Gateways
A Unified Messaging (UM) IP gateway represents a physical Voice over IP (VoIP) gateway, IP Private Branch eXchange (PBX), orSession Border Controller (SBC) hardware device. Before a VoIP gateway, IP PBX, or SBC
can be used to answer incoming calls and send outgoing calls for voice mail users, a UM IP gateway must be created in the directory service.
After you install your Client Access and Mailbox servers, you need to create UM IP gateways, and if you need them to support IPv6, you must also:
1. Create a new UM IP gateway or configure an existing UM IP gateway with an IPv6 address for each of the IP gateways, IP PBXs, or SBCs on your network. When youre creating and configuring the required UM IP
gateways, you must add the IPv6 address or the Fully Qualified Domain Name (FQDN) for the UM IP gateway. If youre adding the FQDN to the UM IP gateway, you must have created the correct DNS records to resolve
the UM IP gateway FQDN to the IPv6 address. If you have an existing UM IP gateway, you can use the Set-UMIPgatewaycmdlet to configure the IPv6 address or FQDN.
2. Configure the IPAddressFamily parameter on each UM IP gateway. To enable the VoIP gateway to accept IPv6 packets, you must set the UM IP gateway to either accept both IPv4 and IPv6 connections, or accept only
IPv6 connections, by using the Set-UMIPgateway cmdlet.
Prepare-MoveRequest.ps1
Recoverable Items folder
To protect from accidental or malicious deletion and to facilitate discovery efforts commonly undertaken before or during litigation or investigations, Microsoft Exchange Server 2013 uses the Recoverable Items folder. The
Recoverable Items folder replaces the feature known as the dumpster in Exchange Server 2007. The Recoverable Items folder is used by the following Exchange features:
Terminology
Delete. Item is deleted from any folder and placed in the Deleted Items default folder.
Soft delete. Item is deleted from the Deleted Items default folder (or Shift+delete) and placed in the Recoverable Items folder.
Hard delete. item is marked to be purged from the mailbox database. This is also known as a store hard delete.
Description
New-MailboxImportRequest
Starts the process of importing a .pst file to a mailbox or personal archive. You can create more than one import request per mailbox. Each request must have a unique name.
Set-MailboxImportRequest
Changes import request options after the request is created or recover from a failed request.
Suspend-MailboxImportRequest
Suspends an import request any time after the request is created but before the request reaches the status of Completed.
Resume-MailboxImportRequest
Remove-MailboxImportRequest
Removes fully or partially completed import requests. Completed import requests aren't automatically cleared. You must use th is cmdlet to remove them.
Get-MailboxImportRequest
Admin roles
User roles
Outlook Web App Policies
Compliance management
In-place eDiscovery & hold
Auditing
Data loss prevention
Retention policies
Retention tags
Journal rules
Organization
Sharing
Apps
Protection
Malware filter
Connection filter
Content filter
Outbound spam
Quarantine
Mail flow
Rules
Delivery reports
Message trace
Accepted domains
Connectors
Mobile
Mobile device access
Mobile device mailbox policies
Public
folders
Public folders
Public folder mailboxes
Unified messaging
UM dial plans
UM IP gateways
Server Health and Performance
Managed Availability
Exchange 2013 introduces the concept of managed availability. Managed availability runs on every Exchange 2013 server. Its made up of two processes, the Exchange Health Manager Service (MSExchangeHMHost.exe) and the Exchange
Health Manager Worker process (MSExchangeHMWorker.exe), and the following asynchronous components:
Probe engine The probe engine takes measurements on the server.
Monitoring probe engine The monitoring probe engine stores the business logic about what constitutes a healthy state. It functions like a pattern recognition engine, looking for patterns and measurements that differ from
a healthy state, and then evaluating whether a component or feature is unhealthy.
Responder engine When the responder engine is alerted about an unhealthy component, its first action is to try to recover that component. Managed availability enables multi-stage recovery actions. The first attempt may
be to restart the application pool, the second attempt may be to restart the corresponding service, and the third attempt may be to restart the server. And, the final attempt may be to put the server offline, so that it no longer
accepts traffic. If all of these actions fail, an alert is sent to the help desk.
accepts traffic. If all of these actions fail, an alert is sent to the help desk.
For more information about managed availability, see Lessons from the Datacenter: Managed Availability , and Server Health, Monitoring, and Performance Cmdlets .
Exchange workload Management
An Exchange workload is an Exchange Server feature, protocol, or service thats been explicitly defined for the purposes of E xchange system resource management. Each Exchange workload consumes system resources
such as CPU, mailbox database operations, or Active Directory requests to run user requests or background work. Examples of E xchange workloads include Outlook Web App, Exchange ActiveSync, mailbox migration, and
mailbox assistants.
Settings can be customized. For more information, see Exchange Workload Management and Server Health, Monitoring, and Performance Cmdlets .
Includes the following components:
System Workload management (new in Exchange 2013)
Resource policies
New-ResourcePolicy
Remove-ResourcePolicy
Get-ResourcePolicy
Set-ResourcePolicy
Workloadmanagement policies
New-WorkloadManagementPolicy
Remove-WorkloadManagementPolicy
Get-WorkloadManagementPolicy
Workload policies
New-WorkloadPolicy
Remove-WorkloadPolicy
Get-WorkloadPolicy
Set-ResourcePolicy
User workload management (called user throttling in Exchange Server 2010)
Manage throttling policies
New-ThrottlingPolicy
Get-ThrottlingPolicy
Set-ThrottlingPolicy
Remove-ThrottlingPolicy
Get-ThrottlingPolicyAssociation
Set-ThrottlingPolicyAssociation
Configuration
examples:
Change workload management policy settings for all servers in your organization
New-WorkloadPolicy OrgIMAPWorkloadPolicy -WorkloadType IMAP -WorkloadClassification Discretionary -WorkloadManagementPolicy GlobalOverwrittenWorkloadManagementPolicy
Change workload management policy settings for a specific server
New-WorkloadPolicy DublinIMAPWorkloadPolicy -WorkloadType IMAP -WorkloadClassification Discretionary -WorkloadManagementPolicy DublinWorkloadManagementPolicy.
Set-ExchangeServer -WorkloadManagementPolicy DublinWorkloadManagementPolicy -Server Dublin01.
Workload management reference