<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Allowing non-Administrators to control Hyper-V</title><link>http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/17/allowing-non-administrators-to-control-hyper-v.aspx</link><description>By default Hyper-V is configured such that only members of the administrators group can create and control virtual machines.&amp;#160; Today I am going to show you how to allow a non-administrative user to create and control virtual machines. Hyper-V uses</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Allowing non-Administrators to control Hyper-V</title><link>http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/17/allowing-non-administrators-to-control-hyper-v.aspx#7148910</link><pubDate>Fri, 18 Jan 2008 15:36:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7148910</guid><dc:creator>Aitor Ibarra</dc:creator><description>&lt;p&gt;Ben,&lt;/p&gt;
&lt;p&gt;Thanks for this great post! It was great to find that in AzMan you can also edit / define roles; e.g. I edited the &amp;quot;user&amp;quot; role so that users could pause VMs very easily. And I like that changes in AzMan seem to be reflected immediately in Hyper-V admin, so it must be checking permissions before every operation.&lt;/p&gt;
&lt;p&gt;I don't suppose you could show us how to restrict control of specific VMs to specific users/groups?&lt;/p&gt;
&lt;p&gt;cheers,&lt;/p&gt;
&lt;p&gt;Aitor&lt;/p&gt;
</description></item><item><title>re: Allowing non-Administrators to control Hyper-V</title><link>http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/17/allowing-non-administrators-to-control-hyper-v.aspx#7151201</link><pubDate>Fri, 18 Jan 2008 20:44:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7151201</guid><dc:creator>Aitor Ibarra</dc:creator><description>&lt;p&gt;follow up on restricting users to particular VMs: I can see how to create new scopes, and give users rights in the scope, but not how to associate VMs with particular scopes. Is this what the Authorization Rules are for? If so, as they are scripts, looks like it could be very flexible (e.g. it might be possible to write a rule that allowed users in a particular role access to all VMs with names containing &amp;quot;Sales&amp;quot;). But to be honest, I think most users would find it easier if, having defined the scope in AzMan, scope membership of a VM could be set as part of the VM settings in the Hyper-V manager.&lt;/p&gt;
</description></item><item><title>re: Allowing non-Administrators to control Hyper-V</title><link>http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/17/allowing-non-administrators-to-control-hyper-v.aspx#7152435</link><pubDate>Fri, 18 Jan 2008 22:49:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7152435</guid><dc:creator>Wesley</dc:creator><description>&lt;p&gt;Ben, I hope that you are writing all of this in a way that leads to future publication. How about sections on using legacy software in Hyper-V with sections on optimizing DOS networks, evaluating physical video adapters for use with VMs, etc. I was at my doctors office last week and he had a portable PC with a VM and some old database he continues to use that his var can not port.&lt;/p&gt;
</description></item><item><title>re: Allowing non-Administrators to control Hyper-V</title><link>http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/17/allowing-non-administrators-to-control-hyper-v.aspx#7692717</link><pubDate>Thu, 14 Feb 2008 16:40:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7692717</guid><dc:creator>Marko Jagodic</dc:creator><description>&lt;p&gt;If users use full version of win 2008 to manage VMs located on server 2008 core, what rights (permissions) they need to have on core system?&lt;/p&gt;
&lt;p&gt;Just adding their domain account in InitalStore does'n work. They still cannot manage VMs due to authorization issues...&lt;/p&gt;
&lt;p&gt;If we are using WMI, what permission must be granted in order to execute script?&lt;/p&gt;
</description></item></channel></rss>