Hi,

I am pretty much new to FIM, and exploring it further.

I would like to stop synchronizing the manager field from HR system and pushing the manager field to AD for disabled users.

Please help me with the above requirement.

Thanks

-Kunal Jain

Are you using synchronization rules or clasic rules extensions? Does the HR system indicate if the user is disabled?

Hi Paul,

Thanks for the reply.

Currently rule extensions are configured in the system. The HR system does indicate that the user is disabled. The system is a live system and I do not have any proper documentation from the client.

Please let me know

You can check the status attribute in the rules extension and skip any change to the cs attribute if the status is not the desired status, does that sound helpfull. in Peusdo code it is something like

if (mventry["status"] == "Enabled")
{
  csentry["manager"] = mventry["manager"]
}
else
{
  //do nothing
}

Hi Paul,

The FIM now only has view of active users from the HR Database. Now, there is another System in place already which disables the user in AD and also clears out the manager field for the user. But since the ADMA connector is active for disabled users it updates the manager field for that user again.

How can we disconnect the ADMA connector for disabled users.

You need to write the deprovisioning code for the ADMA to 'disconnect' when the attribute changes to the desired state, and set the deprovisioning option on the ADMA to 'make them disconnector' not 'stage a delete on the object for the next export run'.

But you can also configure metaverse deletion rules to automatically deprovision when the HR connector space object is 'disconnected' because it is filtered from the view, you can configure it via the metaverse designer and set 'Configure object deletion rule', select the 2nd option and then check the HR agent, beware this will also deprovision all other connected CS objects for the particular MV o