> 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/remote-ui/overview.md).

# Overview of the Patch My PC Publisher Remote User Interface

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

{% hint style="danger" %}
**PRE-RELEASE DOCUMENTATION**

This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.

Once this feature is released, it will be announced, and this banner will be removed.
{% endhint %}

Patch My PC (PMPC) Publisher consists of two parts:

* **Windows "PatchMyPCService" service -** Which performs key tasks such as cataloging third-party updates and publishing them to Microsoft WSUS, Configuration Manager (ConfigMgr), and Intune. This runs on a server, usually under the **SYSTEM** context or a dedicated service account.
* **Settings console -** Also known as the *user interface*, which is where you configure products, schedules, connections, and options.

Traditionally, the Settings console had to be run directly on the server. The *Remote UI* feature of Publisher removes that requirement, meaning you can now run the Settings console on your own workstation and connect to the **PatchMyPCService** across the network.

## Benefits of using the Remote UI

Using Remote UI offers the following benefits:

* **No more signing in to the server -** Publisher can be managed from your workstation instead of opening a remote desktop session to the server every time.
* **Delegate safely -** Specific administrators can be delegated to manage only the areas of the Publisher they are responsible for (for example, only WSUS, or only Intune), without granting them administrative rights on the server itself.
* **Fits secure environments -** Remote UI only talks to your own Publisher service. It does not need direct Internet access, even to download product or service updates, as these flow through the **PatchMyPCService**.

## How it works

* The **PatchMyPCService** exposes a small, secure management interface on the server.
* Your Settings console connects to that interface using Integrated Windows Authentication, i.e., the same sign in your computer already uses for file shares and other domain resources. You are identified by your Windows account; no password is typed or stored by Publisher.
* Every privileged action still happens on the server, performed by the **PatchMyPCService**. The Settings console simply asks the **PatchMyPCService** to read or change settings on your behalf.
* Your level of access is decided by the groups your user account belongs to on the server (see [Access and Permissions Reference](/patch-my-pc-publisher/remote-ui/technical-references/access-permissions-reference.md) for more information).

## Running Publisher Locally versus Remotely

There are two supported scenarios for running Publisher:

<table><thead><tr><th width="288.4444580078125" valign="top">Scenario</th><th valign="top">What happens</th></tr></thead><tbody><tr><td valign="top"><strong>PatchMyPCService</strong> and Settings console on the same server</td><td valign="top">The Settings console talks to the <strong>PatchMyPCService</strong> locally. This path is always available and needs no certificate.</td></tr><tr><td valign="top">Settings console on a different computer (Remote UI)</td><td valign="top">The Settings console connects across the network over HTTPS. This requires remote access to be turned on and a server certificate to be in place (see <a href="/pages/MC2eSXAc1NMvl8apleJP">Using a Different Computer</a> for more information).</td></tr></tbody></table>


---

# 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/remote-ui/overview.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.
