locked
Issue with Outlook slowness on remote sites, Exchange 2016 RRS feed

  • Question

  • We recently migrated some users from exchange 2010 to 2016. We see users having issues with slowness in outlook. I mean opening outlook and selecting one mail or the other takes 5-6 seconds time to load. Initially I thought there is some issue with outlook but it is not. Let me explain.

    We have a total of 8 exchange servers in below sites. In each site we have 2 exchange 2010 and 2 exchange 2016 servers with DAG enabled.
    In first site, we have 4 exchange servers
    In second site, we have 4 exchange servers

    For Internal and External name spaces we are using common name space.

    The problem is,
    In first site, users don't have any problems with slowness in outlook, as I can see they are connecting to local exchange sever.

    But in second site, users are having slowness in outlook. After checking the resource monitor on a PC, found that outlook is trying to contact exchange server in First site instead of Second site and it has huge latency. When I add a local host entry on a PC and pointing autodiscover URL to local exchange server in Second site then outlook slowness issue is resolved. 
    Normally users should connect to the exchange server where the mailbox is located but it is not happening in our case. I am not sure why outlook is contacting exchange server located in remote site. 

    This problem wasn't there on exchange 2010 mailboxes and I can see outlook is successfully contacting to the local exchange servers where the mailbox is located.  We are in the process of migrating mailboxes to 2016 and we got stuck with this issue.

    I couldn't able to figure out the problem. Can anyone help me on this.

    Friday, June 1, 2018 9:23 AM

Answers

  • Thanks for your reply Manu.

    I have checked on both sites and both showed same URI but with different site names. I have further checked with Microsoft professional support on this and they suggested us to use multiple name spaces instead of single name space where there are bandwidth and network challenges. So as per there suggestion, I have created multiple name spaces on both the sites and after that issue is resolved.

    The strange thing is it worked earlier in Exchange 2010 for so many years and it didn't worked after moving to Exchange 2016. 

    • Edited by Vinay.Manchi Monday, June 25, 2018 5:30 PM
    • Proposed as answer by Niko.Cheng Tuesday, June 26, 2018 1:24 AM
    • Marked as answer by Vinay.Manchi Wednesday, June 27, 2018 9:51 AM
    Monday, June 25, 2018 5:29 PM

All replies

  • Hi Vinay,

    Please run the following command in two sites and check if any differences:

    Get-ClientAccessService |fl name,AutoDiscoverServiceInternalUri,AutoDiscoverSiteScope

    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Niko.Cheng Thursday, June 7, 2018 8:51 AM
    Monday, June 4, 2018 9:29 AM
  • Thanks for your reply Manu.

    I have checked on both sites and both showed same URI but with different site names. I have further checked with Microsoft professional support on this and they suggested us to use multiple name spaces instead of single name space where there are bandwidth and network challenges. So as per there suggestion, I have created multiple name spaces on both the sites and after that issue is resolved.

    The strange thing is it worked earlier in Exchange 2010 for so many years and it didn't worked after moving to Exchange 2016. 

    • Edited by Vinay.Manchi Monday, June 25, 2018 5:30 PM
    • Proposed as answer by Niko.Cheng Tuesday, June 26, 2018 1:24 AM
    • Marked as answer by Vinay.Manchi Wednesday, June 27, 2018 9:51 AM
    Monday, June 25, 2018 5:29 PM
  • Hi Vinay,

    Glad you solved the issue, and thanks for your sharing. Please mark it as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, June 26, 2018 1:26 AM