Tuesday 22 January 2013

How to change the Recipient Scope




What is a Recipient Scope ?

Recipient scope is the specified portion of Active Directory hierarchy that the Exchange Management Console (EMC) and the Exchange Management Shell uses for recipient management. When you set the recipient scope to a specific location within Active Directory, you can view and manage all recipients stored in that location, including all the containers under it.

The EMC and Shell always start with the recipient scope at the domain-level of the computer that is running the management interface. Neither the user account that's being used nor the Exchange servers being managed has bearing on the default value of the recipient scope.

How to change the Recipient Scope from EMC

In the console tree, click Recipient Configuration.
In the action pane, click Modify Recipient Scope.
In Recipient Scope dialog box, select one of the following options:
View all recipients in forest   Click this button to work with all recipients in the forest. To use a specific global catalog server, select the Global Catalogcheck box and then click Browse. In Select Global Catalog, select the global catalog server that you want to use. If you don't specify a global catalog server, Exchange automatically selects an available one. 

View all recipients in specified organizational unit   Click this button to work with all recipients in a specific organizational unit (OU) and all OUs under it. Click Browse, and then, in Select Organizational Unit, select the OU that you want to use.

To use a specific domain controller, select the Recipient Domain Controller check box. If you don't specify a recipient domain controller, Exchange automatically selects an available one.
Click OK.

How to change the Recipient Scope from EMS

Set-AdServerSettings -ViewEntireForest $true

If you would like to use a specific GC while using EMS, you add a parameter "PreferredGlobalCatalog"

Set-AdServerSettings -ViewEntireForest $true -PreferredGlobalCatalog NameoftheGC.Domain.com

No comments:

Post a Comment