> 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/installation-guides/configmgr.md).

# Install Publisher with ConfigMgr

This guide will walk you through the process of installing the publisher in a Configuration Manager environment.

*Applies to: On-premises Publisher*

## Before Getting Started

Here are a few important resources below you get started.

### Free 30-day trial

{% hint style="info" %}
Before you get started, make sure you take advantage of our [free trial](https://patchmypc.com/free-trial)!
{% endhint %}

### Free Setup Call with an Engineer

{% hint style="success" %}
**Tip**: Did you know you can schedule a free setup call with an engineer if you prefer to have an engineer from Patch My PC perform a guided install with you in your environment?

\
<https://patchmypc.com/setup-call>
{% endhint %}

### Video Installation Guide

If you prefer using a video guide, you can watch the video version below.

{% embed url="<https://www.youtube.com/watch?v=lTajAHmxsCY>" %}

### Continue Guide

Next up, start with the **requirements**

{% content-ref url="/pages/-MYtJmfpYiuK80SPJb4t" %}
[Requirements](/installation-guides/configmgr/requirements.md)
{% endcontent-ref %}


---

# 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/installation-guides/configmgr.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.