We have over a dozen Hyper-V 2008 R2 Servers (standalone, not Server Core or OS role) in our organization. Love it! Great stuff.
That said, the management of Hyper-V Server leaves a bit to be desired at times. To be specific,
how can I create "read only" users that can user Hyper-V Manager to connect to our corp Hyper-V Servers, but only to see which virtual instances are running? In other words, user JSmith might have full-control over HVcorp1 server (local admin on that server), but only read-access to the HVcorp4 server. Is this possible? Can they simply be assigned to a local group on the HVcorp4 server -- such as the "users" group?
I found this Technet article which explains some of this functionality, but the process seems unnecessarily laborious.
http://social.technet.microsoft.com/wiki/contents/articles/hyper-v-delegate-access-control-and-management.aspx
Isn't there a better way?? If so, how?
Thanks,
Chumplet
Honestly, I'm somewhat ashamed to say that for all of our Hyper-V Server use around here, we don't actually use SCVMM at all. We do, however, have access to that product by nature of our MSDN Subscription.
Can you help me understand how SCVMM is rolled out? Would I install it onto a stand-alone box that users would connect to? Should the self-service portal be installed on a separate box, or on the same?
Thanks.