This content has been marked as final. Show 7 replies
Are you using OOTB conectors for AD and Exchange?
If yes, then it should work by default.
If not you need to add disable trigger to task.
Anyway share the error log and disable task details.
Your Disable User tasks might be Rejected...
And Check for the task in both of them...
The one which is in Provisioning status, the task might not be triggered
There is no task triggered for AD and exchange when user was disabled. The orc_update column is showing some previous date while for all other resources which got revoked successfully it is showing the correct date on which the user was disabled.
open disable user task under AD and exchange. see if Disable trigger is added on this task or not. try disable one user manually and see if the AD account is disabled or not. Even call disable user task manually and see if this works1 person found this helpful
yes disable trigger is added and it is working for many users during recon. only for one or two users this issue is happening.
Is that user disabled in OIM. what is end date for those user. compare data for failed user with successfully terminated user
yes user is disabled in OIM but AD and Exchange resource status for that user is Provisioned.