# Download and Install *Applies to: Patch My PC Publisher* {% hint style="success" %} Please review the [core Publisher requirements](https://docs.patchmypc.com/patch-my-pc-publisher/publisher-requirements/core-requirements), which apply regardless of the platform being used, before beginning installation. {% endhint %} ## Where should I install the Publisher? When using the Publisher to publish both applications and updates to ConfigMgr, it should be installed on the top-level Software Update Point (SUP). In a ConfigMgr hierarchy, this would typically be the CAS which holds the Software Update Point 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. In some environments, the Software Update Point role is hosted on a remote site system rather than the site server itself. In these cases, the 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 the Publisher must be co-located with WSUS to successfully publish update metadata. For environments using WSUS only (without ConfigMgr), the same principle applies. The 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. If you are using the 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 [Publisher Requirements](https://docs.patchmypc.com/publisher-requirements/core-requirements#software) for supported operating systems). Because Publisher is capable of creating and managing applications and updates in Intune, it should be treated as a high-trust system and secured accordingly, with restricted access and appropriate credential protection. Use the table below to understand where the Publisher should be installed in your environment. | Scenario | Where to install Publisher | Note | | ---------------------------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- | | **ConfigMgr (with WSUS)** | **Top-level SUP** | The Publisher uses the local WSUS API to publish update metadata. Downstream WSUS servers inherit metadata automatically. | | **ConfigMgr (with WSUS and remote SUP)** | **Remote site system hosting the top-level SUP** | The Publisher must be installed on the server hosting the top-level WSUS instance, not necessarily the site server. | | **WSUS only (no ConfigMgr)** | **Top-level WSUS server** | Update metadata must be created on the upstream WSUS server so it can replicate to downstream WSUS servers. | | **Intune only** | **Any suitable Windows system** | The Publisher communicates directly with Intune via Microsoft Graph. | | **Mixed environments** | **Top level WSUS Server /** **SUP** | Install the Publisher on the top-level WSUS/SUP server if publishing updates to both ConfigMgr/WSUS and Intune. | {% hint style="success" %} **Tip** Some customers who use Intune only choose to install the 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](https://docs.patchmypc.com/patch-my-pc-publisher/publisher-requirements/core-requirements) and [additional requirements needed for Intune publishing](https://docs.patchmypc.com/patch-my-pc-publisher/publisher-requirements/intune-requirements). {% 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 the 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, the Publisher provides a fully supported alternative that allows publishing to Intune while keeping control within your environment. {% endhint %} ## Download the Publisher To download the Publisher installer, follow the steps below: 1. Open a web browser. 2. Navigate to the following URL:\ [**https://patchmypc.com/msi**](https://patchmypc.com/msi) {% hint style="info" %} **Note** SHA256: 97979d37fd8c0ed0c0609837b595e1a25878282289545bd75ab956b0effef026 {% endhint %} 1. The download will begin automatically.
Download the Publisher from https://patchmypc.com/msi
2. Once complete, confirm that the file **`PatchMyPC-Publishing-Service.msi`** has been downloaded. 3. Copy the installer to the target server, if required, then proceed to [Install the Publisher](#install-publisher). ## Install the Publisher After carefully observing and understanding the [requirements](https://docs.patchmypc.com/patch-my-pc-publisher/publisher-requirements), install Publisher by following the steps below: 1. Once you have [downloaded the Publisher](#download-publisher), double click the msi to launch the installer. 2. Click **Next** to begin the installation wizard. Agree to the terms of service and click **Next** again.
Install Publisher and accept the end-user license agreement
3. If you are only using the Publisher to publish applications and updates in Intune, you can check the **Enable Microsoft Intune standalone mode\*** box. Click **Next**.
Optionally select Intune standalone mode
\*Intune standalone mode simply removes some tabs in the Publisher that are specifically used for publishing applications and updates to ConfigMgr and WSUS. These tabs can be re-enabled retrospectively after installation from the Advanced tab in Publisher. 4. Select a folder to install the Publisher, and click **Next**. The default folder is `C:\Program Files\Patch My PC\Patch My PC Publishing Service\`.
Select the folder for the Publisher installation files
5. When you are ready to being, click **Install**.
Begin Publisher installation
6. Click **Yes** if you receive a UAC prompt. When installation has completed, you can choose to not immediately launch the Publisher by un-checking **Launch Patch My PC Publishing Service**. Click **Finish**.
Authorize and Complete Installation
### What Next? Once the Publisher is installed, configure it based on how you plan to use it. Choose the scenario that best matches your environment: * [Scenario 1: ConfigMgr - Applications only](https://docs.patchmypc.com/patch-my-pc-publisher/scenario-based-guidance/installation-and-configuration/scenario-1-configmgr-applications-only) * [Scenario 2: ConfigMgr - Applications and Updates (WSUS)](https://docs.patchmypc.com/patch-my-pc-publisher/scenario-based-guidance/installation-and-configuration/scenario-2-configmgr-applications-and-updates-wsus) * [Scenario 3: WSUS (Standalone)](https://docs.patchmypc.com/patch-my-pc-publisher/scenario-based-guidance/installation-and-configuration/scenario-3-wsus-standalone) * [Scenario 4: Intune – Applications and Updates](https://docs.patchmypc.com/patch-my-pc-publisher/scenario-based-guidance/installation-and-configuration/scenario-4-intune-applications-and-updates) * [Scenario 5: Mixed environment (ConfigMgr, WSUS and Intune)](https://docs.patchmypc.com/patch-my-pc-publisher/scenario-based-guidance/installation-and-configuration/scenario-5-mixed-environment-configmgr-wsus-and-intune) --- # 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/download-and-install.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.