Systems Management

Old thread I know but this may help someone. Google has released an MSI for standalone deployment, download from here:

http://www.google.com/chrome/eula.html?msi=true

Enable the Windows Installer logging policy with the parameter 'voicewarmup' and re-deploy. Logs will be written to %SystemRoot%\TEMP on the target workstations so clear that out first.

Remember to turn the policy off: with it on, the engine writes ALL MSI activity to a log.

I deployed chrome via GPO/MSI.

On the packaging machine, it was in "C:\Documents and Settings\Administrator\Local Settings\Application Data\Google\Chrome\Application\"

and on the the final machine it got installed in

C:\WINDOWS\system32\config\systemprofile\Local Settings\Application Data\Google\

Which is not a proper place (but is the profile of the system user) and maybe configured in the MSI but it works well and perhaps you may want to tweak that.

The MSI I created is 27.2 MB

I've had similar problem with "C:\WINDOWS\system32\config\systemprofile" and application deployment via SMS/SCCM. The only way I could see to get around this was to tick in the "Package" "Program" properties, in the "Environment" tab, to set it to run "only when a user is logged" on, and to "run with user's rights". But I can't see any options like that with a Group Policy install.

Among my Vista users who have installed Chrome, about one third have installed to " C:\Program Files\Google\Chrome\Application\", yet the rest have the default install at "c:\Users\%userprofile%\AppData\Local\Google\Chrome". Does anyone know why it installs in two different locations?

Downloading chrome from the usual location (http://www.google.com/chrome) will result in a single-user installation into AppData (partially to avoid permission/UAC issues, I think). Download the Google Pack (choosing only Chrome, unless you want the others) and you will get an installation in Program Files.

I downloaded chrome from Google pack, but the way I packaged it was different. I unselected all the of the programs except chrome, downloaded Google_updater.exe and saved it. I then launched Google_Updater.exe useing the App Deploy Re-packager and had it install chrome. I finished capturing the changes and got rid of Google_updater evidence. That worked pretty well.

For Enterprise deplooyment of Chrome, please follow this link:
http://msiworld.blogspot.com.au/2012/06/packaging-google-chrome-for-enterprise.html

Thanks for posting... it was about time to get something for enterprise. Is anyone from Firefox watching this thread? :D

I've found a guide for using the new enterprise MSI file, hopefully should make the process a bit easier:

http://bdts.com.au/tips/48-msi-packaging/156-deploy-google-chrome.html