Jump to content

Recommended Posts

Posted

Been playing with this all day and the magic answer does appear to be as others have said above in that inside the Chrome GPO set the following:-

 

Enable to creation of roaming copies for Google Chrome profile data = ENABLED

Set user data directory = ENABLED (my path is r:\chrome\User Data)

Set the roaming profile directory = ENABLED (but leave the path blank)

 

These settings are working for me, the profile.pb is now being written to C:\Users\%username%\AppData\Roaming\Google\Chrome\User Data\Default whereas the cache and the user settings etc roam nicely from r:\chrome

 

I think it was the redirecting the profile.pb to a network drive and that being locked which was causing all my problems. So far, no Chrome complaints today :)

Posted
  1. Enable to creation of roaming copies for Google Chrome profile data = ENABLED
  2. Set user data directory = ENABLED (my path is r:\chrome\User Data)
  3. Set the roaming profile directory = ENABLED (but leave the path blank)

FWIW, with local profiles and UE-V you only need to enable the first policy. :)

 

the profile.pb is now being written to C:\Users\%username%\AppData\Roaming\Google\Chrome\User Data\Default whereas the cache and the user settings etc roam nicely from r:\chrome

Won't having Chrome's cache on the R:\ drive gradually fill up your file server (and be slower compared to the local drive)? :confused:

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...