# Connection and Source Options
*Applies to: Patch My PC Publisher*
## Overview
The **Connection and Source Options** section defines how the Publisher connects to ConfigMgr and where application source content is stored on disk. This section must be correctly configured before the Publisher can create ConfigMgr applications or the [ConfigMgr Appliction Manager](https://docs.patchmypc.com/patch-my-pc-publisher/administration/configmgr-apps/form-controls/configmgr-application-manager) utility can be used.
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. The Publisher also relies on the SMS Provider to perform operations such as triggering SUP synchronizations, creating and modifying applications, and distributing content.
The SMS Provider configuration is shared across the Publisher. When you configure the SMS Provider from [ConfigMgr Apps > Options](https://docs.patchmypc.com/patch-my-pc-publisher/administration/configmgr-apps/options), the same settings are automatically used in other areas of the product, including [Updates > Options](https://docs.patchmypc.com/patch-my-pc-publisher/administration/updates/options) and the [Sync Schedule](https://docs.patchmypc.com/patch-my-pc-publisher/administration/sync-schedule) tab.
To connect to the SMS Provider, the [ConfigMgr Remote Console is required](https://docs.patchmypc.com/patch-my-pc-publisher/publisher-requirements/configmgr-requirements/software) to be installed on the same device as the Publisher. If the ConfigMgr Remote Console is *not* installed, the following message is also indicated in the Publisher when attempting to Configure the SMS Provider.
The PatchMyPC.log will also indicate when the ConfigMgr Remote Console is not installed:
`An error occurred Error checking ConfigMgr connection: Unable to find the Assembly: AdminUI.WqlQueryEngine, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 [PatchMyPC_Core.Exceptions.ConfigApiException] HResult: -2146233088`
For information on how to configure the SMS Provider connection, please see: [Configure the SMS Provider Connection](https://docs.patchmypc.com/patch-my-pc-publisher/publisher-reference/configure-the-sms-provider-connection).
## Source Folder
The **Source Folder** is required because every ConfigMgr application relies on a defined content source location for each deployment type. This source path 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 Deployemnt Type Content Location in ConfigMgr.
{% hint style="info" %}
**Note**
The Publisher automatically creates a root **Applications** folder in the configured UNC source path. The name of this folder is not configurable.
{% endhint %}
All application content generated by the 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 the 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="warning" %}
**Important**
The source folder structure is critical to the Publisher operations. The Publisher evaluates both the ConfigMgr database object and the corresponding content directories when making decisions about 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 %}
For more information on the requirements, see: [Permissions](https://docs.patchmypc.com/publisher-requirements/configmgr-requirements/permissions#content-source-folder).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.patchmypc.com/patch-my-pc-publisher/administration/configmgr-apps/options/connection-and-source-options.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
