How to deploy Windows Management Framework 4.0 using Config Manager 2012

WMF 4.0 requires the .Net 4.5.x framework as a pre-requisite.   Two reboots are required: the .net framework will require a reboot and the WMF will require a reboot.

I chose to make the .net framework a dependency of the WMF 4.0 deployment and to suppress all reboots.  The deployment will then install .Net 4.5.1 and wait until the next reboot when it will then continue to deploy WMF 4.0 which will also wait for a reboot.

Here’s how I did it:

1. Create the .Net 4.5.1 application.  To do this, see my step-by-step guide here.

2. Create the WMF 4.0 application.  To do this, refer to my step-by-step guide here on deploying WMF 3.0 here, but make the following changes to the guide: 

– Download WMF 4.0 instead of WMF 3 obviously!

– Change all references in the application to the name Windows Management Framework 3.0 to Windows Management Framework 4.0 (Again – obvious!)

–  Change step 10 in the WMF 3.0 installation guide:

The detection method should now detect version 6.3  of the powershell executable as shown below: (The actual full version number is 6.3.9600.16406)

WMF4DetectionRule

 

– Change step 15 in the WMF 3.0 installation guide:

Add the .net framework 4.5.1 as a dependency of the WMF 4.0 application:

wmf4Deps

 

Then deploy only the WMF 4.0 Framework application.

 

Once deployed successfully, the powershell version can be confirmed by opening a powershell window and typing $psversiontable at the prompt:

powershell v4

 

2 Comments

  1. I’ve scoured the web looking for the best way to do this for our enterprise. I cannot thank you enough for taking the time to put this together (screen shots and all). This has been very beneficial. Cheers and have a pint of John Bull Bitter for me all the way across the pond!

Leave a Reply