Wreaking Havoc with Your Schema
There are a number of ways to cause problems in your Active Directory schema. We include a few examples here so that you can be fully aware of the problems.
Let’s start by considering the main base classes of attributeSchema, classSchema, and top. Imagine we decide to add a new mandatory attribute to top. As all classes derive from top, the mandatory attribute requirement is suddenly added to every class and attribute throughout the schema in one go. Since none of the existing classes and attributes have this value, they all suddenly become marked as invalid. They still exist and can be used, but they cannot be modified at all. New timestamps cannot be added, USNs cannot be changed, replication stops, and effectively your Active Directory grinds to a halt. The reason that the objects cannot be modified is that Active Directory does a special check when existing instances of objects are modified to make sure that all mandatory attributes have been set. If they have not all been set, which they won’t have been in this case, Active Directory will not allow any attribute changes from now on. The only solution is to remove the new mandatory attribute or set a value for the attribute on every single object in every NC in the entire forest.
There are also concurrency problems. Having a Schema FSMO is perfectly fine, but that doesn’t necessarily stop members of Schema Admins from attempting to run two schema-modifying applications at the same time. Every time ...