How to Deploy .Net Framework 4.5.1 using Configuration Manager 2012

https://apis.google.com/_/scs/apps-static/_/js/k=oz.gapi.en_US.XkOp0hVWkkM.O/m=auth/exm=plus,plusone/rt=j/sv=1/d=1/ed=1/am=AQ/rs=AGLTcCNTXv-Q4H6BvmWabwLyHKGHuQOhwA/t=zcms/cb=gapi.loaded_1https://apis.google.com/_/scs/apps-static/_/js/k=oz.gapi.en_US.XkOp0hVWkkM.O/m=plus,plusone/rt=j/sv=1/d=1/ed=1/am=AQ/rs=AGLTcCNTXv-Q4H6BvmWabwLyHKGHuQOhwA/t=zcms/cb=gapi.loaded_0https://apis.google.com/js/plusone.js// 3e3):(d.fillText(String.fromCharCode(55357,56835),0,0),0!==d.getImageData(16,16,1,1).data[0])):!1}function e(a){var c=b.createElement(“script”);c.src=a,c.type=”text/javascript”,b.getElementsByTagName(“head”)[0].appendChild(c)}var f,g;c.supports={simple:d(“simple”),flag:d(“flag”)},c.DOMReady=!1,c.readyCallback=function(){c.DOMReady=!0},c.supports.simple&&c.supports.flag||(g=function(){c.readyCallback()},b.addEventListener?(b.addEventListener(“DOMContentLoaded”,g,!1),a.addEventListener(“load”,g,!1)):(a.attachEvent(“onload”,g),b.attachEvent(“onreadystatechange”,function(){“complete”===b.readyState&&c.readyCallback()})),f=c.source||{},f.concatemoji?e(f.concatemoji):f.wpemoji&&f.twemoji&&(e(f.twemoji),e(f.wpemoji)))}(window,document,window._wpemojiSettings);

// ]]>http://fearthemonkey.co.uk/wp-includes/js/wp-emoji-release.min.js?ver=4.3
http://fearthemonkey.co.uk/wp-includes/js/jquery/jquery.js?ver=1.11.3http://fearthemonkey.co.uk/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1// http://fearthemonkey.co.uk/wp-content/themes/suffusion/scripts/suffusion.js?ver=4.4.7 https://platform.linkedin.com/js/secureAnonymousFramework?v=0.0.2000-RC8.50730-1428&

 November 28, 2013  Posted by at 11:42 Configuration Manager 2012  Add comments

Deploying .Net Framework 4.5.1 using Config Manager 2012 is straightforward once you have the detection rule for it.

If you wish to deploy the Windows Management Framework 4.0 to your Windows 7 SP1 computers then you will need to deploy .Net 4.5.1 as a pre-requisite first.

Here’s how I did it:

Firstly, you will need to download the offline installer for the framework and place the exe on your config manager server where you would normally place the files that you distribute.  I downloaded it from here: http://www.microsoft.com/en-us/download/details.aspx?id=40779

1.  Create a new Application

1 - CreateNewApplication

2.   Select “Manually specify the application information”

2 - General

3.   Specify the application information.  I chose to Allow the application to be installed from the task sequence as I may do this at a later stage.

3 - Application Info

4.  Fill in any details that you would like to appear in the Application Catalog.  I will not be making this available in the Application Catalog as I intend to deploy this to a computer collection so I left these fields at their defaults.

4 - appCat

5.  Click the ‘Add’ button to create a new deployment type.

5 - addDepType

6.  Change the type to ‘Script Installer (Native)

6 - scriptInstaller

7.   Give the Deployment type a meaningful name

7 - DeploymentName

8.  Browse to where you placed the installation .exe on your Config Manager server and complete the rest of the fields as shown in my screenshot below.  Note:  I chose to force a reboot suppression as I do not want computers having to restart at an inconvenient time to the end user.  Also note that I chose to “Run installation and uninstall program as 32-bit process on 64-bit clients” as I found that if I didn’t do this then the uninstallation of it would fail with a ‘16389’ error in the software centre.

netuninstall

9.  Click the ‘Add Clause’ button so that we can configure a detection rule for this deployment.

9 - addClause

10. I looked here for the detection method:  http://msdn.microsoft.com/en-us/library/ee942965(v=vs.110).aspx#detect_net

With that in mind, ensure that your detection rule looks like mine in the screenshot below then click OK:

drule

11. Click Next

11 -detectionSummary

12.  Set the Installation Behavior to : Install for system and the Logon Requirement to: Whether or not a user is logged on.

12 - UserExp

13.  Click the ‘Add’ button on the Requirements screen

13 - reqs

14.  Add any system requirements that you would like for this deployment type.

14 - SysReqs

15.  Click the next button at the Dependency screen unless you would like to add any.

15 - Deps

16.  Click Next at the deployment type summary

16 - depSum

17. If all has gone well you should have a successful message on the deployment type:

17 - depSuccess

18. Click Next on the Deployment Type screen

18 -depNext

19.  Click Next on the Summary

19 - sum

20.  If all went well you should have a success screen:

20 - completionSuccess

21.  All that’s left is to upload the finished application to your distribution point and then deploy it to a computer collection.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s