Microsoft Security | Microsoft Identity Manager
A tool for managing user identities, credentials, and access across on-premises and cloud environments
MIM 2016 SP2: Attrubute changes in AD not importing to Metaverse
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 69%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYA%3C/text%3E%3C/svg%3E)
Yusef Andrews
1
Reputation point
We have an attribute in AD that was previously being populated by MIM but we removed that mapping and cleared the attribute for all user accounts in AD via a separate process. Now, the attribute needs to be cleared in the MIM metaverse. What we've tried to do is map an import attribute flow (from data source to Metaverse) but when doing an ADMA, I get no changes on that attribute for person objects in the metaverse. The ideal result would be that the ADMA sees that the attribute was cleared in AD then carries that cleared/Null/Black attribute back to the metaverse object.
Microsoft Security | Microsoft Identity Manager
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 1%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
SteinIP 271 Reputation points2021-08-11T11:27:12.037+00:00 Guess Sync no longer considers your ADMA a source for that attribute, and having nothing in AD will not clear out the MV attribute. I think you can make a syncrule that says to take the function Null and put that in the MV attribute.
If that doesnt fix it you might need to do a temporary CSV MA that puts something in the attribute, and then delete the connector space objects of the temp MA to make it remove the values again. Basically same approch as used to remove ghost objects from MV.
-
Yusef Andrews 1 Reputation point
2021-08-11T15:37:53.743+00:00 Thanks for your reply. In our test environment, we ended up just deleting the attribute in the metaverse designer since it was no longer mapped in any MA's. We ran a test sync and didn't notice any issues. Is deleting the attribute a fine solution?
Sign in to comment
Sign in to answer