← All Posts

MECM

Installing .NET 4.0 in an MECM (formerly SCCM) Task Sequence

Adding .NET Framework 4.0 as a step in a Configuration Manager (MECM/SCCM) task sequence for OS deployment.

.NETDeploymentMECM

When building OS deployment task sequences in MECM (formerly SCCM) 2012, you often need .NET Framework 4.0 installed before certain applications will run. Here's the clean way to handle it.

Steps:

  1. Download the .NET Framework 4.0 standalone installer (dotNetFx40_Full_x86_x64.exe) from Microsoft
  2. Create a Package in MECM (formerly SCCM) (no program needed) — just the source files
  3. Distribute the package to your distribution points
  4. In the task sequence, add a "Run Command Line" step after OS install but before application installs
  5. Command: dotNetFx40_Full_x86_x64.exe /q /norestart
  6. Reference the package you created
  7. Add a restart step afterwards if needed

Modern context: .NET Framework 4.x (up to 4.8.1) ships inbox with Windows 10/11. The need to install it manually has largely disappeared. For modern task sequences, focus on enabling Windows Features (like .NET 3.5 for legacy apps) rather than installing .NET 4.x. Better yet, modernize applications to target .NET 8+, which deploys as a self-contained runtime with no OS dependency.