PS C:\> Restart-WebAppPool MSExchangeAutodiscoverAppPool Run PowerShell as administrator and run the following command.
Do this on all the Exchange 2013 or Exchange 2016 servers! There will be no disruption when the MSExchangeAutodiscoverAppPool is restarting. Restart the Autodiscover Application Pool on the Exchange Server 2013 or Exchange Server 2016 servers. To resolve this issue, restart the MS Exchange Autodiscover Application Pool. What is the fix for Outlook not connecting to Exchange? Exchange Server 2010 responds with a 302 redirect back to Exchange Server 2013 or Exchange 2016. Why is it happening?Īfter the mailbox move completed to Exchange Server 2013 or Exchange 2016, it continues to proxy the autodiscover request to Exchange Server 2010. After restarting Outlook, the client remains disconnected. The user starts up Outlook to connect to Exchange Server. The migration of the mailbox was from Exchange Server 2010 to Exchange Server 2013 or Exchange Server 2016. What is happening? The user mailbox migration completes. What if you are going to migrate a lot of users in the coming weeks?.What is the fix for Outlook not connecting to Exchange?.
