Parallels Desktop Enterprise Edition Administrator's Guide
ProductsSupportDocumentation
  • Introduction
  • Upgrading from Business Edition
    • How to Trial Enterprise Edition with Existing Business Edition Per-user License
    • What Happens after a Trial Ends
    • Migrating from Business Edition to Enterprise Edition
    • Migrating from per-device to per-user licensing
  • Getting Started
    • Creating a Business Account and Registering Your License
    • Dividing Users into Groups with Sublicenses
    • Configuring Golden Images and Policies in the Management Portal
    • Installing and Activating Parallels Desktop
  • Configuring the Single Sign-On (SSO) integration with Parallels My Account
    • Prerequisites
    • Starting the Integration Process in Parallels My Account
      • Configuring SSO Integration with Azure/Entra ID
      • Configuring SSO Integration with Okta
      • Configuring SSO Integration with Ping Identity
      • Configuring SSO Integration with JumpCloud
      • Configuring SSO Integration with Google Workspace
    • [OPTIONAL] How to Divide Users into Groups and Assign Them Sublicenses
    • Troubleshooting the SSO Activation
  • Creating and Uploading Virtual Machine Images
  • Mass Deployment of Parallels Desktop and Virtual Machines
    • Deploying via an Invitation Email
    • Mass Deployment Using Mac Management Tools
      • [RECOMMENDED] Deploying Parallels Desktop via MDM App Catalogs Using Configuration Profiles
        • Creating and Editing a Configuration Profile in iMazing
        • Deploying Parallels Desktop via MDM App Catalog (as seen in Jamf Pro)
      • [ALTERNATIVE] Mass Deployment via Deployment Package
        • 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 the Package to Macs
          • Example: 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 Management Portal
    • Golden Images
    • Policies
    • User Groups
    • Virtual Machines
    • Providing Feedback
  • Parallels Desktop for Mac Enterprise Edition Features
    • [DEPRECATED] Using Configuration Profiles
      • Creating a Configuration Profile
      • Applying a Configuration Profile to a License Key
      • Provisioning a Corporate 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
    • 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
    • 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
Export as PDF
  1. Parallels Desktop for Mac Enterprise Edition Features

Setting an Expiration Date on a Virtual Machine

You can set an expiration date for a virtual machine. This can be a useful option if you are preparing a virtual machine for a contractor (or a third party user) and want to make sure that it works only for the duration of the contract.

To set an expiration date for a virtual machine:

  1. Open Parallels Desktop and select the desired virtual machine.

  2. On the Parallels Desktop menu bar, select Actions > Configure to open the virtual machine configuration dialog.

  3. Select the Security tab.

  4. An expiration date can only be set on an encrypted virtual machine. If your machine is not yet encrypted, click Encryption: Turn On, specify an encryption password, and click OK. Make sure to record the password or you will not be able to start the virtual machine. Wait until the encryption process finishes.

  5. To set an expiration date for the virtual machine, click Expiration Date: Set Date, specify a password and click OK. Make sure to record the password to be able to change the expiration settings later. You should keep this password secret to prevent the prospective user of the virtual machine from changing the expiration date.

  6. On the next screen, specify the following options:

    • Do not allow this VM start after: specifies the virtual machine expiration date.

    • Contact info: specifies the system administrator email, phone number, or other contact information. This information will be included in the message that will be displayed to the user when the virtual machine is about to expire. You can include each piece of information on a separate line.

    • Time Server: specifies the time server URL. The virtual machine expiration time will be checked against this server. The default time server is https://parallels.com.

    • Date Check Frequency: specifies how often the date and time should be verified against the time server. You can specify it in minutes, hours, or days.

    • If unable to check date, use VM for: specifies for how long the virtual machine should be kept working if the time server cannot be reached. For the duration of this period, the virtual machine will continue to check the date. If it succeeds before this period is over, the counter is reset, and the virtual machine will continue to work normally.

  7. Click OK when done entering the expiration info.

  8. To modify the current expiration date or password, click Expiration Date: Change Date or Expiration Date: Change Password and enter the new values.

Note: When giving the virtual machine to a contractor, make sure to provide them the encryption password, which is needed to start the virtual machine. Please note that this is NOT the expiration date password you've set in step 5 above. This is the password you set when you encrypted the virtual machine.

When the expiration date approaches, the virtual machine user will be notified as follows: a message will begin to be displayed seven days before the expiration date. The message will be shown to the user every 24 hours and additionally on every virtual machine startup. Once the date is reached, the virtual machine will be locked, so the user will not be able to start or resume it anymore.

PreviousSingle Application ModeNextEnforcing USB Device Policies