Parallels via JSS

The zipping happens because the autodeploy package is a non-flat pkg, that shouldn't be the problem.
/var/log/install.log on the client should tell you what the problem is.

Have you added your license key to the deploy.cfg file?

Make sure you’re using the latest wrapper, that the Parallels Desktop DMG is in the right folder within he wrapper, and that you’re not using Word to edit deploy.cfg.

We did a bunch of work with a client a couple years ago and developed an entire workflow using Self Service to deploy and manage a Parallels VM.

I can't guarantee things still work with newer versions of Parallels but it may give you a starting point.
https://github.com/macfanatic-ca/deployParallels

Thanks for the response everyone.

Does a license key need to be added to the "deploy.cfg file" for it to work? my plan was to de able to be able to deploy Parallels into Self Service and add license key at a later date as we purchase licenses individually rather then a company license

@andrew.nicholas @donmontalvo You seem to have been able to deploy this successfully. We're trying to do this very same thing but are running into an issue as well. We have the AutoDeploy.pkg, we've added our Win 10 VM, modified the deploy.cfg, and added the current .dmg of Parallels.

We keep getting timeouts when uploading to the JSS as well as the app appearing as a .zip (and being compressed from ~23 GB down to ~11 GB. Even when we take the VM out of the .pkg, we're still getting a .zip appended to the end.

Any thoughts? Thanks in advance!

@rosskivowitz From what i can gather you need to also include a volume license to the AutoDeploy package and way to upload the package is do it via JSS portal

@rosskivowitz The package will compress to a .zip file because it is not a flat package, but that shouldn't affect anything on deployment. Does the upload succeed when you use the package without the VM, and are you uploading it via Casper Admin?

Volume license key is required.

Also pd-deploy.zip 2.1.0 was just released.