none
sync-generic-failure error in ADConnect

    Domanda

  • Hi,

    I am getting sync generic error when trying to sync on Prem AD object to Azure AD.

    The error is "A different entry with target identifier already exists"

    Kindly assist me to resolve this error


    Rajesh

    martedì 19 giugno 2018 04:07

Risposte

  • Hi,

    Do you have an OU in your On Prem AD that you do not Sync to Azure AD?

    If not, create an OU and update the Azure AD Connect configuration to not include that OU.

    Then:

    1. Move the On Prem object to that excluded OU
    2. Run a delta sync using PowerShell
    3. Import-Module ADSync  # only needed if the ADSync module is not loaded
    4. Start-ADSyncSyncCycle -PolicyType Delta
    5. Then move the object back to its original location, and run another delta sync

    That solved the problem for me.  I just need to script this, as I've got 80+ objects to fix...

    • Contrassegnato come risposta Rajesh.NSR martedì 24 luglio 2018 18:30
    martedì 10 luglio 2018 23:39

Tutte le risposte

  • Hi,

    Do you have an OU in your On Prem AD that you do not Sync to Azure AD?

    If not, create an OU and update the Azure AD Connect configuration to not include that OU.

    Then:

    1. Move the On Prem object to that excluded OU
    2. Run a delta sync using PowerShell
    3. Import-Module ADSync  # only needed if the ADSync module is not loaded
    4. Start-ADSyncSyncCycle -PolicyType Delta
    5. Then move the object back to its original location, and run another delta sync

    That solved the problem for me.  I just need to script this, as I've got 80+ objects to fix...

    • Contrassegnato come risposta Rajesh.NSR martedì 24 luglio 2018 18:30
    martedì 10 luglio 2018 23:39
  • Thank you!

    This worked for me. 

    venerdì 31 agosto 2018 20:17