Posted on 03-16-2015 10:57 AM
Hello all,
I am looking to remove the to startup screens Chrome shows when a user first launches the application. The "set google chrome as your default browser" and "set auto updates to run". I just want the users to get a default web page when they start the app for the first time and not these two questions. I want to set the default to "no" and auto updates "yes".
Thanks
Solved! Go to Solution.
Posted on 03-16-2015 03:26 PM
I would google and take a look at Chromes "Master Preferences" configuration option. It works really well for doing the initial setup for users.
There was a bug recently for the default browser prompt, that was being investigated, not sure if it has been resolved yet, so if your specifically after this one it might not quite fulfil your needs, the setting was available it was just being ignored.
But for everything else it is very good at controlling pretty much everything and it's very simple to deploy (literally just a single folder you push out that Chrome looks for if there are no settings for the current user, it's independent of the App itself so even if you update the App the preferences remain and if compatible continue to be implemented.
Posted on 03-16-2015 03:26 PM
I would google and take a look at Chromes "Master Preferences" configuration option. It works really well for doing the initial setup for users.
There was a bug recently for the default browser prompt, that was being investigated, not sure if it has been resolved yet, so if your specifically after this one it might not quite fulfil your needs, the setting was available it was just being ignored.
But for everything else it is very good at controlling pretty much everything and it's very simple to deploy (literally just a single folder you push out that Chrome looks for if there are no settings for the current user, it's independent of the App itself so even if you update the App the preferences remain and if compatible continue to be implemented.
Posted on 08-06-2015 07:36 AM
This is an old post, but it is still relevant as the bug has not in fact been resolved. Best as I can tell, an attempt to fix it was made, but the fix caused problems and they backed it out of the code. Nothing has occurred since then (about 2 months ago).
There are in fact two open "issues" for this that can be tracked:
https://code.google.com/p/chromium/issues/detail?id=263803
https://code.google.com/p/chromium/issues/detail?id=224410
Neither issue currently has an "owner." Until someone takes ownership of these issues, I wouldn't plan on a resolution.
Posted on 08-06-2015 10:38 AM
Useful discussion here:
https://jamfnation.jamfsoftware.com/discussion.html?id=9868