More on the accessing the Hyper-V API from Powershellhttp://blogs.technet.com/jamesone/archive/2008/04/19/more-on-the-accessing-the-hyper-v-api-from-powershell.aspx... In which we find VMs, them choose one, start them, stop them , and connect to them. I spent more of the last week than I planned looking at Hyper-V and Powershell, and I'm getting dangerously close to calling myself an expert. There are two WMI objectsen-USCommunityServer 2.1 SP1 (Build: 61025.2)Console connect to a VM without opening the Hyper-V mmchttp://blogs.technet.com/jamesone/archive/2008/04/19/more-on-the-accessing-the-hyper-v-api-from-powershell.aspx#3039979Sun, 20 Apr 2008 01:15:26 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3039979Off Campus<p>It is possible open the Hyper-V console for an individual VM without opening the full mmc.&amp;#160; You</p> re: More on the accessing the Hyper-V API from Powershellhttp://blogs.technet.com/jamesone/archive/2008/04/19/more-on-the-accessing-the-hyper-v-api-from-powershell.aspx#3044582Fri, 25 Apr 2008 03:04:52 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3044582Ibrahim Abdul Rahim<p>Nice post.</p> <p>I can’t find where you get $VSMgtSvc from... and it seems to work better if you change $VSMgtSvc.SystemName to $vm.__SERVER</p> <p>Cheers,</p> <p>Ibrahim</p>re: More on the accessing the Hyper-V API from Powershellhttp://blogs.technet.com/jamesone/archive/2008/04/19/more-on-the-accessing-the-hyper-v-api-from-powershell.aspx#3044589Fri, 25 Apr 2008 03:31:31 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3044589jamesone<p>Ibrahim, sorry I should have said that $vsMgtSvc = Get-wmiObject -nameSpace root\virtualization -class Msvm_virtualSystemManagementService </p> <p>__server is the name of the machine where the WMI command executed and </p> <p>$VsMgtSvc.SystemName is the name of the hyper-V machine. In practice they will usually be the same. </p> Hyper-v and Snapshots (Part 1)http://blogs.technet.com/jamesone/archive/2008/04/19/more-on-the-accessing-the-hyper-v-api-from-powershell.aspx#3048791Fri, 02 May 2008 20:40:07 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3048791James O'Neill's blog <p>The machine is running quite happily and has never been snapped. Late on Monday make a snapshot. This</p> Hyper-v Snapshots part 2.http://blogs.technet.com/jamesone/archive/2008/04/19/more-on-the-accessing-the-hyper-v-api-from-powershell.aspx#3049216Sat, 03 May 2008 14:44:32 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3049216James O'Neill's blog <p>In my last post I explained how snapshots work and gave a little bit of PowerShell for creating a one</p> More on the Hyper-V APIhttp://blogs.technet.com/jamesone/archive/2008/04/19/more-on-the-accessing-the-hyper-v-api-from-powershell.aspx#3053668Sun, 11 May 2008 16:02:21 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3053668James O'Neill's blog <p>In which we see how to set the number of CPUs I started with getting MSVM Computer System objects - which</p>