kkiedrowski
MIS
I have a 2008R2 Server running Hyper-V with a bunch of test machines used by developers and QA testers. Our developers would like to have their VMs not to be touched by the QA testers (no able to stop, pause, turn off, shutdown, start, etc..)
The developers would like access the QA Tester VMs.
The Hyper-V has all internal storage and on the domain.
So far for the developers and the QA tester machines are running Windows 7 so I setup their PCs with HyperV remote access: - but in this setup they have full access to all machines on that Hyper-V
I looked into using the Authorization Manager with the combination of having the VM folders guarded by NTFS permissions:
Folder 1 - test 1 VM: (permissions: Create Owner, System, TestUser, Administrators, Virtual Machines)
Folder 2 - test 2 VM: (permissions: Create Owner, System, Administrators, Virtual Machines)
TestUser is a domain user with standard user rights on the Hyper-V server
TestUser can access, start, stop, Test1VM and Test2VM through the hyper-v console.
With the use of the authorization manager I was able to prevent TestUser from changing configuration of the VMs but no manipulating them.
Wondering if anybody knows how to make this scenario work and if so how-to steps?
The developers would like access the QA Tester VMs.
The Hyper-V has all internal storage and on the domain.
So far for the developers and the QA tester machines are running Windows 7 so I setup their PCs with HyperV remote access: - but in this setup they have full access to all machines on that Hyper-V
I looked into using the Authorization Manager with the combination of having the VM folders guarded by NTFS permissions:
Folder 1 - test 1 VM: (permissions: Create Owner, System, TestUser, Administrators, Virtual Machines)
Folder 2 - test 2 VM: (permissions: Create Owner, System, Administrators, Virtual Machines)
TestUser is a domain user with standard user rights on the Hyper-V server
TestUser can access, start, stop, Test1VM and Test2VM through the hyper-v console.
With the use of the authorization manager I was able to prevent TestUser from changing configuration of the VMs but no manipulating them.
Wondering if anybody knows how to make this scenario work and if so how-to steps?