[RECOMMENDED] Deploying Parallels Desktop via MDM App Catalogs Using Configuration Profiles

Instead of preparing deployment packages, many modern MDM solutions allow you to deploy known apps via their built-in app catalogs.

This method, however, requires you to accompany the pre-existing Parallels Desktop installation package with a configuration profile containing a specific license key or an instruction to activate the app via Single Sign-On.

Some of the MDM solutions like Jamf Pro already have preconfigured profiles for Parallels Desktop for Mac. In case your preferred MDM solution does not, the next easiest way to achieve that is to use iMazing's Profile Editor app.

Note: If your MDM solution does not have a built-in app catalog, and you would like to use a script to create the deployment package, use the following permanent link to get the latest version of the Parallels Desktop for Mac DMG: https://link.parallels.com/link/66a0eecfbfZ6/

A configuration profile with licensing information will persist on target Macs and help you keep your users' copies of Parallels Desktop for Mac activated even through a complete reinstallation (if you include a licensing key in it) or force an SSO sign-in window to pop up at the restart (if you set SSO as the default activation method in the profile). Having a pre-installed licensing profile (preferably protected from removal) will prevent a user of Parallels Desktop for Mac 20.3.0 or newer from activating their copy of Parallels Desktop for Mac with another key.

Note: In your Parallels Desktop for Mac deployment process, we suggest that you deploy the configuration profile first and Parallels Desktop for Mac second.