> 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/network.md).

# ConfigMgr Network Requirements for Patch My PC Publisher

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

If Patch My PC (PMPC) Publisher is installed on the Microsoft ConfigMgr Site Server, no additional network requirements are needed beyond those listed on the [core Publisher requirements](/patch-my-pc-publisher/requirements/core-requirements.md) page.

However, if Publisher is installed on a remote device, the following additional requirements must also be met:

<table><thead><tr><th width="137" valign="top">Remote Port</th><th width="104" valign="top">Protocol</th><th width="161" valign="top">Purpose</th><th width="177" valign="top">Direction</th></tr></thead><tbody><tr><td valign="top">1433</td><td valign="top">TCP</td><td valign="top">Scan for supported products</td><td valign="top">Publisher TO Configmgr SQL Server</td></tr><tr><td valign="top">135</td><td valign="top">TCP</td><td valign="top">RPC Endpoint Mapper</td><td valign="top">Publisher TO SMS Provider</td></tr><tr><td valign="top">445</td><td valign="top">TCP</td><td valign="top">SMB</td><td valign="top">Publisher TO Server hosting the Content Source Folder</td></tr><tr><td valign="top">49152 - 65535 *</td><td valign="top">TCP</td><td valign="top">RPC Dynamic Port Range</td><td valign="top">Publisher TO SMS Provider</td></tr></tbody></table>

**\*** Default dynamic RPC port range.

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

The Site Server ultimately determines which SMS Provider is contacted. Consideration should be given to all Site Systems that hold the SMS Provider Site System role.
{% 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/requirements/configmgr-requirements/network.md?ask=<question>&goal=<user_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.