Restart-WebAppPool MSExchangeAutodiscoverAppPool The suggestion was based on a Microsoft KB article … Outlook logon fails after mailbox moves from Exchange 2010 to Exchange 2013 or Exchange 2016.Įssentially, the resolution suggested is to restart the Autodiscover App Pool on the Exchange 2016 server where the “problem” mailbox resides. In my frustration, I posted a question to the community in hopes for a quick response and I got one. This is not an ideal resolution by any stretch of the imagination. Unfortunately, the only resolution we stumbled across was to delete the Active Directory user account and associated mailbox, and create brand new items for both. Export the mailbox contents to PST, delete the mailbox, and create a new one on Exchange 2016.Export the mailbox contents to PST, delete the mailbox, and create a new one on legacy server and move to Exchange 2016.Delete the Outlook profile and recreate.Also, the issue exists on other workstations and varying Outlook clients while attempting to connect to the same mailbox.Įfforts to resolve the issue that were unsuccessful, included… Also, the users are able to connect to their Exchange 2016 mailbox using OWA and smart devices.Īnd when the mailbox is moved back to the legacy Exchange server, Outlook connects without issue. And, unfortunately, during the Outlook profile reconfiguration, the option to run the Outlook connection status and autoconfiguration tests are unavailable to see what the issue might be from the workstation.Īutodiscover is confirmed to be configured properly and works fine and tests using work without error.Īgain, other users are able to connect to their Exchange 2016 mailboxes. What’s odd to me is that this experience is inconsistent with other mailboxes that were previously moved to Exchange 2016 and Outlook is connecting without issue.Įssentially what happens after an existing mailbox has been moved to Exchange 2016 and the Outlook client is restarted, the autoconfiguration process fails during the “Log on to server” task.Īs a result, Outlook is never able to attach to the mailbox on Exchange 2016 or update the existing profile. One of the latest issues I’ve experienced has been with an Outlook client (2010 or newer) not connecting to a mailbox that has been moved to (or even newly created in) Exchange 2016. Choose Outlook and type your question in the search box.Lately, it seems as if I run across some new issue or anomaly on a weekly basis after implementing Exchange 2016 for one customer or another. It’s quite frustrating but it does wonders for building a personal knowledge base. Get more information about Outlook on the Web (OWA) by visiting. This option saves email addresses when you send messages. The private computer option logs out of email after eight hours of inactivity. Select the private computer option if you are the only person who uses that computer and it is managed by VUMC. In addition, it does not save email addresses when you send messages. For security reasons, the public computer option logs out of email after 30 minutes of inactivity. Examples of a public computer include clinical workstations, computers in a public place, those shared in an office, and kiosks. Select the public option if you are checking email on a public computer that will be used by more than one person. Please review the choices and their behaviors below: Outlook on the Web (OWA) Security Options Public or shared computer Your choice could be different depending on where you are. The Outlook on the Web (OWA) login page has two security options that allow you to indicate if you are using the software on a public or private computer. Outlook on the Web (OWA) is available for VUMC computers without access to the full Microsoft Office 365 experience, and to VUMC employees who need to login to their email when away from the main Medical Center network. Overview Sign-in to Outlook on the Web (OWA)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |