In my work to get Google Chrome being a good citizen in an enterprise environment it is not time to look at roaming the Chrome settings. Chrome has support for roaming profile data and it can be enabled using a Group Policy which is great. Is it perfect, no it doesn’t roam Extensions for example. Is that a problem in an enterprise, perhaps I will cover that in a later post.
Note: that this settings disable cloud sync of Chrome settings for the end-users.
The file is stored per default in C:\Users\%UserName%\AppData\Roaming\Google\Chrome\User Data\Default and it is called Profile.pb which in my scenario is fine then I can roam it using UE-V in Windows 10. You can move the file it creates using another Group Policy setting: “Set the roaming profile directory” so we can choose to save it somewhere else that is synced by another solution perhaps.
The .xml template used for UE-V is really simple, it only includes the profile.pb file.
The file can be downloaded here:
We then register the new template either using PowerShell or an UE-V Template share.
And the result is an amazing end user experience!