Re: ADAM Schema Import Error

Tech-Archive recommends: Speed Up your PC by fixing your registry

Another interesting problem/feature (depending on how you look at it) with
the MS-AdamSchemaW2K3.ldf schema that you get as a result is that the user
object in ADAM is not bindable as it does not implement either a bindProxy
or msds-bindableObject aux class. As such, it is good for sync, but may not
do what you want it to do if you need to use ADAM for any time of bind
scenario. The behavior can be difficult to figure out if you aren't already
an ADAM expert who can pick up on these types of distinctions easily.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Lee Flight" <lef@xxxxxxxxxxxxxxx> wrote in message
news:%23NCAG$8GIHA.3548@xxxxxxxxxxxxxxxxxxxxxxx
Hi

is you are exporting your full AD schema for import into ADAM
then you should not import MS-AdamSchemaW2K3.ldf; I never
recommend that people import that file, using ADSchemaAnalyzer
as described is the better approach.

Lee Flight


"cyberdrew" <webmaster@xxxxxxxxxxxxx> wrote in message
news:1193764649.028184.52220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I followed the following steps exactly as Lee Flight laid them out in
a previous post, thanks:

Install an ADAM instance and create the naming context that you want
in it,
do not apply any LDIFs

Run ADSchemaAnalyzer load the exchange extended schema from the DC
as the *target*, load the (minimal) ADAM schema as the base. Then
check
the "Mark all non-present elements as included" menu option and then
"Create LDIF File...". The resulting LDIF is around 3MB (2091
entries)

Load the LDIF just created into the ADAM Schema

Load MS-AdamSyncMetadata.LDF into the ADAM schema

Create the ADAMSync XML file and assuming that it is only user
objects that
you want, use

<object-filter>(&amp;(objectCategory=Person)(objectClass=User))</
object-fil­ter> ADAMSync /install and the ADAMSync /sync as usual

Except my LDIF file was about 1.85MB and on the minimal adam schema, I
loaded the MS-AdamSchemaW2K3 file.




.

Relevant Pages

  • Re: ADAM sync problem
    ... I have a real hard time synchronizing my ADAM with our AD here. ... I do not import any ldif files and finish the setup. ... use the AD Schema Analyzer to create an ldif file that I would import ... I create the ldif file and import it in my ADAM. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Creating a Computer Object in ADAM
    ... Using the ADAM Schema MMC Snap-In, I determined that the Schema Master ... Directory Server Diagnosis ...
    (microsoft.public.windows.server.active_directory)
  • Re: Creating a Computer Object in ADAM
    ... schema spans the config set and schema update must be made ... ADAM How To ... Importing directory from file "compobj.ldf" ... On ldifde -j is the path to the log file, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Syncing domain to ADAM
    ... Will not synchronize attribute distinguishedname. ... Deleting attribute. ... Equivalent object in the source schema is ... although I was connecting and binding to my ADAM ...
    (microsoft.public.windows.server.active_directory)
  • Re: Synchronize only attributes you want ADAMSync
    ... you can have a smaller schema than the ADAM default installation. ... The problem with include elements in ADAMSync, as you have found, ... Saved configuration file. ...
    (microsoft.public.windows.server.active_directory)