strategicpana.blogg.se

\Microsoft\Edge Dev\User Data\Default\Preferences \Microsoft\Edge Beta\User Data\Default\Preferences

\Microsoft\Edge Dev\User Data\Default\Bookmarks \Microsoft\Edge Beta\User Data\Default\Bookmarks \Microsoft\Edge Dev\User Data\Default\Cookies \Microsoft\Edge Beta\User Data\Default\Cookies

# This is for the new MS Edge Chromium browser rolled out in 2020. If I manually login using my full UPN (same AD account) Sync works via Azure. It keeps logging in with my Work Domain\UserID which cannot sync. Since the Profile.pb is not (yet) available, it's not working as smoothly as our Chrome DEM policy.but this is a start. I'm running both Edge Beta & Dev, so you will see duplicates. Mine was very very large, so I'm trying to scale it back a little. Please give this a try and let me know your results. Focus right now for me was to see if we could capture all settings. ZIP file was 35MB in size, but we might be able to optimize this by excluding stuff we don't need. I could not detect any broken or missing settings. With the config file content above I was able to roam the start page, theme, favorites, saved passwords, etc. So we need to wait for the final release to see how this would behave. HKCU\Software\Microsoft\Windows\CurrentVersion\Internet SettingsĪs 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 I switched to the Beta channel, this installs Edge in the Program Files folder.Īfter that I ran the Edge browser through the Profiler and done some quick and dirty 'optimization' to create this Config File: The Canary channel installs Edge in the LocalAppData folder, not what you want.