Resolves an example of "unable to register SPNs during installation of VMM and SCP"

Recently due to the experimental environment problems, so reinstall virtual machine Manager R2, the installation of the following problems.

650) this.width=650; "height=" 630 "title=" clip_image002 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/ M00/6e/ca/wkiom1wh2iqj8p_zaajkl0g6054646.jpg "border=" 0 "/>

And from the problem description, the problem is that "if the SPN and SCP are not registered, the VMM console on the other computer will not be able to connect to this VMM Management Server, and deploying the Hyper-V host to a bare metal computer will fail." ”

This is done in the way it provides.

Run cmd with administrator, type the following command and return the correct registration information

650) this.width=650; "height=" 186 "title=" clip_image004 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/ M01/6e/ca/wkiom1wh2i_x3wwqaad93uqr8jo189.jpg "border=" 0 "/>

Use "regedit" to open the Registry viewer to check for the existence of the key value "Vmmserviceprincipalnames", whose path is:

"Software\Microsoft\Microsoft System Center Virtual machine Manager server\setup\vmmserviceprincipalnames"

650) this.width=650; "height=" "title=" clip_image006 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/ M02/6e/ca/wkiom1wh2jhszo7laagolwhpdu8129.jpg "border=" 0 "/>

Use the tool "ConfigureSCPTool.exe" to configure the SCP, which is located under the system Center Virtual Machine Manager installation directory:

C:\Program Files\Microsoft System Center R2\virtual Machine Manager\setup

650) this.width=650; "height=" 334 "title=" clip_image008 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/ M00/6e/ca/wkiom1wh2jsd1iogaagvcaa9_bk909.jpg "border=" 0 "/>

Run cmd as Administrator and enter the above directory to execute the following command,

650) this.width=650; "height=" 214 "title=" clip_image010 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/ M01/6e/ca/wkiom1wh2jbaf6vjaadjarqyg9y899.jpg "border=" 0 "/>

Finally, restart the VMM server, install the VMM console on the remote server, and connect to the VMM Management server to resolve the issue.

650) this.width=650; "height=" 464 "title=" clip_image012 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/M02/6E/C7/ Wkiol1wh2ldqey05aag1nbwx8bk074.jpg "border=" 0 "/>

This article is from "Xu Ting blog-it technology sharing" blog, please be sure to keep this source http://ericxuting.blog.51cto.com/8995534/1664183

Resolves an example of "unable to register SPNs during installation of VMM and SCP"