Broken .pkg installer for MacOS 14.3

I am unable to install box drive to MacOS 14.3. This is a brand new machine. The installer error log shows:

```
Feb  1 00:05:22 mylaptop Installer[2586]: Could not load resource readme: (null)
Feb  1 00:05:22 mylaptop Installer[2586]: Could not load resource license: (null)
Feb  1 00:05:27 mylaptop installd[690]: PackageKit: ----- Begin install -----
Feb  1 00:05:30 mylaptop installd[690]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “BoxDrive.pkg”." UserInfo={NSFilePath=./postinstall, NSURL=file:///Users/me/Downloads/BoxDrive.pkg#BoxDesktopScripts.pkg, PKInstallPackageIdentifier=com.box.desktop.installer.scripts, NSLocalizedDescription=An error occurred while running scripts from the package “BoxDrive.pkg”.} {
        NSFilePath = "./postinstall";
        NSLocalizedDescription = "An error occurred while running scripts from the package \U201cBoxDrive.pkg\U201d.";
        NSURL = "file:///Users/me/Downloads/BoxDrive.pkg#BoxDesktopScripts.pkg";
        PKInstallPackageIdentifier = "com.box.desktop.installer.scripts";
    }
Feb  1 00:05:30 mylaptop Installer[2586]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Feb  1 00:05:30 mylaptop Installer[2586]: Displaying 'Install Failed' UI.
Feb  1 00:05:30 mylaptop Installer[2586]: 'Install Failed' UI displayed message:'The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.'.
```

None of the forum topics and tips resolve the problem. I see someone else has posted on this as well. The failure occurs for the installer from box.com and from homebrew too.

Fixing this is mission-critical, because it is not feasible to go access necessary files one by one through the web portal.

landon yarrington

February 07, 2024 23:13

I learned the cause of the failure problem is that Box's Team ID is not explicitly allowed in the device profile. Users have two options: 1) ask your IT admins to alter the profile to allow Box products to be installed; 2) nuke all device profiles and `jamf` software as root. You should probably do #1 and not #2. But if you are determined to do #2, open a terminal and:

sudo su -
launchctl remove com.jamfsoftware.*
launchctl remove com.jamf.management.daemon
jamf flushPolicyHistory
jamf flushCaches
jamf removeFramework
cd /Library/LaunchAgents
rm -rf com.jamf*
cd /Library/LaunchDaemons
rm -rf com.jamf*
exit

Box Support: you need to do a better job of alerting users that this is a potential issue instead of burying it in online forum documentation, which I had to find this myself: https://support.box.com/hc/en-us/articles/360043697474-Installing-and-Updating-Box-Drive#h_01HAYMPWJ6H0SRFWGYQXP82VN7

Comments