ext-compare tools.
In
general I would want to question what your goal is – like Al I am assuming you
want to make the schema more manageable. Basically a convenience so you don’t
have to worry about managing and documenting the differences. That’s quite
different from a technical necessity, where
PROTECTED] On
Behalf Of Al Mulnick
Sent: Thursday, September 14, 2006 3:29 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] Handling different schemas - managing &
maintaining updates
Yep, the schema analyzer would
be a good tool to have hold of.
I have to ask th
Yep, the schema analyzer would be a good tool to have hold of.
I have to ask though: is the goal to make this mish-mosh manageable by making it all the same (i.e. cookie-cutter?)
Or is there some other goal you're describing?
I'm assuming that you want it to be the same across the enterprise to
To: ActiveDir@mail.activedir.org
Sent: Wednesday, September 13, 2006 8:37 AM
Subject: RE: [ActiveDir] Handling different schemas - managing & maintaining
updates
Without wishing to appear facetious :) - I would suggest if the company
follows ITIL practices then they already have a change mgmt and c
in each.
--Paul
- Original Message -
From:
[EMAIL PROTECTED]
To: ActiveDir@mail.activedir.org
Sent: Wednesday, September 13, 2006 2:37
PM
Subject: RE: [ActiveDir] Handling
different schemas - managing & maintaining updates
Without wishing to appea
Without wishing to appear facetious :) - I would
suggest if the company follows ITIL practices then they already have a change
mgmt and config mgmt process and/or system which helps achieve your
goal.
As far
as best practices are concerned, I would aim for a 'core' schema config which is
