Hyper-V – you may not have permission!
So I decided to replace VMWare ESXi with Server 2008 R2 Hyper-V. The main reason for this was disk support. My home setup is pretty much cobbled togther from bits I had at hand. ESXi only supports SATA (or SCSI) disk and no support for USB drives, and I only had a couple of small SAta disks, but some large IDE and USB disks. I didn’t really want to buy a new large SATA disk, so I thought I would try Hyper-v.
Lets skip to now, and I have a working Hyper-V setup, with all my disks in, great, but what a saga it was getting here!
When I installed ESXi, it just worked. Installed it, downloaded the client, ran it, all good. Hyper-V was not the same simple process. I installed the Server 2008 r2 Hyper-V only server, which is essentially a Server 2008 Core install (cmd line only), with just the Hyper-V bits installed, to have as small a foot print as possible. This is great, but obviously means you need to admin it from another machine, not a problem. So I downloaded the Windows 7 Remote Admin Tools, installed them and launched the hyper-V console, that would be it you would think, oh no! You get an error about not having permissions to access the server. After much searching it turns out to remotely access the server you need to enable all sorts of firewall, DCOM and azman rights, the list is pretty large. Fortunately one of the developers on the Hyper-V project has developed a script to do most of these for you (outside of his job I might add, not paid by MS!), this can be found here – http://code.msdn.microsoft.com/HVRemote.
So I ran this tool, all ran fine, and so I thought that was it. I didn’t get the authorisation error, but then when I did connect, I got an error that “You might not have permission to perform this task”, ever so helpful. So I messed around for hours re-running scripts, changing settings etc, and then i fixed it. The error, that I was accessing the machine through an IP rather than a host name! Yes I should have checked it earlier, but what a stupid error, adn error message.
But, its up and working now, so lets see how it is.
Tags: error, Hyper-V, Virtualisation
This entry was posted on Sunday, August 16th, 2009 at 8:16 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Glen Says:
Matt Says:
Cory Says:
