"For anyone reading this looking for a true enterprise version.
Here's a quick guide to get you started, maybe Google could take pointers if they want to take enterprise users seriously.
I cannot find anything in the EULA to prevent this http://www.google.com/chrome/intl/en-GB/eula_text.html however I will have it thoroughly checked before deploying it and I suggest you do the same.
1. Get the GPO pack and decide your settings, disabling Google Update (for at Least Chrome) completely. Setting Install and Update to 0.
This will stop admins and users alike installing Chrome from any method (I've found).
2. Set the Chrome policies in the GPO (careful of the content settings as at the time of writing this the downloaded ADM file has the wrong values for some of the registry keys. Find the keys that are not being set correctly and modify the ADM file increasing the registry key values by 1)
3. Download the 'Chrome_Installer.exe' from
http://dl.google.com/chrome/install/<Version Number>/chrome_installer.exe
where version number for '12.0.742.100' would be '742.100'
4. Repackage the executable using the cmd line 'chrome_intaller.exe --system-level' using you favorite Application packaging software (WISE and AdminStudio tested OK), you should be able to use AppDeploy's Re-packager too.
5. Customize the package, removing the uninstall shortcut and some registry keys. You may wish to change the install directory to avoid future issues (remember to change the registry keys to match). If you need to deal with 64bit machines you need to extract the 'wow_helper.exe' from the Chrome.7z and place it with the Chrome.exe and use logic to only install on 64bit machines (see the thank you below). That said on my Windows 7 64bit I had no issues without the 'wow_helper.exe' being present but I guess it is there for a reason. This a good time to put in a custom 'master_preferences' file (I've attached mine if it helpes).
6. Package your MSI and deploy as you wish, standard MSI commands apply. If you're using WISE set the MSI to uninstall old versions (haven't tried with other packaging software) and then to release a new version after testing, repeat procedure and the MSI will update automatically previous versions.
Thanks go out to all the frustrated admins out there trying to get this working correctly in their own environments. Google Chrome is good! please let us use it?
Special thanks go out to AngelD from AppDeploy.com for the final pieces of the puzzle. http://www.appdeploy.com/messageboards/tm.asp?m=56478"
At my employer we ran into a situation where we needed to uninstall several versions of Chrome that had been installed to user PCs using the Google Pack, so the uninstall strings were different than what is listed here. To silently uninstall the current version, 12.0.742.112, use this command line:
"C:\Program Files\Google\Chrome\Application\12.0.742.112\Installer\setup.exe" --uninstall --force-uninstall --system-level
Google Updater remains behind, but as noted in Rob Mensching's blog (http://robmensching.com/blog/posts/2008/9/13/Correction-Google-Chrome-uninstalls.-eventually), Updater goes away after several hours.
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
