Automated Application Management for Microsoft Endpoint Manager

Simplify third-party application management

Knowledge Base ArticlesRequest Trial

When a New Application Update is Available for SCCM Base Installations

In this article, we will explain the options available when an application update is available. This information will help clarify the functionality of some of our base install options, which are highlight below.

Topics covered in this article:

Option 1: Update existing application’s metadata, deployment type, detection method, and content files (Default)

When this option is selected, the Patch My PC Publisher will automatically update the various pieces of metadata associate with the application, as well as the content files themselves. The metadata that will be updated is:

  • Title:
    • Based on customer settings, such as not including the version, or custom application name
  • Version:
    • Updated to reflect the new version synchronized from the catalog
  • Detection Method:
    • PowerShell based detection method updated to ensure the new version is detected
    • The script will be re-signed based on customer settings

Alongside this metadata, the content itself will be updated. This means the binaries for the old version of the application will be removed, and the new binaries will be copied to the application source directory. Once complete, the Publisher will trigger a content update on the Deployment Type for the Application or a package refresh if it is a package.

Because we are updating the existing application in this scenario, we have some consideration to keep in mind.

  • Existing Deployments:
    • If the application which was updated has required deployments then the targeted devices will receive the updated policy on their next Machine Policy refresh, including the new detection method, as we’ve created an application revision. The result is that machines may run this installation and update the software based off this application deployment. Be aware of this when creating any required deployments of the Patch My PC managed applications.
    • If the application which was updated has available deployments then the targeted devices will be installing the latest available version of these applications which Patch My PC provides when the user selects install.
  • Task Sequences:
    • If you are referencing these Patch My PC managed applications within a task sequence then you will always be deploying the latest available version of these applications which Patch My PC provides.
  • General Consideration:
    • We will be performing an ‘update content’ on these packages and applications. Any requests for this content while it is being refreshed will, of course, fail, stating that content is not available. Be aware of this, especially with task sequences that reference the content. It could be good to coordinate your publisher’s sync schedule with your high-traffic imaging days and times.

Option 2: Create a new application without modifying any previous applications

This scenario is much more straight forward. Whenever a new application update is available a new application will be created. The publisher will not take any action on the previously created application versions.

Even with simplicity comes a couple of considerations.

  • Application Sprawl:
    • If left unchecked this approach could end up leaving tens of application versions per app, or more, in your Configuration Manager environment.
      • Periodically review old application versions and deployments.
  • Task Sequences:
    • Task sequences that reference Patch My PC managed applications will likely be referencing old versions of the application.
      • Periodically review and update your task sequence references as needed