This article has been archived. It is offered "as is" and will no longer be updated.
If the Windows 2000 domain controller has the Server for NIS component from Services for UNIX 2.0 Japanese installed, you cannot upgrade a Microsoft Windows 2000 Server domain controller to Windows Server 2003.
Additionally, when you try to upgrade to Microsoft Windows Server 2003, you may be prompted to run Schupgr.exe to upgrade your schema. When you run this tool, you may receive the following error message:
Schema update failed: attribute in may-contain does not exist.
Note This problem also occurs if you try to add a new Windows Server 2003 domain controller to a domain in which Services for UNIX 2.0 is installed.
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 UID that is used by Windows Server 2003.
Services for UNIX 2.0 Japanese is not supported on Windows Server 2003.
Note If you have already removed Services for UNIX 2.0, you cannot apply the following hotfix. See the "More Information" section.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next release that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The Japanese version of this update has the file attributes (or later file attributes) 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 item in Control Panel.
Date Time Version Size File name ------------------------------------------------------------------- 03-May-2001 22:38 10,752 Renameattribute.exe 24-May-2003 02:00 5.2000.602.12 1,643,008 Nis2ad.exe 24-May-2003 02:00 5.2000.602.12 1,686,016 Nisctrl.dll 24-May-2003 02:00 5.2000.602.12 1,643,008 Nismap.exe 24-May-2003 06:11 5.2000.602.12 83,456 Nisprop.dll 24-May-2003 06:13 5.2000.602.12 144,384 Nissvc.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Any applications or scripts that try to read the value of the uid attribute may now not get the information that is stored in it because the attribute that stored the information is now renamed as the uid-SFU-V2 attribute. All such applications and scripts should be modified to query the uid-SFU-V2 attribute, or the information in this attribute should be migrated to the new attribute that is named uid to maintain the compatibility.
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. As a result, you have to wait until the attributeSchema rename process is replicated among all the domain controllers in the forest.
You can expect the Windows Server 2003 upgrade to complete successfully after the replication completes. For installation specifics, see the Hotfix.txt file that is included with the hotfix. When you install the fix, keep the following points in mind:
Run the SFU2-Q821732-X86-JPN.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.
If you have already removed Services for UNIX 2.0
If you have already removed Services for UNIX 2.0, you cannot apply this hotfix.
To upgrade to Windows Server 2003 if you have already removed Services for UNIX 2.0, follow these steps:
Obtain this hotfix (SFU2-Q821732-X86-JPN.exe) from Microsoft Product Support Services, and save it to a convenient directory (for example, C drive).
Open a command prompt:
Click Start, click Run, type cmd, and then click OK.
Change to the directory that contains the hotfix (cd c:\).
Run the hotfix with the /x option: SFU2-Q821732-X86-JPN.exe /x
A dialog box appears. Type the path of a directory to put the hotfix files in (for example, C:\q821732), and then click OK.
The directory will be automatically created if it does not exist.
When the dialog box disappears, switch to the directory that contains the hotfix files (for example, cd c:\q821732).
Run the appropriate renameattribute.exe command, depending on where and how you are logged on:
On a domain controller (as a domain administrator), run the command without any parameters:
On a member server (as a domain administrator), specify a domain controller as the parameter:
On a member server (but not as a domain administrator), specify the account and password as additional parameters: