Enrolling with management server failed with 500 status

This isn’t a comprehensive “if you get this, these are all the solutions” post. This is more of a “this worked for me, and it may work for you, too” post. If you’re using sudo profiles renew -type enrollment to enroll a Mac in your MDM via DEP (or “automated device enrollment”), you may get… Continue reading Enrolling with management server failed with 500 status

Troubleshooting “zsh: operation not permitted”

If you try to run a script from the Terminal in macOS, you may get an error that says zsh: operation not permitted. As of this writing, the top Google search results for that all point to needing to grant the Terminal full disk access (either via System Preferences > Security & Privacy > Privacy… Continue reading Troubleshooting “zsh: operation not permitted”

Command to add a secure token to a macOS user account

If you run sysadminctl -secureTokenStatus firstuseraccount and see a secure token is enabled for that first account but run sysadminctl -secureTokenStatus seconduseraccount and see a secure token is not enabled for that second account, you can try adding a secure token to the second account, so it can turn on FileVault or become a FileVault-enabled… Continue reading Command to add a secure token to a macOS user account

“Invalid Message – The message could not be parsed.” with Jamf Cloud

Invalid Message – The message could not be parsed. is an odd error message for a jamf recon when you’re using Jamf Cloud, because if you Google that error message, there are only two results: FYI – Invalid Message – The message could not be parsed. Devices not updating inventory (Invalid Message – The message… Continue reading “Invalid Message – The message could not be parsed.” with Jamf Cloud

Conflict 409 Error: Duplicate alternate MAC address for Jamf API call

Acknowledgements Major shoutout to Ben Toms from the MacAdmins Slack for pointing out what the issue is. The exact error message If you have a script that doesn’t return the actual response but just gives you an error code, you may get an error code of 409. If you Google something like 409 conflict jamf… Continue reading Conflict 409 Error: Duplicate alternate MAC address for Jamf API call

Adobe Package Downloader error on Big Sur

If you get a The installation cannot continue as the installer file may be damaged. Download the installer file again. error when trying to run the Adobe Package Downloader.app on Big Sur, the quickest workaround (as of the writing of this blog post) is to copy the Adobe Package Downloader.app (or, more precisely, the .dmg… Continue reading Adobe Package Downloader error on Big Sur

“An error occurred during personalization” when updating to macOS 11.2

Update Since I wrote this, Apple has already released macOS 11.2.1, so maybe this is no longer an issue? Not 100% sure. So see below if you are experiencing this issue. What’s the error? You may see this error when trying to download the update to macOS 11.2 if you’re on macOS 11.1. Software Update… Continue reading “An error occurred during personalization” when updating to macOS 11.2

If you can log in and use sudo but can’t unlock Sys Pref prefpanes in Big Sur

I and at least one other person on the MacAdmins Slack saw situations in which a known working password (can log into the computer, can use sudo to escalate privileges in the terminal) on an admin account is not working in System Preferences to unlock a prefpane. Special thanks to owen on the MacAdmins Slack… Continue reading If you can log in and use sudo but can’t unlock Sys Pref prefpanes in Big Sur

Fix for VirtualBox Extension Pack postinstall script hanging in Munki

The problem If you’ve been running the VirtualBoxExtPack.munki.recipe AutoPkg recipe, and you’ve noticed the VirtualBox Extension Pack postinstall script in Munki hanging indefinitely (30 minutes and beyond), it’s because the license hash has changed. The fix According to @jessepeterson (the maintainer of that AutoPkg recipe), the license hash doesn’t change very often, but it did… Continue reading Fix for VirtualBox Extension Pack postinstall script hanging in Munki

If Jamf recon is launching a du process that causes a CPU spike

If Jamf inventory (jamf recon) causes an extended CPU spike specifically related to the du command, you can fix that by going, in the Jamf settings, to Computer Management > Computer Management – Management Framework > Inventory Collection, and then uncheck the Include home directory sizes checkbox. That is a system-wide setting, but especially if… Continue reading If Jamf recon is launching a du process that causes a CPU spike