So it turns out that one item is able to be managed via a config profile.

Set the home page to open on launch, but not on new creation of new tabs or pages.

So the first thing was to work out what we actually wanted to manage or setup for the user. Here is what I have come up with that gets the job done for my environment. I was hoping to find something to make my life easier with Google Chrome but alas my Google-Fu failed me. Hat tip to Greg Neagle for his AutoPKG recipes. We then have AutoPKG automatically download the latest ESR and add the CCK autoconfig files to the app bundle before wrapping it up in a nice installer package that is then imported directly into Munki which makes my life very easy. With Firefox, we use the CCK to generate autoconfig files. This brought about a little challenge in that Google Chrome does not fully utilise MCX / Config profiles to control all of its settings, so its not quite as easy to manage as Safari. What this does is, It simply removes all the Google Software Updater files which due to whatever reasons could’ve gotten corrupt or having issues with the automatic updater.I had a request to add the Google Chrome web browser to our builds.

You can now go to the about page of the browser and it’ll automatically start the update process. Open Google Chrome and It’ll show a yellow bar on top which would have a button to turn on the automatic updates, press that and it’ll ask for password to enter, once you’re done with that. $ sudo rm -rf /Library/Google & sudo rm -rf ~/Library/Googleģ.

Open Terminal window and fire the following command:.

If you’ve tried to update your Google Chrome and the update failed because of the error 11 issue, Then here’s a simple and easy solution that’ll let you update your Google Chrome again and fix the issue once & for all.įirst try fixing with the following instructions on this page: If it fails, try below: How to Fix Google Chrome Update Failed (error 11) Issue on Mac OSX

Chrome update mac