PSHyperv Release Rss Feed

Updated Release: R2 SP1 (Mar 19, 2011)

jamesone — Fri, 15 Apr 2011 21:44:17 GMT

Before Downloading
When you download a Zip it is flagged as coming from the internet. You should go to file properties and remove the block on the file before Unzipping it and using the the contents. If you don't do this PowerShell's execution policy will block the files unless you set it to "bypass. "
There is a cmd file to configure the library, please run this from a command prompt not from explorer.

The R2 "Gold" version has been stable for just over a year.
In SP1 I have fixed the bugs I was notified of , and more which I found. The help files contained numerous errors which have been fixed, although I daresay a few remain.
The final changes are still being made to the documentation the previous version is still available.
I have introduced support for script blocks in a few places where I could see it would make sense, So for example, you can pipe VMs into Add-VMDisk, and use an code block to turn the VM names into VHD names.
I have added support to Ping-VM for the IP address which is now sent back from the VM by the Key/Value Pair integration components
I have also added support for the RemoteFX graphics controllers introduced in SP1 and , last but not least
Set-VMmemory and handling of the memory settings WMI object now support dynamic memory.

When I have tested the download process works sucessfully this message will be removed and this release will be made the default.

Released: R2 SP1 (Mar 19, 2011)

Fri, 15 Apr 2011 21:44:17 GMT

Updated Release: R2 SP1 (Mar 19, 2011)

JAMESONE — Sun, 20 Mar 2011 00:22:16 GMT

Before Downloading
When you download a Zip it is flagged as coming from the internet. You should go to file properties and remove the block on the file before Unzipping it and using the the contents. If you don't do this PowerShell's execution policy will block the files unless you set it to "bypass. "

The R2 "Gold" version has been stable for just over a year.
In SP1 I have fixed the bugs I was notified of , and more which I found. The help files contained numerous errors which have been fixed, although I daresay a few remain.
I have introduced support for script blocks in a few places where I could see it would make sense, So for example, you can pipe VMs into Add-VMDisk, and use an code block to turn the VM names into VHD names.
I have added support to Ping-VM for the IP address which is now sent back from the VM by the Key/Value Pair integration components
I have also added support for the RemoteFX graphics controllers introduced in SP1 and , last but not least
Set-VMmemory and handling of the memory settings WMI object now support dynamic memory.

When I have tested the download process works sucessfully this message will be removed and this release will be made the default.

Released: R2 SP1 (Mar 19, 2011)

Sun, 20 Mar 2011 00:22:16 GMT

Before Downloading
When you download a Zip it is flagged as coming from the internet. You should go to file properties and remove the block on the file before Unzipping it and using the the contents. If you don't do this PowerShell's execution policy will block the files unless you set it to "bypass. "

The R2 "Gold" version has been stable for just over a year.
In SP1 I have fixed the bugs I was notified of , and more which I found. The help files contained numerous errors which have been fixed, although I daresay a few remain.
I have introduced support for script blocks in a few places where I could see it would make sense, So for example, you can pipe VMs into Add-VMDisk, and use an code block to turn the VM names into VHD names.
I have added support to Ping-VM for the IP address which is now sent back from the VM by the Key/Value Pair integration components
I have also added support for the RemoteFX graphics controllers introduced in SP1 and , last but not least
Set-VMmemory and handling of the memory settings WMI object now support dynamic memory.

When I have tested the download process works sucessfully this message will be removed and this release will be made the default.

Created Release: R2 SP1

JAMESONE — Sun, 20 Mar 2011 00:20:27 GMT

Before Downloading
When you download a Zip it is flagged as coming from the internet. You should go to file properties and remove the block on the file before Unzipping it and using the the contents. If you don't do this PowerShell's execution policy will block the files unless you set it to "bypass. "

The R2 "Gold" version has been stable for just over a year.
In SP1 I have fixed the bugs I was notified of , and more which I found. The help files contained numerous errors which have been fixed, although I daresay a few remain.
I have introduced support for script blocks in a few places where I could see it would make sense, So for example, you can pipe VMs into Add-VMDisk, and use an code block to turn the VM names into VHD names.
I have added support to Ping-VM for the IP address which is now sent back from the VM by the Key/Value Pair integration components
I have also added support for the RemoteFX graphics controllers introduced in SP1 and , last but not least
Set-VMmemory and handling of the memory settings WMI object now support dynamic memory.

When I have tested the download process works sucessfully this message will be removed and this release will be made the default.

Updated Release: R2 Gold (Jan 18, 2010)

jamesone — Mon, 18 Jan 2010 19:54:04 GMT

Release Notes
This update from the RC version contains more changes than would be normal , hence it is designated as "Gold" rather than "release". I expect there to be corrections to the on-line help text.

This release was produced to exploit PowerShell V2 and as a PowerShell module it will not run on v1 If you are running an R2 server OS, or are doing remote management from Windows 7 then you have PowerShell V2. If you are running on "Classic" 2008, you will need to upgrade the supplied PowerShell V1 to V2 or stick to V1 of the library

From any computer which runs PowerShell Version 2, the Module will manage remotely or locally manage "classic" or R2 versions of Hyper-V. It can be installed on servers, and in R2, Core installations and Hyper-V server support PowerShell.
Changes for "2"
*Online help
*Support for localization (only English is provided, but there is a single place to make changes to support other languages)
*Menu system similar to the PowerShell configurator
*Support for -whatif -confirm -verbose -force switches throughout.
*Improved flexibility with parameters and piping of data.
*Functions use standardized PowerShell verbs with aliases to provide backwards compatibility.

Since the RC stage I have added
*Support for PowerShell remoting
*Support for clustering

Thanks to the people who helped out with this release, too many to mention but I will single out Mike Kolitz as the person who has given most help.

With V1 people who were new to PowerShell asked a number of questions which are covered in the documentation, (how to load the functions), so please have a look at it. If you have checked the documentation and are stuck, or you get an error that you think you shouldn't or want to improve something please say so+. Your feed back is still wanted. I've created a thread on the issue tracker for typing and spelling errors in V2 Messages, help and documentation.

One final request. I work as an evangelist for Microsoft, not a developer. This project has been done with some "work" time and some "personal" time; because it stems from my employment the copyright in it belongs to Microsoft but it is licensed in way that gives you the maximum amount of freedom. If you using it has made you feel more positive about Hyper-V , PowerShell or Microsoft in general, or you have used it in an interesting project then a quick mail to me so I can show people it was worth doing would be appreciated.

Released: R2 Gold (Jan 18, 2010)

Mon, 18 Jan 2010 19:54:04 GMT

Updated Release: R2 Release candidate2 (Oct 29, 2009)

jamesone — Mon, 18 Jan 2010 19:46:22 GMT

The code was updated to RC2 on December 8th. Changes are very minor.

This release was produced to exploit PowerShell V2 and as a PowerShell module it will not run on v1 If you are running and R2 server OS, or are doing remote management from Windows 7 then you have PowerShell V2. If you are running on "Classic" 2008, you will need to upgrade the supplied PowerShell V1 to V2 or stick to V1 of the library

From any computer which runs PowerShell Version 2, the Module will manage remotely or locally manage "classic" or R2 versions of Hyper-V. It can be installed on servers, and in R2, Core installations and Hyper-V server support PowerShell.
Changes for "2"
*Online help
*Support for localization (only English is provided, but there is a single place to make changes to support other languages)
*Menu system similar to the PowerShell configurator
*Support for -whatif -confirm -verbose -force switches throughout.
*Improved flexibility with parameters and piping of data.
*Functions use standardized PowerShell verbs with aliases to provide backwards compatibility.

Thanks to the people who helped out with this release, too many to mention but I will single out Mike Kolitz as the person who has given most help.

With V1 people who were new to PowerShell asked a number of questions which are covered in the documentation, (how to load the functions), so please have a look at it. If you have checked the documentation and are stuck, or you get an error that you think you shouldn't or want to improve something But please say so+. This build is designated a release candidate so your feed back is still wanted. I've created a thread on the issue tracker for typing and spelling errors in V2 Messages, help and documentation. The current download is built from 30382 in the source tree. The documentation was built for an earlier release and needs some updates.

One final request. I work as an evangelist for Microsoft, not a developer. This project has been done with some "work" time and some "personal" time; because it stems from my employment the copyright in it belongs to Microsoft but it is licensed in way that gives you the maximum amount of freedom. If you using it has made you feel more positive about Hyper-V , PowerShell or Microsoft in general, or you have used it in an interesting project then a quick mail to me so I can show people it was worth doing would be appreciated.

Released: R2 Release candidate2 (Oct 29, 2009)

Mon, 18 Jan 2010 19:46:22 GMT

Updated Release: R2 Gold (Jan 18, 2010)

jamesone — Mon, 18 Jan 2010 18:16:51 GMT

Released: R2 Gold (Jan 18, 2010)

Mon, 18 Jan 2010 18:16:51 GMT

Updated Release: R2 Gold (Jan 14, 2010)

jamesone — Mon, 18 Jan 2010 18:15:52 GMT

Updated Release: R2 Gold (Jan 14, 2010)

jamesone — Mon, 18 Jan 2010 18:10:06 GMT

Created Release: R2 Gold (Jan 14, 2010)

jamesone — Fri, 15 Jan 2010 01:47:43 GMT

Released: R2 Gold (Jan 14, 2010)

Fri, 15 Jan 2010 01:47:43 GMT

Updated Release: R2 Release candidate2 (Oct 29, 2009)

jamesone — Tue, 08 Dec 2009 23:49:02 GMT

Released: R2 Release candidate2 (Oct 29, 2009)

Tue, 08 Dec 2009 23:49:02 GMT

Updated Release: R2 Release candidate (Oct 29, 2009)

jamesone — Tue, 08 Dec 2009 23:48:40 GMT

Updated Release: R2 Release candidate (Oct 29, 2009)

jamesone — Sun, 01 Nov 2009 00:16:46 GMT

This release was produced to exploit PowerShell V2 and as a PowerShell module it will not run on v1 If you are running and R2 server OS, or are doing remote management from Windows 7 then you have PowerShell V2. If you are running on "Classic" 2008, you will need to upgrade the supplied PowerShell V1 to V2 or stick to V1 of the library

From any computer which runs PowerShell Version 2, the Module will manage remotely or locally manage "classic" or R2 versions of Hyper-V. It can be installed on servers, and in R2, Core installations and Hyper-V server support PowerShell.
Changes for "2"
*Online help
*Support for localization (only English is provided, but there is a single place to make changes to support other languages)
*Menu system similar to the PowerShell configurator
*Support for -whatif -confirm -verbose -force switches throughout.
*Improved flexibility with parameters and piping of data.
*Functions use standardized PowerShell verbs with aliases to provide backwards compatibility.

Thanks to the people who helped out with this release, too many to mention but I will single out Mike Kolitz as the person who has given most help.

With V1 people who were new to PowerShell asked a number of questions which are covered in the documentation, (how to load the functions), so please have a look at it. If you have checked the documentation and are stuck, or you get an error that you think you shouldn't or want to improve something But please say so+. This build is designated a release candidate so your feed back is still wanted. I've created a thread on the issue tracker for typing and spelling errors in V2 Messages, help and documentation. The current download is built from 30382 in the source tree. The documentation was built for an earlier release and needs some updates.

One final request. I work as an evangelist for Microsoft, not a developer. This project has been done with some "work" time and some "personal" time; because it stems from my employment the copyright in it belongs to Microsoft but it is licensed in way that gives you the maximum amount of freedom. If you using it has made you feel more positive about Hyper-V , PowerShell or Microsoft in general, or you have used it in an interesting project then a quick mail to me so I can show people it was worth doing would be appreciated.

Released: R2 Release candidate (Oct 29, 2009)

Sun, 01 Nov 2009 00:16:46 GMT