Ulf B. Simon-Weidner wrote: (...)
Note that no matter what - I'm usually always testing 3rd-Party Schema Extensions first, meaning to verify OID, prefix, LinkIDs, document MapiIDs and consult the customer in the risk of those, and verify the Structure (classes, how they are added to existing objects) default permissions, and look at the migration path if needed. Next step is to pull the domain in a virtual environment and test the schema extension there. Then I start with the extension in production where I follow above mentioned steps. However I'm always curious for other suggestions ;-)
Not much to add ... I'm following the same rules for schema extension. First some kind of review - even for standard extensions delivered with Windows 2003 or Exchange I'm performing a check of the elements You mentioned (OID etc) against the current schema because there can be something introduced by third party in the schema which may interfer with this extensions.
Then lab and after testing in the lab schema update procedure as well as DR procedures I'm going with schema upgrade in the real environment - separated network segment with DCs in it and operation is performed on these DCs.
-- Tomasz Onyszko http://www.w2k.pl/blog/ - (PL) http://blogs.dirteam.com/blogs/tomek/ - (EN) List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
