Parallels deployment

DennisMX
Contributor II

Hi,

We are using Jamf to deploy Parallels to certain users.
I guess that starting from Catalina it stopped working, it just fails.

Installation failed. The installer reported: installer: Package name is Parallels Autodeploy Package
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “ParallelsDesktop-15.1.1.pkg”.)

When performing a manual install it asks for Downloads, Desktop and Documents access.
Using the PPPC tool i've uploaded that config, but when opening it. The Documents access is not shown and cannot add it either.
Could this be the issue?

Anyone else having this issue?

24 REPLIES 24

larry_barrett
Valued Contributor

Are you installing 64 bit Parallels?

mschroder
Valued Contributor

Parallels comes with a kernel extension. You need to whitelist that kernel extension before you attempt to install the package, otherwise the installation will fail. But this is not really new with Catalina, this was already needed with 10.13.4 if my memory serves me well.

I would have a look at /var/log/install.log on a node where the install fails. This provides a bit more info than the policy log.

andrew_nicholas
Valued Contributor

Are you repacking 15.1.1 into a pkg? The Autodeploy tool needs only the dmg from Parallels.

DennisMX
Contributor II

Already had the KXE deployed.
It just stopped working after upgrading to Catalina.
I have non-Catalina laptops installing this package without any issues

In the VAR/LOG/install.log it shows: launch path not accessible

full log after i presses Install:

2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Referenced component packages (1) trustLevel=100
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: -[IFPKGDerivedDocument sortedPackageLocations]: result = ( "file://localhost" )
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: -[IFDInstallController(Private) buildInstallPlanReturningError:]: location = file://localhost
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: file://localhost/Library/Application%20Support/JAMF/Downloads/ParallelsDesktop-15.1.1.pkg.unzip/ParallelsDesktop-15.1.1.pkg
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Set authorization level to root for session
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Administrator authorization granted.
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Will use PK session
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Using authorization level of root for IFPKInstallElement
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Starting installation:
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Configuring volume "Macintosh HD"
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Preparing disk for local booted install.
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Free space on "Macintosh HD": 479,65 GB (479650811904 bytes).
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: Create temporary directory "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T//Install.4859G1ctVT"
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: IFPKInstallElement (1 packages)
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: Adding client PKInstallDaemonClient pid=4859, uid=0 (/usr/sbin/installer)
2019-12-04 14:44:14+01 C02Y12JTJHD3 installer[4859]: PackageKit: Enqueuing install with framework-specified quality of service (utility)
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: ----- Begin install -----
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: request=PKInstallRequest <1 packages, destination=/>
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: packages=( "PKJaguarPackage <id=com.parallels.autodeploy.package, version=15.0.0, url=file://localhost/Library/Application%20Support/JAMF/Downloads/ParallelsDesktop-15.1.1.pkg.unzip/ParallelsDesktop-15.1.1.pkg>" )
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: Set reponsibility for install to 4793
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: Extracting file://localhost/Library/Application%20Support/JAMF/Downloads/ParallelsDesktop-15.1.1.pkg.unzip/ParallelsDesktop-15.1.1.pkg (destination=/Library/InstallerSandboxes/.PKInstallSandboxManager/3813CC5A-0E95-418E-BDAB-57BAF79FCFAF.activeSandbox/Root, uid=0)
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: prevent user idle system sleep
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: suspending backupd
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: Using trashcan path /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/PKInstallSandboxTrash/3813CC5A-0E95-418E-BDAB-57BAF79FCFAF.sandboxTrash for sandbox /Library/InstallerSandboxes/.PKInstallSandboxManager/3813CC5A-0E95-418E-BDAB-57BAF79FCFAF.activeSandbox
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: Shoving /Library/InstallerSandboxes/.PKInstallSandboxManager/3813CC5A-0E95-418E-BDAB-57BAF79FCFAF.activeSandbox/Root (0 items) to /
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: Executing script "./postflight" in /Library/Application Support/JAMF/Downloads/ParallelsDesktop-15.1.1.pkg.unzip/ParallelsDesktop-15.1.1.pkg/Contents/Resources
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit:
** launch path not accessible
2019-12-04 14:44:14+01 C02Y12JTJHD3 installd[1051]: PackageKit: Failed task attributes: { NSFileCreationDate = "2019-08-06 13:40:24 +0000"; NSFileExtensionHidden = 0; NSFileGroupOwnerAccountID = 0; NSFileGroupOwnerAccountName = wheel; NSFileHFSCreatorCode = 0; NSFileHFSTypeCode = 0; NSFileModificationDate = "2019-08-06 13:40:24 +0000"; NSFileOwnerAccountID = 0; NSFileOwnerAccountName = root; NSFilePosixPermissions = 420; NSFileReferenceCount = 1; NSFileSize = 52016; NSFileSystemFileNumber = 882420; NSFileSystemNumber = 16777223; NSFileType = NSFileTypeRegular; }
2019-12-04 14:44:14+01 C02Y12JTJHD3 install_monitor[4864]: Temporarily excluding: /Applications, /Library, /System, /bin, /private, /sbin, /usr
2019-12-04 14:44:14+01 C02Y12JTJHD3 install_monitor[4864]: Re-included: /Applications, /Library, /System, /bin, /private, /sbin, /usr
2019-12-04 14:44:15+01 C02Y12JTJHD3 installd[1051]: PackageKit: releasing backupd
2019-12-04 14:44:15+01 C02Y12JTJHD3 installd[1051]: PackageKit: allow user idle system sleep
2019-12-04 14:44:15+01 C02Y12JTJHD3 installd[1051]: PackageKit: Cleared responsibility for install from 4859.
2019-12-04 14:44:15+01 C02Y12JTJHD3 installd[1051]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “ParallelsDesktop-15.1.1.pkg”." UserInfo={NSFilePath=./postflight, NSURL=file://localhost/Library/Application%20Support/JAMF/Downloads/ParallelsDesktop-15.1.1.pkg.unzip/ParallelsDesktop-15.1.1.pkg, PKInstallPackageIdentifier=com.parallels.autodeploy.package, NSLocalizedDescription=An error occurred while running scripts from the package “ParallelsDesktop-15.1.1.pkg”.} { NSFilePath = "./postflight"; NSLocalizedDescription = "An error occurred while running scripts from the package U201cParallelsDesktop-15.1.1.pkgU201d."; NSURL = "file://localhost/Library/Application%20Support/JAMF/Downloads/ParallelsDesktop-15.1.1.pkg.unzip/ParallelsDesktop-15.1.1.pkg"; PKInstallPackageIdentifier = "com.parallels.autodeploy.package"; }
2019-12-04 14:44:15+01 C02Y12JTJHD3 installd[1051]: PackageKit: Running idle tasks
2019-12-04 14:44:15+01 C02Y12JTJHD3 installer[4859]: install:didFailWithError:Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “ParallelsDesktop-15.1.1.pkg”." UserInfo={NSFilePath=./postflight, NSURL=file://localhost/Library/Application%20Support/JAMF/Downloads/ParallelsDesktop-15.1.1.pkg.unzip/ParallelsDesktop-15.1.1.pkg, PKInstallPackageIdentifier=com.parallels.autodeploy.package, NSLocalizedDescription=An error occurred while running scripts from the package “ParallelsDesktop-15.1.1.pkg”.}
2019-12-04 14:44:15+01 C02Y12JTJHD3 installd[1051]: PackageKit: Removing client PKInstallDaemonClient pid=4859, uid=0 (/usr/sbin/installer)
2019-12-04 14:44:15+01 C02Y12JTJHD3 installd[1051]: PackageKit: Done with sandbox removals
2019-12-04 14:44:15+01 C02Y12JTJHD3 installer[4859]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Starting softwareupdate CLI tool
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdated[838]: Adding client SUUpdateServiceClient pid=4932, uid=0, installAuth=NO rights=(), transactions=0 (/usr/sbin/softwareupdate)
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Query for available updates: FINISHED
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdated[838]: Adding client SUUpdateServiceClient pid=4932, uid=0, installAuth=NO rights=(), transactions=0 (/usr/sbin/softwareupdate)
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Controller: Waiting for SUAppStoreUpdateController to populate initial list of available updates
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Waiting for available updates to be initially populated
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Done waiting for available updates to be initially populated
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Controller: Done populating initial list of available updates: [] with major os updates: []
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Controller: Time interval since last scan - 385.433695
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Controller: shouldScan - 1, productKeysInActiveForegroundTransactions - 0
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdate[4932]: Controller: Scan is in progress
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdated[838]: Adding client SUUpdateServiceClient pid=4932, uid=0, installAuth=NO rights=(), transactions=0 (/usr/sbin/softwareupdate)
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdated[838]: SUScan: Scan for client pid 838 (/System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated)
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdated[838]: Got status 200
2019-12-04 14:44:20+01 C02Y12JTJHD3 softwareupdated[838]: SUScan: Using catalog https://swscan.apple.com/content/catalogs/others/index-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz
2019-12-04 14:44:21+01 C02Y12JTJHD3 softwareupdated[838]: JS: No bundle at/Applications/SafeView.app
2019-12-04 14:44:21+01 C02Y12JTJHD3 softwareupdated[838]: bridgeOS: Minimum bridge version requirement satisfied ((null)), skipping search for bridgeOS update
2019-12-04 14:44:22+01 C02Y12JTJHD3 softwareupdated[838]: JS: 10.15.1
2019-12-04 14:44:23+01 C02Y12JTJHD3 softwareupdated[838]: JS: No bundle at/Applications/SafeView.app
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: bridgeOS: Minimum bridge version requirement satisfied ((null)), skipping search for bridgeOS update
2019-12-04 14:44:25+01 C02Y12JTJHD3 SoftwareUpdateNotificationManager[837]: AssertionMgr: Take com.apple.softwareupdate.NotifyAgentAssertion-BadgingCountChanged assertion with type BackgroundTask for pid 837, id 0x850C
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: SUScan: Elapsed scan time = 5.3
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Refreshing available updates from scan
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: SUStatisticsManager: Successfully reported statistics for category 5
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Adding client SUUpdateServiceClient pid=837, uid=502, installAuth=NO rights=(), transactions=0 (/System/Library/PrivateFrameworks/SoftwareUpdate.framework/Versions/A/Resources/SoftwareUpdateNotificationManager.app/Contents/MacOS/SoftwareUpdateNotificationManager)
2019-12-04 14:44:25+01 C02Y12JTJHD3 SoftwareUpdateNotificationManager[837]: AssertionMgr: Cancel com.apple.softwareupdate.NotifyAgentAssertion-BadgingCountChanged assertion for pid 837, id 0x850C
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Scan (f=1, d=0) completed 2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: 0 updates found:
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdate[4932]: SUPrefPaneController: Scan has ended
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdate[4932]: Controller: Scan finished successfully, awaiting updates available notification
2019-12-04 14:44:25+01 C02Y12JTJHD3 SoftwareUpdateNotificationManager[837]: Controller: Received availableUpdatesChanged notification; new updates: []; new major updates: [041-83630, 061-26589]
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Removing client SUUpdateServiceClient pid=4932, uid=0, installAuth=NO rights=(), transactions=0 (/usr/sbin/softwareupdate)
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Removing client SUUpdateServiceClient pid=4932, uid=0, installAuth=NO rights=(), transactions=0 (/usr/sbin/softwareupdate)
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Removing client SUUpdateServiceClient pid=4932, uid=0, installAuth=NO rights=(), transactions=0 (/usr/sbin/softwareupdate)
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Adding client SUUpdateServiceClient pid=837, uid=502, installAuth=NO rights=(), transactions=0 (/System/Library/PrivateFrameworks/SoftwareUpdate.framework/Versions/A/Resources/SoftwareUpdateNotificationManager.app/Contents/MacOS/SoftwareUpdateNotificationManager)
2019-12-04 14:44:25+01 C02Y12JTJHD3 SoftwareUpdateNotificationManager[837]: AssertionMgr: Could not cancel com.apple.softwareupdate.NotifyAgentAssertion-BadgingCountChanged assertion - no assertion found for pid 837
2019-12-04 14:44:25+01 C02Y12JTJHD3 SoftwareUpdateNotificationManager[837]: (null):softwareupdated: Service connection invalidated!
2019-12-04 14:44:25+01 C02Y12JTJHD3 SoftwareUpdateNotificationManager[837]: (null):softwareupdated: Service connection invalidated!
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Removing client SUUpdateServiceClient pid=837, uid=502, installAuth=NO rights=(), transactions=0 (/System/Library/PrivateFrameworks/SoftwareUpdate.framework/Versions/A/Resources/SoftwareUpdateNotificationManager.app/Contents/MacOS/SoftwareUpdateNotificationManager)
2019-12-04 14:44:25+01 C02Y12JTJHD3 softwareupdated[838]: Removing client SUUpdateServiceClient pid=837, uid=502, installAuth=NO rights=(), transactions=0 (/System/Library/PrivateFrameworks/SoftwareUpdate.framework/Versions/A/Resources/SoftwareUpdateNotificationManager.app/Contents/MacOS/SoftwareUpdateNotificationManager)

mschroder
Valued Contributor

I have not tried PD 15.1.1, but I had no problems with 15.0 or 15.1.2 on Catalina. I always repackage after having done the autodeploy config, but I don't see that making a difference.

andrew_nicholas
Valued Contributor

Was the deploy package made with the latest version of their redeploy tool?

DennisMX
Contributor II

I downloaded all packages again from their website.
Autodeploy package seems to be version 15.0.0 from the logs

Then the only thing I did was dragging the Parallels Desktop 15.1.2 DMG to the Parallels desktop folder and editing the config file to add our license key.
That Autodeploy.pkg was uploaded to Jamf and deployed using the Jamf Self Service app

donmontalvo
Esteemed Contributor III

@DennisMX wrote:

Installation failed. The installer reported: installer: Package name is Parallels Autodeploy Package installer: Installing at base path / installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “ParallelsDesktop-15.1.1.pkg”.)

If you're deploying a PKG, its not the deployment wrapper which is an MPKG.

Unless they released a new deployment method.

We wouldn't know, we dropped Parallels since they absolutely stink.

IMHO VMware Pro is a much better solution for enterprise.

--
https://donmontalvo.com

DennisMX
Contributor II

@donmontalvo What do you mean with :
"If you're deploying a PKG, its not the deployment wrapper which is an MPKG."
It sound like you knowing what i'm doing wrong.

I downloaded the autodeploy, opened the package contents and dragged the Parallels DMG into that.

Dennis

donmontalvo
Esteemed Contributor III

Whats the suffix of the autodeploy package?

--
https://donmontalvo.com

mschroder
Valued Contributor

In my case the suffix of the autodeploy package is ".pkg", what I find strange in the logfile you showed is the "ParallelsDesktop-15.1.1.pkg.unzip" part of the path.

Not applicable

I'm having the same issue. If I install it manually through the GUI it works fine. When I deploy it through Jamf, I get the same error you had.

Not applicable

I was able to deploy it by wrapping the PKG into a PKG and running:

installer -pkg "/Library/Application Support/Rocketman/Parallels Desktop Autodeploy.pkg" -target /

I think, maybe, when editing the contents of a PKG it becomes "unsigned" making Jamf not trust it? I'm not sure, but running the PKG through a script seems to work for me. Let me know if you get that to work @DennisMX b5242b96ac7941629e74024e13d3b8bd

tlarkin
Honored Contributor

I am deploying Parallels Desktop Business Edition v15 to all Macs. I dropped the pkg payload and the license key into their deployment kit and it is working for me. The logs you posted seem to bark about a postflight script in the PKG. how exactly are you deploying it? Also, I think this also happens if you are using their licensing and out of licenses FYI

tlarkin
Honored Contributor

Also, the deployment kit is a non flat package, non deep signed package, and not notarized meaning if you download it from the internet, with a browser it will have quarantine tags on it for Gatekeeper. To get around this, you can run xattr -c /path/to/package.pkg to strip out the flags and it should run if that is in fact your issue

DennisMX
Contributor II

I got this fixed while working with support.
When packages are uploaded to jamf they are zipped.
When using Chrome the zipping process will break the application when deployed using jamf.

So for now we use safari for uploading packages.

Heavy_D
Contributor III

@tlarkin I been tasked to do the same, and I am a bit of a visual learner would you mind showing me what you did to deploy v15 Successfully with its corresponding key and got it to work please.

Heavy_D
Contributor III

So I am getting the following Error when following and deploying Parallels install with the Parallels Mass Deployment package. Despite adding the correct configuration profile and .dmg as stated in the guide.
deb1e54b4a18440a94c594459774a03b

Executing Policy Install - Parallels Desktop Downloading https://use1-jcds.services.jamfcloud.com//download/19727f945eb74fb797d9d257fa52498e/Parallels%20Desktop%20Autodeploy.pkg.zip?token=e72445b8fc6c433cac0db3bbf93ef992cjtfqzyajayrkkthpak74swa35qopq1p... Installing Parallels Desktop Autodeploy.pkg.zip... Installation failed. The installer reported: installer: Package name is Parallels Autodeploy Package installer: Installing at base path / installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “Parallels Desktop Autodeploy.pkg”.)

Has anyone tried doing the Mass Deployment option package?

UPDATE: So following @DennisMX suggestion I was using Chrome switched to Safari and I got different results:
It executes the the policy and installs Parallels like it should.

Executing Policy Install - Parallels Desktop Downloading https://use1-jcds.services.jamfcloud.com//download/19727f945eb74fb797d9d257fa52498e/Parallels%20Desktop%20Autodeploy.pkg.zip?token=e72445b8fc6c433cac0db3bbf93ef992cjtfqzyajayrkkthpak74swa35qopq1p... Installing Parallels Desktop Autodeploy.pkg.zip... Successfully installed Parallels Desktop Autodeploy.pkg.zip.

tlarkin
Honored Contributor

@JarvisUno All I did was put in my license key in their script and drop the parallels DMG into the package and then tossed it into jamf

Ken_Weinstein
New Contributor

@tlarkin , I'm new to Jamf and Macs in general. Trying to get used to this. I need to deploy 2 Parallels Pro Editions. You referenced a script. was that from Parallels or a Jamf script? Can I still put the license key for each in its own script? I wish the JumpStart was spread out over a longer period of time. Lots of info right away, but I'll get there. Thanks for the help.

mschroder
Valued Contributor

@Ken.Weinstein Did you have a look at the Administrator's Guide from Parallels? It describes how to prepare a pkg for deployment.

tlarkin
Honored Contributor

@Ken.Weinstein I just followed the Parallel's docs on this. They have a tool you can use to do this and that is what I followed. I didn't do anything custom outside their docs really.

ricardtolosa
New Contributor III

The deployment pkg was broken until a couple of weeks ago, we had a case open with Parallels. Now it works well with v15 and v16.
Follow the guide and that’s all, should work with no further issues.

Rhio
New Contributor III

CHROME YOU BASTARD - I hate hate hate that the solution to my hours of issues and searching and working with their support was that YOU CANNOT USE CHROME (thank you guys for posting here) as its zipping process appears to break this package.

Again for those who stumble through this USE SAFARI or ADMIN, DO NOT USE CHROME :)

(just had to put that in caps so it really stood out lol)