How to deploy .NET Framework 4.6.2 with SCCM. Easy step by step guide with pictures explaining how to create the application in Configuration Manager.
One of our customers that was still on .NET Framework 4.5.2 experienced problems with the December 2016 patches from Microsoft, one patch simply would not install and reported an error. Upgrading the customer to .NET Framework 4.6.2 solved their problem and all updates installed successfully. There was no reason why they didn’t upgrade, they where just that some applications would stop working and hesitated. So after upgrading them I decided to write this guide.
This guide explains in detail how you create the .NET Framework 4.6.2 application, set a detection method for it and then deploy it with SCCM.
OS Requirements for .NET Framework 4.6.2
- Windows 7 SP1 32-Bit
- Windows 7 SP1 64-Bit
- Windows 8.1 32-Bit
- Windows 8.1 64-Bit
- Windows Server 2008 R2 SP1 64-Bit
- Windows Server 2012 64-Bit
- Windows Server 2012 R2 64-Bit
Creating the .NET Framework 4.6.2 Application in ConfigMgr
Download .NET Framework 4.6.2 (Offline Installer) from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=53344
Install string for .NET Framework 4.6.2 (All operating systems)
NDP462-KB3151800-x86-x64-AllOS-ENU.exe /passive /norestart
We will use a registry key and value to detect if the correct version is installed.
- Hive: HKEY_LOCAL_MACHINE
- Key: SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
- Value: Release
- Data Type: Integer
- Operator: Equals
- Value: 394806 (394802 for Windows 10)
wusa.exe KB3151800 /uninstall /quiet /norestart
Software Library -> Applications
Right click and create a new application. We want to manually specify the application information.
Fill in the general information of the .NET Framework 4.6.2 application. Check “Allow this application to be installed from the Install Application task sequence action without being deployed” if you want to install .NET Framework during OS deployment. This allows computers not targeted by any deployments, like unknown computers, to install .NET Framework.
Under deployment type, create a new deployment type and select “Script Installer” and “Manually specify the deployment type information”.
Specify the name of the deployment type.
Specify the source for .NET Framework 4.6.2, enter the install and uninstall string from earlier in this guide.
We start by entering the detection rule that will detect the presence of the application on all operating systems except Windows 10.
Then we add another detection rule to detect the presence of .NET Framework 4.6.2 on Windows 10 computers.
Make sure the connector says “Or”. The application is detected successfully if the first or second clause is evaluated to be true.
Chose Install for system, whether or not a user is logged on, and hidden, for the User Experience window.
No requirements needed as .NET Framework 4.6.2 will install over any previous version. We also don’t need to specify any dependencies.
Optional: I always prefer to supersede older version of an application. .NET Framework 4.6.2 do not require previous version to be uninstalled, so no need to check that. Right click on the application, select Supersedence, and add any previous versions of .NET Framework that you want to supersede.
Deploy .NET Framework 4.6.2 with SCCM
The application is good to go and you are now ready to deploy .NET Framework 4.6.2 with SCCM. Right click on the application and select deploy. It is good practice to install or upgrade .NET Framework on a pilot collection before you upgrade in case it affects any line of business applications. Select a collection to target your computers and deploy .NET Framework 4.6.2.