> 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/base-install-options/content-distribution.md).
# Content Distribution section in Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
The **CONTENT DISTRIBUTION** section on the **Base Install Options** tab of Patch My PC (PMPC) Publisher controls how Publisher distributes application content to ConfigMgr Distribution Points (DPs) when apps are published.
By default, Publisher automatically distributes application content as soon as you create a new application. This ensures content is available on DPs as soon as possible, preventing deployment failures caused by missing or undistributed content.
## **Automatically distribute content for any newly created applications**
When you enable the **Automatically distribute content for any newly created applications** option (which is by default), and no DP Groups are configured, Publisher distributes content to all DPs in the site. This is the most common configuration and ensures applications are broadly available without additional administrative effort.
If the **Automatically distribute content for any newly created applications** option is disabled, Publisher does not distribute any content. In this scenario, administrators must manually distribute content using the ConfigMgr console after creating or updating applications. This approach is generally not recommended, as it increases operational overhead and can lead to deployment failures if content distribution is missed or delayed.
## Manage Distribution Point Group(s)
When Publisher is configured to use DP Groups (by clicking **Manage Distribution Point Group(s)**), Publisher distributes content only to the DPs in those groups. This allows administrators to control distribution scope and reduce unnecessary replication.
### To Manage Distribution Point Group(s)
1. Load Publisher.
2. Navigate to **ConfigMgr Apps | Base Install Options**.
3. Scroll down to the **Content Distribution Options** section and click **Manage Distribution Point Group(s)**.
4. On the **Select DP Groups for Content Distribution** screen, check the relevant checkboxes then click **OK**.
In the following example, the environment includes a DP Group containing a Cloud Management Gateway (CMG). The administrator does **not** want Publisher to automatically distribute application content to the CMG.
To achieve this, only the on-premises DP Group (**BBCM1**) checkbox is checked on the **Select DP Groups for Content Distribution** screen, whilst the checkbox group containing the CMG (**BBCMG1**), is left unchecked.
---
# 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/base-install-options/content-distribution.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.
