Skip to main content

We are excited about recent updates that make Chrome on macOS easier to deploy and manage. Our work with the Google Chrome for Enterprise Team is ongoing, and this first release benefits not only Jamf Pro admins, but everyone who manages Mac at scale. Look for more information in the form of a blog, but here are the highlights:

Updates to the installer - Chrome is now available as a PKG in addition to the standard DMG. This is the preferred installer format for mass distribution, and is available from the Chrome Browser Enterprise Installers website.

Initial Support for Application & Custom Settings - Chrome Browser Cloud Management (CBCM) is a a single location to set Chrome policies on multiple platforms. Google simplified the process of deploying the enrollment token by leveraging Jamf's new Application & Custom Settings payload.

This work comes from user feedback and @alexbauer from the Chrome for Enterprise Team is joining this thread to hear your thoughts!

Chrome Enterprise Browser Support can be reached here.

Update 6/11/2020 - The Chrome for Enterprise Team has published a new kBase on Managing Chrome Browser Updates with Jamf Pro (macOS)

Maybe a difference with Jamf running it as Root?


I wish I knew. Moving to the cloud based instance of Jamf has been a nightmare. The shear number of issues I have had is truly staggering. I would go back in an instant if I could.

I'm currently migrating devices from OnPrem to the Cloud. My process for updating the Chrome base install (via Self Service policy) is to go out to Google's site to download the universal pkg. I then upload this into Jamf directly - I don't repackage or make any changes. We've been deploying Chrome out this way for quite some time.

I will note that with Jamf Cloud I'm using App Installers process to update existing Chrome installs - no need to download a package from Google to upgrade. I'm also looking at using App Installers as a potential means to do my base install since it not only will upgrade existing installs but will install it on a device that never had Chrome to begin with. Initially testing is looking great - does what I'm expecting.

While an old thread, I thought I would provide some rather undocumented things I've found....


The Chrome for enterprise download doesn't always install the googlesoftwareupdate component...

https://support.google.com/chrome/answer/111996?hl=en#zippy=%2Cmac
Note: Download Chrome Again, Step 3, on Mac... Download and install Google Software Update again.

URL: https://dl.google.com/mac/install/googlesoftwareupdate.dmg

This kinda works like Microsoft MAU .app in which its an app that runs on schedule from a launchdaemon... It reads and applies settings from com.google.keystone... 

It installs mainly in /Library/Application Support/Google/GoogleUpdater/*

Is google Software update still needed to get chome to update automaticity (with out asking the user on chrome first launch)?

Also The google documentation (https://support.google.com/chrome/a/answer/9179243?hl=en) for creating a software update package is basically run a Snapshot app to capture changes when installing. Which is a not a great way to make a package. Anyone else doing something different?

Is google Software update still needed to get chome to update automaticity (with out asking the user on chrome first launch)?

Also The google documentation (https://support.google.com/chrome/a/answer/9179243?hl=en) for creating a software update package is basically run a Snapshot app to capture changes when installing. Which is a not a great way to make a package. Anyone else doing something different?


You can either use google admin and set a policy there or you can do what we do, leverage instalomator to check and install for updates on a weekly basis.

You can either use google admin and set a policy there or you can do what we do, leverage instalomator to check and install for updates on a weekly basis.


Yep Installomator lets us customize things way more than the Jamf App installers. We've now moved to only leveraging Jamf App installers as a monthly task for any devices that didn't get patched somehow with Installomator.

Another issue for us was that we couldn't limit who could see or get patched via installomator as some apps we require to have licensing for and with Jamf App Installers you can't limit who sees them.

Is google Software update still needed to get chome to update automaticity (with out asking the user on chrome first launch)?

Also The google documentation (https://support.google.com/chrome/a/answer/9179243?hl=en) for creating a software update package is basically run a Snapshot app to capture changes when installing. Which is a not a great way to make a package. Anyone else doing something different?


I've been using Jamf's App Installers to install Chrome for the last few years. I have one setup to upgrade existing installs and another setup as an available install via Self Service targeting devices that don't have Chrome. If you have Jamf, this is what I would recommend. I haven't had to touch it since I moved it to App Installers.

You can either use google admin and set a policy there or you can do what we do, leverage instalomator to check and install for updates on a weekly basis.


I do install a plist with our Chrome PKG, but I assume you still need google updater installed to have it update with out a chrome popup asking the user to enable auto updates.

Terms & ConditionsCookie settingsAccessibility statement