The Service Principal Name could not be registered in AD DS for the SCVMM 2012 R2 Management Server

December 21, 2015 at 11:14 am in Private Cloud, SCVMM 2012 R2, SPN by Wim Matthyssen


Sometimes when installing a new System Center Virtual Machine Manager (SCVMM) 2012 R2 Management server you can receive following message at the end of the installation: “Setup completed successfully with warnings”. Like you can read in the error message, this means the installation was successful only the Service Principal Name (SPN) could not be registered in Active Directory Domain Services (AD DS) for the SCVMM Management Server. If the SPN and SCP are not registered, SCVMM consoles on other computers will not be able to connect to this SCVMM Management Server and deploying a Hyper-V host to a bare-metal computer will not work. This problem occurs when your installing your SCVMM Management Server with an account that has insufficient rights to make chances to AD.


To fix this problem run following commands as a domain administrator from a command prompt:

1) Use setspn.exe to create SPN for SCVMM server using the following command:

"C:\Windows\system32\setspn.exe  -S SCVMM/hostname.domain accoutname".

As example:

"C:\Windows\system32\setspn.exe -S SCVMM/VMM-01.contoso.local CONTOSO\mgrscvmm".

2) Add SPN values to following registry key "Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup\VmmServicePrincipalNames".

3) Run "C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\setup\ConfigureSCPTool.exe -install" to configure SCP.


This should fix the issue and also concludes this blog post.

Hope it helps, till next time!

Wim Matthyssen (@wmatthyssen)

Share on LinkedInTweet about this on TwitterShare on Google+Share on Facebook