Automating the world one-liner at a time…
Windows Management Framework 3.0 CTP1 makes some updated management functionality available to be installed on Windows 7 SP1 & Windows Server 2008 R2 SP1. Windows Management Framework 3.0 contains Windows PowerShell 3.0, WMI & WinRM.
Windows PowerShell 3.0 Some of the new features in Windows PowerShell 3.0 include:
WMI WMI in Windows Management Framework 3.0 CTP1 introduces:
WinRM With Windows Management Framework 3.0 CTP1:
Windows PowerShell Web Service Windows PowerShell Web Service enables an administrator to expose a set of PowerShell cmdlets as a RESTful web endpoint accessible via the Open Data Protocol (OData). This provides remote access to invoke cmdlets from both Windows and non-Windows clients.
Windows Management Framework 3.0 CTP1 can be installed on the following supported operating systems:
Windows PowerShell 3.0 requires version 4.0 of the common language runtime (CLR). CLR 4.0 is includes with the Microsoft .NET Framework version 4.0.
To install WMF 3.0 CTP1:
To uninstall the WMF 3.0 CTP1:
Locate and uninstall the following installed Windows Update: KB2506143
This software is a pre-release version. Features and behavior are likely to change before the final release.
This preview release is designed to enable the community to experience and review the preliminary designs and direction of key features Windows PowerShell 3.0 and to solicit feedback before features are finalized.
Travis Jones Windows PowerShell PM Microsoft Corporation
Why do you support only the latest OS? Windows Vista is just a generation older and still in mainstream support yet Microsoft treats Vista customers badly because it wasn't so successful. Please support VIsta SP2.
Is there an other way to give feedback to the powershell team unlike commentating this news?
Unfortunately it's not included in the Microsoft Connect program
Simple question: will 3.0 RTM support XP and Vista, just like 2.0 does?
I'd have thought 3.0 was the time to add the long missing "Print..." feature to the ISE. Sigh ;-(
There's a suggestion on Connect:
Vote it up :)
Are you going to have blog posts here explaining and outlinging the new features? Kind of pointless to release a CTP if you don't follow up with explanations of what is new, right?
I hope everyone is enjoying the packge so far... Here are some answers to the questions I see in the comments so far.
How does this build compare to the one in Developer Preview? - Almost identical
The Help Content that is packaged in the CTP1 can be applied to the Developer Preview. Just use Update-Help -SourcePath <location of help content>
Windows PowerShell Web Service - This is really called the Management OData Web Services. A whitepaper and link to SDK samples are here archive.msdn.microsoft.com/mgmtODataWebServ
The PowerShell V2 engine is in fact deployed with the WMF3.0 CTP1. To use it, run powershell.exe -version 2.0
You can read the release notes without instalilng the CTP. Simply extract the CAB file and find the file named "WMF CTP1 Release Notes". To install the CTP you need to run the contained MSU. i.e., extracting the CAB alone does not install it.
We will be publishing a whitepaper similar to the one included for WMI & Management OData Web Services with more information on Workflows in the near future.
It does not install on non-English versions of Win7 SP1. To install on non-English OSes you will need to install the English Language Pack first.
For all feedback and bugs, Connect is the place: connect.microsoft.com/powershell. Remember to have people vote your suggestions up!
Most of the blogging will be on the Server & Cloud blog for now (blogs.technet.com/.../server-cloud). The samples and whitepapers included in the package are intended to get you started until we're able to open up completely.
Sneaky. Probably a good choice in the long run, but not the usual meaning of "side-by-side deployment". The engines are side-by-side, but the hosts are replaced with the new versions. It would be better to be clear about this in the README.
Another subtle gotcha I've noticed - the V3 console host defaults to STA, whereas the V2 one defaulted to MTA.
All in all, it is looking like a great release.
PowerShell team, I can understand about XP not supported but Vista is a current product and supporting WMF 3.0 only on the latest released OS is not right. When did Microsoft turn into Apple? Did Vista users pay MS any less than Windows 7? Windows VIsta is being ignored. Please clarify if WMF 3.0 RTM is going to supported on Windows Vista SP2.
Any PowerShell V3 Forums yet? Or is it just connect only?
Will the ISE support plug-ins? *I read about the WinRM plug-ins, but didn't see anything related to ISE extensibility.
Is there any documentation on updated self-hosting the PowerShell scripting environment? Will it change at all?
Would be really nice if ExpandoObject type objects had first class support. Meaning the "Virtual Members" were treated like first class properties as opposed to just a Key-Value collection. Also discussed on StackOverflow:
Quote: "In addition, the following requirements apply:
1.WMF 3.0 CTP2 can be installed only on English language operating systems. If you are using a non-English version of Windows, you must first install the English Language Pack "
How, if at all, can I install an english langauge pack? Is the a download available? Does it install on each WIN7 version ... if ... ? I've got a german version of WIN7 x64 Professional and HomePremium running.