> 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/install/where.md). # Where to Install Patch My PC Publisher *Applies to: Patch My PC Publisher V3.x* Where you install Patch My PC (PMPC) Publisher depends on your environment: * [ConfigMgr (with WSUS)](#configmgr-with-wsus) * [ConfigMgr (with WSUS and remote SUP)](#configmgr-with-wsus-and-remote-sup) * [WSUS only (no ConfigMgr)](#wsus-only-no-configmgr) * [Intune only](#intune-only) * [Mixed environments](#mixed-environments) {% hint style="success" %} **Tip** Please review the [Core Requirements for Publisher](/patch-my-pc-publisher/requirements/core-requirements.md) before continuing, as these apply regardless of the platform being used, before beginning installation. {% endhint %} ## ConfigMgr (with WSUS) When using Publisher to publish both applications and updates to Microsoft ConfigMgr, Publisher should be installed on the top-level Software Update Point (SUP). In a ConfigMgr hierarchy, this would typically be the CAS, which holds the SUP Site System role. This allows Publisher to publish updates directly into WSUS using the local WSUS API, ensuring that update metadata is created locally and then inherited naturally by any downstream WSUS servers. ### ConfigMgr (with WSUS and remote SUP) In some environments, the SUP role is hosted on a remote Site System rather than the Site Server itself. In these cases, Publisher should be installed on that remote server, provided it is the top-level SUP. The key requirement is not the Site Server, but the server hosting the top-level WSUS instance, as Publisher must be co-located with WSUS to successfully publish update metadata. ## WSUS only (no ConfigMgr) For environments using WSUS only (without ConfigMgr), Publisher must be installed on the top-level WSUS server, as this is where update metadata is authored. When WSUS synchronizes, that metadata is then replicated to any downstream WSUS servers, ensuring consistency across the hierarchy. ## Intune only If you are using Publisher for Intune publishing only, it does not need to be installed on a WSUS or ConfigMgr server and can be installed on any suitable Windows system (see [Core Software Requirements](/patch-my-pc-publisher/requirements/core-requirements.md#software) for supported operating systems). As Publisher can create and manage applications and updates in Intune (through direct communication with Intune via Graph calls), it should be treated as a high-trust system and secured accordingly, with restricted access and appropriate credential protection. {% hint style="success" %} **Tip** Some customers who use only Intune choose to install Publisher on a dedicated Azure virtual machine. A B2-size virtual machine or equivalent is commonly used. The virtual machine should still meet or exceed the [minimum core requirements](/patch-my-pc-publisher/requirements/core-requirements.md) and [additional requirements needed for Intune publishing](/patch-my-pc-publisher/requirements/intune-requirements.md). {% endhint %} {% hint style="info" %} **Note** If you intend to publish third-party applications and updates to Intune only, we generally recommend using Patch My PC Cloud, our cloud-based service, as it removes the need to manage on-premises infrastructure and simplifies ongoing operations. However, some customers are required to use Publisher instead (such as those with restrictions around enterprise application usage, environments that require GCC High, or scenarios where cloud-hosted services are not permitted). In these cases, Publisher provides a fully supported alternative that allows publishing to Intune whilst keeping control within your environment. {% endhint %} ## Mixed environments If you are publishing updates to both ConfigMgr/WSUS and Intune, you should install Publisher on the top-level WSUS/SUP server. --- # 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/install/where.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.