Hi i was wondering if anyone has deployed Parallels 12 with the following restriction
Locking down what images they can use
Password Protect it so new images cannot be created by users .
i was advised i can do this by a console but i cant seem to find it
In addition i would like to know the following best way to package it
best way to maintain images
Any advise would be grateful as we are looking to test and deploy it this week
Best answer by donmontalvo
Make sure you're using version 1.2.8 of the wrapper. See page 50 for download link.
We usually re-name the wrapper to fit our Naming Standards. The only folder you need to go to is the Parallels folder. That's where the deploy.cfg is, and it needs to be edited (add your business license, set to Shared, disable updates, etc.). Add the unaltered Parallels installer DMG into the same folder as deploy.cfg, then upload the PKG to JSS.
I sent an email to the Parallels dev team to please stop using spaces in their URL. ;)
What you're probably looking for is the AutoDeploy Tool Parallels produces. I use it for packaging the installer with the license and a few customizations. When new instances of Parallels release I just generate a new installer via the AutoDeploy tool and then test/vet/deploy. I've not had any experience with lock down of user images but the tool does work pretty well for the things I've needed.
Andrew, how are you deploying Parallels via Casper? Every time I import the pkg file with the Parallels DMG built into it, it gets compressed to a Zip file and it won't deploy for me. I think I'm missing a step somewhere with the deployment via Self Service.
We usually re-name the wrapper to fit our Naming Standards. The only folder you need to go to is the Parallels folder. That's where the deploy.cfg is, and it needs to be edited (add your business license, set to Shared, disable updates, etc.). Add the unaltered Parallels installer DMG into the same folder as deploy.cfg, then upload the PKG to JSS.
I sent an email to the Parallels dev team to please stop using spaces in their URL. ;)