Forum Discussion
Sync isn’t available for this account
- Thanks,
so the problem only happens on Hybrid environments where Edge doesn't use (fails to recognize) the UPN and instead uses the old fashioned down-level logon name (pre-Win 2000 era style).
Irony is that Edge on Windows Server 2019 which is newer uses the old style and on Windows server 2016 which is older uses the new UPN style.
HotCakeX Same domain, same (hybrid) account, different OS. The problem is that the Microsoft Edge First-run Wizard uses the wrong username (SAM) on Windows Server 2019, where as the same wizard on Windows Server 2016 uses the correct user name (UPN).
Best regards,
Dennis.
so the problem only happens on Hybrid environments where Edge doesn't use (fails to recognize) the UPN and instead uses the old fashioned down-level logon name (pre-Win 2000 era style).
Irony is that Edge on Windows Server 2019 which is newer uses the old style and on Windows server 2016 which is older uses the new UPN style.
HotCakeX is there any way to modify an existing DOMAIN\User profile to a correct UPN, i.e. mailto:user@domain.com profile? Adding a new profile, renaming the old profile, and replacing the new profile with the old one as suggested below does not help that fact that I have setup my local Edge profile on my laptop with both my existing Chrome and Firefox favorites already. I was hoping to not have to start from scratch again. It would also be a great feature to simply export the data from a profile to make future issues like this easier to resolve.
Any updates on this? I want to start rolling out Edge for my Windows 10 clients in our hybrid environment, but this annoying UPN issue is preventing this. Any workarounds known? (without creating/deleting profiles)
