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...
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
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
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
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
- 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.
