> 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/overview.md).
# Overview of Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
Patch My PC (PMPC) Publisher is our on-premises publishing service that automates the creation, update, and lifecycle management of third-party applications and updates for Microsoft management platforms such as Configuration Manager (ConfigMgr), WSUS, and Intune.
Publisher integrates with:
* Microsoft Windows Server Update Services (WSUS)
* Microsoft Configuration Manager (ConfigMgr)
* Microsoft Intune
It allows organizations to deploy and maintain third-party software using the same native workflows they already use for Microsoft updates and applications.
## Capabilities
Publisher downloads the Patch My PC catalog to retrieve curated metadata for third-party applications. Based on your configuration, it can:
* Publish third-party updates to WSUS.
* Create and update applications in ConfigMgr.
* Create and update Win32 apps (and updates) in Intune.
* Maintain and update previously published third-party applications and updates.
All publishing actions respect the target platform's native security, authentication, and deployment mechanisms.
Publisher does not replace WSUS, ConfigMgr, or Intune. It extends them by automating third-party application packaging and update publishing.
---
# 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/overview.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.
