SCCM direct replacement compared with supersedence

While deleting the old version and replacing it with the new version in the source location might seem easier, it is not the best practice in SCCM (Microsoft Configuration Manager) for several reasons. Here’s a detailed breakdown of why supersedence is preferred and what potential risks you face by simply updating the content directly.

What Happens When You Replace Source Files and Update Content?

Update Content Workflow:

• Replacing the installation files at the source location and selecting "Update Content" will redistribute the new files to distribution points (DPs).
  • Existing deployments will use the updated content the next time they execute.
  Risks of Replacing Source Files:

  - **No Version Control**: SCCM won’t know that the content has changed unless you also update the application’s version or metadata in the console.
  
     - **Deployment Confusion**: If the new version has different installation requirements, behaviors, or dependencies, the older deployments might break.
  
        - **Client Cache Issues**: SCCM clients cache content locally. If the cached version is mismatched with the new files, the deployment may fail unless the client cache is cleared.
  
           - **No Rollback Mechanism**: If the new version has issues, rolling back to the old version becomes difficult since you replaced it.
  

Why Use Supersedence Instead?

Automatic Upgrades:

• Supersedence allows you to specify that the new version of the application replaces the old version during deployment.
  • SCCM handles uninstallation of the older version and installation of the new version automatically.
  Version Control and Reporting:

  - With supersedence, SCCM maintains a clear record of which version was deployed and upgraded.
  
     - You can track **compliance** and detect issues if some clients didn’t upgrade successfully.
  
     **Testing and Validation**:
  
        - You can **test the new version** with a subset of devices before rolling it out organization-wide, minimizing the risk of issues.
  
           - Supersedence ensures smooth deployment even if there are dependencies or custom detection rules.
  

1. Client Cache Management:
   • SCCM properly invalidates cached content when a new version is introduced via supersedence.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin