> 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/deploying-the-package-to-macs.md).

# Deploying the Package to Macs

This section contains instruction on how to deploy the Parallels Desktop autodeploy package using the following solutions:

* [Jamf Pro](/landing/pd-ag/parallels-desktop-business-administrators-guide/deploying-parallels-desktop-for-mac-business-edition/alternative-mass-deployment-via-deployment-package/deploying-the-package-to-macs/example-jamf-pro.md)

{% hint style="warning" %}
**Note:** In some cases, when deploying the Parallels Desktop autodeploy package on a computer running macOS Catalina or later, you may get an error message saying, "*Parallels Desktop Autodeploy.pkg cannot be opened because the developer cannot be verified*".\
\
To work around this issue, please do the following. Once you have prepared the autodeploy package (but before you deploy it), right-click on the package and select **Open** from the context menu. In the dialog that opens, click the **Open** button and wait until macOS completes the file verification. Once the file is verified, use the deployment tool of your choice to deploy the package. See also <https://kb.parallels.com/124989>
{% 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 dynamically 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/deploying-the-package-to-macs.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 `build a script that syncs our docs to a CMS` 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.