Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Exchange2010 upgrade to 2016 2010 users are unable to access their mailboxes through the 2016 agent, resulting in a connection failure.

2025-01-15 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/03 Report--

Environment description: 1 AD and certificate, 4 2010 front and back end (NLB and DAG), 2 2016 full roles.

Problem: when the mail flow is switched to 2016, the mailbox originally on 2010 cannot be connected through OUTLOOK, but it can be automatically discovered and configured successfully. Error enabling OUTLOOK Times, unable to connect to the server.

Reason: because EX2016 uses outlook anywhere to connect and proxy to 2010 of the user's mailbox. However, when 2010 users use the 2016 agent, the outlook anywhere in the client outlook does not check "in a fast network, first use HTTP to connect, and then use TCP/IP to connect", resulting in a failed connection to the EX2016 server.

The configuration needs to be changed on the server, which is achieved by modifying the OutlookProviderFlags option. The specific commands are as follows:

The following command forces Outlook to connect to Exchange using OutlookAnywhere mode:

Set-OutlookProvider EXPR-OutlookProviderFlags:ServerExclusiveConnect

Set-OutlookProvider EXCH-OutlookProviderFlags:ServerExclusiveConnect

Unset to:

Set-OutlookProvider EXPR-OutlookProviderFlags:None

Set-OutlookProvider EXCH-OutlookProviderFlags:None

For the main reasons, please refer to the following documents:

The FQDN of the MAPI/RPC client connection is the same as the FQDN of the HTTPS client connection

MAPI/RPC needs to set a unique FQDN separately and cannot be shared. Such as:

New-ClientAccessArray-Name "cas"-Fqdn "bjcas.test.com"-Site "BJ"

Https://blogs.technet.microsoft.com/exchange/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations/

* * this solution is only a temporary measure. Please use only a unique ClientAccessArray domain name and need to be manually updated by the client (outlook repair feature).

If you migrate directly, there will be a large number of outlook pop-up windows for later users (prompting the administrator to make changes), resulting in a poor user experience.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report