user attributes not flowing to metaverse
Using FIM to sync objects from a one AD to another AD (ADone->FIM->ADtwo). It was working about 2 months ago. Some changes were made - target OU, mail designations. Also a number of users were moved out of the source OU, just a couple left for testing. Deleted all the objects in the target AD adn deleted the CS for all 3 MAs. Now when trying to re-establish 2 test users, they appear in ADone CS and also in the metaverse but only with uid - no attributes. The run profiles do not throw any errors (other than for 3 admin users that are in FIM - sync-rule-flow-provisioning-failed). Was this caused by the clearing of the CS's?Bill
September 8th, 2011 6:26pm

Hi There, Have you checked the attribute precedence and the flow rules that are being applied? Are you using the classic or declarative sync rules? The attribute should be flowing in there fine if ADOne is the authoritative source. When you clear a FIM CS, it can get hairy as it removes all the objects including your synchronization rules. So declarative rules may not be there at this point. Check to make sure your sync rules are present in the Metaverse for the source MA ADOne. If that still isn't working, check attribute precedence and relationship critieria. Thanks Bhttp://identityminded.wordpress.com
Free Windows Admin Tool Kit Click here and download it now
September 8th, 2011 6:56pm

Thanks for the direction, attribute precedence had flipped. Using declarative provisioing. I reset all the attributes and they now show up in the metaverse and in the FIM portal.. but the users were not being provisioned to ADtwo. When I try to do a preview on one of the users from the FIM CS I got an error, Synchronization rule baed provisioning failed. Found a missing "." in the DN mapping. Appears to be working now. Thanks again.Bill
September 8th, 2011 8:03pm

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

Other recent topics Other recent topics