Resolution
fact
Exchange Migrator 1.x
fact
Exchange Migrator 2.x
symptom
SynchGroupMemberships failed to fetch props for cn=DLName,cn=DL,cn=Recipients,ou=Site,o=Org - DL Membership is not being updated during dirsync
cause
The path stored in the projectName-SynchtoTarget or projectName-SynchtoSource tables for the previously synched DL is not correct due to the target account being moved, renamed or deleted.
fix
note
Exchange Migrator 1.x
fact
Exchange Migrator 2.x
symptom
SynchGroupMemberships failed to fetch props for cn=DLName,cn=DL,cn=Recipients,ou=Site,o=Org - DL Membership is not being updated during dirsync
cause
The path stored in the projectName-SynchtoTarget or projectName-SynchtoSource tables for the previously synched DL is not correct due to the target account being moved, renamed or deleted.
fix
There are two ways to resolve this issue:
- Use Microsoft OSQL or Microsoft SQL Enterprise Manager to update the targetObj entry in projectName-SynchtoTarget or projectName-SynchtoSource (depending on the direction of the DIRSYNC) table of the Exchange Migrator database to reflect the correct path to the target object.
- Move or rename the object back to it's original location or name. If you have deleted the object, execute the EMCLI DIRSYNC using the /CLEARTABLES switch. However, please keep in mind that if the source and target objects do not have a matching email address, it is possible this could cause DIRSYNC to create a duplicate object.
note
Moving forward keep in mind that Exchange Migrator is storing the LDAP path to the target object. If the target object is moved or renamed,the path is no longer accurate and EM will not be able to find the target object. This can lead to DL memberships or permissions not being correctly updated.
Additional Information
Formerly known as NETIQKB35353