Hyper-V Program Manager
A long time ago, I did a post about how to allow non-Administrative users to control Hyper-V. Then I did a post that showed you how to script this whole configuration. Finally, I did a post that showed you how to setup a “Hyper-V Administrators” group to make the whole process easier.
Well, time has passed and we have made things significantly easier for you here.
With Windows 8, Windows 8.1, Windows Server 2012 and Windows Server 2012 R2 you will now find that the Hyper-V Administrators group is already present:
All you need to do these days is to add your user account to the Hyper-V Administrators account, and you can do everything with Hyper-V without having to be a local administrator on the system.
While it might be easier it's just not granular enough.
AzMan provided that, VMM solves most of it as well, but the feature we need in our company, which is Enhanced Session mode is not supported by VMM. Which leaves us with two options, add everyone to the Hyper-V Administrators group (which is very much overkill) and use VMConnect or use VMM/App Controller console and lose the ability to copy/paste... . Hopefully this will be solved in a future release.
Agreed. As a school that runs VMs for students, we find that adding everyone to HyperV Admin group is over kill. We needed the granular access to limit specific functions of modifying let say the Ethernet adapter settings, etc. This really fails to do what Azman did. Please bring it back in an update, why would you all even remove it?
We tried this and it doesn't work.
We use a 2 node Windows server 2012R2 Hyper-v cluster and user workstation is windows 8.1.
We added the standard domain user account to the local "Hyper-V Administrators" group on both servers and rebooted the servers and the user's workstation but the error is "you do not have administrative permissions on this cluster." when you try to connect using MMC with FCM on the user's workstation.
Same issue as this post social.technet.microsoft.com/.../problem-with-granting-remote-access-to-hyperv-manager
and they claim Microsoft say this problem/bug/feature will not be fixed?
So do we have to just make the user a local admin on the Hyper-V server or should this feature work? Is there something else we need to bear in mind?