Managing Hyper-V remotely in a workgroup can be challenging to configure. This is still the case for Windows Server 2016. For a testing environment I needed to remotely manage Windows Server 2016 core server with the Hyper-V role enabled from Windows 10 with the Hyper-V manager. I used the following manual configuration:
- Client with Hyper-V Manager (Windows 10). This client is called win10-01
- Server with Windows Server 2016 core version with the Hyper-V role enabled. The server is called hv-02
- Both systems are in the same workgroup called “workgroup”
- Both systems have the same username and password.
Configuration on the Windows Server 2016 server:
- Enable Remote Management
Configure-SMRemoting.exe -Enable
- Open firewall for Remote Computer Management
Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true -PassThru Set-NetFirewallRule -DisplayGroup 'Remote Event Log Management' -Enabled true -PassThru
- Open firewall for ping (ICMPv4)
Set-NetFirewallRule -DisplayName “File and Printer Sharing (Echo Request – ICMPv4-In)” -Enabled True -PassThru
- Enable Remote Desktop and allow remote connections
cscript.exe c:\Windows\System32\SCregEdit.wsf /AR 0
- Enable Remote disk management
Set-NetFirewallRule -DisplayGroup 'Remote Volume Management' -Enabled true -PassThru
Configuration on the Windows 10 client:
- Create a host file with IP address and hostname of the server. Make sure you can ping the hostname
- Make sure that the network type is part of a private network before executing the WINRM command
- Enable Remote Management
winrm quickconfig
- For Managing remote systems
winrm set winrm/config/client @{TrustedHosts="Name of the Server"}
- Enable remote disk Management (add this command on both systems) firewall rule
Set-NetFirewallRule -DisplayGroup 'Remote Volume Management' -Enabled true -PassThru
- Open c:\windows\system32\dcomcnfg.exe and allow ‘anonymous logon’ for local and remote access.
After making this settings I was able to manage the Windows Server 2016 server with the following tools remotely:
- Hyper-V manager
- Computer Management
- Disk Management
Hi
You forgot to add single quote (‘) in below command.
winrm set winrm/config/client ‘@{TrustedHosts=”Name of the Server”}’
Thank you, fix my problem in Windows 10, in Hyper V host I have to created a user similar to my user in my Windows 10 PC
Hello! Thank you very much for such complex information. Unfortunately, after following each step carefully, I still wasn’t able to connect to my Hyper-V server. The only difference is that I’m using Server 2012 R2. How can I know what it is that I’m missing? Thank you again in advance!
thank you very much …
Thanx alot! Spend alot of time figuring this out
This article was fantastically helpful for me after the instructions above did not work:
https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/manage/remotely-manage-hyper-v-hosts
Hi,
I ran with this issue and found out that.. I had to follow this article from technet as above.. but discovered that two gpo needs to be enabled.. if you disable one of the other than it will not connect.. I had used windows server 2016 RTM with hyper-v host and connecting from windows 10 client on a non joined domain.
allow delegating fresh credentials
allow delegating fresh credentials with ntlm-only server authentication
Regards,
Ravi
This was my third attempt at getting this working in my home lab. Finally got it working with this tutorial! Definitely added this to my notes.
Brilliant worked in one go -> client: Windows 10 Server HyperV core 2012 R2
Thank you Ivo.
Geert
How would you setup things to remotely manage the Windows Firewall on a Hyper-V Core 2016 server? Can’t get it to work.
Martijn
I’ve compiled detailed instructions of the steps from this article (and one other one) that I used to successfully complete this configuration. See my blog post here: http://mattslay.com/using-hyper-v-manager-to-remotely-connect-to-a-windows-hyper-v-server-2016/
**FOR THOSE WHO ARE STILL HAVING PROBLEMS CONNECTING TO THEIR HYPER-V SERVER TO HYPER-V MANAGER ON HOST/MANAGEMENT PC**
On the winrm configuration for trusted hosts, make sure the name of the server is not caps!!!