Windows PowerShell
Windows PowerShell is a task-based command-line shell and scripting language designed especially for system administration. Built on the .NET Framework, Windows PowerShell helps IT professionals and power users control and automate the administration of the Windows operating system and applications that run on Windows.Windows PowerShell allows you to run scripts, functions, and modules of cmdlets. Cmdlets are simple verb-noun commands that help you automate management of roles and features that run on the Windows operating system.
After you install WMF 4.0, Windows PowerShell is upgraded to version 4.0.
Windows6.1-KB2819745-x64-MultiPkg.msu [18.4 MB]
Windows6.1-KB2819745-x86-MultiPkg.msu [14.1 MB]
Windows8-RT-KB2799888-x64.msu [17.5 MB]
New Features, functionality and updates included in this new WMF 4.0
- Windows PowerShell
- Windows PowerShell Integrated Scripting Environment (ISE)
- Windows PowerShell Web Services (Management OData IIS Extension)
- Windows Remote Management (WinRM)
- Windows Management Infrastructure (WMI)
- Windows PowerShell Desired State Configuration (DSC)
Supported Operating System
IMPORTANT: your system requires .NET Framework 4.5- Windows 7 SP1
- x64: Windows6.1-KB2819745-x64-MultiPkg.msu
- x86: Windows6.1-KB2819745-x86.msu
- Windows Server 2008 R2 SP1
- x64: Windows6.1-KB2819745-x64-MultiPkg.msu
- Windows Server 2012
- x64: Windows8-RT-KB2799888-x64.msu
- and Windows Embedded 7
This package is not compatible with the following server applications
- System Center 2012 Configuration Manager (not including SP1)
- System Center Virtual Machine Manager 2008 R2 (including SP1)
- Microsoft Exchange Server 2007, 2010 and 2013
- Microsoft SharePoint 2013 and Microsoft SharePoint 2010
- Windows Small Business Server 2011 Standard
Along with this package, the PowerShell team released a couple of interesting document
- Windows Management Framework 4.0 Release Notes.docx [89KB]
- Desired State Configuration Quick Reference for Windows Management Framework 4.0.pdf [244KB]
- Desired State Configuration Quick Reference for Windows Management Framework 4.0.pptx [73KB]
Some of the new features in Windows PowerShell 4.0 include
- Support for workflow and remote script debugging
- Improved workflow authoring experience to make it more consistent with script authoring
- Added PipelineVariable as a common parameter
- Better support for downloading updatable help by using Save-Help and Update-Help in offline scenarios
- Updated version from 3.0 to 4.0
- Several bug fixes and performance improvements
Windows PowerShell ISE in Windows Management Framework 4.0 introduces
- Support for Windows PowerShell Workflow debugging
- Support for remote script debugging
- IntelliSense support for Windows PowerShell Desired State Configuration resources and configurations
Windows PowerShell Web Services (Management OData IIS Extension)
enables an administrator to expose a set of Windows PowerShell cmdlets as a RESTful web endpoint accessible by using OData (Open Data Protocol). This provides remote access to run cmdlets from both Windows-based and non-Windows-based client computers or devices.- Improved error messages in event logs
- Endpoint versioning support
- Autopopulation of OData dispatch schema fields
- Support for complex types
- Multilevel association support
- Ability to perform large binary stream transfers
- Support for non-Create/Read/Update/Delete (CRUD) actions
- Key-As-Segment URL syntax support
- Constrained resource operations
Windows PowerShell Desired State Configuration (DSC)
Windows Management Framework 4.0 introduces Windows PowerShell Desired State Configuration (DSC), with the following highlights:- Local configuration manager for applying configurations on the local computer
- Windows PowerShell language extensions for authoring DSC documents
- PSDesiredStateConfiguration module and DSC-related cmdlets
- A set of built-in DSC configuration resources
- DSC service for distributed access to DSC resources
KNOWN ISSUE: PARTIAL INSTALLATION WITHOUT .NET FRAMEWORK 4.5
When you attempt to install WMF 4.0 on Windows 7 or Windows Server 2008 R2 without .NET Framework 4.5, only the prerequisite QFEs that are included in the package are installed. The installation process attempts to install WMF 4.0, but fails. The two prerequisite QFEs remain on the computer after WMF 4.0 installation fails.
To repair your WMF 4.0 installation after this failure, install .NET Framework 4.5, and then run the WMF 4.0 MSU installation package again to install WMF 4.0. The installation process skips the QFEs, and installs WMF 4.0.
Finally... Don't forget to do Update-Help
Update-Help -Verbose -Force
Thanks for Reading! If you have any questions, leave a comment or send me an email at fxcat@lazywinadmin.com. I invite you to follow me on Twitter @lazywinadm / Google+ / LinkedIn You can also follow the LazyWinAdmin Blog on Facebook Page and Google+ Page
Excellent entry, FX! Very informative. I would have put 'Important: your system requires .NET Framework 4.5' and 'KNOWN ISSUE: PARTIAL INSTALLATION WITHOUT .NET FRAMEWORK 4.5'in big red capital letters, since many people don't notice it (did that mistake myself: http://www.happysysadm.com/2013/08/how-to-upgrade-windows-2008-r2-sp1-to.html).
ReplyDeleteCarlo
Thanks for your comment Carlo! Appreciated! I will update the post and try to make it more noticeable ;-)
Deletesaving the help files and moving them to the offline servers most of us use in finance world is a big deal ... Save-Help
ReplyDeletehttp://technet.microsoft.com/en-us/library/hh849720.asp
I will post shortly what I did to get my help files to my off line server: I'm sure Xavier will make this look much better :P since this is the best help file I found so far on this topic lol.