SCCM Software Deployment in 2025: Step-by-Step Mastery

Estimated reading time: 6 minutes

Unleashing SCCM for Software Deployment

Microsoft System Center Configuration Manager (SCCM)—now tucked into Endpoint Manager—is your heavy hitter for rolling out software across Windows fleets in 2025. Whether it’s pushing Notepad++, custom EXEs, or the latest patches, this guide digs into every angle of SCCM deployment on Server 2022 or Windows 11 clients. From prepping your environment to nailing deployments, troubleshooting flops, and syncing with Intune, it’s stacked with detailed steps, PowerShell firepower, and pro-level hacks. This is your SCCM playbook—deep, practical, and built for IT warriors.

Step 1: Prep Your SCCM Environment

What You Need: SCCM 2309+ (latest vibe as of 2025), SQL Server 2022, a distribution point (DP), and clients with the SCCM agent humming. Set boundaries and discovery in the console—hit Administration > Hierarchy Configuration to scope your domain.

Verify It: Open the SCCM Console, swing to Monitoring > System Status. All green lights? You’re primed. If not, check SiteComp.log on the server—fix red flags like SQL perms or DP woes.

Step 2: Craft the Application

Build It: In the SCCM Console, cruise to Software Library > Applications. Click “Create Application.” For an MSI (e.g., Notepad++ 8.6), point to the npp.8.6.Installer.x64.msi, let it snag settings—install command defaults to msiexec /i "npp.8.6.Installer.x64.msi" /qn. Detection? Registry key HKLM\Software\Notepad++, value “InstallLocation”.

Custom EXE: Go manual—set Name: “MyApp,” Publisher: “TechyCo,” Version: “1.0.” Install command:

setup.exe /silent /norestart

Detection: File C:\Program Files\MyApp\app.exe, version “1.0”.

Push It: Right-click > “Distribute Content,” pick your DP. Wait 5-15 mins—track it in Monitoring > Distribution Status. Stuck? Check distmgr.log.

Step 3: Deploy to the Masses

Target: Hit Assets and Compliance > Device Collections. Use “All Workstations” or craft a query-based collection:

select SMS_R_System.ResourceId, SMS_R_System.Name from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "%Windows 11%"

Deploy: Right-click your app > “Deploy.” Pick your collection, set “Required” (mandatory) or “Available” (optional), schedule a maintenance window (e.g., 2 AM), and tick “Allow metered connections.” Monitor in Monitoring > Deployments—shoot for 90%+ success in 24 hours.

Step 4: PowerShell Muscle

Automate It: Fire up SCCM PowerShell (Console > “Connect via Windows PowerShell”):

New-CMApplication -Name "Notepad++ 8.6" -SoftwareVersion "8.6" -Publisher "Notepad++ Team"
Add-CMDeploymentType -ApplicationName "Notepad++ 8.6" -DeploymentTypeName "MSI" -MsiInstaller -ContentLocation "\\SCCM\Sources\npp.8.6.Installer.x64.msi" -InstallationBehaviorType InstallForSystem -InstallCommand 'msiexec /i "npp.8.6.Installer.x64.msi" /qn'
Start-CMContentDistribution -ApplicationName "Notepad++ 8.6" -DistributionPointName "DP01.company.local"
Start-CMApplicationDeployment -Name "Notepad++ 8.6" -CollectionName "All Workstations" -DeployAction Install -DeployPurpose Required

Adjust paths and names—runs like a dream.

Step 5: Intune Co-Management

Sync Up: In SCCM, flip to Administration > Cloud Services > Co-management. Enable it, slide “Application” workload to Intune. In Intune, craft a Win32 app—convert npp.8.6.Installer.x64.msi to .intunewin with the IntuneWinAppUtil tool, set install command msiexec /i "npp.8.6.Installer.x64.msi" /qn, deploy to an Azure AD group. SCCM owns on-prem, Intune grabs cloud.

Troubleshooting

Client Fails: Peek at C:\Windows\CCM\Logs\AppEnforce.log—error 0x87D00324 means detection’s off; tweak the rule (e.g., file version). No go? Force a policy pull:

Invoke-WMIMethod -Namespace "root\ccm" -Class "SMS_Client" -Name "TriggerSchedule" -ArgumentList "{00000000-0000-0000-0000-000000000021}"

DP Hiccups: Check distmgr.log—redistribute if hung. Reboot the DP if it’s DOA.

Best Practices

• Pilot First: Test on a “Beta” collection—5-10 boxes—before going wide.
• Throttle It: Cap DP bandwidth in Properties > Schedule—50 Mbps daytime max.
• Clean House: Retire old apps monthly—keeps Software Center tight.
• Log Deep: Dump deployment stats:
  Get-CMDeployment | Select-Object ApplicationName,CollectionName,DeploymentTime,SuccessPercent

FAQ

Q: SCCM for macOS?
A: Nope—Windows only. Intune’s your mac game.

Q: Co-management clash?
A: Avoid overlap—set Intune to “Windows Update for Business only” if SCCM’s king.

Q: Package size limit?
A: 8GB max—split giants into chunks.

Q: Stuck deployment?
A: Restart the SMS Agent Host service:

Restart-Service -Name CcmExec

Glossary

Win32 App: Intune’s non-store app wrapper.rosoft System Center Configuration Manager (SCCM)—now part of Endpoint Manager—remains a powerhouse for pushing software to Windows fleets in 2025. Whether it’s Adobe Reader, custom apps, or Windows updates, this guide dives into deploying software with SCCM on Server 2022 or Windows 11 clients. From setup to troubleshooting, we’ll cover every detail, with PowerShell shortcuts, Intune co-management tips, and pro-level insights for IT admins.

SCCM: System Center Configuration Manager—endpoint boss.

DP: Distribution Point—SCCM’s content mule.

MSI: Microsoft Installer—app package standard.

Step 1: Prep SCCM Environment

Prerequisites: SCCM 2309+ installed (latest as of 2025), SQL Server 2022, a distribution point (DP), and clients with the SCCM agent. Ensure boundaries and discovery (AD System Discovery) are set—check Administration > Hierarchy Configuration.

Verify: In SCCM Console (Configuration Manager Console), go to Monitoring > System Status. All green? You’re ready.

Step 2: Create the Application

Package It: In SCCM Console, navigate to Software Library > Applications. Click “Create Application.” For MSI apps (e.g., 7-Zip), point to the .msi, auto-detect settings. For scripts (e.g., custom EXE), use “Manually specify”:
– Name: “7-Zip 24.01”
– Install command: msiexec /i "7z2401-x64.msi" /qn
– Detection: Registry key HKLM\Software\7-Zip, value “Path”.

Distribute: Right-click the app > “Distribute Content.” Select your DP, wait 5-15 mins for replication (check Monitoring > Distribution Status).

Step 3: Deploy to Clients

Target: Go to Assets and Compliance > Device Collections. Use an existing collection (e.g., “All Workstations”) or create one with a query (e.g., OS = Windows 11).
Deploy: Right-click the app > “Deploy.” Pick your collection, set “Required” (forces install) or “Available” (user choice), schedule now or later (e.g., 2 AM maintenance window), and enable “Allow clients to use a metered connection.”

Monitor: Under Monitoring > Deployments, watch success rates—aim for 90%+ within 24 hours.

PowerShell Shortcut

Automate deployment:
New-CMApplication -Name "7-Zip 24.01" -SoftwareVersion "24.01" -Publisher "Igor Pavlov"
Add-CMDeploymentType -ApplicationName "7-Zip 24.01" -DeploymentTypeName "MSI" -MsiInstaller -ContentLocation "\\SCCM\Sources\7z2401-x64.msi" -InstallationBehaviorType InstallForSystem -InstallCommand 'msiexec /i "7z2401-x64.msi" /qn'
Start-CMContentDistribution -ApplicationName "7-Zip 24.01" -DistributionPointName "DP01.company.local"
Start-CMApplicationDeployment -Name "7-Zip 24.01" -CollectionName "All Workstations" -DeployAction Install -DeployPurpose Required

Notes: Run in SCCM PowerShell (right-click Console > “Connect via Windows PowerShell”). Adjust paths/names.

Intune Co-Management

Setup: In SCCM, enable co-management (Administration > Cloud Services > Co-management). Slide “Application” workload to Intune. In Intune, create a Win32 app with the same .msi, deploy to an Azure AD group—SCCM handles on-prem, Intune cloud.

Troubleshooting

Client Fails: Check C:\Windows\CCM\Logs\AppEnforce.log—error 0x87D00324 means detection failed; tweak the rule.
DP Issues: distmgr.log on the site server—redistribute if stuck. Reboot DP if desperate.

Best Practices

• Test First: Deploy to a pilot collection (e.g., 5 PCs) before prod.
• Bandwidth: Set DP throttling (Properties > Schedule)—50 Mbps max during work hours.
• Cleanup: Retire unused apps monthly—keeps Software Center lean.

FAQ

Q: Can SCCM deploy to macOS?
A: No, Windows only—use Intune for macOS.

Q: What’s co-management?
A: SCCM + Intune sharing duties—e.g., SCCM for on-prem, Intune for remote.

Q: How big can packages be?
A: Up to 8GB per app—split larger ones.

Glossary

• SCCM: System Center Configuration Manager—endpoint management tool.
• DP: Distribution Point—SCCM server hosting content.
• MSI: Microsoft Installer—package format for apps.
• Win32 App: Intune’s format for non-store apps.