3SysAdmins.com

The Tech Blog of a Sysadmin.

Remote Administration of Hyper-V Server 2012R2

One of the first things you will want to do once you have installed your copy of Hyper-V Server 2012 is to disconnect the monitor and configure the rest from a workstation. This is easier said than done, but by following these few steps you should be up and running in no time. The easiest way to be able to perform the rest of the config from a workstation is to enable remote desktop. There are two steps to getting this working.

Enable RDP Connections to the Server

  •  Firstly, enable remote desktop in sconfig
  •  Run "netsh advfirewall firewall set rule group="Remote Desktop" new enable=yes" to open up the firewall
  •  Use powershell, netsh or sconfig to apply a static IP (sconfig requiring least effort)

You should now be able to dial in. Which steps are required next now depends on whether this deployment is going to be in a domain or workgroup environment.

Enable Remote Management from a Domain Joined Computer;

  • From your windows 8 workstation or server 2012 machine add the Hyper-V Manager tools
  • Make sure the workstation and Server are registered in DNS
  • From Sconfig on the Hyper-V server run the enable remote management option
  • Run winrm quickconfig on the client machine
  • Run the command "netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes" on the client machine to open up remote managment.

Enable Remote Management from a Workgroup Joined Computer;

All the steps above need configuring as well as;

  • Run "winrm set winrm/config/client @{TrustedHosts="SERVER NAME"}" on the client changeing the Server Name to suit, this adds the server to the list of trusted hosts for remote management connections on the workstation.
  • You may need to add host files in place of DNS names as well in this scenario.

Other things I have come across in my time with Hyper-V server include checking the winrm service is running on the server side, and that is that it is entirely possible to use the tools within windows 10, but it is quite a convoluted task in a workgroup test lab environment if you already have access to windows 8 or server 2012. This is because unless you can leverage kerberos, you also need to enable https as the transport method and provide a suitable cert. All of this i intend to cover in a later post, and remember also that it is not possible to connect in remotely from the Hyper-V RSAT tools for windows 7.

I hope this has been helpful to anyone who has stumbled across the article.

 

Add comment


Security code
Refresh

Get instant updates via email

Simply enter your email address to subscribe for updates - 3SysAdmins will never share your details with any third parties.

FeedBurner Subscription