Automating the world one-liner at a time…
We hope that you’ve been enjoying all of the great new Windows PowerShell 3.0 features in Windows Server 2012. We wanted to make sure that everyone knows the final release of Windows Management Framework 3.0 is also available for download from the Microsoft Download Center.
Windows Management Framework 3.0 makes much of the same great management functionality from Windows Server 2012 available to earlier versions of Windows. Windows Management Framework 3.0 allows you to install Windows PowerShell 3.0 (including a new version of WMI and WinRM) on the following Operating Systems:
Note: You must uninstall any of the pre-release packages of Windows Management Framework prior to installing the final release.
Travis Jones [MSFT] Program Manager – Windows PowerShell Microsoft Corporation
I still have customers on XP and Vista. If I install WMF 3.0 on my development PC, are there any safeguards against developing scripts using features of 3.0 that won't work in Powershell v2?
Are there any plans to make WMF 3.0 available on XP and Vista?
For completeness, it's probably worth noting in this post that Windows 8 includes PowerShell 3.0 as well, even though it's mostly implied by its exclusion from the downlevel list provided :)
Is it possible to install the new Windows 8 PS Modules (technet.microsoft.com/.../hh801904.aspx) too on older Windows versions?
Let me just ask one very important question: Where is all these new modules and cmdlets in powershell 3, installed in windows 7, server 2008R2? When I type get-module -listavailable there is no new modules such as DHCP, NetTCPIP and others.
What about regional/localized versions? What do we have to do? Install english version , wait for localized version, the uninstall, and re-install localized version? Or do we have to install the english version and then update only the commandline version of the help file using update-help ? Is there any chm or visual help file except for the powershell one?
Hi Wayne - There are no plans for making WMF 3.0 available on Windows XP or Windows Vista. The PowerShell Language between V2 and V3 is largely backwards compatible. You won't be able to write things like workflow, or use PS 3.0 simplified syntax for foreach-object and where-object if you want the scripts to run on Windows PowerShell 2.0. If you do want to verify compatibility before sending to your customers that are using Windows PowerShell 2.0, you can test them on your machine by running the following command: "powershell.exe -version 2". This will load the Windows PowerShell 2.0 Engine on a machine that has Windows PowerShell 3.0 installed.
Hope this helps.
Travis Jones [MSFT]
Hi James - You are absolutely correct. Windows PowerShell 3.0 is installed on Windows 8 and Windows Server 2012 by default. The package described in this blog post is strictly to bring Windows PowerShell 3.0 down to previous versions of Windows. Thanks for pointing this out!
When writing scripts/functions for Windows PowerShell 2.0, use the Windows PowerShell 2.0 option in WMF 3.0. To start Windows PowerShell 2.0, type: powershell -version 2. To confirm, type $psversiontable.psversion.major. The return value should be 2.
Because Windows PowerShell supports CLR 4.0 and .NET 4 and 4.5, we cannot backport it to Windows XP or Vista.
June Blender [MSFT]
Senior Programming Writer
Hi Tom -
The new modules listed there are only included as part of the roles/features that ship with Windows Server 2012, and in some cases they are also available on Windows 8. Unfortunately, they cannot be installed on previous versions of Windows.
Hi Alex -
I believe the answer just provided to Tom also covers your question.
That's great news. I could install the Windows Management Framework 3.0 on my German Windows 7 64 Bit within a couple of minutes and without any problems. Except that Update-Help still doesn't seem to work.
Hi, Gina. Travis has asked me to jump in here to answer your questions.
WMF 3.0 is already localized. It installs on localized versions of Windows and includes support for all Windows Server locales. So, no, you do not need to install an English version. After installing WMF 3.0, you should see user messages in the locale set for Windows. Of course, cmdlet names, parameter names, are not localized.
Help is different. Updatable Help is designed for multi-language support. However, the Help topics for Windows Server modules are available only in English right now.
When you run Update-Help, it looks for help in the locale set for Windows. If it doesn't find it, it looks for a parent language (e.g. de for de-de), and then a fallback language. For now, you'll get only English. When help becomes available in other languages, the Update-Help command will download and install them automatically.
We're now collecting data to determine which languages/locales PowerShell users really want and need. To supplement the research that our international affiliates are coordinating, users can request help for a particular language or locale on Connect (connect.microsoft.com/PowerShell). Please search for the language name (i.e. German, Arabic, Portuguese, Polish) in the bug title and vote for the language that you want.
In addition to Updatable Help, you can read help online in the TechNet Library (Get-Help -Online). You can also use the "build-a-book" or "Print Multiple Topics" feature of TechNet to create a PDF of a custom collection of topics. However, if you do this, please remember that our help topics are updated every day and your PDF will become outdated over time.
June Blender (juneb) [MSFT]
I have been working hard with your script to clone VM's and I have failed to add a very simple requirement: that the new VM gets started after is finished cloning it. I tried to add Sart-VM right before "$a ++"
but the script fails. I guess that this part gets executed while the importing is not yet done.
How would you change the script to clone and start a VM?
I can be reached is v e n e f a x at g m a i l
I truly appreciate your help
So the "2500+" cmdlets that I have been so excited about for the past few months are only available on Sever 2012 or Windows 8? ... are there any modules not tied to Roles and Features on the new Operating Systems that can be installed on Win7?
powershell 3.0 Lost half module in windows7!
i install .net4.5,then install powershell 3.0 from windows7-sp1,
but found it less some moudles than windows 8
Running environments are the same, but less than half moudles , why?
a Simple cmdlets(function) "Get-NetIPAddress",windows8 have but can not run in windwos7,it's right ?
powershell 3.0 in windows 7 is Semi-finished products!
powershell 3.0 in windows 8 is full version.