Skip to content
Update SCCM Application Content on Distribution Points

Update SCCM Application Content on Distribution Points

Written By Jitesh Kumar
Last Updated July 18, 2024
Posted In SCCM
SHARE

Learn how to update SCCM Application content on distribution points. You have different options for managing content on distribution points in SCCM. The updated content options in available for SCCM application deployment types.

However, based on the content type that you want to update, You can select Update Distribution Points or create a schedule for when the site updates the content for the object. This option is useful for an object whose content changes frequently.

When you update the source file location for deployment by adding new files or replacing existing files with a newer version, update the content files on distribution points. Use the Update Distribution Points or Update Content actions.

  • The site copies the content files from the original package source location to the content library on the site that owns the package content source.
  • It increments the package version.
  • Each instance of the content library on site servers and on distribution points updates with only the changed files.

Configuration Manager then distributes the new version of the content set to replace the previous set and any of its incremental versions. After the new content set is distributed, later incremental changes to the source files are again replicated by BDR.

Patch My PC

Applications always use binary differential replication (BDR), Learn how Configuration Manager uses binary differential replication (BDR) to update content

Update SCCM Application Content on Distribution Points

Let’s follow the Process to update content on distribution points, and You can use the Update Distribution Points or Update Content actions. Here basically, we will see how to use update content options.

In the Configuration Manager Console, Navigate to the Software Library workspace, expand Application Management, and select the Applications node.

Select an application in the Applications node that you want to update and select the Deployment Types tab. Right-click on the existing deployment type and select Update Content.

Select Update Content - Update SCCM Application Content on Distribution Points
Select Update Content – Update SCCM Application Content on Distribution Points

A prompt will appear with the message, “Are you sure that you want to refresh the content for this deployment type? Refreshing content will create a new revision of this application and may cause clients to be updated” Click on Yes to proceed.

Click Yes - Update SCCM Application Content on Distribution Point
Click Yes – Update SCCM Application Content on Distribution Point

Once the content is updated successfully, you will get a prompt “Update Content completed successfully” Then select OK.

Update Content completed successfully
Update Content completed successfully

Note – The package version for applications is always 1. When you update the content for an application deployment type, Configuration Manager creates a new content ID for the deployment type, and the package references the new content ID.

Update Content ID - SCCM Application Content on Distribution Points
Update Content ID – SCCM Application Content on Distribution Points

While running Update Content, you may encounter an error: The specified folder does not exist, or the computer running the Configuration Manager console has no Read permissions to the specified shared folder.

The error message typically appears when you don’t have permission to access the folder path or the application content is not available inside the specified application content location in SCCM. Ensure you have the appropriate permissions or the application source has accessible.

Update Content Error - Prompt
Update Content Error – Prompt

Update SCCM Application Content Using PowerShell Commands

You can use the PowerShell Commands or SCCM PowerShell commandlets to Update SCCM Application Content. You can launch the SCCM PowerShell CommandLets from the console itself.

Related Posts – 3 Best Methods to Import SCCM PowerShell Module Cmdlets

Click on the Drop-Down option on the top left side corner of the console and click on Connect via Windows PowerShell option. 

Click on Connect via Windows PowerShell - Update SCCM Application Content Using PowerShell Commands
Click on Connect via Windows PowerShell – Update SCCM Application Content Using PowerShell Commands

Click on A on the following warning about the untrusted publisher.

Do you want to run software from this untrusted publisher?
File F:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.PowerShell.Types.ps1xml is published by CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US and is not trusted on your systemOnly run scripts from trusted publishers.
[V] Never run [D] Do not run [R] Run once [A] Always run [?] Help (default is “D”): A

Run the following PowerShell command Update content on a distribution point. You will need to change the value mentioned in the following command as per your environment.

Update-CMDistributionPoint
-ApplicationName
-DeploymentTypeName
[-ManifestPath ]
[-DisableWildcardHandling]
[-ForceWildcardHandling]
[-WhatIf]
[-Confirm]

For example, I am running the command below to update content for the Zoom Application.

Update-CMDistributionPoint -ApplicationName "Zoom Application" -DeploymentTypeName "Zoom - Windows Installer"
Update-CMDistributionPoint - Update Application Content Using PowerShell Commands
Update-CMDistributionPoint – Update SCCM Application Content Using PowerShell Commands

Author

Written by

Jitesh has over 5 years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus area is Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.

Discussion

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Intune

Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws

Key Takeaways Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws! In the July 2026 Patch, Microsoft introduced new features designed to improve the overall Windows experience. The update adds enhancements to Windows Update for more flexible update management and introduces Point-in-Time Restore, providing an additional recovery option for […]

AC Anoop C Nair 9 min read
Intune

2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws

Key Takeaways 2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws! The June 2026 Windows 11 Patch Tuesday update brings several improvements to File Explorer. It adds support for additional archive formats, including UU, CPIO, XAR, and NuGet Packages (NUPKG). The update also preserves View and Sort preferences in […]

AC Anoop C Nair 10 min read
Intune

2026 May KB5089549 KB5087420 Windows 11 Patch | 0 Zero Day Vulnerabilities and 120 Flaws

Key Takeaways The Windows 11 May 2026 Patch KB5089549 KB5087420 Update brings important security fixes, performance improvements, and reliability enhancements across the operating system. The update introduces new features such as Xbox Mode for gaming, File Explorer improvements, enhanced input and sharing experiences, better taskbar and Windows Hello reliability, and additional enterprise management capabilities for […]

AC Anoop C Nair 8 min read
SCCM

ConfigMgr 2603 Introduces New Early Update Enrollment Process

Key Takeaways In this post we are discussing the ConfigMgr 2603 Introduces New Early Update Enrollment Process. Microsoft has officially released Configuration Manager version 2603 to the Early Update Ring, giving organizations an opportunity to test upcoming improvements before the global production rollout. The release is targeted at enterprises running ConfigMgr version 2409 or later […]

AC Anoop C Nair 3 min read