Earlier in this series of posts I changed our sync target from form “OU=” to “DC=”. This was done to carefully skirt around a small issue. Now with our new found knowledge of logging in ADAMSync, let’s give it another try.So let’s go ahead in to our previous config file and change this line: <target-dn>dc=SyncTargetDC</target-dn> To read: <target-dn>ou=SyncTargetOU</target-dn> Of course, this hopefully means you have created one such NC in your ADAM environment.From there, I went ahead and installed and ran my config:
C:\WINDOWS\ADAM>adamsync /install localhost:50000 ADAMSyncDemo.XMLDone.C:\WINDOWS\ADAM>adamsync /sync localhost:50000 ou=synctargetou /log OULog1.txt
Processing Entry: Page 2, Frame 1, Entry 22, Count 1, USN 0 Processing source entry <guid=ba50fb2e1bdd53468913b5d023460185> Processing in-scope entry ba50fb2e1bdd53468913b5d023460185. Adding target object CN=Builtin,ou=SyncTargetOU. Adding attributes: sourceobjectguid, objectClass, instanceType, showInAdvancedViewOnly, creationTime, forceLogoff, lockoutDuration, lockOutObservationWindow, lockoutThreshold, maxPwdAge, minPwdAge, minPwdLength, modifiedCountAtLastProm, nextRid, pwdProperties, pwdHistoryLength, uASCompat, lastagedchange, Ldap error occured. ldap_add_sW: Naming Violation. Extended Info: 00002099: NameErr: DSID-03050F78, problem 2005 (NAMING_VIOLATION), data 0, best match of: 'ou=SyncTargetOU'. Ldap error occured. ldap_add_sW: Naming Violation. Extended Info: 00002099: NameErr: DSID-03050F78, problem 2005 (NAMING_VIOLATION), data 0, best match of: 'ou=SyncTargetOU'.
C:\>err 2099# for hex 0x2099 / decimal 8345 : ERROR_DS_ILLEGAL_SUPERIOR winerror.h# The object cannot be added because the parent is not on the# list of possible superiors.
Finished (successful) synchronization run. Number of entries processed via dirSync: 168 Number of entries processed via ldap: 2 Processing took 13 seconds (0, 1085446656). Number of object additions: 52 Number of object modifications: 118 Number of object deletions: 0 Number of object renames: 112 Number of references processed / dropped: 58, 7 Maximum number of attributes seen on a single object: 18 Maximum number of values retrieved via range syntax: 0
Probably just a typo, but at the top of the post when you talk about changing <target-dn>, the pre-change and post-change values are the same.
Great series, though.
Ah yes! I copied from the wrong file. Thanks for the correction. :)
Very helpful blog. For the layman syncing from a domain to an ADAM partition requires modifying the builtin containers superior list. It seems that the only attribute that is editable is possInferiors however. Could you detail how you allowed the sync to populate this container into the ADAM partition. Thanks fo all the great info !