After installing Windows Server 2016 Hyper-V on a small office network without domain or AD, I had big troubles with managing the server from Hyper-V Manager.
Found a guide from Microsoft that looked that it would solve the problem. But after trying “all” the steps there was still no luck with connecting to the server.
These were the steps that most useful to me:
On the Hyper-V host to be managed, run the following as an administrator:
- Enable-PSRemoting will create the necessary firewall rules for private network zones. To allow this access on public zones you will need to enable the rules for CredSSP and WinRM.
- Enable-WSManCredSSP -Role server
On the managing PC, run the following as an administrator:
Set-Item WSMan:\localhost\Client\TrustedHosts -Value “fqdn-of-hyper-v-host”
Enable-WSManCredSSP -Role client -DelegateComputer “fqdn-of-hyper-v-host”
Additionally you may need to configure the following group policy: ** Computer Configuration | Administrative Templates | System | Credentials Delegation | Allow delegating fresh credentials with NTLM-only server authentication **
Click Enable and add wsman/fqdn-of-hyper-v-host
I did not do the last and optional step because I didn’t know how to do it. Of course that was the missing part!
To get to the Computer Configuration you have to start the “Local Group Policy Editor“. You can search for it in Windows or run the command “gpedit.msc“.
Also for those who don’t know, FQDN is “Fully Qualified Domain Name”.