We are trying to do the same, but are also failing to get this to function.
And you are right, this Edge version is WAY better.
The fact that the official status is BETA might not help us out here..
MOST of us like to get ahead of things like this, as the release is next week. I don't want to be scrambling around after the next Windows Update goes live, trying to patch together a solution. I was hoping that we could either rely on VMware as a strategic partner...or at least come together as a community to resolve this upcoming disaster. We all remember how much of a pain Chrome was to capture...this is no different.
"On January 15, 2020, Microsoft is expected to begin the automatic rollout of the new version of Microsoft Edge based on the Chromium engine through Windows Update on devices running the Windows 10 April 2018 Update (version 1803) and newer releases to replace the legacy version."
Tick Tock, Tick Tock.
I've done some quick tests.
The Canary channel installs Edge in the LocalAppData folder, not what you want.
So I switched to the Beta channel, this installs Edge in the Program Files folder.
After that I ran the Edge browser through the Profiler and done some quick and dirty 'optimization' to create this Config File:
As you can see, settings are stored in a folder called 'Edge Beta', probably because this new Chromium Edge gets installed next to the existing Edge. So we need to wait for the final release to see how this would behave.
With the config file content above I was able to roam the start page, theme, favorites, saved passwords, etc. I could not detect any broken or missing settings.
The .ZIP file was 35MB in size, but we might be able to optimize this by excluding stuff we don't need. Focus right now for me was to see if we could capture all settings.
Please give this a try and let me know your results.
1 person found this helpful
Mine was very very large, so I'm trying to scale it back a little. I'm running both Edge Beta & Dev, so you will see duplicates.
Since the Profile.pb is not (yet) available, it's not working as smoothly as our Chrome DEM policy...but this is a start.
It keeps logging in with my Work Domain\UserID which cannot sync. If I manually login using my full UPN (same AD account) Sync works via Azure.
# This is for the new MS Edge Chromium browser rolled out in 2020. **NOT WORKING WELL YET **
<LocalAppData>\Microsoft\Edge Beta\User Data\Default\Cookies
<LocalAppData>\Microsoft\Edge Dev\User Data\Default\Cookies
<LocalAppData>\Microsoft\Edge Beta\User Data\Default\Bookmarks
<LocalAppData>\Microsoft\Edge Dev\User Data\Default\Bookmarks
<LocalAppData>\Microsoft\Edge Beta\User Data\First Run
<LocalAppData>\Microsoft\Edge Dev\User Data\First Run
<LocalAppData>\Microsoft\Edge Beta\User Data\Default\Preferences
<LocalAppData>\Microsoft\Edge Dev\User Data\Default\Preferences
I'm hoping that that Chrome's manual (profile.pb) will be added...but there's not much discussion on the topic.
Here is my Google Chrome settings to compare. It's very simple.
# Based on this support article, to make Google Chrome work with roaming user profiles:
# The roaming user profile contains information such as bookmarks, autofill data, passwords, per-computer browsing history, browser preferences, and installed extensions.
# It doesn’t contain information about cookies, browsing sessions, cached or downloaded files, and other local browser instance and transient data.
<LocalAppData>\Google\Chrome\User Data\First Run
1 person found this helpful
Looks like there is a different thread on this topic here: Edge Chromium template
Please use the ones in that thread, as the ABOVE settings will result in a large Zip file.