Hi,
Does anyone have a working Google Chrome config file that actually works?
The one available for download from VMware just isn't good enough for a corporate environment. We have it deployed at multiple sites for different customers, and without fail, we end up with Chrome profiles regularly bloating over 1gb up to 6gb, which means log off times are absolutely horrendous. Again, this isn't an isolated occurrence, but is happening at any site that uses Chrome. The fact we can't use DirectFlex with Chrome only adds to the problems.
We have tried modifying that config file in many different ways to exclude various files; however, the way Google have built Chrome means you inevitably end up excluding parts containing useful user settings, thus making the config file useless.
I know this is more the fault of Google for making a good browser in the worst possible way for corporate environments, but there has to be a solution to make UEM/ Chrome a viable combination.
Unfortunately, telling a customer not to use Chrome doesn't cut it in the real world.
Hi,
Also try the following:
[IncludeFolderTrees]
<LocalAppData>\Google\Chrome
[IncludeRegistryTrees]
HKCU\Software\Google\Chrome
[ExcludeFolderTrees]
<LocalAppData>\Google\Chrome\User Data\Default\Cache
<LocalAppData>\Google\Chrome\User Data\Default\Application Cache
<LocalAppData>\Google\Chrome\User Data\Default\Storage
<LocalAppData>\Google\Chrome\User Data\Default\Local Storage
<LocalAppData>\Google\Chrome\User Data\Default\Media Cache
#<LocalAppData>\Google\Chrome\User Data\Default\Extensions
<LocalAppData>\Google\Chrome\User Data\Default\Session Storage
<LocalAppData>\Google\Chrome\User Data\Default\GPUCache
<LocalAppData>\Google\Chrome\User Data\Default\Web Applications
<LocalAppData>\Google\Chrome\User Data\Default\Sync Data
<LocalAppData>\Google\Chrome\User Data\Default\Sync Data Backup
<LocalAppData>\Google\Chrome\User Data\WidevineCDM
<LocalAppData>\Google\Chrome\User Data\EVWhitelist
<LocalAppData>\Google\Chrome\User Data\Default\Pepper Data\Shockwave Flash\CacheWriteableAdobeRoot
<LocalAppData>\Google\Chrome\User Data\pnacl
<LocalAppData>\Google\Chrome\User Data\recovery
<LocalAppData>\Google\Chrome\User Data\SwiftShader
<LocalAppData>\Google\Chrome\User Data\ShaderCache
<LocalAppData>\Google\Chrome\User Data\PepperFlash
<LocalAppData>\Google\Chrome\User Data\Default\IndexedDB
[ExcludeFiles]
<LocalAppData>\Google\Chrome\User Data\Default\ChromeDWriteFontCache
<LocalAppData>\Google\Chrome\User Data\Safe Browsing Bloom
<LocalAppData>\Google\Chrome\User Data\Safe Browsing Bloom Prefix Set
<LocalAppData>\Google\Chrome\User Data\Safe Browsing Download
<LocalAppData>\Google\Chrome\User Data\Safe Browsing UwS List
<LocalAppData>\Google\Chrome\User Data\Safe Browsing UwS List Prefix Set
<LocalAppData>\Google\Chrome\User Data\ev_hashes_whitelist.bin
Raymond
Having read that Chrome is a pain I packaged the portable version of Chrome that is available at portableapps.com.
I can then use UEM to save the settings related to that version, also utilizing directflex.
It's taking a while to hone the 'excludes' but my config file is currently 94Mb.
Would you be able to upload your config file somewhere? It doesn't sound like a bad workaround.
Hi,
Also try the following:
[IncludeFolderTrees]
<LocalAppData>\Google\Chrome
[IncludeRegistryTrees]
HKCU\Software\Google\Chrome
[ExcludeFolderTrees]
<LocalAppData>\Google\Chrome\User Data\Default\Cache
<LocalAppData>\Google\Chrome\User Data\Default\Application Cache
<LocalAppData>\Google\Chrome\User Data\Default\Storage
<LocalAppData>\Google\Chrome\User Data\Default\Local Storage
<LocalAppData>\Google\Chrome\User Data\Default\Media Cache
#<LocalAppData>\Google\Chrome\User Data\Default\Extensions
<LocalAppData>\Google\Chrome\User Data\Default\Session Storage
<LocalAppData>\Google\Chrome\User Data\Default\GPUCache
<LocalAppData>\Google\Chrome\User Data\Default\Web Applications
<LocalAppData>\Google\Chrome\User Data\Default\Sync Data
<LocalAppData>\Google\Chrome\User Data\Default\Sync Data Backup
<LocalAppData>\Google\Chrome\User Data\WidevineCDM
<LocalAppData>\Google\Chrome\User Data\EVWhitelist
<LocalAppData>\Google\Chrome\User Data\Default\Pepper Data\Shockwave Flash\CacheWriteableAdobeRoot
<LocalAppData>\Google\Chrome\User Data\pnacl
<LocalAppData>\Google\Chrome\User Data\recovery
<LocalAppData>\Google\Chrome\User Data\SwiftShader
<LocalAppData>\Google\Chrome\User Data\ShaderCache
<LocalAppData>\Google\Chrome\User Data\PepperFlash
<LocalAppData>\Google\Chrome\User Data\Default\IndexedDB
[ExcludeFiles]
<LocalAppData>\Google\Chrome\User Data\Default\ChromeDWriteFontCache
<LocalAppData>\Google\Chrome\User Data\Safe Browsing Bloom
<LocalAppData>\Google\Chrome\User Data\Safe Browsing Bloom Prefix Set
<LocalAppData>\Google\Chrome\User Data\Safe Browsing Download
<LocalAppData>\Google\Chrome\User Data\Safe Browsing UwS List
<LocalAppData>\Google\Chrome\User Data\Safe Browsing UwS List Prefix Set
<LocalAppData>\Google\Chrome\User Data\ev_hashes_whitelist.bin
Raymond
Thanks Raymond - I've implemented your suggestions. I'll monitor it over the next few days to see if it reduces the size significantly and update the post when I know the result. ![]()
You can download the GPO template for Chrome from http://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip Among other valuable settings, these policies allows you to specify where to store the data directory (appdata\roaming) and also lets you store the cache directory independently (appdata\local).
We are using direct flex successfully because we specify "Export at logoff" to cope with the many chrome.exe's that spawn. This results in a quick login but possibly a slow chrome launch.
Here is our config:
#dont do export at exit because of how many exe's chrome spawns
[IncludeRegistryTrees]
HKCU\Software\Google
[IncludeFolderTrees]
<AppData>\Google\Chrome
[ExcludeFolderTrees]
<AppData>\Google\Chrome\User Data\Default\Application Cache
<AppData>\Google\Chrome\User Data\Default\Local Storage
<AppData>\Google\Chrome\User Data\Default\Media Cache
[ExcludeFiles]
*.tmp
Did this work for you ?
Ray
I'm still monitoring, but it does seem to be doing the trick. ![]()
Good to hear, let us know if there are unforeseen issues
