So I replaced my copy of Parallels Desktop Autodeploy with the latest copy from the vendor (10.2.1), and it now fails to install. Has anyone else seen this behavior?
I've noticed the same issue here. Seems Parallels installs fine for the most part but the autodeploy fails for me during the serialization part, so when the user opens Parallels, they're prompted to sign in to a Parallels account. I also tried putting the serialization part into a separate script to run as a policy (prlsrvctl install-license -k --deferred) but that failed too. I previously had 10.2.0 up on the JSS and it deployed fine and testing the separate activation policy also worked fine.
Curiously, running the same exact command in the Terminal locally works fine, so for now I'm resorting to wrapping the licensing command using osascript for the user to run in Self Service. Terminal opens, runs the command, pauses for 15 seconds to give the command enough time to run, then closes.
#!/bin/bash osascript -e 'tell application "Terminal" to do script "prlsrvctl install-license -k <yourkeyhere> --deferred"' sleep 15 osascript -e 'tell application "Terminal" to quit'
Not the most elegant of solutions but it works. The autodeploy packager hasn't been updated in a while so will probably have to wait for Parallels to fix.
Thanks Andrew. We don't include license in the Autodeploy package. We comment out all the License part in the Autodeploy. When it tries to set the cep to off it shows "set command option is available only in Parallels Desktop for Mac Pro or Business Edition".
It shows Parallels Desktop business edition only after the License Activation.
I am using Parallels Autodeploy 1.2.5 for packaging Parallels Desktop 11. When installed the package for the first time its fails with the error "prlsrvctl: command not found". If I install the same package again, it installs and work. Also we don't include License in the package, we comment the License part. Since its not activated we can't use "prlsrvctl set" commands, it will display "set command option is available only in Parallels Desktop for Mac Pro or Business Edition"
Thanks & Regards,
@karthikeyan.mac If you need to get the Parallels 11 instances out the door right away, one thing you might want to try is to repackage the prlsrctl commands and deploy those with an earlier preference order to see if that addresses the issues. I haven't tested this but I will and can report back.
Thanks @Peterson! I'm testing it out now and it looks to package the License Key correctly, however the CEP and other optional settings do not appear to set correctly.
[Edit]: Deploying through JAMF appears to set most things correctly. My initial tests were done as direct PKG installs which did not set CEP or preferred directory.
@ITVTickets These are the direct download links I use to grab everything:
Parallels AutoDeploy Download (Current v1.2.7)
Latest PD 11
Latest PD 10