Article ID: 890893 - Last Review: March 26, 2008 - Revision: 3.1 The SPNs that Virtual Server requires are not registered in Active Directory when you try to install Virtual Server 2005 on a Windows-based domain controllerSYMPTOMSWhen you try to install Microsoft Virtual Server 2005 on a domain controller that is running Microsoft Windows, the service principal names (SPNs) that Virtual Server requires are not registered in Active Directory. CAUSEThis issue occurs because the Network Service account that Virtual Server uses does not have permission to write the SPNs to Active Directory. Therefore, the SPN for vssrvc/NetBIOS_Name and vssrvc/Fully_Qualified_Domain_Name are not registered in Active Directory. RESOLUTIONYou can safely ignore this error if the SPNs are already registered in Active Directory. To determine whether the SPNs have been registered, you can use the Setspn command at the command prompt, for example: setspn -L NetBIOS_Name If the SPN's have been registered in Active Directory, the following output is displayed: vssrvc/NetBIOS_Name vssrvc/Fully_Qualified_Domain_Name vmrc/NetBIOS_Name:VMRC_Port vmrc/Fully_Qualified_Domain_Name:VMRC_Port If the SPNs have are not registered in Active Directory, you can use Active Directory Service Interfaces (ADSI) Edit or Set spn at the command prompt to manually register the SPNs. To do this, follow these steps: 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.
| Article Translations
|

Back to the top
