Parallels Desktop Business Edition Administrator's Guide
ProductsSupportDocumentation
  • Introduction
    • Business Edition Features Overview
  • Deploying Parallels Desktop for Mac Business Edition
    • Deploying via an Invitation Email
    • Mass Deployment Using Mac Management Tools
      • Prerequisites
      • Supported Mac Management Tools
      • Preparing the Autodeploy Package
        • Downloading the Autodeploy Package
        • Specifying a License Key
        • [OPTIONAL] Adding the Parallels Desktop Installation Image
        • [OPTIONAL] Adding a Virtual Machine
          • Installing Parallels Tools
          • Preparing Windows for Mass Deployment
          • Common Configuration Options
        • Adding Windows Application Stubs
        • Configuring Deployment Options
        • Single Application Mode
        • [MANDATORY] Creating a Flat Package
        • Testing the Autodeploy Package
      • Deploying Parallels Desktop and Virtual Machines on Macs
        • Deploying with Jamf Pro
          • Automating Parallels Desktop Initial Setup with a Configuration Profile
        • Using a Script to Change VM Options
    • Enrolling Virtual Machines in Azure Active Directory
  • Parallels Desktop for Mac Business Edition Features
    • Using Configuration Profiles
      • Creating a Configuration Profile
      • Applying a Configuration Profile to a License Key
      • Provisioning a Corporate VM Image
        • Creating a VM Image
        • Creating a Configuration Profile
        • Installing a VM Image on a Mac
      • Enabling Major Version Upgrades
        • Creating a Configuration Profile
    • Participating in the Customer Experience Program
    • Locking a Virtual Machine on Suspend
    • Activating Using a Corporate Account
    • Restricting a Virtual Machine Configuration with a Custom Password
    • Restricting User Actions in Parallels Desktop with a Custom Password
    • Setting an Asset Tag in the Virtual Machine BIOS
    • Using Custom Graphics and Links in the Control Center
    • Hiding Developer Tools in the Parallels Desktop GUI
    • Encrypting a Virtual Machine using the Command Line
    • Single Application Mode
    • Setting an Expiration Date on a Virtual Machine
    • Enforcing USB Device Policies
    • Resetting the Guest OS Password
    • Setting Up a Local Update Server
      • Setting Up a Local Web Server
      • Creating the Parallels Update XML File
      • Configuring Individual Macs
    • Configuring Parallels Desktop Update Branch
    • Customizing the Support Center Option
Powered by GitBook

Other Resources

  • Community Forum
  • Knowledge Base
  • Request Support

Social Media

  • Facebook
  • Twitter/X
  • YouTube
  • LinkedIn

© 2025 Parallels International GmbH. All rights reserved.

On this page
  1. Deploying Parallels Desktop for Mac Business Edition
  2. Mass Deployment Using Mac Management Tools
  3. Preparing the Autodeploy Package

[OPTIONAL] Adding a Virtual Machine

Previous[OPTIONAL] Adding the Parallels Desktop Installation ImageNextInstalling Parallels Tools

Last updated 6 months ago

Choosing the Deployment Method

Adding a virtual machine to the autodeploy package is optional. You can mass deploy Parallels Desktop only and install virtual machines on individual Mac computers later. Consider the following possible scenarios:

  • If you are deploying Parallels Desktop on either Apple Silicon or Intel-based Mac computers (but not both at the same time), you can include a virtual machine in the autodeploy package, so it will be installed on a Mac as part of the deployment process.

  • The recommended approach is to deploy without any virtual machines in the autodeploy package and instead provision a corporate VM image using a Configuration Profile in Parallels My Account. This method is especially useful when you plan to deploy Parallels Desktop on both Apple Silicon` and Intel-based Mac computers at the same time. For more information, please see and .

Note: Architectural differences between Intel-based and Apple Silicon Macs require different virtual machines for each of them, even if the operating system type and version are the same. If you have both kinds of Macs in your organization and would like to deploy Parallels Desktop with a virtual machine on all of them, you need to create two autodeploy packages (one for Apple Silicon and another for Intel-based Macs) and deploy them separately.

There are two ways to include a virtual machine in the autodeploy package: as a downloadable link or as a local file manually added to the package. Regardless of which one you choose, take the following steps first:

  1. Configure the virtual machine as described in the subsections of this chapter;

  2. FULLY STOP the virtual machine by opening Actions in the macOS menu bar and choosing Shut Down. Suspending or pausing it will not suffice;

  3. Reduce the size of the selected virtual machine by doing one of the following:

    • Open the Parallels Desktop Control Center, right-click on the virtual machine, and select Prepare for Transfer;

    • Alternatively, open the Parallels Desktop Control Center, right-click on the virtual machine, and select Show in Finder. Right-click on the virtual machine .pvm file and select Compress {vm_name}.

[RECOMMENDED] Including a Virtual Machine as a Downloadable Link

Several popular MDM solutions have been known to experience issues with deploying large packages. As a way to mitigate this, you can amend the deploy.cfg file to include a link to a file share location with the virtual machine file instead of including it in the package. Take the following steps:

  1. Upload the compressed file to a permitted cloud storage that would be accessible to all target Macs (e.g., OneDrive or Google Share). Make sure the resulting link is direct and open to all the users affected by the deployment. The best way is to choose Share with anyone.

  2. Open the deploy.cfg file in a text editor, same as when , scroll to the Virtual Machines section and add the download link there exactly as described, following the instructions carefully.

Note: You can find out about other configuration options in the deploy.cfg file from .

[ALTERNATIVE] Adding a Virtual Machine File to the Autodeploy Package

To add a virtual machine to the autodeploy package directly, simply copy the virtual machine file to the Virtual Machine(s) sub-folder that can be found under Bundle > Virtual machine(s) . More than one virtual machine can be added to the autodeploy package if needed.

Read on to learn about modifications that you can make to the virtual machine configuration before adding it to the autodeploy package.

Using Configuration Profiles
Corporate VM Image Provisioning
specifying a license key
this chapter