none
GALSync issue with FIM 2010 RTM - Don't get exported contacts in the other forests :-( RRS feed

  • Question

  • Dear FIM Masters,

    I'm running FIM 2010 RTM on top of Windows Server 2008 R2 Enterprise with SQL Server 2008 R2.

    I've try to migrate the old MIIS 2003 database and keys that responsible for Exchange 2003 cross-forest GAL sync. but nothing happens.

    Right now, I'm using ForestA with Exchange 2010 SP3 Rollup 6 and Exchange 2003 SP2 & 2010 SP3 Rollup 6 at Forest B. The FIM is installed at Forest B.

    I'd try to install a new server with the FIM and try configure the management agents from scratch. but no luck. This is my situation at every step at both of the management agents:

    1. Full Import (Stage Only) - sucess (no errors).

    2. Full Synchronization - completed-sync-errors, after that there's list of users at the Operations view, and when I'm clicking on each object I see the "extension-attribute-not-present" on Data source attributes - proxyAddress, homeMDB, targetAddress.

    3. Export (at Forest A) - stopped-extension-dll-exception (with no details)

    Export (at Forest B) - completed-export-errors (with "ma-extension-error).

    After that I got no new contacts in both of the forests of mailboxes, so I can't see them at the Active Directory Users and Computers and at the Exchange Contacts :-(.

    I tried to migrate the old MIIS, and to install a fresh FIM - but no luck. Also, I'm afraid that when I'll set it everything up it will duplicate the contacts from the old MIIS instead of overwrite/update them - can I avoid that?

    Please assist,

    Thanks.


    Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb | E-mail: msilforums@ben-shushan.net

    Saturday, December 6, 2014 7:32 AM

All replies

  • Hi Netanel,

    Considering step 2 - check what attributes are selected on each agent and if they have attribute flows to Metaverse. You can find it in Agent's properties.

    Considering step 3 - please check Event Application log. You would find error details here.

    To avoid creating duplicates in management agent, you should create join rules first (in agent's properties), so FIM would know that this contact is corresponding to this user in another forest.

    And run first synchronizations on all agents with disabled provisioning (Tools->Options-> Disable "Enable provisioning rules extenstion") so all suitable objects matching between domains would join each other.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    Sunday, December 7, 2014 8:46 PM