> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/configmgr-apps-tab/app-manager.md). # App Manager in Patch My PC Publisher *Applies to: Patch My PC Publisher V3.x* Clicking the **App Manager** tab under the **ConfigMgr Apps** section in Patch My PC (PMPC) Publisher opens **App Manager**, which lets you view and manage applications in ConfigMgr that were created using Publisher. It provides a centralized interface to review application properties, deployments, task sequence usage, and dependency relationships before performing application cleanup.
App Manager
App Manager queries the ConfigMgr SMS Provider and displays only applications published by Publisher. {% hint style="info" %} **Note** Publisher relies on both the application XML representation stored in the ConfigMgr database and the associated content source folders to validate previous update versions and retained application chains. These components are evaluated together by Publisher to ensure application retention and lifecycles are managed correctly. Removing an application directly from the ConfigMgr console deletes the console object but does not remove the corresponding content source folder from disk. This leaves orphaned content remaining on disk. Whilst Publisher is designed to tolerate this condition, it is not the recommended cleanup approach. App Manager is the preferred tool when performing application cleanup for Publisher-created applications. It ensures that the ConfigMgr application object and the related content source paths are removed together, maintaining consistency between the console and the file system. {% endhint %} The table below outlines the available columns in this form:
Column nameDescription
PublisherDisplays the software vendor associated with the application as identified by Publisher's metadata.
TitleShows the application name as it appears in the ConfigMgr console.
VersionIndicates the application version defined during publishing. This value is used by Publisher to evaluate update ordering and supersedence.
Release DateDisplays the date the application was published (created) in ConfigMgr.
DeploymentsShows the number of active ConfigMgr deployments associated with the application.
DependenciesDisplays the number of dependency relationships where this application depends on another application.
Dependent DTsShows how many deployment types depend on this application. This indicates downstream usage that can block deletion.
Dependent TSDisplays the number of task sequences that reference this application.
Model NameDisplays the internal ConfigMgr CI Unique ID for the application. This value is primarily used for backend identification and troubleshooting. This column is not displayed by default.
{% hint style="success" %} **Tip** Right-clicking any column heading allows you to choose which columns are displayed and also to use drag-and-drop to put them in a custom order. Clicking a column heading also changes it's sort order. Highlighting a row in the application results table and pressing **Ctrl + C** will copy the entire row to the clipboard. This is useful for application management and troubleshooting scenarios. {% endhint %} {% hint style="info" %} **Note** Applications referenced by task sequences cannot be deleted until those references are removed. {% endhint %} ## Search The **Search** field is used to quickly filter results in App Manager. When application results are already displayed, the list is filtered automatically as you type. No additional action is required to apply the search. The search evaluates all visible columns in the results grid. Matching results are shown dynamically based on the entered text. Clearing the search field restores the full list of results. ## Refresh button Clicking **Refresh** refreshes the data from ConfigMgr to ensure the application information displayed is up-to-date. ## Select All/Select None buttons Clicking **Select All** selects every application currently visible in the list. This is commonly used when performing bulk actions such as deleting multiple applications. Clicking **Select None** clears any current selection. ## Extract Content button Clicking **Extract Content** copies the source content of the selected applications to a folder. This action is commonly used to review, validate, or back up application files before making cleanup decisions in ConfigMgr. Multiple applications can be selected at the same time using **Ctrl + Click** or **Shift + Click**. When multiple applications are selected, the **Extract Content** action processes each application in a single operation and stages the content together. ### To extract the content for one or more published applications 1. Load Publisher. 2. Navigate to the **ConfigMgr Apps** tab and click **App Manager** to launch it. 3. Locate the application or applications you want to extract the content for using the available filters. 4. Click the relevant applications. 5. Click **Extract Content**.
Clicking 'Extract Content'.
6. On the **ConfigMgr App Extraction** screen, enter the name of the folder you want to extract the content to, then click **OK**.
'ConfigMgr App Extraction' screen
{% hint style="info" %} **Note** The destination can either be a local path or a valid UNC path. If the specified folder does not exist, it will be created automatically. {% endhint %} The content is then extracted, and once the extraction is complete, the **Bulk Export Complete** dialog is displayed showing the results of the export.
'Bulk Export Complete' dialog
After you click **OK**, Windows Explorer opens the folder selected for the extraction so that you can review the results. {% hint style="info" %} **Note** Each application is written to its own subfolder within the selected destination, making it easier to inspect version-specific files and decide whether to retain the content or safely remove it. Only applications with available source content can be extracted. If the destination folder does not already exist, it is created automatically during the extraction process. {% endhint %} ## Delete Deployment(s) button Clicking **Delete Deployment(s)** removes all ConfigMgr deployments associated with the selected applications. This action does not delete the applications themselves. The **Deployments** column shows the total number of deployments for each application. Reviewing this column before proceeding helps confirm the scope of the action. {% hint style="success" %} **Tip** Multiple applications can be selected at the same time using **Ctrl + Click** or **Shift + Click**. When multiple applications are selected, deployments for all selected applications are removed in a single operation. {% endhint %} ### To delete deployments for one or more applications 1. Locate the applications whose deployments you want to remove by using the available filters. 2. Click to select the required applications. 3. Click **Delete Deployment(s)**. 4. When prompted, review the confirmation dialog and confirm that you want to remove all deployments for the selected applications. After confirmation, Publisher removes the deployments from ConfigMgr. The application objects and their content remain unchanged. ## Delete Application(s) button Clicking **Delete Application(s)** deletes all the selected applications. Multiple applications can be selected at the same time using **Ctrl + Click** or **Shift + Click**. ### To delete one or more applications 1. Locate the applications you want to delete by using the available filters. 2. Click to select the required applications. 3. Click **Delete Application(s)**. 4. When prompted, review the confirmation dialog and confirm that you want to delete the selected applications. After confirmation, Publisher removes the selected applications from ConfigMgr and also the related content from disk. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.patchmypc.com/patch-my-pc-publisher/manage/configmgr-apps-tab/app-manager.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.