How to sequence Google Chrome for App-V 4.5
Posted by Jacques on Sunday, 18 January 2009
- Try to find a stand-alone installer instead of using Google Update (quite a challenge)
- Start Monitoring and just install Chrome normally
- Stay in monitoring and move the whole Google folder from the user’s AppData\Local folder to the Q: drive, e.g Q:\GChrome.010\Google
- Still in Monitoring, delete all the created Chrome shortcuts. Create a new one pointing to the Q: location.
- Edit the new chrome shortcut and add the –no-sandbox (dash dash no dash sandbox) after chrome.exe
- Launch Chrome using this shortcut.
- Close monitoring and complete your package.
- It is not necessary to create a streaming block 1 nor to configure anything, the setting will be lost.
- Save your package and publish it.
You will find detailed info on the Chromium Sandbox concept on http://dev.chromium.org/developers/design-documents/sandbox
January 29th, 2010 at 6:59
I followed your instructions and moved the installed files to Q:\Chrome.001\Google. Unfortunately when I deployed Chrome it didn’t retain the default homepage that I set. It also didn’t remember that I selected “Don’t ask again” on wether or not Chrome is the default browser. Any thought’s on why the sequencer would miss these items?
Thanks.
Like or Dislike:
0 
0
November 10th, 2010 at 11:31
I had this problem too.
It seems that Chrome “hard codes” the location for the user’s configuration file. You might have noticed that when you run the Chrome.exe from Q: it creates files in the profile (again).
Thankfully Chrome supports command line parameters so you can override the default profile directory setting when you create the shortcut. My shortcut has the target modified to this
Q:\GChrome.v01\Google\Chrome\Application\chrome.exe –user-data-dir=”Q:\GChrome.v01\Google\Chrome\User Data”
Hope this helps.
Like or Dislike:
0 
0
December 13th, 2010 at 11:07
@ Adam
you have to change the profile folder adding the following parameters: -no-sandbox -user-data-dir=%USERPROFILE%\GoogleChrome (for example)
Like or Dislike:
0 
0
January 17th, 2011 at 9:23
Jacques,
Everything worked fine. Except that when Chrome is published, it opens but on top of the page is a tab which says “You are using an unsupported command-line flag: –no-sandbox. Stability and security will suffer.” I can click the x button & close the comment. But do you know of any place while sequencing that this can be turned off? I checked under OPTIONS while sequencing, but couldn’t find anything there.
Thanks,
Latha.
Like or Dislike:
0 
0
March 3rd, 2011 at 9:15
Adam,
thats located in : C:\Users\*username*\AppData\Local\Google\Chrome\User Data
Its an exlusion in appv turning that off will help
Like or Dislike:
0 
0