I’m planning on writing an article on deploying the Box for Office Integration client package using SCCM which requires the .Net Framework to be pre-installed (amongst other pre-requisites) so I thought I’d first write this post on deploying the framework so I can refer to it in the upcoming post.
We’re going to deploy this as an application and not a package since you can only have dependencies on applications.
Download the .NET Framework 4.0 Standalone Installer
To start off download the .NET 4.0 standalone installer from Microsoft and save it to your SCCM software repository.
I briefly mentioned the importance of having a clear and easy to understand folder structure to store your images, software and packages in the repository. Personally, I have a dedicated folder called “.NET Frameworks” with subfolders for each version that I’ll be deploying.
Make a note of the UNC path where you save the installer.
Create the .NET Application in SCCM
Again, I suggest you create a dedicated folder for .NET Frameworks under Application Management > Applications and create subfolders for each .NET framework version that you’ll be deploying.
Right-click on your chosen folder under Applications and select “Create Application”.
Select “Manually specify the application information”
Enter the name of the application, publisher and software version. Click on Next
Leave the default in the next screen
Click on Add on the Deployment Types screen
Select “Script Installer” and click on Next
Enter the name of the application and click on Next
Enter the following information:
Content location: specify the UNC path to the directory where you saved the installer
Installation program: dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT
Uninstall program: dotNetFx40_Full_x86_x64.exe /uninstall
Click on Next. On the Detection Method screen click on “Add Clause…” and enter/choose the following information:
Setting type: Registry
Key: SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
Data Type: Integer
Select “This registry setting must exist on the target system to indicate presence of this application”
Click on OK
In the User Experience screen enter/choose the following:
Installation behavior: Install for system
Logon requirement: Whether or not a user is logged on
Installation program visibility: Normal
Adjust the maximum run time for this program as you see fit (default is 2 hours)
Click on Summary and finish the wizard.
Back on the Create Application wizard click on Next > Next > Close
Distribute the .NET 4.0 Application to the Distribution Points
Right-click on the application you just created and select Distribute Content
Click on Next. Click on Add > Distribution Point. Put a check next to the Distribution Point you want to distribute the application to.
Click on Next > Summary and close the wizard.
Select the application and you should notice a yellow circle under “Content Status”. Give it a few minutes and this should turn GREEN as shown below:
Deploy the .NET 4.0 Application to your Collection
Right-click on the .NET Framework application and select Deploy. Click on Browse and select a target collection to deploy the package to.
Click on Next > Next > then decide whether to make the package mandatory (required) or available (optional). In my case I’m making this a mandatory application.
In the next step you can schedule when you want the package to be installed.
Click on Next and decide on the user experience for this application deployment.
You can optionally create alerts for successful and failed deployments in the next screen.
Click on Next > Next > Close.
That’s it. The .net framework package should be installed in due course.