![]() ![]() If you are presented with the square window, which we believe occurss if you have a half baked domain name in use in O365, then the fix is the registry AutoDiscover fix to tell Office to sod off, and stop trying to talk to O365 servers for auth. It truly is a nightmare to administer and could have been made much simpler. The main issue we have with this client, is that they are not big enough to go down the Office VL route so have to put up with the 'several' Microsoft Accounts (non-O365) to register every 30 copies of Office 2016 H&B. Hopefully this is just progression pains as they work towards their authentication utopia.īack to the topic in hand, a SQUARE box represents Office 365 credentials whereas a portrait RECTANGULAR Authentication window represents a Microsoft account, not necessarily linked to your office 365 account. Let's be frank, Microsoft haven't got a clue how to manage user accounts fort their differing websites/portals and it's all very messy. ![]() The AutoDiscover Registry fix has resolved the issue however, this took over 5 hours to get to this point.įor anyone reading this post with similar issues, please pay attention to the box format that the username and password is presented within.Īs per my posted picture above, the box is square and this is asking for an Office 365 account, not for a Microsoft Account. Since the fix, we haven't had a single complaint about random, unexpected password prompts. We dealt with the issue for about 2 or 3 months, during which we had to constantly clear credential manager, rebuild profiles and even had to resort to using OWA for 1 user temporarily. This link outlines enabling modern auth for all office products. ![]() The link below has a section that shows how to enter this for Outlook 2013, but just change the 15 to 16 for Outlook 2016. I know the link is for Exchange Online, but I assume the PowerShell commands are the same once you are connected to the Exchange instance.Īs for the client, you just need to create the "EnableADAL" registry keys. The solution that ended up working for us was to enable modern authentication on both the client and server side and disable legacy authentication. Users would get the popup constantly and it was causing a lot frustration for both our users as well as our support team. We had a similar issue with cloud exchange and Outlook 2016. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |