Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I've installed Microsoft Hyper-V Server 2008 R2 on a spare box. How do I configure and manage the server?

I configured as much as I could find to be

  • open
  • on
  • allow
  • etc.

Now back at my desk (Windows Vista 64-bit) I want to make the server do stuff, for example:

  • create the RAID volume
  • create virtual machines
  • make it hyper

I can't remote desktop to it:

alt text

I can't use Computer Management to manage Hyper-V*ness*, or the drives:

alt text

I tried downloading the Windows Vista Management Tools for Hyper-V, but they apparently do not apply to my system:

alt text

There is no domain. I tried adding my desktop login/pass as an account on the server, but my 21-character password (including spaces and special characters) doesn't meet the server's password requirement.


That's what I've tried, but you can ignore all that. Let's start over:

How do I manage Microsoft Hyper-V Server 2008 R2?


Note: Because of the Hyper-V limitations, I just repurposed the server and abandoned Hyper-V server. Hyper-V was an interesting idea, but not yet ready for real world production use.

As a result I won't be checking answers to see if they work (as if you should need a wiki to figure out how to configure a server). I'll make this a community wiki, so that others continue to have a place to figure out how to manage a Hyper-V server - but I'll no longer be monitoring it.

share|improve this question
    
"Hyper-V was an interesting idea, but not yet ready for real world production use" - ohkay, we run VMWare which does the same stuff as Hyper-V and we have over 30 virtual servers running on a blade centre. Not ready for production use? Riiight –  Mark Henderson Jan 3 '10 at 0:13
    
i'm sure it's technically quite capable. –  Ian Boyd Jan 8 '10 at 21:39

7 Answers 7

I hate to ask the obvious, but are the client & server both set to the same time & time zone? I'm assuming you already set the remote properties to the "less secure" option in sysdm.cpl to get to this point?

As far as a user, I'd just create a user on the server and login using computername\username

share|improve this answer
    
Timezone: Yes. Less secure: Yes, although Hyper-V server you configure it from a console mode UI. Create user: i cannot, it doesn't accept the password. –  Ian Boyd Sep 3 '09 at 21:31
    
Update: Looks like your suggestion did indeed let me connect with RDP. i fixed the timezone earlier today, and it didn't fix it right away. Now that i've come back to it few hours later it does work. Now i can connect to the empty desktop - but Hyper-V server doesn't let you manage the server locally. –  Ian Boyd Sep 3 '09 at 21:40
    
Yes, the free download seems to come without a lot of the tools to make life easier, the walkthrough here may help netometer.com/video/tutorials/… –  Kara Marfia Sep 4 '09 at 12:06

Check Out Remote Server Administration Tools for Windows 7

http://www.microsoft.com/downloads/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en

Quote: Remote Server Administration Tools for Windows 7 enables IT administrators to manage roles and features that are installed on remote computers that are running Windows Server 2008 R2 (and, for some roles and features, Windows Server 2008 or Windows Server 2003) from a remote computer that is running Windows 7. It includes support for remote management of computers that are running either the Server Core or full installation options of Windows Server 2008 R2, and for some roles and features, Windows Server 2008. Some roles and features on Windows Server 2003 can be managed remotely by using Remote Server Administration Tools for Windows 7, although the Server Core installation option is not available with the Windows Server 2003 operating system.

This feature is comparable in functionality to the Windows Server 2003 Administrative Tools Pack and Remote Server Administration Tools for Windows Vista with Service Pack 1 (SP1).

share|improve this answer
    
Similar to the other software package, "This update does not apply to your system." –  Ian Boyd Sep 3 '09 at 21:43
    
Oops... Blew past the 'Windows Vista' part when reading. It may be that you need to have Windows 7 client to manage Hyper-V R2 but I'm not sure. Good Luck –  AJ. Sep 3 '09 at 22:26

You are very close to success! Here are links to the key pieces I believe you need:

KB article 952627: Description of the Windows Vista Management Tools update for the release version of Hyper-V

KB article 952627 includes a link to the Remote Management Update for Windows Vista for x64-based Systems download location.

Finally, you can use the CMDKEY utility on your Vista workstation to configure appropriate user credentials to authenticate to the Hyper-V host automagically.

share|improve this answer

I had the same problems as you. This wsf file and associated instructions got rid of all the problems I was having, now I can connect through the Hyper-V Manager snapin, as well as the Computer Management snapin, from a Vista SP2 machine.

share|improve this answer

Depending on your Domain/Worgroup architecture between the server machine and client you're attempting to use to connect remotely, there could be a lot of configuration to do.

http://code.msdn.microsoft.com/HVRemote

The above tool will enable you to easily connect using Hyper-V Manager from a client workstation.

As for configuring the disks, I would suggest using the DISKPART command-line utility on the server itself.

share|improve this answer

Regarding the issue with your password not meeting the server's password requirement, you probably have the "Password must meet complexity requirements" policy enabled.

This TechNet article has the details. In a nutshell, with this option enabled, your password must meet the following criteria:

  • Passwords cannot contain the user's account name or parts of the user's full name that exceed two consecutive characters.
  • Passwords must be at least six characters in length.
  • Passwords must contain characters from three of the following four categories:
    • English uppercase characters (A through Z).
    • English lowercase characters (a through z).
    • Base 10 digits (0 through 9).
    • Non-alphabetic characters (for example, !, $, #, %).
share|improve this answer

If I were you, I'd start with John Howard's blog. He's got a lot of tips and tools for configuring and managing Hyper-V on Server Core (which is what Microsoft Hyper-V Server is.)

Start here:

http://blogs.technet.com/jhoward/archive/2008/11/14/configure-hyper-v-remote-management-in-seconds.aspx

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.