Domain schema update

On the schema master , open up the registry using regedt To use it, we need to first register the Dynamic Link Library DLL file for the snap-in by typing the following command at the command prompt:.

Run it from the Schema Master Domain Controller. This will generate our unique OID root which is :. All new classes will follow X. So in this case, our class OID will follow the branch. All new attributes will follow X. So in this case, our attribute OID will follow the branch. However, our test shows that if we set a value in this custom attribute In this case : male , it would show the value.

So we have added the custom attribute successfully in Active Directory Schema. Go to Properties. Step 5: Locate and modify the attributeDisplayNames attribute by adding a value in the below format:. The schema is the blueprint for data storage in Active Directory. In this article, we have discussed about Schema and it's structure. We have covered Schema classes and Schema attributes. Finally, we have discussed how to add custom attribute in Schema and what are the points that we should consider before we extend the Schema.

As Schema is one of the most critical component of Active Directory, we have to plan very well and test the deployment properly before we implement in production.

Also, appropriate backout plan is important which is typically restoring the Active Directory from Backup. Office Office Exchange Server. Not an IT pro? United States English. Post an article. Subscribe to Article RSS. Click Sign In to add the tip, solution, correction or comment that will help other users. Report inappropriate content using these instructions.

You should always prefix your names in the schema with company and solution name to make them unique relative to other schema extensions. So for example the attribute name should be contoso-hrdb-Gender. The AD schema reflects the basic structure of the catalog and is critical for its proper functioning. New versions of Microsoft OS contain new objects and attributes, so for their normal functioning as domain controllers, the administrator of the domain needs to update the Active Directory Schema.

The command returns the ObjectVersion attribute value, which is the version number of the Active Directory Schema. In our example, the schema version is 69, which corresponds to Windows Server R2.

The following table lists the correspondence between Windows Server versions and versions of the Active Directory Schema. Since these versions were released in different years, and each new version carries more functionality than the previous one, each operating system has its own schema version.

Therefore, when you add a new Windows Server based domain controller to an organization where existing DCs are running Windows Server , you will need to update your AD schema to the level of Windows Server In Windows R2 and lower, to successfully add the controller running a newer Windows Server version, you have to manually update the forest and the domain schema version. In Windows Server and newer, when you add a new domain controller, the schema is updated automatically.

To do this, you will need an adprep utility from the installation media with Windows Server To upgrade the version of the domain schema, log on to the DC with the Infrastructure Master role. To successfully upgrade the AD schema, your account must be a member of the following domain security groups :. Also, note the forest and domain functional levels. Domains in the AD forest can have different modes of operation functional levels.

For example, one of the domains can work on Windows mode, and the rest in Windows R2 mode. The forest scheme can not be higher than that of the oldest domain.