Cannot Upgrade Windows 2000 Server to Windows Server 2003 with Windows Services for UNIX 2.0 Installed

You may not be able to upgrade a Microsoft Windows 2000 Server domain controller to Windows Server 2003 if the Windows 2000 domain controller has the Server for NIS component from Services for UNIX version 2.0 installed. Also, when you try to upgrade to Windows Server 2003, you may be prompted to run Schupgr.exe to upgrade your schema, and when you run this tool, you may receive the following error message:

The upgrade may not work because the attributeSchema 'uid' that is used by Windows 2000 Server for the NIS schema is not compatible with the one that is used by Windows Server 2003.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Important If Services for UNIX version 2.0 has already been removed, this hotfix cannot be installed. In that case, you must run Renameattribute.exe, the attribute renaming program. To rename the attribute without installing the hotfix:

1. On a domain controller for Active Directory directory service, log on with administrative credentials.
2. Extract the contents of the hotfix. To do this, type the following command at a command prompt, and then press ENTER:
   Q293783_SFU_2_X86.exe /x
   Renameattribute.exe is extracted to the folder where you placed the Q293783_SFU_2_X86.exe file.
3. Run Renameattribute.exe from the folder where you extracted it in step 2.

Note The purpose of this hotfix is to permit you to upgrade from Windows 2000 to Windows Server 2003. Microsoft has not tested Services for UNIX 2.0 on Windows Server 2003. For more information about interoperability, visit the following Microsoft Web site:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

The attributeSchema 'uid' is included for RFC 2307 compliance by Server for NIS. However, it is the attributeSchema 'msSFUName' that is actually used in Server for NIS. The fix is to stop copying the msSFUName values to uid, and to rename the attributeSchema 'uid' to 'uid-SFU-V2'. Replication of the schema update to all the peer domain controllers can take some time. Because of this, it is important to wait until the attributeSchema rename process is replicated among all the domain controllers in the forest. The Windows Server 2003 upgrade should complete successfully after the replication completes.

For installation specifics, see the Hotfix.txt file that is included with the hotfix. Remember the following information when you install the fix:

• Run the Q293783_sfu_2_x86_en.exe file from its current location or save it to disk and then run it.
• After the installation, wait for the schema to be propagated to all the domain controllers that are peers to this domain controller before you upgrade to Windows Server 2003.