<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Scripting Hyper-V with WMI and PowerShell: Part 1 – Introduction + Querying State</title><link>http://blogs.technet.com/benp/archive/2008/08/11/scripting-hyper-v-with-wmi-and-powershell-part-1-introduction-querying-state.aspx</link><description>Scripting Hyper-V with WMI and PowerShell Part 1 – Introduction + Querying State Introduction When it comes to scripting Hyper-V there are really 2 methods: 1. Using the virtualization WMI provider that ships with Hyper-V. 2. Using the cmdlets provided</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Programming Hyper-V with WMI and C# - Getting Started</title><link>http://blogs.technet.com/benp/archive/2008/08/11/scripting-hyper-v-with-wmi-and-powershell-part-1-introduction-querying-state.aspx#3103573</link><pubDate>Mon, 11 Aug 2008 21:44:56 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3103573</guid><dc:creator>Richard's Weblog</dc:creator><description>&lt;p&gt;You may have seen from a recent post that I received a new laptop that was capable of running Hyper-V.&lt;/p&gt;
</description></item></channel></rss>