12 Steps to Remotely Manage Hyper-V Server 2012 Core

I feel your pain! Have you setup a Microsoft Hyper-V Server 2012 Core edition and now trying to remotely manage it in a workgroup (non-domain) enviornment?

Hopefully I can help ease your frustration. Maybe you have some tips that I missed which could help others (leave comments HERE).

If Microsoft did one thing that really tested my patients it’s trying to remotely manage a 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 hits on this topic. It appears a lot of you out there are having similar issues. I feel very confident this time that I have it down.

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.

  1. Configure date and time (select #9).
  2. Enable Remote Desktop (select #7). Also select the ‘Less Secure’ option.
  3. Configure Remote Management (select #4 then #1).
  4. 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.
  5. Configure network settings (select #8). Configure as a static IP. Same subnet as your home network. Don’t forget to configure the DNS IP.
  6. Set the computer name (select #2). Rename the server and reboot.
  7. 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.
  8. Launch PowerShell. In the black cmd window, run the following command: start powershell
  9. 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
  10. Reboot the server (select #12).
  11. 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
  12. 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.

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 environment and still be able to remotely manage it.

Question for you

Have you setup Microsoft Hyper-V Server Core?

About Chris Davis

Computer / Technology enthusiast. Very passionate about Systems Administration. I enjoy helping others try and reach their goals. You can follow Chris on if you'd like.

Comments

  1. Thanks Chris, another great tutorial. I’ve set up my VMSERVER in a virtual domain, followed your instructions as per above to the ‘T’, but am unable to remotely connect to the VDS (get the message “You do not have access rights to Logical Disk Manager on VMSERVER1.”). I’ve logged into my virtual Windows 8 Client using and administrator account setup as per your Virtual Lab series, and duplicated the account on VMSERVER1 machine. VMSERVER1 has not been migrated onto the virtual domain, so maybe this could be the problem. Any advice?

    • Thanks for the comment Jeremy!

      Couple quick questions:

      1) Are you RDP’ed into the Hyper-V Server using the same account as your client?

      2) Did you run the following command on ‘both’ the server and client?

      Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”

  2. hello. nice article btw.
    i am getting RPC unavailable on hyper v and disk mgmnt i have ran HVRemote…as well as read and read. disable firewall on both machines. i can look at users and such through computer management from my client machine but disk and hyper v RPC unavailable. I believe i followed your article to a T. but i will try again. any help is greatly appreciated. thanks!!

  3. i got it. i had to put my client machine in the servers host file. it coudln’t resolve me. thanks agian!!!

  4. Hi Chris, I’m in a Domain Environment, but trying to configure Hyper-V access remotely. I’ve followed your steps above and can access the Computer Manager, Remote Desktop etc, but still get the RPC error when trying to connect from my WIndows 8 Client. Do you have any suggestions?

  5. Hi Chris,

    I can’t get the remote management to work unless I set the Dcom remote access to ANONYMOUS. Any ideas why that is, I’ve followed your steps several times to make sure I got them right.

  6. Have you tried to use 5nine manager? It is domain independent and can manage different hyper-v versions remotely. And what is best for core it gives GUI for local management.

  7. You do not need to create a local admin account that mirrors your desktops account. You can “manage the server as” servername\username from server manager and it works fine. Though, I must say it has been a few days and Google mania to successfully connect and manage the Hyper-V server from a workgroup in my test environment. This was one of the more helpful sites. Thanks for that.

  8. Anyone else having the problem that I listed above for the DCOM permissions? I don’t want to pay for a manager utility, This is a demo environment.

  9. I really appreciate your article, it’s the best one I’ve come across. I believe that I’ve followed your instructions exactly but I still cannot manage the hyper-v server. I can RDP into it just fine, but when I try to connect through the hyper-v management tool I only get the error, “You do not have the required permission to complete this take. I can’t think of what would be causing that, any insight here?

    • I know you said you followed the instructions but did you make sure to run step number 11 on the ‘client’ computer as well (the computer you are running Hyper-V Manager from)?

  10. I did number 11 as best as I could tell. My host file contains “10.0.0.101 hyper-v” and from an elevated powershell I ran that the command to allow “Remote Volume Management” through the firewall. I made sure it was allowed under Windows Firewall with Advanced Security. I even created a new Windows 8 client VM and followed the same steps exactly to try an eliminate a problem with the client-side steps. Usernames and passwords match exactly on the server and client.

  11. Hello. Running Win 8.1 Pro as a Hyper-V server (home use). Can anyone confirm that the above works for Win 8.1? Noticed there’s a trackback that shows that it does, I’d like a second confirm before taking the plunge. Thanks

  12. I have followed the above steps, I am using a win7 pro x64 machine to manage my Hyper-V servers. I currently have a 2008 server running and can connect and manage it with the Hyper-V Manager form Win 7, I have loaded a Hyper-V 2012 Core machine and followed the above steps, but when I try to connect it (2008 Hyper-V is connected) it tells me connection Failed, it does resolve the 2012 computer name under Hyper-V manager but states the operation on computer “IP address” Failed. Not sure what I have incorrect.

  13. Hi,
    I’m having this error on my Hyper-V Manager, said:
    “Hyper-V encountered an error trying to access an object on Computer ‘myserver’ because the object was not found. the object might have been deleted, or you might not have permission to perform the task. Verify that the Virtual Machine Management service on the computer is running. if the service is running, try to perform the pask by using Run as Administrator”

    I’m using Windows 8.1 in here

  14. How about connecting to a Hyper-V 2012 server from Win8 logged in with a hotmail account? I, perhaps foolishly, tied my Win8 install to my hotmail account and when I attempt to use Hyper-V manager it doesn’t give an option to ‘connect as’. I’ve tried adding username@hotmail.com as a local admin and can’t get a format for the command that works. I can add username with password, not hotmail.com.

    • Oh wow… this is a new one! I haven’t tested this out so I am not sure if I can help (yet).

      • Chris Bridge says:

        I’ve got the same problem on Win8.1
        Can’t Remote Desktop to the Hyper-V 2012 R2 server, or use Hyper-V Manager, I managed to use Server Manager using the right click, Manage As … feature.

        • Chris Bridge says:

          I found this which has helped, a little..
          http://code.msdn.microsoft.com/HVRemote

          After adding a new (local) user to my Wn8.1 client, and as an additional administrator on the Hyper-V, I can control the Hyper-V from the Server Manager on the Win8.1 client. However, I still cannot Remote Desktop :(

          The HVRemote script is trying to do an nslookup, but failing, as my DNS server is my home router, and it’s not responding to the nslookup (I’ve added the client and servers both on reserved DHCP ip addresses each).

          • Chris Bridge says:

            The following are working from Server Manager:
            ->Dashboard, right click server name
            – Restart Server
            – Windows Powershell
            – Computer Management opens,
            but can’t open Disk Management gives: “The RPC server is unavailable”
            – Hyper-V Manager opens, and I appear to have privileges, yay!
            – Remote Desktop Connection
            (takes an age Initiating Connection… then gives up).
            – Configure Windows Automatic Feedback

        • Chris Bridge says:

          running this via Powershell against the server (or local console) this fixed my RDP problem:

          netsh advfirewall firewall set rule group=”remote desktop” new enable=Yes

  15. Hey Chris just want to say GREAT post, I appreciate you taking the time out to do the video it was informative and helpful in my home lab I have here. Running ESXI 5.5 with nested Hyper V 2012 R2 << had some issues trying to get it to work with remote management but your video helped. Thank you

  16. Kushal Goaten says:

    Hi chris thank you for the tutorial. its the best 1 i have found on the web . I followed your steps. everything went smoothly until the last part. here is a screenshot – http://i43.tinypic.com/33ettl2.png Even after that i tried the Hyper-V manager and i could add a VM. But when i want to use the virtual cd/dvd drive i get this error – http://tinypic.com/r/54ynbo/5. I am using Windows 7 x64 client. can you help me?

    • I am in the same situation Windows7 and 64bit. I get the same error messages. I am getting really tired of this.

      Today is my third day at trying to get this to work. It find it difficult to believe that MS would produce a product that is so hard to configure

  17. On my Server 2012 GUI Client I’m able to manage other Server 2012 GUI Servers. (These only started to work once I ran the HVRemote tool) I’ve since installed two more servers 1) Hyper-V Server 2012 R2 and 2) Server 2012 Core and I’ve used all the same logins/passwords as my other Server 2012 GUI Servers and ran the HVRemote tool and they will NOT connect. Errors in Computer Manager include: Cannot Manage the OS of target computer which makes no sense as they’re configured just as the Server 2012 GUI’s are.

  18. Kushal Goaten says:

    I have nearly done it malcolm. I can mount and boot the ISO if the iso is located on the harddisk on the server pc.

  19. On the machine you want to manage, run dcomcnfg.

    Go to Component Services, then Computers and right-click My Computer and choose Properties.

    Go to the COM Security tab, and under Access Permissions, click Edit Limits.

    Click ANONYMOUS LOGON and check the Remote Access box under Allow.

    Click OK, then OK again.

  20. Problem: Followed everything to the letter. Still stuck on Hyper-V Manager saying “Access denied. Unable to establish communication between X and Y”. (on a in 8.1 client)

    Applied the “dcomcnfg” solution by Sebastian Tipping (above) NOT “on the machine you want to manage” (that ‘core’ machine/server does not have this tool anyway) but applied it on THE CLIENT.

    Works like a charm! :D

  21. jeff punya says:

    Is everything the same to configure from a licensed windows server 2012 (not 2012 r3) to a hyper-v 2012 the same as this tutoria?

  22. try this my friends it’s allot easier
    http://code.msdn.microsoft.com/Hyper-V-Remote-Management-26d127c6#content
    if you want complete steps let me know

  23. Enable-NetFirewallRule -DisplayGroup “Remote Desktop”

    before step 7

  24. thanks trevor – worked for me too!

  25. Thanks Chris, I really liked your tutorial. It was consistent to the point and easy to follow.

    However, I had some problems after running the Enable-NetFirewallRule settings on both the server and the client. Once I rebooted the server, the Hyper-V Manager on the Windows 8.1 client could not connect to the Microsoft Hyper-V Server 2012 R2. The message said that it was a permission issue. On the server I added following PS Cmdlet and rebooted to resolve the problem:

    Enable-NetFirewallRule -DisplayGroup “Hyper-V”

    Previously on the client I tried to use Server Manager to access the Hyper-V server; both systems are on a WORKGROUP domain. I had already added the cmdkey setting for the local user. I had to add the Hyper-V server as a trusted host with the following PS Cmdlet to resolve the problem:

    Set-Item WSMan:\localhost\Client\TrustedHosts –Value -Concatenate

    I’m not sure why I had problems, but everything works OK now.

  26. Does anyone know where I go to “strict RPC filter in Threat Management Gateway”. I don’t were to start to do this function. -Joe

    • ***Before you follow this, ensure you have a full backup of your TMG Server and you have local access, just in case you cut yourself off from the server!!***

      The RPC filter is usually controlled on a per rule basis, so you can have fine control over this. RIght click the rule in the TMG console and select Configure RPC Protocol. Now untick the strict RPC compliance option. Click OK, then apply the new rule base.

      You should now be able to get access. Hope this Helps!

  27. I got a similar error message to this and found that I had missed a step:

    6. Set the computer name (select #2). Rename the server and reboot.

    I did this and was able to connect successfully through hyper-v manager on a 2012 server.

  28. Hi,

    I have a server in my local network which has already HyperV installed. it has static IP 10.60.60.23. I have 3 clients inside that Hyper V. I’m using these 3 for my testing. Is there any way to RDP these 3 servers inside my HyperV from my Laptop ?

  29. Paulthefish says:

    Thanks a million!!! I tried all sorts of commands and couldn’t get it to work. Did you’re 12 steps and bang it worked!!!!

  30. Fantastic!
    Thanks!

  31. I’m getting The operation on computer “servername” failed when trying to connect via hyper-v manager. My situation was a little different in that I had to install the gui version of server 2012 because I need to verify that all the drivers were installed. Then rolled back to the core only. Then installed the hyper-v role via command line. The only step that I was not able to run was ◾Enable-NetFirewallRule -DisplayGroup “Remote Volume Management” on the client machine. Doesn’t recognize the term enable-netfirewallrule.

    • Rooky mistake… Thank you Microsoft for not letting windows 7 machines run management tools on server 2012. I pulled down vtutilites solved my problem.

  32. I believe everyone here that this is a great step-by-step, but I can’t manage my Hyper-V server after performing these steps. I can ping it, and it can ping other systems on the network. However, I can’t use RDP to get to it, nor can I connect to it with Hyper-V Mgr on my Win 8 machine. Why does MS have to make everything so darned complicated? I have been screwing with it for two hours, and still can’t do anything useful with it…

  33. Great start, and a lot of time and effort for you to get this figured out.
    I had two issues (I think)…
    1. I did need to set the Enable-NetFirewallRule… Before I could get Remote Desktop to work.
    2. I resorted to using the HVRemote tool referenced in one of the above replies when it did not work. Turns out that in addition to having the IPV4 addresses added to client and server hosts file I also needed separate line entries for the IPV6 addresses.
    Now I have it all working and under control from my Windows 8.1 machine and free Hyper-V 2012 R2

    Ross

  34. I can manage Hyper-V 2012 R2 server from the manager in windows 8. Is it possible to use Hyper-v manager from WIN 2008 server to manage Hyper-V 2012 R2? The Hyper-V manager in 2008 says “operation on computer failed”
    Thanks, Rob

  35. Violetta says:

    Thank you, Chris! Grate work!

  36. jojo balingit says:

    I followed every step. everything works fine when the client and server are connected to the same router. But I need to manage this server from a remote location ie at home at a local starbucks. Here is the setup:

    Server has a public static IP. When I am at home, I can do RDP. I can run MMC and add the firewall snap-in and if needed make changes.

    Problems: When I click on Disk Management I get the error THE RPC SERVER is unavailable. When I go to the HyperV manager, get th eerror: RPC Server Unavailable. Unable to establish communication between “the hypervserver” and “the client”.

    aside from the steps, I did the edit limits, allow anonymous, the cmdkey for user/pass, the wsman set-item command. port 135 is open, firewall disabled, no antivirus.

    I am pretty sure it has something about netbios or dns. Or is it even doable to completely manage a hyper v 2012 R2 from a different location not on the same network?

    PLEASE HELP!

  37. shyamsingh says:

    Hello Chris,

    I’ve followed the instructions and for the most part of it, everything seems to work out but when I tried to create a virtual machine, I get this error:

    Startup memory

    Out of Bounds

    Specify a memory between 32 and 32

    I don’t understand why but it is not allowing me to assign more than 32 MB of memory to a virtual machine.

    I went ahead and tried using powershell and hyper-v manager and ended up with the same in both.

    For the record, I have installed Hyper-V Server Core in VMWare Workstation 10 with 1 processors, 2 cores, 2 GB of memory and 60 GB of hard disk.

    Please let me know what I’ve been doing wrong or what could be the issue behind this and possible resolution.

    Thanks

  38. Yusuf Stark says:

    Hi, something I’d like to add as a side note in case anyone runs into the same problem as me.

    I followed your video to the T but I was still having permission problems, 2 hours later and a fresh install and I solved the problem.

    The username is “case sensitive”, so if you have a username on your win8 client of “Yusuf” and on your Hyper-V server your username is “yusuf” you won’t be able connect via the Hyper-V Manager.

    One way to check this is to look at the name of your Users folder on both client and server. Can be fixed by recreating matching users on both computers, no fresh install needed.

    Hope this helps anyone who is having trouble.

    Oh as well if anyone wants to run the old RDP client on win8 instead of the new RDP in the Microsoft App Store, download and install the “Jump Desktop Client” and it installs the old RDP along with the Jump Client. You don’t have to use the Jump Client afterwards, just search for “remote desktop connection” in your start menu. :)

  39. Super article, shame that I totally missed stage 11! But got it this time. Thank you

  40. Chris your awesome, got it to work, thanks for your hard work on this, this will help us a lot!

  41. Sebastian Tipping’s reply helped my a lot, it seems to be something in Windows 8.1 Pro that prevents the local machine from accessing the server. I’m guessing this is easier in Windows 7.

  42. Chandramas says:

    Hi, I had no problem with anything until step 13, then I received an error when I tried to type Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”
    on my client powershell (I run it as administrator)
    The error I receive is in Italian That says that the command “Enable-NetFirewallRule” is not regnized. (I have on my client a Win 7 in Italian)
    (Sorry I feel dumb, but I’m seeing this for the first time )

    • Chandramas says:

      I am dumb! Sorry, you wrote clearly it was for Win 8. Now I have to find a different way to deal with this problem. Thanks anyway because your tutorial was really easy to follow!

  43. many thanks, amazing job, a video thats allow me do all my work properly in 1 shot.

  44. diamondtech says:

    When I do Step 11
    11.Enable Client Firewall Rule. On your client machine, launch an elevated PowerShell prompt and type the following command: ◾Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”
    I get the error

    The term ‘enable-netfirewallrule’ is not recognized as the name of a cmdlet, function, script file, or operable program
    . Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At line:1 char:23
    + enable-netfirewallrule <<<< -displaygroup "remote Volume Management"
    + CategoryInfo : ObjectNotFound: (enable-netfirewallrule:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Yes I am trying this on Windows 7 Ultimate, I just want to get Hyper V manager working so I can create some simple VM's. Anyone else running into this.
    I can remote desktop to the system no problem, but Hyper V manager just gives me the wonderful "The operation on computer 'hypervm' failed. Thanks for any pointers. Yes I know Windows 7 is not supported with 2012 R2, but is sounds like from other posts I have read you can get it working, just without all the enhanced functionality. Let me know if I am wrong.

    Thanks
    Tom

  45. Here’s a solution alot simplier.
    1 – install VMware esxi on your server
    2- instal vsphere client on your client machine
    3 – log into it…

  46. Like DiamondTech above, I am also unable to run the Powershell “Enable-NetFirewallRule” command on my Windows 8 machine. Maybe JDB is right…

    • I am amazed at how friggin’ stupid all this is – Microsoft hasn’t made this difficult on purpose. They have just been very sloppy in providing a means of managing this. It was released before it was finished, in my opinion. Why I should spend a day getting started on this is beyond me.
      Still trying to resolve the above issue with the Enable-NetFirewallRule

      • Try HVRemote. Seems to smooth out the hiccups, or at least mine. Had nothing to do with the firewall – it was a networking issue. Managing workstation could find the server, but the reverse wasn’t true.
        Still think MS did a sloppy job on this – no excuse for it…

  47. EDUARDO HERNANDEZ says:

    HI, Chris Davis

    WHEN PLACED IN POWERSHELL:

    Enable-NetFirewallRule-DisplayGroup “Windows Remote Management”
    Enable-NetFirewallRule-DisplayGroup “Remote Event Log Management”
    Enable-NetFirewallRule-DisplayGroup “Remote Volume Management”

    A MESSAGE APPEARS:

    The term ‘Enable-NetFirewallRule’ is not recognized as the name of a cmdlet, function, script file, or operable program
    . Check the spelling of the name, or if a path was included, Verify That the path is correct and try again.
    At line: 1 char: 23
    + Enable-NetFirewallRule <<<<-DisplayGroup "Remote Volume Management"
    + Categoryinfo: ObjectNotFound: (Enable-NetFirewallRule: String) [], CommandNotFoundException
    + FullyQualifiedErrorId: CommandNotFoundException

    THANKS FOR YOUR HELP

    REGARDS

Trackbacks

  1. […] want to use the awesome native Hyper-V Manager built into Windows 8/8.1, you need to follow some arcane steps first. But it’s well worth the hassle; you can then manage your Hyper-V server from Starbucks […]

Leave a Reply