FIM GAL Sync Confusion
I am in the processes of migrating our current Exchange 2010 forest users into an Exchange 2010 Resource forest with linked accounts. I have setup a management agent for both the Source and Resource Forest. However I don't understand how to get the data to traverse across. My Source agent is showing objects that are synced, but the Resource forest is not showing any objects synced. Can anyone shed some light on this for me?Yehoshua | RHCT - RHEL5 | MCSE - 2K3 | MCTS - Exchange 2007 | MCTS - Vista - Configuration | MCDST
July 29th, 2010 11:28pm

GAL Sync will not take mailboxes from the source forest and create linked mailboxes in the target forest. It will take mailboxes in the source forest and create contacts in the target forest. The purpose of this DLL is to synchronize address books - not migrate mailboxes. ILM/FIM can be used to do what you are trying to do but it will be a considerable amount of custom development. Unless you are talking about 100's of thousands of mailboxes I would suggest you purchase a 3rd-party mail migration tool or write your own powershell scripts to do what you are trying to do. -Jeremy
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2010 11:49pm

I understand that FIM will not create linked mailboxes in the target forest. What I need is: Take current contacts in my source Forest and move them to the Resource Forest. Duplicate Distribution Groups from the Source to the Resource Forest. Create mail-enabled users in the Resource Forest that are linked to the Exchange Mailboxes in the Source forest. This prepares mailbox for cross forest migration. After this is done, the Users need to keep their attributes in sync between the source and resource forest. The link below leads me to believe that FIM is the recommended method to make this happen. http://technet.microsoft.com/en-us/library/ee633491.aspx So I really need to create custom code to migrate into a resource forest?Yehoshua | RHCT - RHEL5 | MCSE - 2K3 | MCTS - Exchange 2007 | MCTS - Vista - Configuration | MCDST
July 30th, 2010 3:04pm

OK, Thanks for the info. It really helps us understand your scenario. Here is how the GALSync DLL applies to your problem: 1 - This should work out of the box. Make sure provisioning is enabled. 2 - GALSync will create the source DL's as contacts in the target forest. This is probably not what you want to do if the users in the target need to examine DL membership. You will need to write custom code to get the groups out of the source and provision them as groups in the target. 3 - GALSync will not do this. It can be done but you need custom attribute flow and mvextension. 4 - GALSync will not do this. You need custom attribute flow. I am going to recommend you look a 3rd-party mail migration tools unless you have a long-term identity management strategy that includes ILM/FIM and you want to use this project to learn the product and establish the technology in your organization.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2010 6:30pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics