none
Sync errors using ADDSync RRS feed

  • Question

  • We are trying to get ADDSync to work with Office 365.


    servers: Windows 2012 r2


    Environment: ADDSYNC

    Cloud Service: Office 365

    Federated Domain Services are setup and working


    Our ADDsync (used to be dirsync) isn’t running properly anymore. We deleted a ton of test accounts, but some of them still existing only in the metaverse, they are gone in office365 and in our local ad. How do we get rid of them, they are getting sync-generic-failures. I've tried full sync on both connectors but each time it gives sync-generic-failure. How do I remove the item from the metasync. There are accounts about 1400 accounts that only exist in the metaverse. They are no longer in active directory or in the cloud. I've asked around the office 365 forum but no one seems to know how to get rid of the accounts from the metaverse.


    Thanks,


    Mike
    ​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​

    Friday, March 27, 2015 2:55 PM

All replies

  • So If I get this right, you have orphan objects in MV. Not connected to anything.

    In that case, If they are only in MV, this is a way to do - not supported though AND NOT RECOMENDED - yet the only option sometimes.

    1. Back up the FIMSynchronizationService DB.

    2. Go to SQL Database FIMSynchronizationService and run a query

    "DELETE * From mms.metaverse where connector is NULL". Please check the syntax of the query as I am not 100% sure. Should be something along those lines.

    Run a select before deleting, to see if these are in fact the accounts your are looking for, due diligence, etc.


    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Nosh Mernacaj Thursday, May 28, 2015 6:48 PM
    Friday, March 27, 2015 3:15 PM
  • Hi Mike,
    there are different possibilities... Is it a lab or production environment ?
    If it's a lab ? Have you try to clear yours MAs (delete all objects in the MA) ?
    If the join rule will work fine, when you run next full import on MAs, Accounts will be join between AD Local and Azure AD.

    Let me know your result.

    Joris


    Joris Faure

    Friday, March 27, 2015 3:52 PM