> 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-client/prerequisites.md).

# Patch My PC Client Prerequisites

*Applies to: Patch My PC Client*

The Patch My PC (PMPC) Client has the following Prerequisites:

* You must use the PMPC Portal, and it must be connected to your Intune tenant.
* Your PMPC company must be connected to the same Intune tenant used to manage the devices from which you want to gather reporting data.
* You need to use PMPC Cloud to deploy and manage your third-party apps, updates, and Custom Apps.
* If you have TLS encryption enabled on your endpoints, you need to bypass the following:

<table><thead><tr><th width="217" valign="top">Domain</th><th width="249.99993896484375" valign="top">Reason</th><th width="69.00006103515625" valign="top">Port</th><th width="115.33331298828125" valign="top">Protocol</th></tr></thead><tbody><tr><td valign="top">portal.patchmypc.com</td><td valign="top">Client enrollment/Region discovery</td><td valign="top">443</td><td valign="top">https</td></tr><tr><td valign="top">*.patchmypc.com</td><td valign="top">Client communication</td><td valign="top">443</td><td valign="top">https</td></tr></tbody></table>

* Configure an **allow** rule on your firewall for the following:

<table><thead><tr><th width="216.99993896484375" valign="top">Domain</th><th width="249.99993896484375" valign="top">Reason</th><th width="69.00006103515625" valign="top">Port</th><th width="115.33331298828125" valign="top">Protocol</th></tr></thead><tbody><tr><td valign="top">portal.patchmypc.com</td><td valign="top">Client enrollment/Region discovery</td><td valign="top">443</td><td valign="top">https</td></tr><tr><td valign="top">us.portal.patchmypc.com</td><td valign="top">Client communication</td><td valign="top">443</td><td valign="top">https</td></tr><tr><td valign="top">eu.portal.patchmypc.com</td><td valign="top">Client communication</td><td valign="top">443</td><td valign="top">https</td></tr><tr><td valign="top">api.patchmypc.com</td><td valign="top">Client communication</td><td valign="top">443</td><td valign="top">https</td></tr><tr><td valign="top">*.digicert.com</td><td valign="top">CRL checking</td><td valign="top">80</td><td valign="top">http</td></tr></tbody></table>

{% hint style="danger" %}
**Important**

Wildcard entries in this article do not cover apex hosts.
{% endhint %}


---

# 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-client/prerequisites.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.