Apple’s documentation on deploying custom packages using Apple Business Essentials lacks in-depth examples of real-world implementations. Here are two!
Your organization must have an approved tax status under “Organization Settings” at business.apple.com. Once received, turn on custom apps:
Copy the appropriate download URL, writing it down somewhere for later. I’m deploying to Apple Silicon, so I chose the ARM distribution.
zoomusInstallerFull.pkg
. Per Apple, “the package must begin to download when the link is used. The link can’t lead to a webpage with another link.”In terminal, run shasum -a 256 zoomusInstallerFull.pkg
. The output should look something like the following. We want to copy the long string of numbers and letters, excluding the filename.
Terminal output:
08104901aee19f3d08d9cb449fb0cc77379712ce31f9a12612bf8be3675da971 zoomusInstallerFull.pkg
Desired SHA-256 hash:
08104901aee19f3d08d9cb449fb0cc77379712ce31f9a12612bf8be3675da971
Follow through with the package installation on your machine/a testing machine. With the app open, write down the app version. In Zoom’s case, it is written at the bottom of the login page. (If it isn’t, you can use the app’s “about” pane. With the app open, select its name in the macOS menu bar and click “About Zoom Workplace”)
In Finder, open the applications folder and find zoom.us
. Right click and select “Show Package Contents”. In the Contents
folder, open Info.plist
. We’re looking for the CFBundleIdentifier
’s value, which in this case, is us.zoom.xos
. Write this down.
<key>CFBundleIdentifier</key>
<string>us.zoom.xos</string>
zoom.us
and press “Get Info” (alternatively, press command + i).Click the small app icon so that it is selected and then press command + c to copy the icon.
Open Preview.app
, and in the macOS menu bar, select “New from Clipboard” (or command + n). Save the file as a .png
somewhere on your disk.
In Apple Business Essentials (ABE), under the apps tab, select “New Package”. The fields are to be filled out as follows:
zoom.us
CFBundleIdentifier
you wrote down in step #6.png
you saved in step #9I didn’t add any System Extensions, Privacy Preference Permissions, or Login and Background Item Management items.
Essentials.app
, find your new package, and press install. (It may take a little while for the package to appear – it took around 10 seconds in my case.)That’s it! During the app install process, the user might be prompted to choose whether to “Automatically keep the Zoom Workplace app up to date”. My recommendation is to keep this checked and press done, otherwise the Sysadmin will need to regularly upload update packages into ABE. I encourage users at this point to also configure the necessary app permissions so that they don’t experience any hiccups during their first meeting:
To get set up for screen sharing:
(AFAIK, there isn’t a way to automate this part of the setup…)
Back in ABE, you can view app installation status on assigned devices:
The process for deploying Chrome’s package is more or less the same as Zoom’s. However, what isn’t obvious at first is that Chrome has a download page targeted at enterprise users where you can choose to download a .pkg
instead of a .dmg
installer. Google likes to obfuscate their download URLs, but with a little bit of trickery it can be acquired:
Otherwise, the installation follows in the same order as Zoom. Follow steps #1-11, changing the names and icon as needed.
Happy deployment!