#MAC OS X+WHERE IS AUTOFILL PREFERENCES KEPT FOR CHROME UPDATE#

I like using Whitebox Packages to create my pkg’sįirst we will start with a pre-install script that will remove any pre-existing content, so that if we need to update these preferences later we can be sure that our package will remove any items before installing the new items. Then I can copy them from there with a script later. What I like to do is to store those items in the Scripts folder in /Library. We also need to store the other files that need to go into the users home folder.

Package it all up and craft some pre/post flight scripts.įirst create a package that deploys our Google Chrome Master Preferences file into /Library/Google So now we have all the pieces we need, how do we deploy it to client machines?

This can easily be achieved by simply using the touch command ie. Now to disable the first run / welcome screen, we have to create an empty file called First Run inside the ~/Library/Application Support/Google/Chrome folder. That will set up the default preferences. Now create a folder called Default inside ~/Library/Application Support/Google/Chrome and place the Preferences file inside this Default folder. 'removed_old_component_pepper_flash_settings': true 'device_id_salt': 'qPIPmfV9u7CJGs6aXx9DxA=' 'suppress_first_run_default_browser_prompt': true It should be stored in /Library/Google/Google Chrome Master Preferencesīelow is the content of my Master Preferences file, its just plain JSON Google uses a file called “ Google Chrome Master Preferences” This file can contain some basic preference settings that will be applied. To manage pretty much everything else we will have to create some text files.

#MAC OS X+WHERE IS AUTOFILL PREFERENCES KEPT FOR CHROME HOW TO#

I won’t go into the details on how to create a profile from a plist with MCX to Profile because Tim has already written good documentation on his site. Then I used MCX to Profile to generate a config profile from this plist. To create a profile for this, I first created the plist with the setting i wanted with the following command defaults write checkInterval 0 This then causes the Google Keystone auto update mechanism to never check for updates. This is disabled by simply setting the checkInterval to 0 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.

#MAC OS X+WHERE IS AUTOFILL PREFERENCES KEPT FOR CHROME DOWNLOAD#

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.

I had a request to add the Google Chrome web browser to our builds.

Mac os x+where is autofill preferences kept for chrome