• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 18 subscribers
  • Views 8161 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

MMAD Console Displays Incorrect Synced Objects

rreda
over 8 years ago

I have an odd issue that just started yesterday. I am testing and had 12 synced objects from source to target. Yesterday I added one more and the DSA synced and incremented to 13 synced objects. After that I added 2 more objects, waited for sync and all objects synced with no errors 15 total but the MMAD console still shows 13. I checked the stats portal and I see all 15 objects.

I checked to make sure there were no issues with the ADAM DB and it was fine. I have restarted the MMAD console and the DSA. This morning I performed a full resync and now it shows only 9 objects synced. For a test I added a few words in the description field of one object and that did get synced to the target object.

I am not sure what else it could be. I am running version 8.12, I see 8.13 is out but this was working perfectly before yesterday and getting ready for a pilot. Any suggestions?

Parents
  • 0 over 8 years ago

    The data presented above, is pulled from AD LDS. As the data changes in AD LDS, it is not always refreshed. 

    You can validate what is actually inscope by running an LDAP query in AD user and computers. The default LDAP filter is 

    (&(|(&(objectClass=group)(objectCategory=group))(&(objectClass=printQueue)(objectCategory=printQueue))(&(objectClass=user)(objectCategory=user))(&(objectClass=volume)(objectCategory=volume))(&(objectClass=inetOrgPerson)(objectCategory=inetOrgPerson))(&(objectClass=computer)(objectCategory=computer))(&(objectClass=contact)(objectCategory=contact)))(!(&(|(objectClass=user)(objectClass=group)(objectClass=computer))(isCriticalSystemObject=TRUE))))

    Depending on your settings, Only merge them or Create objects in... the above will show you what source side. 

    If you are only Sync'ing (No migration sessions) you can export the mapping data. The mapping data will reflect only the objects currently in scope of the sync. So if you change the snyc setting and do a full sync,only the objects currently in sync will be present in the mapping data. 

     

Reply
  • 0 over 8 years ago

    The data presented above, is pulled from AD LDS. As the data changes in AD LDS, it is not always refreshed. 

    You can validate what is actually inscope by running an LDAP query in AD user and computers. The default LDAP filter is 

    (&(|(&(objectClass=group)(objectCategory=group))(&(objectClass=printQueue)(objectCategory=printQueue))(&(objectClass=user)(objectCategory=user))(&(objectClass=volume)(objectCategory=volume))(&(objectClass=inetOrgPerson)(objectCategory=inetOrgPerson))(&(objectClass=computer)(objectCategory=computer))(&(objectClass=contact)(objectCategory=contact)))(!(&(|(objectClass=user)(objectClass=group)(objectClass=computer))(isCriticalSystemObject=TRUE))))

    Depending on your settings, Only merge them or Create objects in... the above will show you what source side. 

    If you are only Sync'ing (No migration sessions) you can export the mapping data. The mapping data will reflect only the objects currently in scope of the sync. So if you change the snyc setting and do a full sync,only the objects currently in sync will be present in the mapping data. 

     

Children
No Data