> 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-publisherv2/scenario-based-guidance/product-selection-and-discovery/scenario-1-configmgr-applications.md).
# Scenario 1: ConfigMgr Applications
*Applies to: Patch My PC Publisher V2.x*
## Overview
This page provides guidance on how to discover applications in your environment or manually select products for publishing as ConfigMgr applications using the Publisher.
You can scan the ConfigMgr database to automatically discover supported products installed in your environment, or manually browse and select products directly from the Publisher catalog.
After completing the steps in this section, you will be able to enable and publish third party applications that align with your environment’s needs.
## Discovering and Selecting Applications
You can enable applications for publishing in one of two ways:
* [Automatically discover installed products by scanning the ConfigMgr database using the Scan Wizard](#automatically-discover-installed-products-by-scanning-the-configmgr-database-using-the-scan-wizard).
* [Manually browse and select products directly from the product tree on the ConfigMgr Apps tab](#manually-browse-and-select-products-directly-from-the-product-tree-on-the-configmgr-apps-tab).
### Automatically discover installed products by scanning the ConfigMgr database using the Scan Wizard
The [Scan Wizard](/patch-my-pc-publisherv2/administration/configmgr-apps/form-controls/scan-configmgr-database-for-supported-products.md) is generally a recommended starting point. It leverages ConfigMgr hardware inventory data to identify supported third-party products currently present in your environment and compares those results against the Patch My PC catalog. This allows you to review what is installed *today* before enabling publishing.
After running a scan, review the results carefully. The device count and version information help validate inventory accuracy and determine publishing priority. Exporting the results to CSV can assist with internal review, change control discussions, or phased rollout planning.
A common and effective approach is to begin conservatively. Enable a small number of familiar, low-impact applications to understand how ConfigMgr applications are created by the Publisher. Many customers start with widely used utilities such as 7-Zip or Notepad++ to gain confidence in the workflow.
Once you are comfortable with how applications are created and maintained, you can expand product selections or consider enabling [auto-publishing rules](/patch-my-pc-publisherv2/administration/configmgr-apps/form-controls/scan-configmgr-database-for-supported-products.md#auto-enable-products-to-be-published-as-an-application) to automate application lifecycle management over time to create new applications based on discovery thresholds.
### Manually browse and select products directly from the product tree on the ConfigMgr Apps tab
Applications can also be enabled manually by selecting products directly from the [product tree](/patch-my-pc-publisherv2/administration/configmgr-apps/product-tree.md) on the [ConfigMgr Apps](/patch-my-pc-publisherv2/administration/configmgr-apps.md) tab.
Manual selection remains a valid and flexible option, especially when you want to proactively publish applications that may not yet appear in the inventory returned by the scan results.
You can expand vendors to browse available products or use the [Search](/patch-my-pc-publisherv2/administration/configmgr-apps/form-controls/search-products.md) form control to quickly locate a specific application by name.
When selecting products, we recommend to standardize on a single installer variant whenever multiple options are available. For example, some products may provide:
* MSI and EXE variants
* x86 and x64 architectures
* ARM64 variants
In most environments, it is recommended to standardize on a single architecture and installer type, such as **MSI (x64)**, unless there is a specific requirement for an alternative variant.
{% hint style="info" %}
**Note**
This guidance applies to specifically to applications. For updates, it is common to publish multiple variants if they currently exist in your environment, particularly while working toward a longer term standardization strategy.
{% endhint %}
As a best practice, begin by enabling a small number of familiar, low-impact applications to understand how ConfigMgr applications are created by the Publisher. Many customers start with widely used utilities such as 7-Zip or Notepad++ to gain confidence in the workflow.
---
# 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-publisherv2/scenario-based-guidance/product-selection-and-discovery/scenario-1-configmgr-applications.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.
