How to Upgrade the Schema to Upgrade Domain Controllers to Builds After Beta 3

• Microsoft Windows 2000 Advanced Server
• Microsoft Windows 2000 Server

SUMMARY

Microsoft supports upgrading Windows 2000 servers running versions later than Beta 3 rather than requiring a clean installation. Upgrading to later builds requires one or more schema changes that have been made to these builds. This article describes how to check the schema version, how to perform the operating system upgrade, and how to perform the schema upgrade.

MORE INFORMATION

Assume you have RC1 build 2072 installed on all servers in the forest and you want to upgrade to RC2 (this procedure applies if you are upgrading from Beta 3 to RC1 as well):

1. On any domain controller (preferably a domain controller in the parent domain), insert the CD-ROM of the new build and select the Upgrade option (run Winnt32.exe from the CD-ROM). At the beginning of the upgrade process, several files are copied, including the Schema.ini, Sch11.ldf, Sch12.ldf, and Schupgr.exe files (for an upgrade to RC2). If you are upgrading from Beta 3 to RC1, only the Sch11.ldf file is copied. This is also true for later builds and schema changes. The number (11 or 12) in the file name indicates the schema version of the upgrade. You then receive a message indicating that a schema mismatch has been detected.



2. Quit the upgrade process and open a command prompt window. Go to the %SystemRoot%\System32 folder and run Schupgr.exe. You see a "bind" notice and the current schema version, and then the schema is upgraded.



3. When the schema upgrade process is finished, run the new build upgrade again.



4. You need to perform the schema upgrade on only one computer. Replication updates it on all the other domain controllers in the forest.



5. Once the schema is upgraded on all the domain controllers (by replication), you can upgrade them to later builds. You can install different builds in the same forest as long as the schema is the highest schema version used by the builds.

To Check the Schema Version

• Simply run Schupgr.exe on the computer you want to check. You may receive an error message, but the third line does report the version number. If the schema is already upgraded, you are informed of that fact.



• Use Registry Editor (Regedt32.exe) to view the following key:




HKey_Local_Machine\system\CurrentControlSet\services\NTDS\Parameters

The last parameter is the schema version number. Double-click the value to convert it to decimal. Note that Beta 3 is schema version 10, RC1 is version 11, and RC2 is version 12.

To Cause a Domain Controller to Join an Earlier-Build Domain

1. Upgrade one existing domain controller in the domain/forest to the later build. This allows the schema upgrade as noted above. If you simply try to join the older-schema domain, you receive an error message stating that it is not allowed due to the schema change. This does not copy the files; you must use the upgrade process to copy the schema files.



2. Let the replication process replicate the schema change on all domain controllers.



3. Verify the schema version upgrade using one of the methods described above.



4. Bring the new domain controller or server into the domain by using Install or Dcpromo.

Additional query words:

Keywords : kbenv kbsetup
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbhowto