Windows Management Framework (WMF) 4.0 New Powershell Features Overview
Feb 28, 2014

Powershell …. what more do I need to say?

You need it, you gotta have it, and if you are not already using it to manage your infrastructure, you are behind the times. Having said all that, lets take a look at what your future looks like with Powershell 4.0.

Microsoft has released Windows Management Framework 4.0 which enables you to use management technologies available in Windows 8.1 and Windows Server 2012 R2 on some of Microsoft’s older operating systems. The latest release include more features and improvements compared to the previously released preview edition released in July. Windows Management Framework 4.0 include updated versions of Windows PowerShell, Windows PowerShell Integrated Scripting Environment (ISE), Windows PowerShell Web Services (Management OData IIS Extension), Windows Remote Management (WinRM) and Windows Management Infrastructure (WMI) in addition to Windows PowerShell Desired State Configuration (DSC).

Microsoft has also provided a set of release notes and additional quick reference guides which provide information about new features including list of known issues with their workarounds and known incompatibilities with other applications. Moreover, the release notes also provide necessary details for all possible issues and their possible solutions, which arise upon upgrading operating system from old to new version after the installation of Windows Management Framework 4.0 Windows Management Framework 4.0 can be installed on the following platforms except Windows 8.

  • Windows 7 with Service Pack 1 (SP1)
  • Windows Server 2008 R2 with SP1
  • Windows Server 2012
  • Windows Embedded 7

According to official sources, Windows 8.1 includes all the updated features and improvements included with WMF 4 and is available as a free update for Windows 8. Additionally, .NET Framework 4.5 is an essential requirement for the installation of WMF 4.

If you attempt to run the setup of Windows Management Framework 4.0 without .NET Framework 4.5 then the installation will be successful but the components of WMF 4.0 will not be updated.

Windows PowerShell 4.0 includes several significant features that extend its use, improve its usability, and allow you to control and manage Windows-based environments more easily and comprehensively.

Windows PowerShell 4.0 is backward-compatible. Cmdlets, providers, modules, snap-ins, scripts, functions, and profiles that were designed for Windows PowerShell 3.0 and Windows PowerShell 2.0 work in Windows PowerShell 4.0 without changes.

New features in Windows PowerShell

Windows PowerShell Desired State Configuration (DSC) is a new management system in Windows PowerShell 4.0 that enables the deployment and management of configuration data for software services and the environment in which these services run. For more information about DSC, see Get Started with Windows PowerShell Desired State Configuration. DSC uses script-based configuration files that you create using PowerShell ISE. These are converted into MOF files that are used to set or check the configuration of a server using the Start-DscConfiguration cmdlet. DSC is a big topic, and there are lots of cmdlets and configuration files to explore. You might want to start with this TechEd 2013 video.

Powershell 4 - Start-DscConfiguration


Save-Help now lets you save help for modules that are installed on remote computers. You can use Save-Help to download module Help from an Internet-connected client (on which not all of the modules for which you want help are necessarily installed), and then copy the saved Help to a remote shared folder or a remote computer that does not have Internet access.

The Windows PowerShell debugger has been enhanced to allow debugging of Windows PowerShell workflows, as well as scripts that are running on remote computers. Windows PowerShell workflows can now be debugged at the script level from either the Windows PowerShell command line or Windows PowerShell ISE. Windows PowerShell scripts, including script workflows, can now be debugged over remote sessions. Remote debugging sessions are preserved over Windows PowerShell remote sessions that are disconnected and then later reconnected.

Powershell 4 - Get Help Save Help


A RunNow parameter for Register-ScheduledJob and Set-ScheduledJob eliminates the need to set an immediate start date and time for jobs by using the Trigger parameter. PowerShell 4.0 adds the keyword parameter RunNow to make that task easier. Another new parameter for the New-JobTrigger and Set-JobTrigger cmdlets is RepeatIndefinitely for those jobs you want to start and run forever. This eliminates the necessity of specifying a TimeSpan.MaxValue value for the RepetitionDuration parameter to run a scheduled job repeatedly for an indefinite period.

 Powershell 4 - Set-ScheduledJob


Invoke-RestMethod and Invoke-WebRequest now let you set all headers by using the Headers parameter. Although this parameter has always existed, it was one of several parameters for the web cmdlets that resulted in exceptions or errors.

Get-Module has a new parameter, FullyQualifiedName, of the type ModuleSpecification[]. The FullyQualifiedName parameter of Get-Module now lets you specify a module by using the module’s name, version, and optionally, its GUID.

The default execution policy setting on Windows Server 2012 R2 is RemoteSigned. On Windows 8.1, there is no change in default setting.

Starting in Windows PowerShell 4.0, method invocation by using dynamic method names is supported.


This cmdlet was introduced in Windows Server 2012 and has been expanded in Windows Server 2012 R2 to add the Guest Service Interface parameter. This service is turned off by default and must be enabled either through the settings page in Hyper-V Manager for each VM of interest or by using a PowerShell command as in Enable-VMIntegrationService -Name “Guest Service Interface” “Baseline 2012 Server.”

Powershell 4 - Enable VMIntegrationService



Moving files into and out of virtual machines can be problematic. First you need to have the integration services installed and file sharing turned on. This requires only a single PowerShell command, Enable-VMIntegrationService. But then you have to log into the VM and copy the files to or from a network share. Now you only need to type the Copy-VMFile command in PowerShell. It works to copy files both into and out of a VM.

Powershell 4 - Copy-VMFile


Asynchronous workflow jobs are no longer deleted when the time-out period that is specified by the PSElapsedTimeoutSec workflow common parameter has elapsed.

A Passthru parameter has been added to the Enable-JobTrigger and Disable-JobTrigger cmdlets. The Passthru parameter displays any objects that are created or modified by your command.

The parameter names for specifying a workgroup in the Add-Computer and Remove-Computer cmdlets are now consistent. Both cmdlets now use the parameter WorkgroupName.

A new common parameter, PipelineVariable, has been added. PipelineVariable lets you save the results of a piped command (or part of a piped command) as a variable that can be passed through the remainder of the pipeline.

Collection filtering by using a method syntax is now supported.

The Get-Process cmdlet has a new switch parameter, IncludeUserName.

A new cmdlet, Get-FileHash, that gets information about file hashes, has been added. Put simply, the Get-FileHash cmdlet will compute a hash of any file or files you pass to it. You can even choose the algorithm used to compute the hash.

Powershell 4 - Get-FileHash


In Windows PowerShell 4.0, if a module uses the DefaultCommandPrefix key in its manifest, or if the user imports a module with the Prefix parameter, the ExportedCommands property of the module shows the commands in the module with the prefix. When you run the commands by using the module-qualified syntax, ModuleName\CommandName, the command names must include the prefix.

The value of $PSVersionTable.PSVersion has been updated to 4.0.

Where() operator behavior has changed. Collection.Where(‘property –match name’) accepting a string expression in the format “Property –CompareOperator Value” is no longer supported. However, the Where() operator accepts string expressions in the format of a scriptblock; this is still supported.



Get-NetNat is part of the NetNat module that also contains such commands as New-NetNat and Set-NetNat. This ability to configure Network Address Translation on remote machines is at the heart of Microsoft’s hybrid cloud strategy, where you can connect your on-premises machines to machines in the cloud, and they communicate as if they’re on the same LAN. These PowerShell commands make the creation and deletion of virtual NAT connections possible with the running of a simple script.

Powershell 4 - Get-NetNat



Troubleshooting network problems is without a doubt one of the most frustrating exercises an IT administrator must endure. Windows has traditionally provided very little in the way of built-in tools to make this task more bearable. With PowerShell 4.0, your network troubleshooting life just got a lot easier. The Test-NetConnection cmdlet combines a number of tests into one simple command plus a few parameters. For example, the command Test-NetConnection -ComputerName -InformationLevel Detailed would attempt to connect to the website and return a detailed list of diagnostic information.

Powershell 4 - Test-NetConnection



Virtual networking has been one of those areas that require a considerable amount of hands-on troubleshooting when things go wrong. Now you can run a series of tests on your virtual machine network adapter from the convenience of your PowerShell prompt.

Powershell 4 - Test-VMNetworkAdapter



Windows Server 2012 R2 Hyper-V introduces the concept of Generation 2 virtual machines. This completely new architecture includes BIOS firmware that can be updated or replaced entirely. You can use Get-VMFirmware to retrieve the BIOS firmware versions of specified VMs, and the Set-VMFirmware command to change the firmware.

 Powershell 4 - Get-VMFirmware


New features in Windows PowerShell Integrated Scripting Environment (ISE)

Windows PowerShell ISE supports both Windows PowerShell Workflow debugging and remote script debugging.

IntelliSense support has been added for Windows PowerShell Desired State Configuration providers and configurations.


New features in Windows PowerShell Workflow

Support has been added for a new PipelineVariable common parameter in the context of iterative pipelines, such as those used by System Center Orchestrator; that is, pipelines that run commands simply left-to-right, as opposed to interspersed running by using streaming.

Parameter binding has been significantly enhanced to work outside of tab completion scenarios, such as with commands that do not exist in the current runspace.

Support for custom container activities has been added to Windows PowerShell Workflow. If an activity parameter is of the types Activity, Activity[]—or is a generic collection of activities—and the user has supplied a script block as an argument, then Windows PowerShell Workflow converts the script block to XAML, as with normal Windows PowerShell script-to-workflow compilation.

After a crash, Windows PowerShell Workflow automatically reconnects to managed nodes.

You can now throttle Foreach -Parallel activity statements by using the ThrottleLimit property.

The ErrorAction common parameter has a new valid value, Suspend, that is exclusively for workflows.

A workflow endpoint now automatically closes if there are no active sessions, no in-progress jobs, and no pending jobs. This feature conserves resources on the computer that is acting as the workflow server, when the automatic closure conditions have been met.


New features in Windows PowerShell Web Services

When an error occurs in Windows PowerShell Web Services (PSWS, also called Management OData IIS Extension), while a cmdlet is running, more detailed error messages are returned to the caller. In addition, error codes follow Windows Azure REST API error code guidelines.

An endpoint can now define the API version, as well as enforce the usage of a specific API version. Whenever version mismatches occur between client and server, errors are displayed to both the client and the server.

Management of the dispatch schema has been simplified by automatically generating values for any missing fields in the schema. Generation occurs, as a helpful starting point, even if the dispatch schema does not exist.

Type handling in PSWS has been improved to support types that use a different constructor than the default constructor, by behaving similarly to the PSTypeConverter in Windows PowerShell. This lets you use complex types with PSWS.

PSWS now allows expanding an associated instance while running a query. For larger binary contents (such as images, audio, or video), the transfer cost is significant, and it is better to transfer binary data without encoding. PSWS uses named resource streams for transferring without encoding. The named resource stream is a property of an entity of the Edm.Stream type. Each named resource stream has a separate URI for GET or UPDATE operations.

OData actions now provide a mechanism for invoking non-CRUD (Create, Read, Update, and Delete) methods on a resource. You can invoke an action by sending an HTTP POST request to the URI that is defined for the action. The parameters for the action are defined in the body of the POST request.

To be consistent with Windows Azure guidelines, all URLs should be simplified. A change included in Key As Segment allows single keys to be represented as segments. Note that references that use multiple key values require comma-separated values in parenthetical notation, as before.

Before this release of PSWS, the only way to perform Create, Update, or Delete operations was to invoke Post, Put, or Delete on a top-level resource. New in this release of PSWS, Contained Resource operations let users achieve the same results while reaching the same resource less directly, approaching as if these resources were contained.


New features in Windows PowerShell Web Access

You can disconnect from and reconnect to existing sessions in the web-based Windows PowerShell Web Access console. A Save button in the web-based console lets you disconnect from a session without deleting it and reconnect to the session another time.

Default parameters can be displayed on the sign-in page. To display default parameters, configure values for all of the settings displayed in the Optional Connection Settings area of the sign-in page in a file named web.config. You can use the web.config file to configure all optional connection settings except for a second or alternate set of credentials.

In Windows Server 2012 R2, you can remotely manage authorization rules for Windows PowerShell Web Access. The Add-PswaAuthorizationRule and Test-PswaAuthorizationRule cmdlets now include a Credential parameter that enables administrators to manage authorization rules from a remote computer or in a Windows PowerShell Web Access session.

You can now have multiple Windows PowerShell Web Access sessions in a single browser session by using a new browser tab for each session. You no longer need to open a new browser session to connect to a new session in the web-based Windows PowerShell console.


Notable bug fixes in Windows PowerShell 4.0

Get-Counter can now return counters that contain an apostrophe character in French editions of Windows.

You can now view the GetType method on deserialized objects.

#Requires statements now let users require Administrator access rights, if needed.

The Import-Csv cmdlet now ignores blank lines.

A problem where Windows PowerShell ISE uses too much memory when you are running an Invoke-WebRequest command has been fixed.

Get-Module now displays module versions in a Version column.

Remove-Item –Recurse now removes items from subfolders as expected.

A UserName property has been added to Get-Process output objects.

The Invoke-RestMethod cmdlet now returns all available results.

Add-Member now takes effect on hashtables, even if the hashtables have not yet been accessed.

Select-Object –Expand no longer fails or generates an exception if the value of the property is null or empty.

Get-Process can now be used in a pipeline with other commands that get the ComputerName property from objects.

ConvertTo-Json and ConvertFrom-Json can now accept terms within double quotes, and its error messages are now localizable.

Get-Job now returns any completed scheduled jobs, even in new sessions.

Issues with mounting and unmounting VHDs by using the FileSystem provider in Windows PowerShell 4.0 have been fixed. Windows PowerShell is now able to detect new drives when they are mounted in the same session.

You no longer need to explicitly load ScheduledJob or Workflow modules to work with their job types.

Performance improvements have been made to the process of importing workflows that define nested workflows; this process is now faster.



No comment found.

Leave a new comment


Please enter a keyword.

Recent Posts


Copyright © 2017 New Horizons Worldwid, Inc. All rights reserved.