Send me news and updates about the CrossOver Chrome OS. Starting with Google Pixelbook, Chrome OS will be able to run a full Linux environment in a secure virtual. On Mac, download Google Software Update again and try reinstalling If your computer doesn't let you complete these steps, contact the person who has administrator rights to your computer to complete the Chrome update.
How are people deploying Google Chrome with munki? Are you just copying the app bundle to /Applications and be done with it? Or are you copying the app and using postinstall script to enable/disable/configure the automatic updates? My method has just been to copy the app bundle (with optionalinstalls and managedupdates) but I have been thinking about letting Chrome update itself since I'm not always up-to-date with the Chrome releases. I see there's the KeystoneRegistration.framework inside the Chrome bundle which installs /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle or /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle respectively. I'm experimenting with this right now.
There are a couple of solutions but none of them are fantastic. For things that can't be controlled through MCX, we can manually add things to the Master Preferences List:.
1) I'd love to set the default home screen to the 'most visited' home screen, but it always seems to default to the apps one. There is unfortunately no interface for changing the new tab page. There are extensions that do this, and I'm trying to replicate their behavior, but simply adding their manifests to the Master Preferences file isn't doing the trick. For example, chromeurloverrides doesn't seem to take effect, so I'm back to the drawing board.
2) A yellow notification banner runs on first start warning the user that auto updates aren't enabled. I hadn't actually considered allowing chrome to auto update itself, I dismissed it because I was concerned that I couldn't rely on it (internet access only available when a student is logged in). I suppose however that if auto updates are configured and it never gets around to it 'automatically', I still release new chrome versions whenever I'm able toand it will stop pestering users with #2.
Setting autoupdate to on might be a better solution, even if those machines never have admin access. The other downside to turning autoupdate on is that the program should still determine the latest version and give you the little arrow to indicate that you're out of date, even if it can't download new updates. I haven't tested this thoroughly, though. I have not yet found any means to make the yellow bars go away, though - I suspect that's a permanent feature. - Nick McSpadden Nick McSpadden 17/5/2012, 14:04 น.
On Thu, May 17, 2012 at 11:33 AM, Nick McSpadden wrote: 1) I'd love to set the default home screen to the 'most visited' home screen, but it always seems to default to the apps one. There is unfortunately no interface for changing the new tab page.
There are extensions that do this, and I'm trying to replicate their behavior, but simply adding their manifests to the Master Preferences file isn't doing the trick. For example, chromeurloverrides doesn't seem to take effect, so I'm back to the drawing board. Add this to your MCX manifest for Google Chrome: ExtensionInstallForcelist (array) Item - dpjamkmjmigaoobjbekmfgabipmfilij; What it does is silently forces the install of an extension from the Chrome web store called 'Empty New Tab,' which does exactly what it sounds like. Note that this does pull it from the internet, so if you want to avoid this, you'll need to locally host the crx file. There is documentation on the Chromium for Admins site about doing this, but I haven't looked at it beyond the cursory glance. My attempts to recreate the extension's behavior without the extension by adding it to the manifest and/or Master Prefs file was totally unsuccessful, so this is a working and relatively straightforward solution.
Lee Ramsay 17/5/2012, 21:02 น. First of all, thank you Nick McSpadden for the information on managing Google Chrome. I saw that it was posted to too. The autoupdate issue still remains but I think I've found a solution to it. I read quite a lot of Chromium source code, looked through the logs and messed around within Google Chrome.app bundle trying to see what it does while registering for autoupdating.
And fortunately I found some useful stuff. The first thing that is needed is to install and register the Keystone itself.
This is done with the KeystoneRegistration.framework/Resources/install.py script and works just like I thought when writing the initial message for this thread. Cd '/Applications/Google Chrome.app/Contents/Versions/19.0.1084.46/Google Chrome Framework.framework/Frameworks/KeystoneRegistration.framework/Resources/' sudo./install.py -install=Keystone.tbz -root=/ The second part (and the trickier one) is to register Chrome with Keystone. This is done with /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/ksadmin command line application which comes from the initial Keystone install. Yes, and there's two different approaches: 1. Remove Chrome registration from ticket store but leave Keystone installed.
This might be desired if you have some other Google products installed. Remove the whole Keystone and the ticket store (effectively removing Chrome registration too). The Chrome ticket can be removed with the same ksadmin command that was used to register it. For example: cd '/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/' sudo./ksadmin -delete -productid com.google.Chrome The Keystone itself can be removed with the Keystone install script.
For example: cd '/Applications/Google Chrome.app/Contents/Versions/19.0.1084.52/Google Chrome Framework.framework/Frameworks/KeystoneRegistration.framework/Resources/' sudo./install.py -nuke The -nuke option removes Keystone files and the ticket store. Note that there's also the -uninstall option bat that leaves the ticket store on disk. I created a script for this that can be used as a pre-uninstall script: - Hannes Juutilainen tack 30/5/2012, 11:54 น. Ran into a bit of a snag on this one. Since this is python it's sensitive to indenting and whitespace. Copying/pasting from the github link added all kinds of erroneous whitespace. I was able to fix it by making sure there was no whitespace between starting string tag and code, and end of code and closing string tag.
Also TextMate's column select/delete was very handy to strip out most of the extra whitespace github added. Then I needed to fix return value indents on lines 93 and 131. But now it works great! Cheers, tack [email protected] 30/5/2012, 11:59 น. Best practice whenever adding a pre- or post- script to a Munki pkginfo: 1) Save the script to a file.
2) Test running the script from that file. 3) Once it runs correctly: /usr/local/munki/makepkginfo -postinstallscript=/path/to/the/script You can substitute -preinstallscript, -postuninstallscript, -preuninstallscript, or -uninstallscript for the other types of scripts. By using makepkginfo to generate the key and value, you ensure the script is properly encoded for inclusion in a plist file.Greg Hannes Juutilainen 30/5/2012, 12:11 น. Am Mittwoch, 30. Mai 2012 08:40:39 UTC+2 schrieb Hannes Juutilainen: Yes, and there's two different approaches: 1.
Remove Chrome registration from ticket store but leave Keystone installed. This might be desired if you have some other Google products installed.
Remove the whole Keystone and the ticket store (effectively removing Chrome registration too). The Chrome ticket can be removed with the same ksadmin command that was used to register it.
For example: cd '/Library/Google/ GoogleSoftwar eUpdate/ GoogleSoftwareUpdate. Bundle/ Contents/MacOS/' sudo./ksadmin -delete -productid com.google.Chrome The Keystone itself can be removed with the Keystone install script.
For example: cd '/Applications/Google Chrome.app/Contents/Versions/ 1 9.0.1084.52/Google Chrome Framework.framework/ Frameworks / KeystoneRegistration. Framewor k/Resources/' sudo./install.py -nuke The -nuke option removes Keystone files and the ticket store.
Note that there's also the -uninstall option bat that leaves the ticket store on disk. I created a script for this that can be used as a pre-uninstall script: - Hannes Juutilainen On 30.5.2012, at 2.13, Greg Neagle wrote: Thanks for this, Hannes. As a companion and to aid in testing, have you documented the reverse procedure, that is, how to turn off/disable Keystone updates for Chrome? -Greg On May 25, 2012, at 2:33 AM, Hannes Juutilainen wrote: First of all, thank you Nick McSpadden for the information on managing Google Chrome. I saw that it was posted to too.
The autoupdate issue still remains but I think I've found a solution to it. I read quite a lot of Chromium source code, looked through the logs and messed around within Google Chrome.app bundle trying to see what it does while registering for autoupdating.
And fortunately I found some useful stuff. The first thing that is needed is to install and register the Keystone itself.
This is done with the KeystoneRegistration. Framework /Resources/install.py script and works just like I thought when writing the initial message for this thread. cd '/Applications/Google Chrome.app/Contents/Versions/ 1 9.0.1084.46/Google Chrome Framework.framework/ Frameworks / KeystoneRegistration. Framewor k/Resources/' sudo./install.py -install=Keystone.tbz -root=/ The second part (and the trickier one) is to register Chrome with Keystone.
This is done with /Library/Google/ GoogleSoftware Update/ GoogleSoftwareUpdate. Bundle/ Contents/MacOS/ksadmin command line application which comes from the initial Keystone install. You can view the currently registered tickets with -p option and looking at the output reveals the options what Chrome should look like once registered: sudo./ksadmin -p productID=com.google. K eystone version=1.0.9.2865 xc= url= creationDate=2012-05- 2 4 05:50:19 +0000 productID=com.google.
C hrome version=19.0.1084.52 xc= url= creationDate=2012-05- 2 4 09:26:22 +0000 tagPath=/Applications/ Google Chrome.app/Contents/Info.plist tagKey=KSChannelID brandPath=/Library/ Goo gle/Google Chrome Brand.plist brandKey=KSBrandID versionPath=/ Applicati ons/Google Chrome.app/Contents/Info.plist versionKey=KSVersion ksadmin requires at least 4 arguments to register an application with Keystone but looking at the above it's clear that Chrome wants some more. This is also confirmed by looking at the Chromium source code at and its keystoneParameters method. So if you'd do this manually, you'd have this monster command:./ksadmin -register -preserve-tttoken -productid com.google.Chrome -version 19.0.1084.52 -xcpath '/Applications/Google Chrome.app' -url -tag-path '/Applications/Google Chrome.app/Contents/Info.
Plist ' -tag-key KSChannelID -brand-path '/Library/Google/Google Chrome Brand.plist' -brand-key KSBrandID -version-path '/Applications/Google Chrome.app/Contents/Info. Plist ' -version-key KSVersion I've compiled all of this in to a python script that should work without customization on any recent version of Chrome. It checks what version is installed in '/Applications/Google Chrome.app' and then setups the autoupdates accordingly. I'm still testing this but it seems to do it's job: The 'Setup automatic updates' button is gone from the About window and it successfully updates itself. You can get the script from: Just copy/paste as a postinstallscript in to your Chrome pkginfo. - Hannes Juutilainen On 18.5.2012, at 7.20, Mike Pullen wrote: Sorry if I've missed an inferred answer to this question, but- Is it possible to have Chrome autoupdate enabled for all users, even non-admin users?
If so, is there anyone who does use autoupdate on the client end to keep Chrome updated? Then again if so, how do you set up the keystone autoupdater for all users?
It isn't enabled as Chrome is installed- and while there is documentation on how to disable the updater, I can find none detailing how to enable it as a post-flight script. Thanks!
Google Chrome by default updates itself automatically, this is very useful for regular users, you don't have to check updates manually. However, if you don't have enough bandwidth or in an enterprise environment automatic updates will not be a good thing, you can disable automatic google chrome update and then manually update google chrome whenever you want to. Disable Google Chrome automatic updates in Windows.
Launch Windows Registry Editor: click the Start Run menu, type regedit, then click OK button. Screenshot: Launch Windows Registry Editor. Expand the tree in the left pane, Locate to: HKEYLOCALMACHINE/SOFTWARE/Policies/Google/Update If don't see the Google as key there in the left pane under Policies, then you will need to create a key named Google and then create a another key named Update under newly created key Google.
![Google chrome free mac download Google chrome free mac download](http://cdn.osxdaily.com/wp-content/uploads/2012/04/google-chrome-automatic-update.jpg)
Screenshot: Locate to HKEYLOCALMACHINE/SOFTWARE/Policies/Google/Update. Add a new DWORD value named: DisableAutoUpdateChecksCheckboxValue Set it to 1 to disable automatic updates. If you want to enable them, set it to 0. Add a new DWORD value named: AutoUpdateCheckPeriodMinutes Set a number of minutes; for example, 1440 for once a day, 10080 for once a week, and so on. Close the Regedit.exe appliaction. Disable Google Chrome automatic updates in Mac OS. Launch Terminal application in Mac OS.
To turn off Google Chrome automatic updates in Mac OS, please enter the following commands: $ defaults write com.google.Keystone.Agent checkInterval 0 To re-enable updates in Mac OS: $ defaults write com.google.Keystone.Agent checkInterval 1. To set the update frequency in Mac OS: $ defaults write com.google.Keystone.Agent checkInterval frequency Where frequency is a number of seconds; for example, 86400 for once a day, 604800 for once a week, and so on. Disable Google Chrome automatic updates in Linux Chrome updates occur via the standard package management system, so be careful when clicking Yes please to automated update notifications. Install Chromium Google Chrome releases will autoupdate, but Chromium (the open source project) does not. So there is another way: you can build or install. Other resource about Google Chrome Updates.
This document contains information about applying policies to Google Update/Google Installer within the enterprise. Google Update is an end-user application that installs and updates many of Google's applications for Microsoft Windows.
Previous article:. Next article. I managed to find a way to completely stop google chrome from auto updating itself and you can stil re-enable it to update when needed. Just follow the steps below: 1. First, you need to find where the google chrome updater is located (they keep on moving it every once in a while), you can either search for it with windows search or you can right click on the google chrome shortcut then hit 'properties' and on the shortcut tab hit 'Open file location' the 'Update' folder usually is in the google folder just 2 folders back from the location of the google launcher where the shortcut will bring you. Make a backup/archive of the 'Update' folder using winrar or any similar application you prefer.
Delete the 'Update' folder (I'm not sure if you need to close chrome first, but to be sure just close any running google application first including the updater from the task manager if you can.). Open chrome, then hit on 'The Generals' Button??
Which is the former 'wrench' icon. And click on the 'About Google Chrome' button from the drop down to see this 'Update failed (error: 3)' which will verify that the updater is no longer working. Then, in the case that you need to update chrome again just extract the 'Update' folder from step 2 in its proper location (so, maker sure that you note where that is before deleting the folder) and you will be able to update google chrome again. Sorry the english, Goodluck. I've been a long time fan of google chrome since its beginning, but not anymore. I have just replaced google's chrome with opera browser based on the following problem when using chrome on my xp-sp3 pc with quad-core cpu. Symptom: at a cold start, windows' explore (the desktop) was very slow in response to any ui device (mouse, keyboard, etc.) for a long 10+ minutes.
I have installed the google update 'administrator templates', following the suggestion from google, and diligently and painstakingly disabled all the update items under its list. After having removed the chrome via control:add/remove software, and manually removed its data elements under c:Documents and SettingsadminstratorLocal SettingsApplication Datagoogle no slowdown after a cold reboot, and all the symptoms are gone. Conclusion: google chrome must have down some 'evil' things on the background at the starting time. Note that my network connection is set in manual control with a connection icon on the desktop, i usually use its 'enable' and 'disable' to limit the time of internet connection, to minimize the potential of any external attack.
At the start, the network connection is always 'disable'd. What about disabling autoupdate of extensions? Your browsing is OK and suddenly it isn't - then you notice that some of your extension were autoupdated and are now broken. Worst: sometimes extensions change the set of required permission it needs to run. When such thing happpens in an autoupdate, Chrome/Chromium will silently DISABLE the extension until you confirm your allowance to the new permission set. The only feedback you have os this is an 8x8-or-so arrow icon overlayed on the menu button. And your only choices is a) accept the new permissions set, or b) keep the extension disabled.
What now?, you think. Spend a couple hours browsing the code trying to figure out why your fix-this-on-some-specific-pages extension now wants permission to read your data on all Interne? By Murphy's law, this will happen on the worst time possible during the day (e.g.
You're ready to start a presentation to the board, and this require the extension to be working right). Trust me, it's a nice way of ruining one's work day (been there, done that). Not to say the case of new versions of autoupdated extensions that now contain spyware or may harm your computer, which ALREADY happened (Now, answering the question on the first paragraph: there's no way to disable autoupdate of extensions. The feedback from Chromium devs? 'Exposing a way to turn this off to users does not seem worth the cost to me' - Judge it for yourself. I already did my own judgement and figured out that having a slightly faster browser is not worth the cost of giving away control of my computer.