I'm working on to push "com.google.Keystone.plist" file to clients in updating Google Chrome.
<plist version="1.0"> <dict> <key>UpdateDefault</key> <integer>0</integer> <key>updatePolicies</key> <string>global</string> </dict> </plist>
I pushed already the file to a test device but the user has still to activate auto-update by himself? If he declines, its, of course, disabled - it doesn't matter if I pushed the plist file to him or not. I thought its should be automatically forced by the plist file.
What's my final result?
My client doesn't update so far but I just got this notification "Chrome may not be able to keep itself updated". Basically, that's right, if the client using my plist file but on the other hand the user doesn't download the latest version. Anyone an idea?
thanks a lot
We now deploy the GoogleChrome.pkg directly from Google which includes a post install script to initially setup updates. We then use this guide to enforce the auto updates: https://support.google.com/chrome/a/answer/9923111?hl=en
Did it too, using Google Chrome Enterprise instead of the simple (commercial) Google Chrome, as this last one was not digesting the com.google.keystone.plist.
When saying Google Chrome Enterprise for future users going to read this article, I am referencing to this:
The .pkg is working great, and will not override any user information/google account logged in / bookmarks etc.. for your info when deploying it on devices which are having already the commercial Google Chrome in place.
I am installing the Google Chrome Enterprise .pkg with a script.. what do I do next for the "com.google.keystone.plist".... I would appreciate if you could go over the steps to get Chrome installed, push settings (I want to setup homepages, updates and extensions while allowing users to set their own homepages after initial configuration) I am a bit confused how it all fits together... I'll appreciate any guidance..