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.

Important

This section must be correctly configured before the Publisher can create ConfigMgr applications or the App Manager 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. 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.

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 and the Sync Schedule tab.

See Configure the SMS Provider Connection for details on how to configure the SMS Provider connection.

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.

Note

Publisher automatically creates a root Applications folder in the configured UNC source path, which you cannot modify.

All application content generated by Publisher is stored beneath this folder, with vendor and product-specific subdirectories created automatically as applications are published.

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.

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.

Note

See Content Source Folder for more information on requirements.