Remotely controlling Hyper-V VM

Feb 25, 2009 at 9:52 PM
The scripts work brilliantly on Windows 2008 with Hyper-V role enabled.

But I need to control the VMs from a remote machine. Invoking the scripts on Windows 2003 (SP2) gives an error that the WMI virtualization provider was not found. Does the WMI virtualization provider come only with Windows 2008? Is there anyway I can use these scripts from Windows 2003/Vista?

Also, will these scripts work for Hyper-V Server 2008 (the bare metal version)?

Feb 25, 2009 at 10:26 PM
This maybe a bug in the script. I think in some places where Get-WMIObject is called the -ComputerName parameter is not specified and therefore it tries to connect to the local machine (which is Windows 2003) and therefore doesn't find the virtualization WMI provider.

Mar 16, 2009 at 3:36 PM
If you know of places where -computerName is missing please let me know - I thought I had found all the places where this problem occurred some time ago.