Not all the OUs are brought in after ADAM sync

Discussion in 'Active Directory' started by ADAM newbie, May 16, 2008.

  1. ADAM newbie

    ADAM newbie Guest

    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>
    - <query>
    ........left stay the same as the default......
    ADAM newbie, May 16, 2008
    1. Advertisements

  2. ADAM newbie

    Lee Flight Guest


    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:

    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
    Lee Flight, May 19, 2008
    1. Advertisements

  3. ADAM newbie

    Lee Flight Guest

    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
    Lee Flight, May 19, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.