Google Chrome + Non Persistent + App Vols |VMware Communities

We’ve been deploying “Google Chrome Enterprise” AppStack to our users via JMP assignments. And we’re noticing that the Chrome Archive file can go up to 200-400 MB. This causes the Chrome application to launch very late.


Are there any recommendation on how to deploy Google Chrome Enterprise where we can retain as much settings as possible without expanding the zip file too much?



We use DEM folder redirection + Roam AppData


I’ve heard ideas of enabling RoamingProfileSupportEnabled policy does anyone have experience with that?




As of now the settings in place are:











<LocalAppData>GoogleChromeUser DataDefaultApplication Cache

<LocalAppData>GoogleChromeUser DataDefaultCache

<LocalAppData>GoogleChromeUser DataDefaultLocal Storage

<LocalAppData>GoogleChromeUser DataDefaultMedia Cache





Source link

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *