Hi, we're using FIM to sync objects from a customer AD to our AD (CusAD->FIM->OurAD). In the outbound sync rule we have some attributes set to 'initial flow only', amongst these is the proxyAddresses attribute. The customer had 2 users with the same proxyAddresses in their AD, and removed the mail attributes from one of the objects to solve the conflict. However in our AD the proxyAddresses remains the same, since it is set to initial flow. I've tried deleting the AD user on our side as well as the person object in FIM portal to try to force it to sync the user as a new user. This didn't work, probably because the user is still in the metaverse. Is there a way to remove the user from the metaverse, and make FIM re-sync it from the source AD? (I can't set the proxyAddresses to sync all the time, because when a users mailbox is migrated to our Exchange 2010, an extra x500 address is added on our side.) Thanks in advance! Enrico

It's get deleted when there is no connectors. You can disconnect connectors using Connector tab of the Metavese Search.

Hm, I think I'm going about this the wrong way...Since the attributes are set to 'Initial Flow Only' I can just clear them in the destination AD, and they'll stay that way. I'll try that first :) Thanks for your reply Robert.

Enrico, if you configure an attribute as "initial flow only", this means the attribute will only be populated once when the object is created in the Connector Space of the connected data source. Once it's created there, it's ready to be exported (created in the actual data source). So if you'd want those initial flow only's to reoccur you'd have to delete the target user. Do a delta import, delta sync and most likely the user will be reprovisioned. BIG BUT: the result might differ on your Object deletion rules for the Person object. I'm not even sure if you can delete the target user in your situation (live mailbox? :) ). What Robert is saying is also true, you can make the MV object go away by disconnecting all it's disconnectors. However, In my opinion using the declarative way there's always a trick available to get done what you want and mostly with very few effort. An alternative approach could be the following: create a manual set (add those two users), create a new SR which just flows the proxyattribute. Create a workflow (to add the SR) and create an MPR which executes the WF based on the created Set. This way you could do a one time sync of these attributes. And then you can modify your WF to remove the SR from the objects. You'd have to test wheteter the proxy attribute isn't recalled. But I don't think so. Either way, as always test thouroughly Happy FIM-ing! [sorry for the whitespace less post, i'm in the poor editor gui]http://setspn.blogspot.com