Next step in HyperV

On August 8, 2012, in HyperVServer, by

I was really hoping to use the coreconfiguration tool http://coreconfig.codeplex.com/documentation but because I’m doing this with 2012 HyperV and not Server 2008 r2 tool, it doesn’t appear to be working.

So the first thing we’re going to type in is

http://technet.microsoft.com/en-us/library/ee815290(v=ws.10)

Sconfig.cmd

(Well actually if you just booted up the server, that’s that main blue dos menu

We’re leaving this in a workgroup.

I already enabled remote management (as you can see above)
“In the Server Configuration tool, configure remote management by typing 4 and pressing ENTER.”

…and it’s at this point in time that I realize that I’m reading instructions for setting up HyperV server in a domain.

So chuck those instructions out the window and follow this blog post instead:

http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/11/11/configuring-remote-management-of-hyper-v-server-in-a-workgroup.aspx

Ah ha now we’re talking… the next step is to set up a workgroup user that can log into the HyperV workgroup server

  1. Select option 3 (Add Local Administrator)
  2. When prompted for an account name – enter the user name that you are using on the Windows 7 desktop (in my case – “Bitz”).
  3. You will then be asked for a password – and again you should use the same password as you are using on the Windows 7 desktop (no – I am not going to tell you my password)

 

And the user is set up successfully.

Next – to enable remote (but read-only) access with device manager – run this command from the command prompt as well: reg add HKLM\Software\Policies\Microsoft\Windows\DeviceInstall\Settings /v AllowRemoteRPC /t reg_dword /d 1 (once again that is a single command).

Enter number 14 to get to the command line

Type in the command shown hopefully not misspelling anything in the process.

Type in SConfig.cmd  to get back to the menu and hit 12 to reboot the server.

Okay now we’re back on my workstation – and for this I need to download – http://www.microsoft.com/en-us/download/details.aspx?id=7887

…and it’s taking forrreeeeevvver to install.  So entertain yourself while I wait for it to install.  It will probably need a reboot too.

Amazing, I don’t need to reboot.

After you have done this you will need to enable the correct remote management tools. To do this:

  1. Open the Start menu
  2. Open Control Panel
  3. Select Programs and Features (or just Programs depending on the Control Panel view that you are using)
  4. Select Turn Windows features on or off
  5. Find Remote Server Administration Tools and Check Hyper-V Tools (under Role Administration Tools) and Server Manager under the top level list
  6. Click OK

Okay did that.

 

Next hack up the host file so it will find the HyperV server

  1. Open the Start menu
  2. Click on All Programs and then on Accessories
  3. Right click on Notepad and select Run as administrator
  4. Once Notepad has opened, use the File menu to Open… a file
  5. Navigate to the “Windows\System32\Drivers\etc” folder on the system drive
  6. Change the file name option from Text Documents (*.txt) to All Files
  7. Open the “hosts” file
  8. At the end of this file – add an entry for your server. The format is basically the IP address of the server followed by the name of the server.
  9. Save the file and exit Notepad.

 

You will need to enable the use of WinRM to connect to your Hyper-V server. To do this you will need to:

  1. Open the Start menu
  2. Click on All Programs and then on Accessories
  3. Right click on Command Prompt and select Run as administrator
  4. Type in winrm quickconfig and hit enter. You will then need to say ‘y’ (yes) to a couple of prompts

 

 Now I should say at this time that I enabled the ping on the remote server so that it would respond to me.  Go to the server, go into item 4 remote management and turn on ping.

  1. Type in winrm set winrm/config/client @{TrustedHosts=”RemoteComputerName”} and hit enter
    1. Substitute “RemoteComputerName” with the name or IP address of your Hyper-V server. In my test environment my desktop computer could not resolve the name of my server – so I just opted to use the IP address. I could also have edited the hosts file on my desktop and used the server name.

 

  1. While we are here – we should also open the firewall on the client side to allow us to remotely manage the servers storage by running this command: netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes

 

 

Now you will need to use HVRemote to enable remote management of Hyper-V on the desktop computer.

  1. Download HVRemote from http://code.msdn.microsoft.com/HVRemote/Release/ProjectReleases.aspx
  2. Open the Start menu
  3. Click on All Programs and then on Accessories
  4. Right click on Command Prompt and select Run as administrator
  5. Change to the directory where you saved HVRemote
  6. Type in cscript hvremote.wsf /mode:client /anondcom:grant /firewallhypervclient:enable /mmc:enable and hit enter.

 

If I’ve done it right

  1. Open the Start menu
  2. Click on All Programs and then on Administrative Tools
  3. Click on Server Manager
  4. You will be automatically prompted for the name of the server that you want to connect to.

…and I’ve not done it right…

hmmm…

And that didn’t help.

…and this is why..

2. You need Windows 8 or Windows Server 2012 to manage Hyper-V of Windows Server 2012 with RSAT.
http://social.technet.microsoft.com/Forums/sk/winserver8gen/thread/174c1794-5e3d-4b35-b14b-7968f119793e

Mismatching betas and released products is nailing me.  Okay I’ll try this again tomorrow night with a Win8 in a workgroup to see if I can remotely manage this box.

 

One Response to Next step in HyperV

  1. Joe Miner says:

    Thank you for posting this detail – please keep it comming!

    did you go with 8G or try 16G of RAM?