Deploying Third-Party Applications
Patch for SCCM can deploy a number of free third-party applications to your endpoints, including:
•Adobe Acrobat Reader
•And more . . .
You do this by selecting an application from the Application catalog and importing it into Microsoft’s System Center Configuration Manager (SCCM). Once there, the installer for the third-party application will be downloaded to one or more distribution points and pushed out to your endpoints using your regular SCCM infrastructure.
You cannot add to or edit the Application catalog that is provided by Ivanti. If you want to add or edit applications, you must use the Application Management > Application workspace in SCCM.
Access to the following URL is required in order to download the Application catalog:
For the complete list of URLs that are required by Patch for SCCM, see:
If you are using a version of Configuration Manager that is older than version 1906, the following site system roles are required:
•Application catalog website
•Application catalog web service
How to Use the Feature
1.Within the Configuration Manager Software Library workspace, expand the Application Management folder and click Ivanti Application Management.
The Application catalog is downloaded and the list of available third-party applications is displayed.
The catalog resides in the C:\Users\<username>\Ivanti\Patch folder in the file named ApplicationDigests.xml.
2.Select the application(s) you want to deploy.
3.Click Import into SCCM.
The Import Applications dialog is displayed.
Application Content Location: Specify the UNC path of the location that you want to use to store the application installers that are downloaded from the vendor. The default value is the path specified on the Application Management tab in the setup wizard. For each application that you import, a unique subfolder will be created at this location that contains the installation package for that application.
Application Owner: Specify which Patch for SCCM administrator that you want to own the third-party applications. The name will be displayed on the endpoint and is typically the person responsible for supporting the application.
Application Automatic Update: Specifies what to do when a new version of the application becomes available from the vendor. You have two options:
•Automatically update the application content: The application will be automatically updated by a background task. The new version of the application will be available to users when the task is complete.
•Create a new application: A new application will be created when new content becomes available. You will need to manually deploy the new application. If you want to delete older versions of an application, you can do so from the Application Management > Applications workspace within SCCM.
These two options determine how a deployed third-party application will be updated (either in place or by creating a new copy). To initiate the update process, you either enable the Update imported applications check box within a scheduled task or you can force an immediate update by clicking the Update Applications toolbar button.
4.Click Import into SCCM.
This will import the third-party applications into the SCCM infrastructure.
5.Verify that the third-party applications have been added to the Application Management > Applications workspace within SCCM.
At this point you can perform your normal SCCM functionality on the applications. For example, you might wish to view the application properties and perform edits using the existing SCCM infrastructure.