Posted on 10-20-2022 10:48 AM
Has anyone figured out a way to set the Chrome homepage (with RestoreOnStartup and RestoreOnStartupURLs keys) but allow users to change it? I've been through a lot of posts and it seems like no one has a solution.
I thought it would be as simple as pushing a com.google.Chrome plist to the user’s Preferences folder, but it doesn’t take unless you also delete the user's Chrome ‘Default’ preference folder under ~\Library\Application Support\Google\Chrome. The problem with that is it can remove some preferences set by the user, which we don't want.
I can’t use a profile (because we don’t want to enforce it). Also, I would use a Chrome Initial Preference file for this, but that only works for first-time run and we need it to hit existing Chrome users as well.
Posted on 10-20-2022 10:52 AM
I can echo this challenge, and I give up on anything that has to fiddle with the user's home folder now. I just enforce it with a profile and tell the user we can either enforce it or open to all.
Posted on 10-20-2022 11:58 AM
@markopolo Here's the approach I use for this:
Posted on 10-20-2022 02:55 PM
Yeah, might have to resort to this even though it's a bit clunky. Thanks for the suggestion!
10-20-2022 01:45 PM - edited 10-20-2022 01:52 PM
You should be able to use a Jamf policy with the following to push a recommended Chrome policy that can still be changed by the user:
defaults write com.google.chrome <key> <value>
I think I had to change Chrome user profiles before it took effect in a test just now but I'm curious how it would work on a fresh install or after reboot.