Since I struggled quite a bit - I am just an enthusiast without any proper training - setting up a Hyper-V Server 2016 (TP4) "CORE" to be remotely managed from the GUI Hyper-V Manager on my Windows 10 Desktop WITHOUT A DOMAIN (Workgroup only),
here is how you do it (quick and dirty):
All those tutorials out there are largely outdated, the steps are actually quite simple, if you do know them...
On the HOST:
Powershell:
PS C:\Users\Administrator>enable-PSremoting
PS C:\Users\Administrator>enable-wsmancredssp -role server
On the CLIENT:
1. Powershell:
PS C:\Users\Administrator>start-service winrm
PS C:\Users\Administrator>Enable-WSManCredSSP -Role client -DelegateComputer *
PS C:\Users\Administrator>stop-service winrm
2. GPEDIT (as administrator)
Local Computer Policy-->Computer Configuration-->Administrative Templates-->System-->Credentials Delegation-->"Allow delegating fresh credentials with NTLM-only server authentication" set "Enabled" and "Add servers
to the list" (click "Show..."), enter "WSMAN/*" as Value, hit OK 2 times.
3. Fire up Hyper-V Manager and connect to server only with IP-address and enter as user "YOURIP\ADMINACCOUNT_ON_HOST" and its passwort. There you go.
No manual firewall settings required anymore. No additional service starting/configuration required anymore. No need to manually configure TrustedHosts anymore. No need to have identical admin-accounts on host and client. No fiddling with hosts files...
BUT
...is the following a BUG?
I noticed a strange behaviour around the hosts file as follows:
If your Windows 10 Desktop client is (or WAS!) domain-joined, the above will only work if you allocate the HyperVHost-hostname to its IP in the client's hosts file. Still you do not need to set "localhost\client\trustedhosts" anywhere, simply mapping
the IP to the hostname works. Did I do something wrong? Is this a known issue?
Just curious. Thanks!
