ADAM : Adsschemaanalyzer tool to extend schema

[fanfan]

Hi,
I'm working with ADAM included in W3K RC2.

I tried the adschemaanalyzer tool but I'm not sure I understand well the
purpose of this product. Can anyone tell me if what I've done is what should
be done ?

I'm trying to synchronize my AD and ADAM instance. So first, I believed I've
got to extend my ADAM shcema to match my AD schema.
For this I used Adsschemaanalyzer :
- I loaded the schema of my ADAM instance : 324 attributes, 49 classes and 8
property sets
- I loaded the schema of my AD : 1980 attributes, 361 classes, 12 property
sets
- At the bottom of the tool, it is said that a comparison is done. But when
I look in the attributes/classes/property sets trees, I really don't think
the total number of my AD schema objects are displayed...
- I created an ldf file.
- I imported my ldf file in my ADAM. 26 entries modified ??

After that, when I launched adsschemaanalyzer , the number of my schema
objects in my ADAM are exactly the same as the beginning.

Is what I've done correct ? if it is, why are the number of my
attributes/classes... still the same ?

thank you for your help
F.

[Lee Flight]

Hi,

What works for me:

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

Run ADSchemaAnalyzer

load the AD 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"

option in the Schema menu and then

"Create LDIF File...".

Load the LDIF just created into the ADAM Schema using
the ADAM version of ldifde.

The resulting LDIF is around 3MB (2091 entries) for an
W2K3 schema extended by Exchange 2003. If your
AD schema has not been extended in anyway you can use
the ms-adamschemaw2k3.ldf file that comes with the ADAM
in the W2K3 R2 release, instructions for loading that file
are in the comments at the head of the file.

Lee Flight

"fanfan" <fan...@discussions.microsoft.com> wrote in message
news:8C594551-A700-4C92...@microsoft.com...

[Lee Flight]

I should have said that those are the steps for synchronizing
your ADAM schema with an AD schema. Producing
a schema LDIF suitable for import into ADAM is main
for the tool in this release.

It also extremely handy as a schema browser for looking
at class/attribute dependencies and for exploring the impact
of schema extensions.

Lee Flight

"Lee Flight" <l...@le.ac.uk-nospam> wrote in message
news:eKjZo$kqFHA...@TK2MSFTNGP09.phx.gbl...

[fanfan]

Thanks Lee !
I did the exact opposite. In my point of view :
- target is ADAM
- base is AD

... doesn't it seem logical ?...
I'm trying your way now...

"Lee Flight" a écrit :