> 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/requirements/configmgr-requirements/software.md).

# ConfigMgr Software Requirements for Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

Patch My PC (PMPC) Publisher has the following ConfigMgr Software Requirements:

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><a href="#configmgr-operating-systems">Operating Systems</a></td><td valign="top"><a href="#configmgr-supported-versions">Supported Versions</a></td><td valign="top"><a href="#configmgr-remote-console">Remote Console</a></td><td valign="top"><a href="#wsus-role">WSUS Role</a></td></tr></tbody></table>

## ConfigMgr Operating Systems

Publisher supports Microsoft Configuration Manager (ConfigMgr) when it is installed on versions of Windows Server currently supported by Microsoft’s supported lifecycle.

{% hint style="info" %}
**Note**

Use the [Search Product and Services Lifecycle Information](https://learn.microsoft.com/en-us/lifecycle/products/) page to determine which versions of Windows Server are currently supported.
{% endhint %}

{% hint style="danger" %}
**Important**

Publisher can be installed on Windows 11 only if it is used solely to publish applications and updates to Intune.
{% endhint %}

## ConfigMgr Supported Versions

ConfigMgr uses a Current Branch servicing model with two releases per year, typically in March and September. Each version is supported by Microsoft for 18 months from its release date. After 18 months, support ends for a version, and it no longer receives updates or technical support from Microsoft.

{% hint style="info" %}
**Note**

Starting with version 2609, ConfigMgr will transition to a single, annual release cadence.
{% endhint %}

Publisher supports ConfigMgr versions that are still within Microsoft’s supported lifecycle.

{% hint style="info" %}
**Note**

See [Microsoft Configuration Manager](https://learn.microsoft.com/en-us/lifecycle/products/microsoft-configuration-manager) for more details of the support dates for each version of ConfigMgr.
{% endhint %}

{% hint style="danger" %}
**Note**

Running unsupported or end-of-life versions of ConfigMgr is unsupported.
{% endhint %}

## ConfigMgr Remote Console

The ConfigMgr Remote Console exposes some SDK helper files Publisher utilizes to connect to the SMS Provider.

{% hint style="info" %}
**Note**

See [Install the Configuration Manager console](https://learn.microsoft.com/intune/configmgr/core/servers/deploy/install/install-consoles) for more information on how to install the console.
{% endhint %}

{% hint style="success" %}
**Tip**

The installation file for the remote console is typically located on the Site Server share, e.g.:

**\\\site-server.contoso.com\SMS\_xxx\tools\ConsoleSetup\ConsoleSetup.exe**
{% endhint %}

{% hint style="danger" %}
**Important**

A reboot is normally required after installing the ConfigMgr remote console; otherwise, you might see the following error logged in **PatchMyPC.log**:

*`An error occurred while connecting to Sms provider as System: Unable to find the Assembly: AdminUI.WqlQueryEngine, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 [PatchMyPC_Sccm.AssemblyResolver+AssemblyNotFoundException] HResult: -2146233088`*
{% endhint %}

If the ConfigMgr Remote Console is *not* installed, the following message is also indicated in the Publisher when attempting to [Configure the SMS Provider](/patch-my-pc-publisher/manage/configmgr-apps-tab/base-install-options/connection-source-options.md#configure-sms-provider-connection).

<figure><img src="/files/4qcJPalnD1a9ey9mSIFG" alt="Configure the SMS Provider - Missing SDK" width="563"><figcaption></figcaption></figure>

## WSUS Role

For Publisher to code-sign PowerShell detection scripts for ConfigMgr applications, the WSUS role must be installed on the Publisher system.

While [limited WSUS API access](/patch-my-pc-publisher/requirements/intune-requirements/software.md#install-the-wsus-updateservices-api) may be sufficient for some operations (such as deserializing the Patch My PC Catalog), Publisher can *only* use code-signing certificates to sign ConfigMgr detection scripts from the WSUS local certificate store.

Certificates located in other Windows certificate stores are not supported for signing ConfigMgr application detection scripts.

Additionally, the WSUS role is required to publish updates, selected on the [WSUS Updates ](/patch-my-pc-publisher/manage/wsus-updates-tab.md)tab, which are synchronized from WSUS into ConfigMgr during a SUP sync.

{% hint style="info" %}
**Note**

See [WSUS Requirements](/patch-my-pc-publisher/requirements/wsus-requirements.md) for more information about the WSUS role 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/requirements/configmgr-requirements/software.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
