Tag: Microsoft Identity Manager
-
Explicit-disconnectors remain in connector space after deleting
—
After exporting some deletes, I noticed that the objects remained as placeholders in the connector space, with a state of explicit-disconnector. The issue this causes is that if the object needs to be re-added to the connector space, it can’t be, because a duplicate anchor value is generated. In the end, the cause of this…
-
MIM 4.5.202.0 download link broken
—
If you are looking for the “latest” MIM 2016 SP1 hotfix, the MIM version history page is not currently up to date. It lists the latest version as 4.5.202.0 (released Aug 30 2018). The KB ref is KB4346632, However, the KB download link is broken. The reason is that there is actually a newer version which…
-
Error encountered trying to prepare the existing metaverse configuration.
—
Import Server Configuration fails: Preparing existing management agent configuration for update completed. Import attribute flow rules compare starting… Import attribute flow rules have been changed. Metaverse configuration validation starting… Metaverse configuration validation successfully completed. Preparing existing metaverse configuration for update starting… An error was encountered while trying to update the metaverse configurations. Exception from HRESULT:…
-
“Management agent update processing FAILED” when trying to update an ECMA2 MA
—
Infuriating product… Export MA from one environment, try to import it to another using “Update Management Agent” and encounter this error: Update management agent from file starting… Reading the import configuration from file. Constructing the new Import Attribute Flow Rules. Begin processing the management agent update information… Management agent file version checking starting… Management agent…
-
ECMA2: Unable to retrieve schema. Error: Exception from HRESULT
—
Developing a new ECMA2? Importing schema? Receiving “Unable to retrieve schema. Error: Excpetion from HRESULT:” message? Not seeing anything helpful in the event log? Same here. It turns out it was a legitimate error, although it could be more usefully phrased. I had simply forgotten to specify an anchor attribute. You must make sure that…
-
Redirecting to the MIM site by default
—
When you start to install MIM, you first need to install SharePoint, which MIM runs on top of. As part of this, you set up a SharePoint website with a name, usually one that matches the domain name, e.g. mimportal.contoso.com After MIM is installed, going to this root URL will confusingly just load a default…