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

Testing the Autodeploy Package

Previous[MANDATORY] Creating a Flat PackageNextDeploying Parallels Desktop and Virtual Machines on Macs

Last updated 1 year ago

Once you have the Parallels Desktop autodeploy package configured, you can test it on a single Mac before you mass deploy it to other Mac computers in your organization.

To test the package:

  1. Copy it to a Mac on which you want to test it. The Mac should have a configuration similar to other Mac computers on which you'll be deploying Parallels Desktop. Specifically, if your target Mac computers don't have Parallels Desktop and virtual machines installed, the test Mac shouldn't have them installed either. If target Macs have an older version of Parallels Desktop, the test Mac should have it installed too, so you can see what the results will be.

  2. To speed up the execution of the package during testing, consider running it from the command line using /System/Library/CoreServices/Installer.app. When executed this way, the package will not be tested by macOS for digital signature, and the usual package verification procedure will be skipped. Please note that if you run the package by double-clicking on it, macOS will warn you that the package is not signed and will not install it. If you run the package by right-clicking and choosing Open, the signature check will be skipped but the verification of the package will take a long time if you have one or more virtual machines in it (because of the large size of a typical virtual machine). When you use the Installer.app to run the package, the installation will commence installing immediately, without any checks or verifications. All of the above only applies when you run the package manually. When you mass deploy it on Mac computers, verification is not performed, and the installation is completely silent.

  3. When the installation is complete, verify that Parallels Desktop is installed, activated, and is functioning properly. If your package is configured to deploy Parallels Desktop in Single Application Mode, try running the application and see that it starts and runs as it should.

  4. Please note that when the package is executed, it writes logs into /var/log/install.log. If you experience issues, examine the logs. If that doesn't help, you can contact for business customers which is available 24/7.

Read on to learn how to mass deploy the package using one of the Mac management tools.

Parallels Support