Windows domain schema version

However, this will only prove that this particular DC has this level and we still does not know the rest of the Domain Controllers.

We could instead use the old but useful dsquery tool and check the same attribute: all in one line. The line must be altered with the correct path to the actual domain and also be directed to each Domain Controller with the -s switch. I wrote a short script that will automatically find all DCs and print the Schema version.

This should make it easy to verify that all Domain Controllers are up to date and that the new Schema has been successfully replicated to every DC in the domain.

Copy the script and make sure the line breaks are not lost. The following documentation contains the programming reference for Active Directory schema. If you are an end-user attempting to debug a printer error, try searching on the Microsoft community site. If you are a developer looking for a general overview of Active Directory schema, see the Active Directory Schema overview topics. If you are looking for programming guidelines for updating or modifying the schema, For more information about extending and customizing the schema, see Extending the Schema , as well as many of the topics in the Active Directory Domain Services and Active Directory Lightweight Directory Services programming guides.

In each of the reference topics, there is a section for each operating system that the topic applies to. In all the methods listed below, the internal root domain used is: prajwal. From the dsquery output, the objectVersion property determines the current AD Schema version which is 88 in this case.

From the output, the objectVersion property value determines the current Active Directory schema version which is 88 in this case. Click OK. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.

Privacy policy. They also determine which Windows Server operating systems you can run on domain controllers in the domain or forest. However, functional levels do not affect which operating systems you can run on workstations and member servers that are joined to the domain or forest.

When you deploy AD DS, set the domain and forest functional levels to the highest value that your environment can support. This way, you can use as many AD DS features as possible. When you deploy a new forest, you are prompted to set the forest functional level and then set the domain functional level.

You can set the domain functional level to a value that is higher than the forest functional level, but you cannot set the domain functional level to a value that is lower than the forest functional level. With the end of life of Windows Server , , and R2, these domain controllers DCs need to be updated to Windows Server , R2, , or