Not all the OUs are brought in after ADAM sync

Newbie to ADAM. After the first time setup ADAM on our server, i created one
instance with partition name (dc=staff,dc=company), ran ldifde to extend ADAM
schema (adamschemaw2k3.ldf and adamsyncmetadata.ldf), rebuilt
MS-AdamSyncConf.xml and sync. From ADAM adsi edit, I couldn't find all the
OUs that are listed under our real AD. I've spent several day working on this
one, but still no luck. Any insight will be greatly appreciated. TIA.


<?xml version="1.0" ?>
- <doc>
- <configuration>
<description>sample Adamsync configuration file</description>
<security-mode>object</security-mode>
<source-ad-name>ad.staff.company</source-ad-name>
<source-ad-partition>dc=staff,dc=company</source-ad-partition>
<source-ad-account></source-ad-account>
<account-domain>staff.company</account-domain>
<target-dn>dc=staff,dc=company</target-dn>
- <query>
<base-dn>dc=staff,dc=company</base-dn>
<object-filter>(objectClass=*)</object-filter>
........left stay the same as the default......

 

Hi

importing the w2k3.ldf file is assumes that your AD schema has not
been extended in any way amore generic approach using ADSchemaAnalyzer
is here:

http://groups.google.co.uk/group/mi....server.active_directory/msg/a5230c40ee28b855

What I would do is use the above to export your AD schema and import it
into a clean ADAM install and also import the syncmetadata.ldf. Then
run the adamsync /install and then run the adamsync /sync but include
the /log option so that we can see how far the sync is progressing.

Lee Flight

 

Also note that for AD objects to sync they must be visible
to the domain account that you are using to perform the sync.

Lee Flight