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.
Cheers,
Ben
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?
Thanks
Hi.
Thanks for your post. When we used Windows 8.1, the group was present and worked well. Unfortunately, in Windows 10 the Hyper-V Administrators group doens't exist anymore.
Why was the group removed, and how can I get it back?
Thank you and best regards,
David
Hello,
on windows 10 education the powershell script doesn't work and the Hyper-V Adminstators Group didn't exists. On a windows 8.1 machine there is a Hyper-V Administartors Groups. So how can we allow non-Adminstrator control Hyper-V under windows 10 education???
David / Monk,
We have tracked down an issue that can cause the group to be missing when you upgrade from one Windows edition to another. We are working on a fix right now, unfortunately there are no work arounds at this point in time.
Ben,
The Groups missing isn’t new – and has been “fixed before”!
https://support.microsoft.com/en-us/kb/2850661
Alas performing an “inplace upgrade” of Win10 Pro to Win 10 Pro (yes same edition) fixes this for most groups except the ‘Hyper-V Administrators group’
Now if I could do a clean re-install of Windows 10 Pro that would be something – but that’s not even possible due to another bug that means you end up with Windows 10 Home (and a 30 minute chat with support to get Pro), which results in an usable install…
Hi Ben,
any news on that fix? I experienced this on my brand new Windows 10 machine, which I primarily bought to use the Visual Studio Android emulator with Hyper-V. Unfortunately this machine came with Windows 10 Home edition, so I had to upgrade it… and ran in exactly that Hyper-V problem.
I really would appreciate a quick solution for that.
Regards Steffen
Steffen,
Did you find a work around for this issue? I believe I have the same issue.
Cheers,
Kym
I think I have found this same issue myself. Upgraded from Win10 Home to Professional and discovered I have no HyperV Admin group. Is there any further information for a fix, regarding this?
Any updates on this? I just installed Windows 10 Enterprise on a new disk and I don’t have the Hyper-V Administrators group after installing the Hyper-V feature. Visual Studio Android Emulator fails to launch with Unable to add user to the Hyper-V Administrators group. Exit code 2220.
Any news?
I upgraded to windows pro solely to use hyper-v.
Ridiculous that one can’t create a ‘magic’ user group oneself. Effectively makes my pc using windows useless for development work.
Ben,
I just got a new Lenovo T460. I enabled Hyper-V and installed Visual Studio 2015 and Xamarin. I get the same error and there is no Hyper-V Administrators group on my machine. I do have other Hyper-V VMs that run fine, so I am sure Hyper-V is working correctly.
I ordered the machine with Win10 Pro (I never switched editions) and I’m sure many other devs will be doing the same.
I just wanted you to be aware that it is not only caused by switching editions.
Thanks,
Paul
Having this issue too, but this machine was never upgraded from a prior OS. Straight from factory x1 Carbon 2016 with Win 10 pre-installed. No Hyper-V Admins group. Always on Win 10 Pro.
I have exactly the same issue, when I upgrade to Windows 10 Education. Any updates on this issue?
I have this issue with Windows 10 Pro. My machine is new, a few weeks old, came from the factory this way – June 2016. ThinkPad P40 Yoga. No Hyper-V Admin group.
The bottom line is this product is defective.
Unfortunately the functionality I need was removed in 2012, to be able to allow users to open Hyper-V Manager console, stop, start and connect to VM’s but not be able to alter any of the attributes.
Shame really, 2008 allowed you to do this
Hi Ben and others.
My environment is WS2016 / W10 Pro.
imho there is a serious usability issue in this area. Or course, we can give “Hyper-V Admin” rights to some accounts without giving them upper rights. But, feel free to correct me if I’m wrong, if those accounts have only “Hyper-V admin” rights, they won’t be able to use Hyper-V Manager because they don’t have enough privileges to run the mmc.
Let’s take an example. My people are Java software developers. They work in a full Java environment, Eclipse, Git, etc. For some purposes, they run some Hyper-V VMs on their PCs. But very few of them are really the PS skills necessary to drive the VMs. What I would expect is to be able to add them in the “Hyper-V Admin” group and no more. They would have enough rights to run Hyper-V Manager and drive their VMs through some nice graphic tools. And AFAIK, this is not possible without given them the full “Admin” rights on their computers.
And this is even worse if you run an Hyper-V Server and want your people to drive their VMs from their local Hyper-V Manager, because in such case, you must give them full Admin rights not only on their workstations but also on the server. This is bad, really bad.
Why not having a Group Hyper-V-Guest-Adminstrators. Those users have no rights on Hyper-V-Host but can access the Hyper-V-Guests through vmconnect. That would be a wonderful feauture for admistration of Linux-guests by a consultant.
Regards Timo