The Global Address List Synchronization Solution (GalSync) allows you to take a mail-box enabled user from one forest, and create a mail-enabled contact object in another forest, allowing the ability to share Global Address Lists (GALs).
However, by default, GalSync puts all of the mail-enabled contacts into a single Organizational Unit (container).
The goal of this document is to provide the necessary steps and details on how to provision the mail-enabled contacts from multiple forests into separate Target Oganizational Units.
The following steps are involved in this process:
To enable ILM to make the provisioning decision, your source management agents need to populate the metaverse with an attribute that can used by your provisioning code to determine the source of an object.
For the scenario in this article, the msExchOriginatingForest attribute is used for this purpose.
All contributing management agents need to populate this attribute in the metaverse with a fully qualified distinguished name of the originating forest.
The following section provides the configuration steps.
In this section, we will cover how to create the OrganizationalUnit structure(OU) in the Active Directory in order to have this work for us.
It is recommended that you have a starting OU for the Target Contacts, so that you can use that in the code later on, and in the Target Contacts container of the Export Management Agent.
This section will walk us through step by step on how to update the GalSync solution to enable provisioning of mail-enabled contacts into separate Target Organizational Units.
It is important that you have the above steps completed before moving to this section as to avoid synchronization errors when testing the solution.
To update your GalSync solution, you perform the following steps:
As a first step, you need to backup and change the name of your GalSync solution
You need to update the Build Output path to prevent the GalSync.XML file from being overwriten.
This is a configuration file that holds the different GalSync Management Agents we have built in the
If by chance you do overwrite this file, follow the steps outlined in
KB 948167 (http://support.microsoft.com/kb/948167).
In this section, you find the required modification steps for your provisioning code.
'// SAMPLE CODE
'// PURPOSE: Illustrate how to have contact objects exported to different
'// organizational Units.
'// MEMORY VARIABLES:
'// myTargetOganizationalUnit: Sets the Target Oganizational Unit for us
'// myOriginatingForest: Captures the originating forest information from the
'// metaverse person object type (msExchOriginatingForest attribute).
'// we force it to lower case to be sure that we can match the data.
Dim myTargetOganizationalUnit As String = ""
Dim myOriginatingForest As String = mventry("msExchOriginatingForest").Value.ToLower()
'// Sets the OU to Provision to
If myOriginatingForest = "sample.microsoft.com" Then
myTargetOganizationalUnit = "ou=Sample MSFT Contacts, " '// the comma is needed
ElseIf myOriginatingForest = "sample.net" Then
myTargetOganizationalUnit = "ou=Sample CONTACTS, " '// the comma is needed
'// If you have additional forests, you will need to add additional ElseIF
'// statements to match those conditions.
'// END NOTE:
'// END OF SAMPLE CODE
In this section you find the required steps for building the solution.
In this section, you will find the steps for testing the updated solution.
The test consist of a verification that the updated solution provisions to the correct OU.
To test the solution: