Hyper-V 2016 configuration Management Series (Part7)

Remotely connect to Hyper-V HOST

For daily operation and maintenance, use remote PowerShell to work. RSAT (remote Management tool) is installed on Windows 10. Then the Hyper-V console is installed:

Before you can connect to Hyper-V remotely, you need to do some configuration from a server and client perspective. In both nodes, run the following cmdlet:

Enable-WSManCredSSP-Role server

On your laptop, run the following cmdlet (hyper-v-host will be replaced by the future Hyper-V host FQDN):

Set-Item WSMan:\ localhost\ Client\ TrustedHosts-Value "10.10.0.5" Set-Item WSMan:\ localhost\ Client\ TrustedHosts-Value "hyper-v-host-01" Set-Item WSMan:\ localhost\ Client\ TrustedHosts-Value "10.10.0.6" Set-Item WSMan:\ localhost\ Client\ TrustedHosts-Value "hyper-v-host-02" Enable-WSManCredSSP-Role client-DelegateComputer "10.10.0.5" Enable-WSManCredSSP-Role client-DelegateComputer "hyper-v-host- 01 "Enable-WSManCredSSP-Role client-DelegateComputer" 10.10.0.6 "Enable-WSManCredSSP-Role client-DelegateComputer" hyper-v-host-02 "

Then, run gpedit.msc and configure the following policy

You can now take advantage of the new Hyper-V Manager feature, which can connect to the Hyper-V using alternate credentials