> 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/connection-source.md).
# Connection and Source section in Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
The **CONNECTION AND SOURCE** section on the **Base Install Options** tab of Patch My PC (PMPC) Publisher defines how Publisher connects to Microsoft Configuration Manager (ConfigMgr) and where it stores application source content.
{% hint style="danger" %}
**Important**
This section must be correctly configured before the Publisher can create ConfigMgr applications or the [App Manager](/patch-my-pc-publisher/manage/configmgr-apps-tab/app-manager.md) can be used.
{% endhint %}
These settings control communication with the SMS Provider and establish the root location used for all Publisher-created ConfigMgr application content. Incorrect configuration can prevent applications from being created, updated, or managed successfully.
## Configure SMS Provider Connection
The *SMS Provider* is the interface that enables all interactions with ConfigMgr, including actions performed in the ConfigMgr console and through supported APIs. Publisher also relies on the SMS Provider to perform operations such as triggering Software Update Point (SUP) synchronizations, creating and modifying applications, and distributing content.
{% hint style="info" %}
**Note**
The SMS Provider configuration is shared across Publisher. When you configure the SMS Provider from the **CONNECTION AND SOURCE** section, the same settings are automatically used in other areas of Publisher, including [WSUS Options](/patch-my-pc-publisher/manage/wsus-updates-tab/wsus-options.md) and the [Sync Schedule](/patch-my-pc-publisher/manage/sync-tab.md) tab.
See [Configure the SMS Provider Connection](/patch-my-pc-publisher/technical-references/configure-sms-provider.md) for details on how to configure the SMS Provider connection.
{% endhint %}
## Source folder
The **Source folder** field needs to be configured as every ConfigMgr application relies on a defined content source location for each deployment type. The path specified is the authoritative location where application files are stored and managed before they are distributed to the Content Library and used by clients.
The image below correlates a source folder configured in Publisher with the Deployment Type Content Location in ConfigMgr.
{% hint style="info" %}
**Note**
Publisher automatically creates a root **Applications** folder in the configured UNC source path, which you cannot modify.
{% endhint %}
All application content generated by Publisher is stored beneath this folder, with vendor and product-specific subdirectories created automatically as applications are published.
{% hint style="success" %}
**Tip**
Each application version is stored in its own UniqueID folder. This results in multiple UniqueID folders under a single application folder, allowing Publisher to track individual application versions and manage application lifecycles correctly.
Application content is stored using the following structure:
**SourceFolder\Applications\Vendor\Application\UniqueID**
When application retention is enabled, retained application content UniqueID folders are moved into a **Retained Apps** folder under **SourceFolder\Applications\Vendor\Application**.
{% endhint %}
{% hint style="danger" %}
**Important**
The source folder structure is critical to Publisher operations. Publisher evaluates both the ConfigMgr database object and the corresponding content directories when deciding on application retention, upgrades, and lifecycle management.
Manually modifying, moving, or deleting folders within this structure can cause inconsistencies between ConfigMgr and the content source, which may lead to unexpected behavior or management issues later.
{% endhint %}
{% hint style="info" %}
**Note**
See [Content Source Folder](/patch-my-pc-publisher/requirements/configmgr-requirements/permissions.md#content-source-folder) for more information on requirements.
{% endhint %}
---
# 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/connection-source.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.
