> 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/provisioning-and-activation-of-parallels-desktop/alternative-deployment-methods/alternative-mass-deployment-via-deployment-package.md).

# Mass Deployment via Deployment Package

This section describes deploying Parallels Desktop for Mac inside a prepared deployment package. This method offers a couple of distinctive benefits:

1. It requires no interaction from end users: as a result, they get Parallels Desktop with one or more virtual machines already installed.
2. It allows deploying more than one pre-configured virtual machines per user.

However, this method requires more work and care, so if the above benefits do not apply to your case, we recommend that you try the [default way](/landing/pd-ag/provisioning-and-activation-of-parallels-desktop/mass-deployment-using-mac-management-tools/recommended-deploying-parallels-desktop-via-mdm-app-catalogs-using-configuration-profiles.md) first.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/pd-ag/provisioning-and-activation-of-parallels-desktop/alternative-deployment-methods/alternative-mass-deployment-via-deployment-package.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.