Blog Post

Core Infrastructure and Security Blog
6 MIN READ

Deleting a Connector Space: When, Why and How

ktackett's avatar
ktackett
Icon for Microsoft rankMicrosoft
Nov 01, 2019
First published on MSDN on Oct 15, 2014 *** PLEASE NOTE: This post is explicitly intended for use with on-prem (FIM/MIM) only and is NOT for use with AAD Connect. Following this process wit...
Updated Feb 20, 2020
Version 3.0
KrisTackett
Ok-34's avatar
Ok-34
Copper Contributor
Dec 03, 2022

I have questions for 5. and 8.

    1. Disable “Synchronization Rule Provisioning”
    2. Disable metaverse object deletion rule
    3. Delete ADMA connector space
    4. Delete FIMMA connector space
    5. Delta synchronize each management agent (Delta synchronization will process disconnectors and, if we’re lucky, should clean these objects out of the metavers
    6. Full Import ADMA and FIMMA
    7. Full synchronization on FIMMA first (we should see all objects projecting into the metaverse)
    8. Full synchronization of the ADMA (we should see joins occurring)
    9. At this step, we may enable “Synchronization Rule Provisioning”
    10. Re-sync both management agents and perform exports (if any)
    11. Recreate object deletion rule


Questions 

 

Should we synchronize all management agents, we have three ADMA, FIMMA and SQL server?

 

full synchronization of the ADMA (we should see joins occurring)

but we did not get any joins. Can we join these manually? can we create a join rule and test it before committing to it.

 

error

The operation failed because UPN value provided for addition/modification is not unique forest-wide