Craig Martin

Learning and sharing

1 minute read

The synchronization engine uses joins to enable rules on connected objects. AAD Connect removed the ability to disconnect joined objects, and it has been asked for as feedback:

Sometimes objects will join with the best of intentions but have unintended consequences, my company seems to be an infinitely renewable supply of weird data. Correcting bad joins unfortunately requires manual intervention, which used to be as simple as disconnecting an object and joining it to its correct match.

AAD Connect does not have the disconnect feature, so the workaround is to:

  • Export the offending Connector Space object using csexport.exe
  • Delete the offending Connector Space object using csdelete.exe
  • Create an import file using the file contents from Step 1
  • Import the file from Step 3 using an import run profile and the ‘resume from existing log file’ option

The process is nicely captured in this blog post: Disconnecting Objects with AADConnect

In the past week I’ve had to do this a few times, almost enough to automate it. If it comes to that I’ll be posting about it again.

You May Also Enjoy

Find MIM Active Workflow Definitions

less than 1 minute read

Need to find the workflow definitions that are actually configured to be active? It’s a good way to find configuration bloat that could be cleaned up.

Event Log Entry Count By Severity

less than 1 minute read

Visualizing the count of Event Log events on a computer can be helpful in some cases: starting to investigate an issue - does the issue coincide with an i...