Due to mergers and acquisitions or legal requirements, customers may have a need to deploy Exchange in a multiple Exchange forest topology. These deployments require the synchronization of recipient objects across disparate Active Directory directory service forests. To learn more about multiple Exchange forest topologies, see Planning for a Complex Exchange Organization.
Microsoft provides the GAL synchronization management agent for synchronizing recipient objects. The version of the GAL synchronization management agent that was included in Microsoft Identity Integration Server (MIIS) 2003 was designed to work with Exchange Server 2003 and relied on the Recipient Update Service (RUS). Because RUS is a deprecated feature and is no longer required for Exchange 2007, the new GAL synchronization management agent that is included in ILM 2007 is designed to function without RUS.
As part of the synchronization process, the ILM 2007 GAL synchronization management agent creates recipient objects in both Active Directory forests. After the recipients are created, the management agent uses the Update-Recipient cmdlet to add the attributes required by Exchange 2007 to complete the provisioning of these recipients.
Note: |
|---|
|
If you are using MIIS 2003, you must run various cmdlets to complete the provisioning process of the mail contacts created by the GAL synchronization management agent. For detailed information about provisioning mail contacts created by MIIS 2003, see How to Deploy Exchange 2007 in a Cross-Forest Topology. The Update-Recipient cmdlet provides an alternative and more efficient method to accomplish this. You can simply run the Update-Recipient cmdlet against the recipient objects created by the MIIS 2003 GAL synchronization management agent to complete their provisioning process.
|
To run the Update-Recipient cmdlet, the account you use must be delegated the following:
-
Exchange Recipient Administrator role
For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.