Knowledgebase

Remotely Manage Hyper-V Server 2012 Core

Search Articles

Remotely Manage Hyper-V Server 2012 Core

3 Views

On the Hyper-V Server 2012 Core system

First make sure you can ping the server by it’s computer name.

From what I read in other forums, you need to be able to resolve the hostname in order to remotely connect to it in Hyper-V Manager from a client.

Remote into the Hyper-V server from your client computer by using Remote Desktop.

Next we need to allow us access through the Hyper-V’s firewall.

I had some troubles trying to only enable the Remote Management display name, so I just went with all by using “*”.

This is not a good idea to do in a production environment (and probably not needed due to having a domain setup), but since we are setting this up for my test lab, I’m OK with it.

Make sure you are in the Powershell prompt (should see “PS C:\…” at the prompt)

If you are not at the Powershell prompt, simply type: powershell

and press enter [powershell]Enable-NetFirewallRule -DisplayGroup "*"[/powershell]

While we are remoted into the server, let’s manually create a VM.

I still have problems creating VMs remotely,

so for now this will have to do. [powershell]New-VM -Name Win8 -MemoryStartupBytes 1GB -NewVHDPath V:\Win8.vhdx -NewVHDSizeBytes 20GB[/powershell]

Of course you will want to fill in whatever Name you want, how much RAM, the path, and how large of a hard drive. On the client computer We need to store the server’s credentials locally on this client computer.

Open an elevated command prompt (runas Administrator) [powershell]cmdkey /add:yourHyper-VServerName /user:yourAdminUsername /pass:[/powershell] cmdkey remote manage hyper-v Type in the administrator password on your Hyper-V server and press Enter.

Now let’s add the Hyper-V Management Tools feature on the client computer.

Open up Programs and Features Select Turn Windows features on or off Expand Hyper-V Select Hyper-V Management Tools and press OK Add Hyper-V Management Tools Feature Now we need to allow remote access to ANONYMOUS LOGON

On the client computer, search for dcomcnfg and Run is as Administrator dcomcnfg remote manage hyper-v 2012

In Component Services, expand Component Services | Computers Right-click on My Computer and select Properties On the COM Security tab, select Edit Limits…

dcomcnfg edit limits Select ANONYMOUS LOGON and place a check in the Allow column of Remote Access box Select OK twice Now launch Hyper-V Manager on the client computer In Hyper-V Manager, select Connect to Server in the Actions pane Type in the name of your server and press OK

Since I want to install Windows 8, we need to attach the ISO I downloaded to the CD-Rom of this VM and then boot to the CD-Rom.

Select Settings in the Actions pane Select DVD Drive then Image file: Browse to your downloaded ISO and press OK Hyper-V Boot to CD-Rom Windows 8 Now let’s start up the virtual machine.

Select Start in the Actions pane Select Connect in the Actions pane You should see a window similar to the one below:Hyper-V Server 2012 Core - Remotely Manage - Start If all went well, you should be able to complete the Windows 8 installation in your new virtual machine.

If you have any troubles, please let me know by leaving a comment below.

What’s Next?

12 Steps to Remotely Manage Hyper-V

Quick run-down Server:

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 -Startup

Type 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.

http://pc-addicts.com/12-steps-to-remotely-manage-hyper-v-server-2012-core/

Was this article helpful?
Views: 3