![]() Restart-WebAppPool MSExchangeServicesAppPool To resolve this issue, run the following commands to restart the Autodiscover Application Pool and the Exchange Web Services Application Pool on the Exchange Server 2013 or Exchange Server 2016 servers: Restart-WebAppPool MSExchangeAutodiscoverAppPool Exchange Server 2010 responds with a 302 redirect back to Exchange Server 2013 or Exchange Server 2016 (depending on the upgrade). Outlook eventually succeeds in looking up the free/busy information if the user waits for 12 hours or longer.Īfter the mailbox move is complete, Exchange Server 2013 or Exchange Server 2016 continues to proxy the EWS request to Exchange Server 2010. ![]() After the mailbox is moved and the user tries to look up the free/busy information for another user in the organization, they see hash marks instead of the expected time blocks.The user's mailbox is moved to Exchange Server 2013 or Exchange Server 2016.This issue occurs in the following scenario: When Microsoft Outlook mailboxes are moved to Microsoft Exchange Server 2013 or Exchange Server 2016, users can no longer see the free/busy information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |