Roaming profiles and Google Chrome sign in

[googlemad]

To help reduce login time for staff I am testing excluding lots of directories from their roaming profile sync including the entire 'Google' folder. The idea being they can just 'sign in' to Chrome and have all their history / extension settings / junk stored on Google's servers rather than ours.

 

However since I have been a bit brutal by killing the entire Google directory from roaming this means Chrome doesn't remember the fact they've signed in so they have to sign in every reboot. Any way to resolve this?

[woreilly]

I tend not to exclude the whole of google, I tend to just redirect User Data, look for the "Set User Data Directory" policy. I put that path as a folder within their home drive i.e. N:\Google Chrome (where N: is the home drive letter).

[jaminben]

We also tend to do what woreilly does and redirected Google data to their home drive.... works pretty well.

[googlemad]

How big is the data generally? Is there a way to make it not store any cache files in there? (This is mainly what was clogging up the profiles, sometimes in terms of GBs rather than MBs!)

[jaminben]

On average ours would be around 80mb\130mb.

[fiza]

We also tend to do what woreilly does and redirected Google data to their home drive.... works pretty well.

 

Does this work if they leave themselves logged in and Chrome open on one workstation and then login & try to open chrome on another workstation?

 

I have found that they have to close Chrome on the original workstation before it will open on the new one. Its the only thing stopping me from redirecting google data for all staff. Currently only have it on for about 4 staff for testing.

[jaminben]

You are correct... they can only use Chrome when logged into one machine at a time.

 

We took the view that moving Chrome out of profiles improved login's for everyone and not just the few who may want to use two machines at once.