Skip to main content

Deploy Parallels Desktop Business Edition on macOS

What

Use a FileWave PKG Fileset to deploy a current Parallels Desktop for Mac Business Edition autodeploy package. The Parallels package handles installation and reads its activation and deployment choices from deploy.cfg, so a separate post-install license script is not required for new deployments.

Before you start

  • FileWave Central and a macOS test group
  • The current Parallels Desktop for Mac installation image and autodeploy package
  • A Parallels Business Edition license key or the SSO configuration used by your organization
  • Any virtual machine image and deployment settings required for your rollout

Download a new autodeploy package for the Parallels build you are deploying. Parallels warns that a configured package from an earlier version or build may not be compatible.

Prepare the Parallels package

  1. Download the installation image and latest autodeploy package from the Parallels mass-deployment prerequisites.
  2. Open the autodeploy package and configure deploy.cfg for your activation method and rollout. For a Business Edition license key, use the package’s License section. Treat the license key as a credential and limit access to the prepared deployment artifact.
  3. Add the Parallels installation image and any virtual machine payloads required by your design, then finish the package by following the current Parallels autodeploy configuration guide.

Deploy with FileWave

  1. In FileWave Central, choose New Fileset, select the PKG Fileset type, and choose the prepared Parallels autodeploy PKG.
  2. Create a Deployment for a small macOS test group.
  3. Verify that Parallels Desktop installs, launches, uses the intended activation method, and registers any included virtual machine for the intended users.
  4. Expand the Deployment only after installation and activation are clean on the test Macs.

Parallels also documents a configuration-profile and app-catalog method. If you use that method, deploy the licensing profile before Parallels Desktop.

Legacy attachment

The 2015 standalone activation Fileset is retained only to identify older deployments. Do not use it for a new rollout; configure activation in the current Parallels package or profile instead.

Related content

No comments to display

Back to top