<div>
Problem seems to be a fluke, so thread no longer needed.
</div>


Problem seems to be a fluke, so thread no longer needed.

<div>
<div class="content wysiwyg-content">
We have a group of 2012r2 hyper-v servers, some of them in a failover cluster, some of them standalone.<br />
<br />
I have a couple developers I want to give permission to open the hyper-v manager to restart their servers. &nbsp;I have given them permissions through GPO that allows them to RDP and open hyper-v manager to manage the non-clustered hyper-v servers, but the same permissions won't work on the clustered hyper-v servers, they get an error saying they don't have permission to connect to the servers.<br />
<br />
I have a security group called 'dev_admin', and on the OU for the hyper-v servers I have a GPO that is giving dev_admin rights for Log in Locally, log in through terminal services, and under restricted groups have put dev_admin into the remote desktop users, and Hyper-v administrators, and to test I even put them into the builtin\administrator group for local admin rights (I don't want to use this except to test, but still no joy)<br />
<br />
BTW the iscsi SAN machine is also in the same OU, so all the servers are getting the same GPO settings.<br />
<br />
What am I missing?
</div>
</div>


We have a group of 2012r2 hyper-v servers, some of them in a failover cluster, some of them standalone.

I have a couple developers I want to give permission to open the hyper-v manager to restart their servers.  I have given them permissions through GPO that allows them to RDP and open hyper-v manager to manage the non-clustered hyper-v servers, but the same permissions won't work on the clustered hyper-v servers, they get an error saying they don't have permission to connect to the servers.

I have a security group called 'dev_admin', and on the OU for the hyper-v servers I have a GPO that is giving dev_admin rights for Log in Locally, log in through terminal services, and under restricted groups have put dev_admin into the remote desktop users, and Hyper-v administrators, and to test I even put them into the builtin\administrator group for local admin rights (I don't want to use this except to test, but still no joy)

BTW the iscsi SAN machine is also in the same OU, so all the servers are getting the same GPO settings.

What am I missing?

Give non-admins permissions to administer hyper-v failover cluster, server 2012r2

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Failover

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.