The biggest issue with managing Google Chrome with UEM is that Chrome stores a lot of data in the %LocalAppData% folder, making it very time consuming to import and export that location.
Google provides an option to make Chrome store the browser user profile information in the Roaming AppData folder, to make it compatible with roaming user profiles.
This option stores most personal Chrome settings in a small 'profile.pb' file. This is a huge improvement over the original location, that can easily grow to 100's of megabytes.
This page describes the solution:
The site provides an ADMX template that can be imported in UEM 'ADMX based settings'.
You only need to enable the setting called 'Enable the creation of roaming copies for Google Chrome profile data'.
This will create the '%AppData%\Google\Chrome\User Data\Default\profile.pb' file, which we will further manage with a UEM config file (attached to this post).
The roaming user profile (profile.pb) contains information such as bookmarks, autofill data, passwords, per-computer browsing history, browser preferences, and installed extensions.
The downside it that the 'profile.pb' file doesn’t contain information about cookies, browsing sessions, cached or downloaded files, and other local browser instance and transient data.
I found out that capturing the 'Cookies' file from the LocalAppData folder, together with the 'profile.pb' file solves the cookies issue.
Attached is a UEM config file that you can use to test this new approach. It's not perfect yet, because some personal settings are still missing, but by including the correct specific files from LocalAppData we might get it to roam all settings, while still maintaining a small and fast UEM profile.
Please give this a try, and let me know what you are missing, or what files need to be included additionally to make this work.