![]() I will also move forward with converting more users to 2FA. I will continue to monitor and report back if I see any issues. Since running the script over 24 hours ago, zero invalid password entries in the Kerio security log, zero reports of the pop-up in Outlook that the password is wrong. I found an article on how to disable AutoDiscovery for Mac ( discovery-for-microsoft-office-for-mac) and ran the applescript on the 3 Macs with 2FA enabled. Every time there was a password failure, there were also AutoDiscovery entries in the Outlook log. UPDATE & FIX 5/3/22: after reviewing the Outlook logs and comparing to the invalid password entries in the security log, it looks like the issue is AutoDiscovery. I have enabled logging in Outlook to see if I can see an event that occurs at the same time as the invalid password attempts in the server logs. Only seeing issues with the 2FA enabled account. Interesting to note that it does not always cause the Outlook error to pop up on the user's screen.Īlso worth noting - I have 2 seperate email accounts configured in my Outlook, one with 2FA, one without. ![]() I put the logs in Excel to compare the time between failures, and it runs like clockwork - 1:15 between errors. ![]() Going back in the log, these errors started as soon as 2FA was enabled. Attempt from IP address every hour and fifteen minutes in the Security log. Very interesting results!įor the 3 users that have 2FA enabled, I see "HTTP/WebDAV: Invalid password for user. I noted the time and went to check the logs in Kerio Connect Admin. I got the "Logon failure: unknown user name or bad password" message once today. Re: Mac Outlook issues after enabling 2fa
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |