SYMPTOMS
When you try to upgrade Microsoft Windows Services for UNIX 3.0 to Microsoft Windows Services for UNIX 3.5 on a Microsoft Windows Server 2003-based computer, you receive an error message that resembles the following:
Error when upgrading NIS Schema. Please look at the log file at:
C:\Documents and Settings\Administrator\Local Settings\Temp\sfusch.log for more details on the error.
Additionally, the Windows Services for UNIX installation rolls back.
You may also notice entries in the sfusch.log file that resemble the following:SFUSCH.log
Start of schema extension. Time: Mon May 9 17:38:35 2005
Schema Naming Context
'CN=Schema,CN=Configuration,DC=example1,DC=com'
FSMO Role Owner
'CN=Adatum,CN=Servers,CN=Example2,CN=Sites,CN=Configuration,DC=example1,DC=com'
DNS Hostname of FSMO
'Adatum.example1.com'
Redirecting schema changes to 'CN=Adatum,CN=Servers,CN=Example2,CN=Sites,CN=Configuration,DC=example1,DC=com'
Default Naming Context
'DC=example1,DC=com'
Domain name = 'example1'
Done with getting information from Active Directory
Checking SFU schema version
Checking SFU V30 schema on server - Adatum
Verifying all extended schema attributes. AD Server = 'Adatum'.
Verifying all extended schema classes. AD Server = 'Adatum'.
Verifying all extended schema classes. AD Server = 'Adatum'.
Verifying all extended auxilliary schema classes. AD Server = 'Adatum'.
Checking existing SFU configuration version
Checking SFU V30 schema on server - Adatum
Verifying all extended schema attributes. AD Server = 'Adatum'.
Verifying all extended schema classes. AD Server = 'Adatum'.
Verifying all extended schema classes. AD Server = 'Adatum'.
Verifying all extended auxilliary schema classes. AD Server = 'Adatum'.
Marking DC as NIS server
SFU Schema Extension did not complete.
End of schema extension. Time: Mon May 9 17:38:36 2005
RESOLUTION
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
To resolve this problem, start the Active Directory Service Interfaces (ADSI) Edit snap-in (ADSI Edit) and rename all Active Directory objects that use the same CN as the domain controller object.
Note ADSI Edit is included with Microsoft Windows Server 2003 Support Tools. To install the Windows Server 2003 Support Tools, double-click Suptools.msi in the Support\Tools folder on the Windows Server 2003 CD.
To do this, follow these steps:
- Click Start, click Run, type adsiedit.msc, and then click OK.
- In ADSI Edit, expand Domain [Adatum], and then expand DC=example DC=com.
- Locate and rename all objects that use the same CN as the domain controller object.
Important The domain controller object is located under OU=Domain Controllers. Make sure that you do not rename the domain controller object.