Hello everyone, I am hoping there is someone here that can help me clear something up. It involves synchronization and connectors. To begin with, in my test environment I have an AD MA for Active Directory and a FIM MA for FIM. The FIM MA has domain (metaverse) --> Domain (FIM) in the attribute flow as an Export. This was all fine and dandy until it was noticed that the Domain wasn't getting populated in the FIM Portal, nor in the Metaverse, therefore users could not access the portal nor could they do any self-service password registration. The FIM MA had already been initialized (Full Import, Full Sync) previously The next day we added 'AD' (String) --> Domain as a Inbound Attribute Flow on the AD Syncronization Rule for the AD MA that has Inbound/Outbound data flow direction. That way when doing an import from the AD MA, it should automatically fill in the Domain attribute in the Metaverse. We noticed that doing the following did NOT work to get Domain populated in the FIM Portal 1. Full Import AD MA 2. Full Sync AD MA 3. Export FIM MA After some thought, I attempted to do the following which DID work: 1. Full Import FIM MA 2. Full Sync FIM MA 3. Full Import AD MA 4. Full Sync AD MA 5. Export FIM MA After that was done, 'AD' appeared in each user record and all of those users were able to access the FIM Portal as well as register for Password Reset. My question is, what was done 'technically' or behind the scenes with the Import and Sync of the FIM MA in the second set of steps above to make this all of the sudden work? Does it have to do with updating connectors so Domain could come across when the Sync Rule is hit on the Export? Sorry to ask such a technical question, but I really would like to wrap my head around how this stuff works. Thanks in advance, Daniel Lackey

What have you done directly after you have updated the synchronization rule in the Portal?It is possible that you made the change in the portal and did not bring the updated synchronization rule into the metaverse.You can use the FIM CS Synchronization Rule Viewer Plus to display the settings of a synchronization rule in the metaverse.The Full import and full synchronization on the FIMMA brought the most recent configuration of your synchronization into the metaverse.Cheers,MarkusPS: by the way - a forum is exactly the right place for techncial questions.Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Ahhhh.....precisely! I do not know why I didn't even think of that. Thank you Markus for clearing my brain on this matter. :)Also thank you for providing a link to the FIM CS Sync Rule Viewer Plus. I think that will come in handy for us.Hopefully this post will help someone with the same problem in the future.Thanks again!Daniel