Automating the world one-liner at a time…
Windows 7 and Windows Server 2008 R2 have been released to manufacturing. Both of these products include Windows PowerShell 2.0 and its exciting new features, such as remoting, ISE, modules, advanced functions, enhanced WMI support, and a variety of new cmdlets, plus a ton of other features. We are proud of this release.
We thank the PowerShell community, specially our MVPs, for helping us to make a great product.
In the next few months, we will release a downlevel package for installing Windows PowerShell 2.0 on Windows XP SP3, Windows 2003 SP2, Windows Vista-SP1 and Windows Server 2008.
Osama Sajid, Program Manager
[Update: Win2k3-SP2 was missed in the original post - thanks Dmitry/Ken]
Thanks I look forward to it. I am assuming that PowerShell v1 scripts will continue to work as is without modification in the V2 environment?
There may be some minor things that won't work in v2.
Whatever breaking changes there are, they should be available in the release notes that should accompany the v2 install (or be available as a seperate download).
The intent was to make everything backwards compatible.
There is actually already some information available on this blog as well as if you check the v2 CTP3 download information.
I believe Exchange 2007 SP2 will be required for PowerShell v2 support.
Why can't you guys release PowerShell 2.0 NOW for Windows XP SP3?
Congratulations for RTMing PowerShell 2.0!
Congratulations PS team! I look forward to the downlevel package when it releases.
C'mon now. Let's give this time to bake. I'd rather have a working release on my XP SP3 machine than garbage.
@ David Moisan,
Exchange 2007 won't be update to run on 2008 R2:
Where can I get the Powershell 2.0 RTM? Do I have to wait for Windows 7 release?
Everybody had said what I wanted to say! So I just add that "in a couple of months" means "PowerShell 2.0 RTM will be released in a couple of months"! I mean PowerShell 2.0 is not actually RTMed.
Ofcourse this is not taking your efforts easy! For that part I really appreciate and admire PowerShell team.
@ Saptagiri Tangudu,
Yes, you need to get Windows 7 or Server 2008 R2 to get v2. That will be the quickest way.
An installer will be released for the others OSs after.
@ Kaveh Shahbazian,
Yes, it can be confusing, v2 has RTMd, now that's different than Release To Web like PowerShell v1 originally was.
v2 will be out first on Windows 7/Server 2008 R2, then for others later...
Can you explain why it will be a few months before v2 is released for XP, Vista, and 2003? Are you holding back intentionally or does it really take you that long to create an installer?
It's Microsoft's prerogative either way, but why not provide the explanation that you know everyone wants?
Gah! Need to dry hump Powershell 2.0!
My unofficial guess, the priorities were on developing and testing v2 on the latest OS release.
I did an upgrade from Vista Ultimate to Windows 7 Ultimate (x64 versions). I had the PowerShell v2 CTP3 installed on Vista before I did the upgrade. How do I know if I now have the PowerShell v2 RTM version? Programs and Features still shows the PowerShell v2 CTP3 installed...
v2 is NOT in the RTM for Win7. I am running it currently, downloaded from MSDN the day it came out. PS v2 is NOT installed, it is v1 that is released with Win7. VERY DISAPPOINTING.