Recipient scopes for Exchange, PowerShell management domain, or entire forest

Exchange Administrative tools can be configured to use a specific subset of Active Directory hierarchies using a particular recipient scope. When you set the recipient scope to a location in the Active Directory, such as a domain or an organizational unit,theExchange Management Shell only allows you to view the recipient information within the specified scope. In this section, let's look at how to set the recipient scope using the Exchange Management Shell .

How do we do that?

can be in Exchange Management Shell used in set-adserversettings command to set a recipient range. For example, to set an OU in the current domain , the command is as follows:

set-adserversettings-recipientviewroot "corp.robin.com/viplab/ Group Headquarters / Technical Center "

You can also use Distinguished Name to specify OU , the command is as follows:

set-adserversettings–recipientviewroot "ou= Technical Center , ou= Group Headquarters , ou=viplab,dc=corp,dc=robin,dc=com "

in theExchange -, the recipient scope is set using theadminsessionadsettingset and act as the global session variable. In theExchangeand the -, is the use ofset-adserversettingscommand. When first startedExchange Management Shell, the default recipient range is set to the current runShelldomain computer. If you change the recipient range, when you restartShellwhen the configuration file is not saved. Of course, we can add the order toPowerShellconfiguration file to overwrite the.

in the previous example, you can set the recipient range to a certain OU . If you are in a multi-domain forest, you can use the -viewentireforest parameter so that the recipient objects of all forests in the session can be managed. The command is as follows:

Set-adserversettings–viewentireforest $True

To change the recipient range to the specified domain, the command is as follows:

Set-adserversettings–recipientviewroot corp.robin.com

If you work in a large environment, there are multiple domains and ou exchange Management Shell efficiency. If your exchange recipient in multiple Span style= "FONT-FAMILY:CALIBRI;" >ad domain or multiple sites, you may have replication delays. To avoid this, we can use the set-adserversettings command to specify the domain controller and GC server.

we can use parameters to set a preferred domain controller and a global catalog server to qualify the recipient range, using -setpreferreddomaincontrollers and the -preferredglobalcatalog parameter to specify the server's FQDN .

Set-adserversettings-viewentireforest $true '

-setpreferreddomaincontrollers robindc01.corp.robin.com '

-preferredglobalcatalog robindc01.corp.robin.com

use a preferred domain controller to make sure that you AD the list of recipients in is very recent and useful. If you specify a specific domain controller in a multi-domain or multi-site to create a recipient, it may take some time to replicate the information to the entire forest. Therefore, setting a preferred domain controller ensures that the current recipient list is up-to-date, even if the information is not replicated to the entire forest

This article from "Robin's Home" blog, declined reprint!

Recipient scopes for Exchange, PowerShell management domain, or entire forest