/build/static/layout/Breadcrumb_cap_w.png

Google Chrome Deployment

OK. I have tried to create a MSI from the offline installer. It works if I install it manually but through group policy it keeps failing with error 1603. I'm thinking it is because this uses a per-user install. Can anyone confirm if they have this working through a GPO? My other thinking is to try to capture the install from the google pack since apparently that uses a system install. Any thoughts?

0 Comments   [ + ] Show comments

Answers (9)

Posted by: adrenaline_nz 10 years ago
Yellow Belt
2
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

Comments:
  • Brilliant! I was looking for an MSI and google sent me to the EXE. You're the best! - noktis 7 years ago
Posted by: anonymous_9363 11 years ago
Red Belt
1
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.
Posted by: dvdzonenz 11 years ago
Purple Belt
1
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
Posted by: donaghs 10 years ago
Senior Yellow Belt
1
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?
Posted by: ajs 10 years ago
Yellow Belt
1
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.
Posted by: hunter.mclaughlin 10 years ago
Senior Yellow Belt
1
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.
Posted by: piyushnasa 8 years ago
Red Belt
1

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

Posted by: wd40 10 years ago
Orange Senior Belt
1
Thanks for posting... it was about time to get something for enterprise. Is anyone from Firefox watching this thread? :D
Posted by: M_A_D_C_A_T 9 years ago
Yellow Belt
1
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
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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