If you check this box, source proxy addresses will always overwrite the proxy addresses in the target, replacing whatever values are there, if any. If this box is left unchecked, the source proxy address will only be added to those target objects where this attribute is currently empty.
If you check this box, any TARGET contacts will be converted into mail-enabled users.
For the scope of this feature a Microsoft Exchange Mail Enabled Contact is defined as an Active Directory contact where the LegacyExchangeDN attribute is not null. A contact will be promoted to a user if the primary SMTP address on the a source object matches the external or target email address of the contact. Once the attributes have been stored on the newly created Microsoft Exchange User on the target, the Contact object will be removed from the target. The source User must have a LegacyExchangeDN. The contacts in the source, that will be converted, must be in a different OU than the Target OU selected on the AD Target tab.
This option may not be selected if the setting Create Mail Enabled Users As on the AD Target Options Users tab is set to Contact, or if the source object is already a contact.
If you check this box, any TARGET groups will be converted into mail-enabled users.
Checking this box will cause Directory Sync Pro for Active Directory to only update those objects that are mail-enabled.
Choose how to configure contacts for delegation.
If you need to migrate mailbox permissions, check the box that adds the x500 proxy to the source. Note that this is one of the only times that Directory Sync Pro for Active Directory makes any changes to a SOURCE object.
If you are migrating your mailboxes into a resource forest, check the Enable Resource Forest box. This will set the Master Account SID on all synchronized mailboxes in the target environment.
You have the option to create your own scripts using PowerShell that can be run against after a sync is completed. The script will run using the target credentials that you entered when creating this profile.
Directory Sync Pro for Active Directory looks for selected object attributes that you have chosen to match objects between the source and target. This screen allows you to control several Directory Sync Pro for Active Directory parameters for this process.
Choose the scope in which Directory Sync Pro for Active Directory should search for matching objects. If you choose Forest, Directory Sync Pro for Active Directory will examine the entire AD forest to match objects. If you choose domain, Directory Sync Pro for Active Directory will only check for matching objects at the domain level for those domains within the scope of this profile.
This is perhaps the most important parameter on this page. What do you want Directory Sync Pro for Active Directory to do if it finds a match based on your chosen mapping parameters? The default is Create or Update. This means that if Directory Sync Pro for Active Directory does not find a match, it will create a new object in the target. If a match is found, Directory Sync Pro for Active Directory will update the attribute values on the target object using the values from the attributes of the source object.
If you choose Create Only, then Directory Sync Pro for Active Directory will create a new object in the target for any unmatched objects. It will not update any attributes for those objects that have been matched.
Choose Update Only to update the attributes from source objects to matched target objects. No new objects will be created if a match is not found. A scenario in which you might choose this would be when the users have been pre-created in the target manually, and you just want to keep changes synchronized.
And finally, Match Only, No update (option not available for Exchange Intra-Forest Profiles) will make no changes to any objects. This is only chosen when you are using another product other than Migrator Pro for Active Directory for AD synchronization. It will import the values that are needed when Migrator Pro for Active Directory performs the ReACL and Cutover actions.
There may be the rare occasion where an object of one type in the source has a matching value for an object of another type in the target. Since these are not the same type, you may want Directory Sync Pro for Active Directory to be more precise in deciding if an object is a match. Check this box to require the type of object to be a final matching criterion.
For example, suppose CN or Common name is one of your matching criterion. And in the source we have a user with a Common Name of Cheryl in the source. In the target, we have a contact with the Common name of Cheryl. Directory Sync Pro for Active Directory would normally match these objects because they have the same Common name. If you check this box, it will consider that the object class is not the same, and therefore these objects do not match after all.
The relink option only comes in to play in the rare occasion that you have reset a profile thereby removing the objects created by this profile from the SQL database. But you did not delete the actual target objects created by Directory Sync Pro for Active Directory. Without the relink option, when this profile is synced again, Directory Sync Pro for Active Directory would not recognize the objects that it may have already migrated to the target as created by itself. This could cause unwanted behavior, depending on your Matching Action choices. This may also cause problems if you had chosen the rename option for collisions, as the rename could be appended or prepended twice due to an already existing renamed target object. We suggest that you leave this box checked. This will allow Directory Sync Pro for Active Directory to look for a special attribute that is populated by Directory Sync Pro for Active Directory in the target so that it knows that this object was created by Directory Sync Pro for Active Directory.
This option works in conjunction with the relink option. If Directory Sync Pro for Active Directory finds an target object that it had previously created based on the special relink attribute, it will mark the matching source object as Ready to Sync. This means the object will be included and updated during the next sync cycle, as long as Update is part of one of your Matching Action choices. We suggest that you leave this box checked.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
