I like this advice as well. In terms of some of the nuts and bolts of how
one might do this, as a software guy, I'm a huge proponent of source code
control/configuration management systems and simple, text-based file formats
for the stuff you stick in your source repository. As such, I believe LDIF
files are the "one true way" to maintain your custom schema stuff.
The ADSchemaAnalyzer (usually associated with ADAM) is probably a useful
tool for doing a lot of the compare and extract work here.
Joe K.
----- Original Message -----
From: [EMAIL PROTECTED]
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 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 present in all instances of ADAM or AD schemas but manage
differences via the ITIL framework (mentioned above).
neil
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx
