> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pd-ag/parallels-desktop-business-administrators-guide/deploying-parallels-desktop-for-mac-business-edition/alternative-mass-deployment-via-deployment-package/preparing-the-autodeploy-package/specifying-a-license-key.md).

# Specifying a License Key

A Parallels Desktop for Mac license key is required to activate Parallels Desktop on target Macs. The key must be specified in the autodeploy package.

You can find the primary key in your Business Account customer area as described in [this chapter](https://github.com/Parallels-Corp/DI-OPS-pd-docs/blob/master/evergreen/getting-started/creating-a-business-account-and-registering-your-license.md). There, you can also issue secondary keys that we recommend to use for activation.

{% hint style="warning" %}
**Attention**: For security reasons, we strongly advise against using your primary key directly. Any compromised secondary keys can be deleted and replaced with new ones.
{% endhint %}

To specify the license key:

1. In the autodeploy package, expand the **Parallels Desktop Autodeploy** > **Scripts** > **License Key and Configuration** folder.

   <figure><img src="https://github.com/Parallels-Corp/DI-OPS-pd-docs/blob/master/evergreen/.gitbook/assets/PDFM-121670_Autodeploy_Pkg.png" alt=""><figcaption></figcaption></figure>
2. Open the `deploy.cfg` file in a text editor.
3. Find the `License` section (second from the top) and enter your Parallels Desktop Business Edition license key as a value of the `license_key` variable. The key must be supplied in the following format: "XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX" (including quotes and dashes).
4. Save the `deploy.cfg` file.

{% hint style="warning" %}
**Note:** Parallels Desktop activation requires Internet access. You need to make sure that **port 443** is opened on target Mac computers so they can communicate with the Parallels License Server. You can also verify that the Mac computers can reach the Parallels License Server at [https://desktop.parallels.com](https://desktop.parallels.com/).
{% 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.parallels.com/landing/pd-ag/parallels-desktop-business-administrators-guide/deploying-parallels-desktop-for-mac-business-edition/alternative-mass-deployment-via-deployment-package/preparing-the-autodeploy-package/specifying-a-license-key.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.