I must be progressing, I'm answering my own questions now!
Just not create a new connector for them in the provisioning method.
cheers,
Alistair
________________________________________
From: Discussion for MS IDM tools liks ILM and FIM <[log in to unmask]> on behalf of Alistair Young <[log in to unmask]>
Sent: 19 February 2020 15:18
To: [log in to unmask]
Subject: Preventing provisioning
Warning. This email did not originate from the University.
You should only open any links or attachments if you are certain this email is genuine and the content is safe.
Warning. This email contains web links and originates from outside of the University.
You should only click on these links if you are certain that the email is genuine and the content is safe.
Dear list, thanks so much for all the advice on the portal, it's still syncing in...
I was wondering if this sounded a bit odd. I got the impression MIM relied on things coming and going from the SQL MA to manage provisioning/deprovisioning. However, it looks like stuff will be in the SQL MA that shouldn't be provisioned to AD. Old accounts that are marked as inactive. AFAICT there is no way to stop IMVSynchronization.Provision from running after a SQL MA sync, regardless of the value of the Mv status attribute of an account. Is this just not the way to use MIM? Anything that is status=inactive should instead be filtered by the SQL MA?
thanks,
Alistair
########################################################################
To unsubscribe from the MICROSOFT-IDENTITY list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=MICROSOFT-IDENTITY&A=1
########################################################################
To unsubscribe from the MICROSOFT-IDENTITY list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=MICROSOFT-IDENTITY&A=1
|