AdamSync Common problems
Here’s a list I have kept of the common problems in attempting to use Adamsync:
Schema mismatch. (Use ADSchemaAnalyzer)
Target partition in Adamsync configuration does not exist in target ADAM. Note: target partition must be an NC head.
MS-AdamSyncMetadata.ldf is not imported
Source AD is W2K and so Replicating Directory Changes permission is not granted for sync account on source AD NC head.
ObjectClass foo is not in the ADAM schema when target-object-class in the ADAMsync configuration is set to foo. foo is usually userProxy.
If target-object-class in ADAMsync is userProxy then objectSID must be in the include element of the ADAMsync configuration.
Account used for ADAMsync /install must be able to write to target ADAM application NC head.
If source-ad-account element is used in the ADAMSync configuration then will probably need /passPrompt on the ADAMSync /install command line.
If object-filter element in ADAMSync configuration uses objectCategory then problems can arise, in particular deletions in source AD will likely not be sync’ed.
object-filter element in ADAMSync configuration needs:
and = “&” use &
or = “|” use & #124;
not = “!” use & #33;
Choice of target-dn restricts the children that can be sync’ed from AD through possSuperiors e.g. if you make your target-dn ou=something and your base-dn is a domain NC head dc=contoso,dc=com then CN=builtin under the domain NC head will cause a sync failure as OU is not a possSuperior of builtinDomain
Not using /log on the ADAMsync /sync when hitting problems.
 Problems with Adamsync aging runs e.g. random objects may be renamed and then moved into the ADAM Lost and Found container. Aging has many problems and is best avoided.