We have been struggling with the above issue since we have been using Edge Chromium (version 80). I tried to create a microsoft tickets but it seems this needs a paid support contract. The testlab computer has the following setup: Could the combination of edge + azure account and roaming profiles be a problem? And even if it is, how can we fix this? So we need to fix this instead of applying workarounds. We are runnning a script to automate the first workaround multiple times a day as users are roaming from computer to computer. When we close and run edge without the parameters, sync and login does not work anymore This forces the loginscreen to appear and we can complete the login and sync is enabled. Run edge with the -force-oneauth parameters. After this edge resets the compatibility mode itself so when start edge the next time it runs normal. Then we get a login screen and can complete login. kill all edge processes, delete the edge folder in appdata and run edge in win7 compatibility mode.
We searched the internet and found 2 workarounds: The user logs in with a roaming profile and when opening edge, nothing seems to happen when clicking the login-button. We have a testlab and replicated the problem. However, more and more users complain that the login-button in edge does nothing (some claim they see the login screen flash very quickly).
This also adds a microsoft account to 'access to work and school' (the local AD is already present). When succeeding, the sync is enabled and favorites in the favorites bar are visible. Then they open edge and try to login using their azure ad account to setup synchronization.
When a roaming user logs in at a computer for the first time they can open without enterying credentials so SSO is working.
0 kommentar(er)
