# SCCM application deployment for third-party software ## What is SCCM application deployment for third-party software? SCCM application deployment for third-party software is the process of packaging, distributing, and installing non-Microsoft applications to managed endpoints through Microsoft Configuration Manager's Application Management workspace. Unlike patch deployment (which uses the Software Updates channel for existing application updates), application deployment handles the initial installation of an application or the deployment of a new version as a complete package. For third-party software, this requires creating application binaries with detection rules, install commands, and content before deploying through the SCCM console. ## Application deployment vs. Software updates deployment in SCCM: when to use which SCCM has two separate channels for getting software to endpoints, and choosing the wrong one can cause deployment failures and compliance gaps. The distinction matters: - **Software Updates deployment (Deploy Software Updates Wizard):** Use this when deploying patches and updates to applications already installed on endpoints. Updates are published to WSUS, synchronized to SCCM, and deployed through Automatic Deployment Rules or the Deploy Software Updates Wizard. This is the standard channel for monthly patching. Third-party patches published by [Patch Connect Plus](https://www.manageengine.com/sccm-third-party-patch-management/) flow through this channel. See the [SCCM patch deployment step-by-step guide](https://www.manageengine.com/sccm-third-party-patch-management/kb/deploy-patches-using-sccm-how-to.html) for this method. - **Application deployment (Deploy Software Wizard):** Use this when installing a new application on endpoints for the first time or deploying a complete new version of an application as a package (not an incremental update). Applications are created in the Application Management workspace with detection rules, install commands, and content sources. This guide covers this method. In practice, use the Software Updates channel for keeping existing applications patched and the Application Management channel for initial installations and major version rollouts. Patch Connect Plus supports both: it publishes patches through WSUS for the Software Updates channel, and it can create application binaries in the Application Management workspace for initial deployments. ## How to deploy third-party applications in SCCM SCCM application deployment distributes third-party software to managed endpoints through the Application Management workspace in the SCCM console. This workspace lets admins create application packages, define detection rules, set install commands, manage licenses, and track deployment status. For third-party applications, the main challenge is preparing the software before deployment: downloading the installer, applying code signing certificates, and creating the application package with correct detection logic. [Patch Connect Plus](https://www.manageengine.com/sccm-third-party-patch-management/application-management.html) handles that preparation automatically for 800+ third-party applications. See the [full list of supported applications](https://www.manageengine.com/sccm-third-party-patch-management/supported-applications.html). ## SCCM application deployment step-by-step Patch Connect Plus simplifies third-party application deployment with its library of 800+ applications ready to be published to SCCM's Application repository. Once applications are successfully published, you can carry out their deployment using the standard SCCM tools. Before you begin, configure the following prerequisites. ### Prerequisites #### Configuring SCCM settings Before creating binaries of third-party applications in Patch Connect Plus, configure the SCCM settings in the Patch Connect Plus console to automatically synchronize the application binaries to your SCCM server. 1. Navigate to **SCCM Settings** under the **Admin** tab in the Patch Connect Plus console. 2. Enter the name or IP address of the Microsoft SCCM server to which the binary details must be synced. 3. Add the credentials of the SCCM admin user. ![SCCM settings in Patch Connect Plus for application deployment](https://www.manageengine.com/sccm-third-party-patch-management/images/admin-app-settings.png) #### Configuring Application Management settings Configure the network share path for all the software binaries in the Application Management settings. 1. Navigate to **Application Management** settings under the **Admin** tab. Enter the network share path where all the software binaries will be stored. 2. Ensure the network path has read/write access enabled with elevated privileges. 3. Set a time interval (for example, 60 or 90 days) for cleaning up outdated application binaries from the repository. Choose an interval based on your organization's retention requirements and available disk space. ![Application Management settings and network share path in Patch Connect Plus](https://www.manageengine.com/sccm-third-party-patch-management/images/admin-appli-settings.png) ### Creating third-party application binaries in Patch Connect Plus 1. Once the prerequisites are met, navigate to the **Application Management** tab in the Patch Connect Plus console. All supported third-party applications will be listed. 2. Select the required third-party application that you want to create in SCCM and click **Create Application**. 3. When the **Application creation in progress** message appears, Patch Connect Plus begins creating the third-party application binaries for SCCM. ![Creating third-party application binaries in Patch Connect Plus](https://www.manageengine.com/sccm-third-party-patch-management/images/app-creation.png) ### Deploying third-party applications from the SCCM console All third-party applications created from the Patch Connect Plus console are listed under **Software Library > Application Management > Applications** in SCCM. To deploy the required application to your endpoints, follow these steps: ![List of third-party applications in SCCM Software Library](https://www.manageengine.com/sccm-third-party-patch-management/images/step1-third.png) 1. Right-click the third-party application you want to deploy and select **Deploy**. ![Selecting Deploy for a third-party SCCM application](https://www.manageengine.com/sccm-third-party-patch-management/images/step2-third.png) 2. In the **Deploy Software Wizard**, select the target collection and click **Next**. For required deployments, the application installs automatically; for available deployments, it appears in Software Center for users to install on demand. ![Selecting the target collection in the SCCM Deploy Software Wizard](https://www.manageengine.com/sccm-third-party-patch-management/images/step3-third.png) 3. On the **Content** page, specify the distribution point or distribution point group from which the application content will be delivered. ![Selecting distribution points for application content](https://www.manageengine.com/sccm-third-party-patch-management/images/step4-third.png) 4. Under **Deployment Settings**, choose **Available** or **Required**. Choose Required for automatic installation without user action, or Available to let users initiate the installation from Software Center. Click **Next**. ![Choosing Available or Required in SCCM deployment settings](https://www.manageengine.com/sccm-third-party-patch-management/images/sd-dp-stpe4.png) 5. Under **Scheduling**, specify when the deployment should be available. For urgent deployments, set the available time to **As soon as possible**. For planned rollouts, account for maintenance windows to minimize user disruption. Click **Next**. ![Scheduling third-party application deployment in SCCM](https://www.manageengine.com/sccm-third-party-patch-management/images/sd-dp-stpe5.png) 6. Under **User Experience**, configure user notification and installation experience settings. ![Configuring user experience for SCCM application deployment](https://www.manageengine.com/sccm-third-party-patch-management/images/sd-dp-stpe6.png) 7. Under **Alerts**, configure the alerts and compliance thresholds for the deployment. ![Configuring application deployment alerts in SCCM](https://www.manageengine.com/sccm-third-party-patch-management/images/sd-dp-stpe7.png) 8. Review the **Summary** page to confirm all selected deployment settings. ![Reviewing SCCM application deployment summary](https://www.manageengine.com/sccm-third-party-patch-management/images/sd-dp-stpe8.png) 9. Click **Next** to complete the wizard. The deployment is created and will run for the target computers according to the configured settings. ![Completing the SCCM application deployment wizard](https://www.manageengine.com/sccm-third-party-patch-management/images/sd-dp-stpe9.png) ## Common SCCM application deployment errors and fixes ### Error: 'Application not detected after installation' The detection rule does not match the installed application. Check the detection method in the application's Deployment Type properties. For third-party applications created by Patch Connect Plus, detection rules are generated automatically based on the application version. If you created the application manually, verify that the detection logic matches the installed file version or registry key. ### Error: 'Content download failed' The application content has not been distributed to a distribution point accessible to the client. Check the content distribution status in SCCM and redistribute the application content if needed. ### Error: 'Requirements not met' The deployment has requirement rules (such as OS version, disk space, or memory) that the target device does not satisfy. Review the **Requirements** tab in the Deployment Type properties and adjust any rules that are too restrictive. ### Error: 'Installation failed, return code 1603' This is a generic MSI installer failure. Common causes include the application already running, a previous version not being fully uninstalled, or an installer requiring elevated permissions. Check `AppEnforce.log` on the client for details of the specific failure. ### Error: 'Superseded or retired' application not deploying The application may have been retired or superseded by another version. Check its status in **Software Library > Application Management > Applications**, review its supersedence settings, and confirm that the intended deployment type remains available.