Hi, Just a question of, is this possible or isn't it? I have a setup, where users are able to request access to groups from the FIM Portal and an approval is fired by that action. This setup works fine and the groups are updated in the portal and in AD if i choose that the member attribute flow precedence is 1 for Portal and 2 for AD. Problem is, that i the Helpdesk users needs to be able to create users with a specifik group membership at user creation. FIM Sync.'s some of the groups and others not. The groups that FIM sync.'s needs to be updated with the new value in the Member attribute ind the portal, when a new user is born with. Member sync. from AD to portal works fine if i set the AD to be 1. ind the order of Flow precedence. If i choose equal precendence, both sources contribute to the MV, but one doesn't change the Member attribute in the other./Frederik Leed

If I'm reading your question correctly you're asking can multiple sources be authoritative for the member attribute in a scenario whereby you're synchronising groups? If so then yes, and equal precedence is what makes this possible OOB. If you are having issues with precedence you should do two things: Update to the latest build: http://support.microsoft.com/?id=2417774. The previous hotfix (which is included in this one as they're cumalative) fixed some issues with equal precedence. Ensure that you are flowing nulls on export for both the AD flow and the FIM MA flow (to properly allow for attribute deletion).

Update to the latest build: http://support.microsoft.com/?id=2417774. The previous hotfix (which is included in this one as they're cumalative) fixed some issues with equal precedence. <-- TJECK! Ensure that you are flowing nulls on export for both the AD flow and the FIM MA flow (to properly allow for attribute deletion). <-- TJECK So i've been trying this equal precedence whole day now. When i change the member attribute on an AD group, delta import, delta sync, i get 2 outbound flows. 1 for FIM MA with the update for the group - The members just added in AD is now flowed to FIM MA 1 for the AD MA with an update for the group - The members just added are now deleted <-- Why is that? I the export the data to FIM and the Delta Confirming import is ok, the group is updated. Delta sync does not create any new flows and i still have that pending export to delete the members in AD. hmmm/Frederik Leed

Update to the latest build: http://support.microsoft.com/?id=2417774. The previous hotfix (which is included in this one as they're cumalative) fixed some issues with equal precedence. <-- TJECK! Ensure that you are flowing nulls on export for both the AD flow and the FIM MA flow (to properly allow for attribute deletion). <-- TJECK So i've been trying this equal precedence whole day now. When i change the member attribute on an AD group, delta import, delta sync, i get 2 outbound flows. 1 for FIM MA with the update for the group - The members just added in AD is now flowed to FIM MA 1 for the AD MA with an update for the group - The members just added are now deleted <-- Why is that? I the export the data to FIM and the Delta Confirming import is ok, the group is updated. Delta sync does not create any new flows and i still have that pending export to delete the members in AD. hmmm... If i then export to AD and delta import, delta sync, then the deletion is again exported to FIM and the members are removed again... /Frederik Leed