Hyper-V Program Manager
A while ago I blogged about how to allow non-administrators to control Hyper-V. You do this by editing the Hyper-V authorization store. What I failed to mention at that time was that this method does not work if you are using SCVMM to manage your Hyper-V servers.
When you start using SCVMM to manage a Hyper-V server, SCVMM creates their own authorization store to be used by Hyper-V. As long as you only use SCVMM to manage your environment – this is fine. But if you want to continue to use the Hyper-V management tools, and want to allow a non-administrator to control Hyper-V – you can do this.
All you need to do is to is follow the directions in my original post – but instead of editing “\ProgramData\Microsoft\Windows\Hyper-V\InitialStore.xml” on the system partition edit “\ProgramData\Microsoft\Virtual Machine Manager\HyperVAuthStore.xml” on the system partition.
Then everything will work correctly.
I'm having issues figuring out the best way for our developers to administer and access VM's for testing in Hyper V core server. There isn't a VMRC anymore, They need some serious tweaking to get the MMC client to connect from their own systems. Is the SCVMM better at this? They used to go to the VS2005 website, pick out their system, load the image they want with an Office version that they want, and then enable an Undo disk, and Login. Is there a good Central Admin method for "users"?
Should they remote into a VM running Win7 that I've configured to use the MMC client and go from there? I'm trying to figure out what this will look like and how it will work for them. Thank you for any information you can throw my way. -JoshG
Ben, we would like to move HyperVAuthStore.xml to the D: drive alongside our VHD and config files. The goal is to facilitate our Windows Server Backup by allowing us to backup only a single volume, D:. We would then modify the registry on the Hyper-V Host (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\StoreLocation) to point to the new location for HyperVAuthStore.xml. Do you happen to know if/how this might affect Hyper-V or VMM operation? I'm betting VMM will barf, and I don't know where/how to change the VMM pointer to that file.