Hi,

I have two synchronization rules targeting Active Directory. The first SR flows some attributes to a specific OU (let's refer to this SR as SR1), and the second SR flows more attributes and dependant on SR1, let's refer to this second SR as SR2.  SR1 is set to 'Enable Deprovisioning'.

I have noticed when I attempt to remove SR2 from a user object in FIM, FIM think it should delete the object in Active Directory and re-create it based on SR1 setting. Is this normal? and is there a way to tell FIM not to delete AD user object is SR2 was removed, but still have SR1. 

Keep in mind that there is no way to disable deprovisioning in SR2 (since it doesn't have 'Relationship' tab).

Thanks. 

Hi Ali,

How is the deletion rule for person in the Metaverse configured?

And how is deprovisioning configured for your AD MA?

Cheers,
Paolo

Hi Paolo,






MV Person deletion rule is set to delete the MV object once the user is disconnected in Active Directory (target system) and an authorative source.


As for AD MA deprovisioning rule, that is set to stage a delete. 


I found an article that (http://blog.ilmbestpractices.com/2010/06/dependent-sync-rules-disconnection-on.html) that seems to indicate that dependant sync rules by default have their 'Enable Deprovisioning' checked. This article discussed how that can be disabled. I have gone through the excerise of disabling the deprovisioning on SR2; and performed a full and made sure the sync rule in MV does have 'false' in DisconnectConnectedObject. However, person objects continued to be deprovisioned once SR2 is removed. 






Thanks.

Hi Ali,

Did you find a solution to this?

I have the exact same issue and it's driving me crazy. Could you please let me know how you solved this?

It is kind of urgent so I would be very grateful if you could get back to me asap.

Thanks