Here are 12 steps to remotely manage Hyper-V Server 2012 Core. Have you setup a Microsoft Hyper-V Server 2012 Core edition and now you want to remotely manage it in a workgroup (non-domain) environment?

Hopefully I can help ease your frustration with this article by showing you what worked for me.

If Microsoft did one thing that really tested my patients it’s trying to remotely manage Hyper-V Server Core in a workgroup environment.

Not long ago, I wrote an article titled Remotely Mange Hyper-V Server 2012 Core but admit I lost steam with wanting to work with it after that article/video. I wasn’t very confident with those instructions because every time I tested it there seemed to be different results.

Earlier today I decided to tackle this one again because I have had a lot of questions on this topic. It appears a lot of you out there are having similar issues. I feel very confident this time that I have all the instructions tested and working.

12 Steps to Remotely Manage Hyper-V

Quick run-down

Server: Microsoft Hyper-V Server 2012 Core (Free Edition)

Microsoft Hyper-V Server 2012 Core (Free Edition) Client: Windows 8 Pro

This next section is what I’m calling the condensed (advanced) version.

Condensed (advanced) Version

Install Hyper-V Server 2012 Core and log in to the console.

Configure date and time (select #9). Enable Remote Desktop (select #7). Also select the ‘Less Secure’ option.

Configure Remote Management (select #4 then #1). Add local administrator account (select #3). Username and password need to be exactly the same as the account you are going to use on the client computer to manage this Hyper-V Server. Configure network settings (select #8). Configure as a static IP. Same subnet as your home network. Don’t forget to configure the DNS IP. Set the computer name (select #2). Rename the server and reboot. Remote Desktop to server. On your client machine, remote to the server via the IP address you assigned it. Use the credentials of the local administrator account you created earlier. Launch PowerShell. In the black cmd window, run the following command: start powershell Run the following commands: Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”

Enable-NetFirewallRule -DisplayGroup “Remote Event Log Management”

Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”

Set-Service VDS -StartupType Automatic Reboot the server (select #12). Enable Client Firewall Rule. On your client machine, launch an elevated PowerShell prompt and type the following command: Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”

ii c:\windows\system32\drivers\etc Add server hostname and IP to hosts file. Right click hosts and select properties. In the security tab, add your username. Give your account modify rights.This is needed because some remote management tools we need to use rely on the hosts file to resolve the name. Without doing this you are highly likely to encounter some errors while trying to create VHDs and such. Error you might see: There was an unexpected error in configuring the hard disk.

There you have it: 12 steps to remotely manage Hyper-V Server 2012 Core.

You should now be able to remotely manage the Hyper-V server from the client machine. This includes managing the Hyper-V server’s disk from within the disk management console on the client. You should be able to create VHD’s successfully as well from within Hyper-V Manager on the client (assuming you installed the feature).

This was a quick tutorial on how to setup a working Hyper-V Server 2012 Core edition in a non-domain (workgroup) environment and still be able to remotely manage it.

Question for you

Have you setup Microsoft Hyper-V Server Core?