Managing a Hyper-V server in a workgroup

Vertigo

Vertigo

Vertigo

Soldato
Joined
28 Dec 2003
Posts
16,498
Ok I have a Hyper-V Server 2008 machine which does not exist in a domain and which I need to be able to manage somehow. Most basic issue I'm having at present is that I can't access disk management to partition up additional drives for VM storage.

I've tried creating a user account on the Hyper-V server named the same as a workstation's account and added it to the administrators group and I can point an MMC with the disk management snapin at it but when I try to actually access it, it says I'm not permitted to access the Logical Disk management service.

Any ideas?
 
Playing with this a bit more, I've actually come to the conclusion that Hyper-V Server cannot be managed properly unless it's joined to a domain.

Of course that then precludes virtualising all the domain controllers on it, which is rather a major bummer. Thanks for that one MS!
 
SCVMM can manage Hyper-V host which is part of workgroup. If you don't have SCVMM setup can you not RDP to the server and manage it?
 
SCVMM is only for managing the Hyper-V aspect of the server, not the standard Server 2008 stuff.

Yes I can RDP into it but Hyper-V Server has even less to it than a Server Core installation so, even once you're remoted in, you can't do a damned thing. Basically, even partitioning disks has to be done with a remote MMC console but, in a workgroup environment, I gave up trying to get this to work as it kept giving me permission errors.
 
Hi,

Sorry, I though you were using Server 2008 with Hyper-V role added.

I had a quick look at MSDN to see if someone had released tool to overcome your issue and found this:

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

There also seems to be a lot of users on that site venting anger Microsoft for having to jump through 2-3 hoops to get start doing basics with Hyper-V Server.

I would also look at this tool for Hyper-V Server:

http://www.smart-x.com/?CategoryID=198&ArticleID=170&sng=1

You may be like me and hate working with command line.
 
Actually that's helped a lot. I can now administer pretty much everything remotely with the notable exception of Hyper-V itself, where the manager just won't connect and says I might have permissions issues.
 
Cracked it I think!

Only remaining issue was that I'd not logged in as the new administrative user I created on the Hyper-V server. Logging in at least once has obviously initialised something and now the manager works :D
 
You must log in or register to reply here.
Back
Top Bottom