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. 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. Chrome 46 was released to users of all the major platforms last month.Īs of September 2015, Chrome accounts for just over 65 percent of the overall browser market, with Apple's Safari at 3.6 percent.I had a request to add the Google Chrome web browser to our builds.
The OS X version of the browser, which has historically been cited by many Mac users as being slower than its counterparts on Windows and Chrome OS, was said to have received a performance boost with the release of Chrome 46, thanks to a reduction in overall memory consumption. While Tuesday's announcement was the first indication of axing Chrome support for legacy OS X users, Google hinted back in April that they were only committed to supporting Windows XP up until the end of the year, encouraging people to upgrade to newer versions of Windows. The announcement came via the official Chrome blog, where the search giant revealed that Mac users will need to be running OS X 10.9 Mavericks or later to receive continued updates for Chrome., According to Director of Engineering Marc Pawliger, Chrome will continue to function on legacy platforms, but will no longer receive regular updates and security patches as of April 2016.
0 kommentar(er)
