“PowerShell 2.0 is built into Windows Server 2008 R2 and Windows 7. For older operating systems, PowerShell 2.0 is scheduled to be available a few months down the road and will include support for Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP1 and Windows Server 2008.”

We are responsible for the confusion because our redistribution is not called PowerShell V2, its called Windows Management Framework. Let’s talk about what motivated that change. In the past, we had a dogs breakfast of management technologies, each releasing on it’s own schedule with it’s own installer, it own approach to supporting downlevel OSes etc. We were trying “shipping our organization”. What is worse is that we never had anyone making sure that these things worked together (they did but if they didn’t, there was no one to hold accountable). Having spent the majority of my career building management products and solutions, I knew that this inconsistency was a problem for the very community we were trying to help.

What we needed to do is to provide a single package with all the management technologies that customers needed. That is what we developed and we called it the Windows Management Framework.

That is why you don’t have a “downlevel package for PowerShell V2”, you have a downlevel package for management.

If by package you mean name and single referenced location, then you have that. If you mean package as in single install source then no, you do not have that, you have 2.

Are there plans to add this to Windows Update in the future?

Timothy Clethan

15 May 2010 2:16 PM

It was a mistake. It just makes it harder to find it, to talk to other people about it, and to understand what's in the package. Not everything has to be a "framework" or a "suite" or a "system" or have a "rich user experience". Ugh.