Skip to main content

Configuring a Hyper-V R2 Core Installation

A little deal I stumbled across online landed a Core 2 Quad Q9400 with 8GB of RAM in my lap for a good price. After struggling with a deep seated desire to put a decent video card in it and lock myself in the office playing video games, I finally decided that putting together a test network would be a much healthier choice. I still locked myself in the office though.

After wasting away an evening troubleshooting the installation, I finally got it working today. Here is a quick summary, for those who are receiving "RPC Server Unavailable" messages and other things of the sort, of what steps I took to get everything working in harmony. You should already be familiar with Hyper-V in general; I'll be leaving some pretty large details out and focusing on the problem areas.

Both client and server will be in the same workgroup (i.e. not a domain), and on the same subnet. The client in my situation was a Windows 7 Professional desktop. Be sure to grab John Howard's Hyper-V Remote Configuration Utility (HVRemote) before you begin and bookmark the homepage!

SERVER SETUP (Workgroup):

  1. Download, burn, and install the Hyper-V R2 Core ISO on the server.
  2. Configure a name for the server and assign it to the same workgroup as your client (Option 1 & 2 in the sconfig.cmd menu).
  3. If the account you plan to use on your client is not named "Administrator", add the name of the account you plan to use as a Local Administrator (Option 3). Be sure to use the same password!
  4. Configure Remote Management (Option 4). Allow ALL options here.
  5. Set a static IP address on the same subnet as your client
  6. Download and install all the latest updates, restart the server.
  7. Using your client, connect to an administrative share on the server ( \\SERVER\C$ for example) and copy over the hvremote.wsf script from John Howard.
  8. Run the commands listed on the HVRemote home page to add a few more firewall rules and allow your newly created account full reign on the server. I also found it useful to run the commands for the administrator account ( cscript hvremote.wsf /add:adminsitrator ).

CLIENT SETUP (Workgroup):

  1. Download and install the Windows Remote Server Administration Tools
  2. Head to Control Panel -> All Control Panel Items -> Programs and Features -> Turn Windows Features on or off. Expand the Remote Server Management tree and install Hyper-V Tools.
  3. Setup a HOSTS file entry to point your client to the static IP address you set for your server.
  4. Run the commands listed for the client side of HVRemote on John Howard's website.
  5. If you need to be able to access the physical disks on your server, you will also need to enable the Remote Volume Management rules in your client firewall:

That's pretty much it, you should be able to connect with Hyper-V at this point, as well as to the server using the Computer Management MMC. If you are still having issues, you can disable BOTH client and server firewalls with the following command (Vista/7/2008 only):

netsh advfirewall set currentprofile state off

That should clear up any firewall related issues you may have, provided you are not using a third party application to perform AV/Firewall duty.

If you are still receiving an "RPC Unavailable" or other error message in Hyper-V Manager, ensure that both your client and server have the same username & password. Things are much simpler if you have both client and server working in a domain, but they will cooperate in a workgroup with some tweaking.

Good Luck!


  1. thanks for this, good addition to the M$ instructions, saved me quite some time I guess..


  2. No problem, hope it helped, best of luck.

  3. Thanks, server setup #8 was the trick for me.

    I am running both client and server in a workgroup, and I could not connect unless I turned off the server firewall, which I did not want to do. Thanks for posting this guide, it's Greatly appreciated!

    Mike in Gaithersburg, MD

  4. Thanks Mike, glad it worked for you. Best of luck in your Hyper-V endeavors.

  5. My hero ... ;-)


Post a Comment

Popular posts from this blog

Outlook Credential Prompt When Opening Exchange 2013 Public Folder

After completing an Exchange 2007 > 2013 migration recently, I was left with one issue that was preventing us from stamping the project as a roaring success and moving on:

Outlook 2013 users were sometimes receiving a single pop-up prompt for credentials whenever they opened the Public Folder (we have only one). One. Single. Prompt.

Google was frustratingly unhelpful because searching for "outlook prompts for username and password when opening public folders" or something similar just resulted in a lot of folks who were always getting a pop-up that wouldn't go away. It was usually caused by an authentication failure of some sort.

However, we were in a different boat - Users got the prompt once when they first launchedOutlook and opened their public folders, but after entering it they could continue - authentication worked. Next time they logged in to their PC, it would happen again. Not a show stopper, but it definitely generated its share of support calls.

Repairing Mailbox Corruption in Exchange 2010

I recently got through recovering an SBS 2011 server after Active Directory face-planted in the middle of a workday. When I say recover, I mean I repeated the entire migration, using a cleaned up secondary DC - it was a fun weekend (expect another post about that experience). Although I thought we were in the clear, I got a call from the client about 24 hours after we had verified everything was working. He indicated that his iPhone had suddenly stopped receiving mail in the inbox (calendar, contacts, sent items were still fine) and throws up an error after spinning in circles for a few minutes that it "cannot connect to mail server".

SCEP Policy Update Troubleshooting

Because I'm a glutton for punishment, I recently started rolling out System Center Configuration Manager 2012 R2 SP1 and System Center Endpoint Protection across our VDI environment. There are always some considerations to be made in a pooled desktop / gold image type environment when loading software that uniquely identifies devices, but lucky for me SCCM/SCEP handled this just fine without any tweaking. However, there were some nuances to how SCEP policies are applied that caused some serious hair-pulling before I spotted the issues.