Forum Discussion
Edge 86.0.622.58 On-premises Sync Not Working Over VPN With Cached Local Login
We are running Edge 86.0.622.58 on Win10 Enterprise 1909 domain joined systems. We are trying to configure the Edge GPO to enable local sync of favorites, but we are unable to get the on-prem s...
Kelly_Y
Do you have any update? We would really like to move to Edge as the default browser for our organization but the inability to locally sync favorites is preventing us from doing so. Perhaps Microsoft should consider using Chrome's implementation of RoamingProfileSupportEnabled which does not require any browser sign-in. The ability to simply redirect the profile.pb file to a network share such as the user's home drive would be sufficient for our purposes.
Do you have any update? We would really like to move to Edge as the default browser for our organization but the inability to locally sync favorites is preventing us from doing so. Perhaps Microsoft should consider using Chrome's implementation of RoamingProfileSupportEnabled which does not require any browser sign-in. The ability to simply redirect the profile.pb file to a network share such as the user's home drive would be sufficient for our purposes.
Kelly_Y
Microsoft
Microsoftjdbst56 I just spoke to our Identity Team and they mentioned that in your case it seems like, in VPN configuration, the Windows API that MS Edge is using, is not returning the account information needed for on-premises. They have asked the following:
Are you able to try the following steps to validate this?
- Delete all user data.
- Launch MS Edge with flag --force-on-prem-profile (msedge.exe --force-on-prem-profile)
If you cannot delete the data, then can you try the following? Create a folder and launch MS Edge with additional parameter: --user-data-dir=<folder-name>
If this works, then it confirms that the previously mentioned new policy the team is investigating will help in your scenario. Unfortunately, there is no ETA for the new policy right now but we will keep an eye out for updates from the team.
Thanks for your patience!
-Kelly
- Do we have any update on this issue? 2,439 views on this issue since Nov 2020 and still no solution. We're supposed to make Edge the default browser next month due to O365 EOL for IE. I guess we have to tell our users that they can't roam their favorites.
- Michael710 We had opened a Microsoft Premier support case two weeks ago just to see if they could give us any ETA on the new policy. Unfortunately there was really no new information other than they are working on it. Here's the summary from the case.
SYMPTOM:
• Customer wants update on new policy being created by Edge team so users will not get implicit sign-in with secondary AAD account if ConfigureOnPremisesAccountAutoSignIn is configured
CAUSE:
• N/A
RESOLUTION:
• After discussing with the Edge team, the new policy being created so users will not get implicit sign-in with secondary AAD account if ConfigureOnPremisesAccountAutoSignIn is configured, is currently still in progress.
• They do not have an exact release date or version yet, but I have indicated to them to let me know as soon as there is an ETA.
• This policy was expected to be released previously but there was a slight delay which caused a setback but they are now working to get this policy in a upcoming version and will share with me the release version as soon as they have confirmed.
• Will re-open case when there is an update on policy - Any news on this GPO? It's been so long since this thread started. On-premises AD profiles are broken in Edge. And this is not just VPN problem.
Clean installation, no Azure or MS accounts, created 3 AD Users.
First user I try gets signed in with "DOMAIN\Username" style profile (as expected). The other two however get continuously signed in with "Profile 1" profile styles.
This was tested twice in different machines. Fix this please, not everyone prefers the Azure treatment.
Thanks
