2 min read

E2K7: How to Change the Recipient Scope

When managing Exchange 2007, the recipient scope for Exchange Management Shell (EMS) and Exchange Management Console (EMC) defaults to the domain where the Exchange servers are located. Recipient scope refers to the specified portion of the Active Directory directory service hierarchy that the Exchange Management Console 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 and all of the containers under it. If your environment has multiple domains, then you may need to change the scope of recipients to find specific accounts.

Changing the recipient scope in the Exchange Management Console

  1. Start the Exchange Management Console.
  2. In the console tree, click Recipient Configuration.
  3. In the action pane, click Modify Recipient Scope.
  4. In Recipient Scope, select one of the following options:
    1. 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 Catalog check 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, Exchange automatically selects an available global catalog server.
    2. 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.
    3. To use a specific domain controller, select the Recipient Domain Controller check box. If you do not specify a recipient domain controller, Exchange automatically selects an available domain controller.
  5. Click OK.


Changing the recipient scope in the Exchange Management Shell

You must change the variable $AdminSessionADSettings.DefaultScope in EMS to change the scope. You can do this by running the following command:

$AdminSessionADSettings.DefaultScope = “<domain name>” (i.e. yourcompany.com)


You can also select a preferred Domain Controller using the following command:

$AdminSessionADSettings.PreferredDomainControllers = “<domain controller name>” (i.e. dc1.yourcompany.com)


You can set the scope to view entire domain with the following command:

$AdminSessionADSettings.ViewEntireForest = $True




  • The Microsoft Management Console (MMC) saves any changes you make to a snap-in as preferences in your user profile on the administrator computer. The recipient scope setting is also saved as one of your preferences. As a result, the next time you start the Exchange Management Console on the same computer, the default setting of the recipient scope is overwritten by the scope that you last specified. However, if you use another computer or a different user account to run the Exchange Management Console, you will need to adjust the recipient scope again.

Changing the recipient scope in the Exchange Management Shell changes the set of recipients that are returned for the Get- cmdlets of the recipient. The recipient scope is accessible by using the $AdminSessionADSettings variable.

Change Recipient Scope PermanentlyIf you are trying to change the recipient scope of Exchange Management Shell permanently you need to modify the Exchange.ps1 file located in ExchangeBin.Locate the line “$global:AdminSessionADSettings.ViewEntireForest = $false” and change it to “$global:AdminSessionADSettings.ViewEntireForest = $true”.

For More Info:http://technet.microsoft.com/en-us/library/bb124791.aspx

Everything to Know About Cloud VDI and Azure Virtual Desktop

By now, most of us have experienced some form of remote work, whether it was during the height of the pandemic or now in the midst of the hybrid work...

What's New in SQL Server 2022 – Licensing Updates

SQL Server 2022 is now generally available and with it come some licensing changes you need to be aware of. Microsoft also announced that SQL Server...

Azure Modernization Assessment: Building a Robust Cloud-Ecosystem Starts Here

The pandemic may have accelerated the cloud journey trend, but cloud momentum isn’t slowing down anytime soon. Cloud adoption increased 25% in the...