# Preparing a Deployment Package
If you haven't already, use the link below to download the Parallels Desktop Autodeploy Package directly to a Mac computer.
[Download the deployment package here](https://link.parallels.com/pd/deployment-package).
{% hint style="danger" %}
**Attention!** Once you have downloaded the `ZIP` file, it is **essential** that you remove any quarantine attributes from it, as they may affect all further steps. To do that, execute the following command in the macOS Terminal:
`xattr -dr com.apple.quarantine /Users/{username}/Downloads/pd-autodeploy.zip`
Make sure the file path matches that of your downloaded package.\
\
If the package has already been unarchived automatically, use the following command: `xattr -dr com.apple.quarantine /Users/{username}/Downloads/Parallels\ Desktop\ mass\ deployment\ paclage`
Make sure the file path matches that of your downloaded package.
To verify that the quarantine attribute has been removed, execute the following command (utilizing a package or folder path):
`xattr -r /Users/{username}/Downloads/pd-autodeploy.zip | grep com.apple.quarantine`
{% endhint %}
The autodeploy package archive contains a folder named "Parallels Desktop mass deployment package `vxxx`", where "`vxxx`" is the autodeploy package version number.
The folder contains the following files:
* **Changelog.txt** — contains a record of changes that were made to the autodeploy package over time.
* **Deploy.cfg** — contains all the parameters that you'll need to check and set, as described [here](https://app.gitbook.com/s/CH2PH40adGxVh4iotxRv/mass-deployment-of-parallels-desktop-and-virtual-machines/mass-deployment-using-mac-management-tools/alternative-mass-deployment-via-deployment-package/preparing-the-autodeploy-package/configuring-deployment-options).
* **Prepare** — contains the build script that creates a flat package ready for deployment.
Take the following steps to populate the package folders:
1. Certain MDM solutions have limitations on the size of hosted deployment packages, e.g., Jamf Pro's own cloud distribution platform has a 20GB limit. If your Windows virtual machine image is under the limit, or your MDM solution doesn't impose one, include the `.pvmp` file in the `Virtual Machine(s)` folder. Otherwise, upload the `.pvmp` file to a shared location accessible to all target machines without authentication, and include the direct download link in the respective section of the **deploy.cfg** file. Review [this page](https://app.gitbook.com/s/CH2PH40adGxVh4iotxRv/mass-deployment-of-parallels-desktop-and-virtual-machines/mass-deployment-using-mac-management-tools/alternative-mass-deployment-via-deployment-package/preparing-the-autodeploy-package/optional-adding-a-virtual-machine) for further advice.\
\
[**Note**: If you are on Jamf Pro and your package exceeds the 20GB limit, you may consider](#user-content-fn-1)[^1] [changing your cloud distribution point](https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/Cloud_Distribution_Point.html) [to alternatives with larger limits (e.g., 30GB on Amazon S3) OR adding a](#user-content-fn-1)[^1] [file server distribution point](https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/File_Share_Distribution_Points.html).
2. Enable adding the Windows application launch icon to the macOS dock upon deployment by copying the application's stub from the `/Users/{username}/Applications (Parallels)/{VM_name}` folder to the `Windows Application(s) stubs to add to Dock` folder of the deployment package.
3. Modify the **deploy.cfg** file:
1. Set the Single Application Mode to yes: `enable_single_application_mode="yes"`
2. \[OPTIONAL] If you plan on enrolling the virtual machines into Intune/Azure Active Directory, make sure to set the **vm\_reset\_hwid** parameter to `yes`. This will regenerate the SMBIOS ID for each separate deployed virtual machine, so they don't all look the same to the AAD. Read more [here](https://app.gitbook.com/s/CH2PH40adGxVh4iotxRv/mass-deployment-of-parallels-desktop-and-virtual-machines/enrolling-virtual-machines-in-azure-active-directory).\
\
[**Note**: If you are using a Parallels Desktop version OLDER than 26 for secondary deployment to the same Mac endpoint, make sure to read the troubleshooting section of](#user-content-fn-1)[^1] [this KB article](https://kb.parallels.com/en/129728#section7).
3. Include a Parallels Desktop license key with the respective number of seats in the **license\_key** parameter or leave it commented for the Single Sign-On experience where the user signs in with their work email address. Read more [here](https://app.gitbook.com/s/19bdEvIobLjdIuA0nqs5/managing-subscriptions-licences-and-seats/creating-additional-license-keys).
4. Create a flat package by right-clicking on the **Scripts** folder of the Autodeploy Package and choosing **Services** -> **New Terminal at Folder**. In the Terminal window, run the following command:\
\
`./prepare --dest {Destination_folder}`, e.g., `./prepare --dest /Users/{user_name}/Downloads`.\
\
This action creates a `.pkg` file in the destination folder that is ready for distribution.
5. Test the deployment package as described [here](https://app.gitbook.com/s/CH2PH40adGxVh4iotxRv/mass-deployment-of-parallels-desktop-and-virtual-machines/mass-deployment-using-mac-management-tools/alternative-mass-deployment-via-deployment-package/preparing-the-autodeploy-package/testing-the-autodeploy-package).
6. See the [next chapter](https://docs.parallels.com/landing/pd-ag/parallels-desktop-sam-guide/creating-a-single-application-mode-setup/deploying-a-package-via-mdm) for deploying the package.
[^1]:
---
# Agent Instructions: 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:
```
GET https://docs.parallels.com/landing/pd-ag/parallels-desktop-sam-guide/creating-a-single-application-mode-setup/preparing-a-deployment-package.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
