I am run in the process of configuring FIM 2010R2 GALSYNC between multiple AD Forests but there are few challenges which I need to understand how FIM will react to it.
1. The environment I am trying to configure GALSYNC on used to have MIIS AD MA connectors many years back. They decided to migrate from MIIS to FIM2010. After the migration there were some issues so they stopped using FIM2010 (it was still using AD DS management agent inherited from MIIS) for GALSYNC.
2. We then moved to powershell scripts through which we manually imported and exported contacts in each domain.
3. Finally it has been decided to deploy a new FIM2010R2 machine dedicated only for the purpose of GALSYNC (which will have AD GAL management agent connector). The server is ready with the management agents ready but here is what I need to understand. If we delete the existing contacts on the target contacts OU from each forest and FIM do a new sync it will create new contacts. I know the emails will be working but there will be NDR issues if users send emails to older mails because the the routing of mail in Exchange recipients is done with the legacyExchangeDN attribute, and the legacyExchangeDN attribute is changed when you recreate the mailbox. And if leave the existing contacts as it is it will try to create duplicate mail enabled contacts or perhaps give existing contact error or something.
I know about the joiner rule mechanism which I have done manually. Is it possible that within the FIM code we can enter the joiner rule instead of the provisioning rule on the GALSYNC MA? Will FIM detect the contacts created by MIIS couple of years ago and will FIM also detect and join manually created contacts? Please advise.
Jimmy George