Hello,

I'm relatively new to FIM and because of a new job back at doing MS servers again.
FIM is part of a MS Lync 2013 installation for one special customer.

Customer manages his AD himself, puts Accounts into a special security group, if Lync should be activated.

Lync is installed in own forest, with trust to customer forest.

FIM creates contacts in resource AD for customer's real accounts. Powershell script updates contacts into forest's lync-group.
Just FIM sync is used, every 30 minutes, with 4 profiles and lcssync.dll used for deprovisioning.

From time to time FIM "sees" delete of e.g. customer\user1234, in my resource forest this contact loses all its attributes, hence the group.
It was removed from Lync but Lync-enable script will try to enable "him" again and runs into error:

-ERROR- enabling   () for Lync
CN=user1234,OU=CUSTOMER,DC=blabla,DC=net
Cannot bind argument to parameter 'Identity' because it is null.

Some time later, I check in customer's AD for account customer\user1234 and it's not deleted nor disabled and "it" has all attributes.
In FIM this connector is placed into "explicit disconnectors" of CUSTOMER AD.
Here I'll do a fix of the problem.

But what's the reason for FIM to see a delete of customer\user1234?
Is there anyway to tell?

Thanks for your advise!

Bye,

Jens

• Edited by Jens Hoffmann (Administrator) 17 hours 43 minutes ago changed some words

One reason may be that user is moved to an OU outside the scope of FIM. In the management agent you select what OUs you want to manage and if the OU is mot selected, it is as good as not existing, together with everything in it.