Chrome.zip

Chrome UEM Config file.

Attachments
Comments

Note: DirectFlex has a limitation with Google Chrome.

The problem is that Google Chrome creates a lot of chrome.exe processes when you use the application. One chrome.exe proces per tab, but also some processes for housekeeping like database integrity checking, etc.

DirectFlex tries to keep track of each of these processes, because the DirectFlex Export should only happen when the last chrome.exe process exits. The problem is that Chrome doesn’t stop these processes in a regular way, so there is no way for Windows and UEM to keep track of the number of processes. Some processes simply stop and disappear without properly notifying Windows, therefor DirectFlex cannot keep track of the number of processes and UEM cannot predict if the DirectFlex export will happen at the correct moment in time.

You have two options: import and export the Chrome settings at logon and logoff.

Or option 2, enable DirectFlex, but select the option to only ‘export at logoff’.

Just worked with at customer on this.  With this config file the Cache folder was still being captured because the "User Data" folder path was missing.

Adding this exclusion resolved the issue.

<LocalAppData>\Google\Chrome\Default\Cache

This template is woefully inadequate - you end up with huge profiles that increase logon times by minutes for any heavy Chrome user. The config below works far better:

Edit - The references to Profile 1 & 2 are because if your organisation allows users to log into Chrome, it creates a new profile path literally named "Profile 1" and does NOT use "Default."

[IncludeFolderTrees]

<LocalAppData>\Google\Chrome\User Data

[IncludeRegistryTrees]

HKCU\Software\Google\Chrome

HKCU\Software\MozillaPlugins

[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\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\Default\Pepper Data\Shockwave Flash\CacheWriteableAdobeRoot

<LocalAppData>\Google\Chrome\User Data\Default\IndexedDB

<LocalAppData>\Google\Chrome\User Data\Profile 1\Cache

<LocalAppData>\Google\Chrome\User Data\Profile 1\Application Cache

<LocalAppData>\Google\Chrome\User Data\Profile 1\Storage

<LocalAppData>\Google\Chrome\User Data\Profile 1\Local Storage

<LocalAppData>\Google\Chrome\User Data\Profile 1\Media Cache

<LocalAppData>\Google\Chrome\User Data\Profile 1\Session Storage

<LocalAppData>\Google\Chrome\User Data\Profile 1\GPUCache

<LocalAppData>\Google\Chrome\User Data\Profile 1\Web Applications

<LocalAppData>\Google\Chrome\User Data\Profile 1\Sync Data

<LocalAppData>\Google\Chrome\User Data\Profile 1\Sync Data Backup

<LocalAppData>\Google\Chrome\User Data\Profile 1\Pepper Data\Shockwave Flash\CacheWriteableAdobeRoot

<LocalAppData>\Google\Chrome\User Data\Profile 1\IndexedDB

<LocalAppData>\Google\Chrome\User Data\Profile 2\Cache

<LocalAppData>\Google\Chrome\User Data\Profile 2\Application Cache

<LocalAppData>\Google\Chrome\User Data\Profile 2\Storage

<LocalAppData>\Google\Chrome\User Data\Profile 2\Local Storage

<LocalAppData>\Google\Chrome\User Data\Profile 2\Media Cache

<LocalAppData>\Google\Chrome\User Data\Profile 2\Session Storage

<LocalAppData>\Google\Chrome\User Data\Profile 2\GPUCache

<LocalAppData>\Google\Chrome\User Data\Profile 2\Web Applications

<LocalAppData>\Google\Chrome\User Data\Profile 2\Sync Data

<LocalAppData>\Google\Chrome\User Data\Profile 2\Sync Data Backup

<LocalAppData>\Google\Chrome\User Data\Profile 2\Pepper Data\Shockwave Flash\CacheWriteableAdobeRoot

<LocalAppData>\Google\Chrome\User Data\Profile 2\IndexedDB

<LocalAppData>\Google\Chrome\User Data\WidevineCDM

<LocalAppData>\Google\Chrome\User Data\EVWhitelist

<LocalAppData>\Google\Chrome\User Data\pnacl

<LocalAppData>\Google\Chrome\User Data\recovery

<LocalAppData>\Google\Chrome\User Data\SwiftShader

<LocalAppData>\Google\Chrome\User Data\SwReporter

<LocalAppData>\Google\Chrome\User Data\ShaderCache

<LocalAppData>\Google\Chrome\User Data\PepperFlash

<LocalAppData>\Google\Chrome\Application\

[ExcludeFiles]

<LocalAppData>\Google\Chrome\User Data\Default\ChromeDWriteFontCache

<LocalAppData>\Google\Chrome\User Data\Profile 1\ChromeDWriteFontCache

<LocalAppData>\Google\Chrome\User Data\Profile 2\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

*.tmp

FYI, if Google Chrome with this config is still making users re-sign into websites (including Google Cloud Sync being paused) each time they login to a new non-persistent session... What fixed this in my environment was enabling the built-in UEM config "Windows Settings > Personal Certificates"

Oddly, when I look at the current user personal certificates via MMC, there is nothing specific to Google Chrome. So I'm not sure what specifically is being persisted in this config to resolve this issue, but it's working for me.

Thanks,

Justin

We are seeing where users Chrome will not launch. The only fix i have found is to delete the app vol for them (which seems heavy handed) and this is only temporary for some users. We are using UEM with app vol set to UIA only.

My configuration is similar to what alsmk2  posted in UEM

Version history
Revision #:
1 of 1
Last update:
‎03-15-2016 05:09 PM
Updated by: