Virtualization Series 1: detailed explanation of win8 Remote Management hyper-v Server Authentication faults

Detailed explanation of win8 remote hyper-v Server Authentication failures

Today, companies use a domain environment for management, but sometimes some PCs or servers are separated from the domain environment based on the company's confidentiality or privacy policies ), this part of the PC or server in the Working Group also needs to be managed, such as hyper-v.

I. Environment Information

Use the win8 computer in the Working Group to remotely manage the hyper-v host in win2012.

Serial number	Device	OS version	Role
1	Ps	Windows server 2012 datacenter	Hyper-v Server
2	Client-1	Windows 8	Working Group

 

Generally, logon authentication for remote management is based on Kerberos authentication.

Ii. Case Process

2.1 install hyper-v manager in win8

 

650) this. width = 650; "src =" http://img1.51cto.com/attachment/201303/113507450.jpg "border =" 0 "/>

2.2 win8 use hyper-v manager to connect to a remote hper-v host

Error message:
Authentication error, no permission

 

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0209254V1-1.jpg "border =" 0 "/>

2.3 go to the troubleshooting step and check the troubleshooting information

Serial number	Project	Query point	Status
1	IP address configured correctly	Hyper-v Server Working Group	OK
2	Ping		OK
3	Firewall data and port settings exceptions		OK
4	Host domain name resolution is normal		OK
5	Disable anti-virus software		OK

 

 

2.4 check that the above information is correct. For permission issues, win8 uses powershell to add the following command and install the RSAT Software Package

 

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/020925J61-2.jpg "border =" 0 "/>

2.5 add hyper-v host using server manage of RSAT in win8

 

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0209252Y7-3.jpg "border =" 0 "/>

Authentication error again, but the device can be found

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0209256159-4.jpg "border =" 0 "/>

The default authentication method is domain authentication.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0209251O8-5.jpg "border =" 0 "/>

2.6 After the authentication method is updated, the hyper-v host is successfully added.

 

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0209251603-6.jpg "border =" 0 "/>

2.7 connect to hyper-v manager through server manage of RSAT package in win8

 

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/020925G94-7.jpg "border =" 0 "/>

2.8 successfully connected to the hyper-v host. The hyerp-v parameter can be configured normally.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0209254222-8.jpg "border =" 0 "/>

OK. Now we can access the hyper-v host for remote management and maintenance. In fact, the Working Group and the domain can collaborate with each other, but for integration security, or the domain environment has better compatibility and scalability.

This article is from the "server & security" blog, please be sure to keep this source http://ciscoart.blog.51cto.com/1066670/1162642