Thursday, 29 October 2015

Exchange 2010 - 2013 Migration: Outlook Client Issue

During an Exchange 2010 to 2013 migration, you may get into a situation where Outlook clients with mailboxes on Exchange 2010 can no longer connect to their mailboxes once the A record for Outlook Anywhere e.g. mail.domain.com is changed to resolve to Exchange 2013.


Cause:

Although there are a number of causes, this may be because the RpcClientAccessServer parameter on the Exchange 2010 mailbox databases is set to the same FQDN as the Outlook Anywhere hostname. This means that once you change the mail.domain.com A record to resolve to Exchange 2013, the RPC/TCP clients will attempt to connect to the Exchange 2013 servers using RPC/TCP which won't work as this is no longer supported by Exchange 2013.

Usually Outlook Anywhere is enabled on Exchange 2010 but this is not always the case. If enabled, the clients *should* fail over to using Outlook Anywhere if they cannot connect using RPC/TCP on fast networks. If not enabled then clients will attempt to connect to Exchange 2013 using RPC/TCP and will fail. (Note that enabling Outlook Anywhere on Exchange 2010 is a required step in an Exchange 2010 to 2013 migration)


Resolution:

To resolve this issue, enable Outlook Anywhere on Exchange 2010 and force the Outlook clients to use HTTPS (Outlook Anywhere) on all connections. By default, on fast connections, Outlook will try to use RPC/TCP then HTTP and on slow connections Outlook will try to use HTTP first then RPC/TCP. This can be configured using Autodiscover by running the below commands from the Exchange Management Shell on Exchange 2010:

Set-OutlookProvider EXCH -OutlookProviderFlags:ServerExclusiveConnect

Set-OutlookProvider EXPR -OutlookProviderFlags:ServerExclusiveConnect

Once this is done, all Outlook clients on Exchange 2010 will be using Outlook Anywhere whether they are inside the office or not and you can change the mail.domain.com A record to resolve to Exchange 2013 so Exchange 2013 can proxy the request for the Exchange 2010 users.

Any clients that don't support Outlook Anywhere need to be configured to use Exchange 2010 by adding specifying mail.domain.com to resolve to the internal IP of your Exchange 2010 servers.


More information:
More information can be found here: http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx










5 comments:

  1. During Exchange migration from 2010 to 2013 you should consider these points:
    1. Acquainted with Release Notes
    2. Requirement of System
    3. Ensures Prerequisite steps are done
    4. Configure the Domain Name System (DNS)
    5. Choose OAB (Offline Address Book)
    6. Check legacy Domain Name System (DNS)
    7. Install Exchange 2013
    8. Prepare Exchange 2013 mailbox
    9. Virtual Directories (Exchange) configuration
    10. Configure of Digital Certification of Exchange 2010/2013
    11. Configure Send Connectors
    12. Deploy UM (Unified Messaging)
    13. Configuration of Outlook
    14. Ensure Virtual Directory Settings
    15. Testing of Exchange 2007 external URL’s
    16. DNS Record changing
    17. Migration of mailbox from Exchange 2010 to 2013
    18. Migration of public folder from Exchange 2013 to 2013
    19. Configuration of new Exchange 2013

    After applying all these steps while migration from Exchange 2013 to 2010, you fill not face any difficulty. If you face any difficulty then you go to another method Stellar Converter for EDB. This is most easily method to easily migration from Exchange 2013 to 2010. Through this method, you can ensure smooth, fast and secure migration.
    https://www.stellarinfo.com/email-repair/edb-pst-converter.php

    ReplyDelete
  2. Exchange Server Migration Features

    Exchange Server Upgrades and Migrations

    Upgrade Exchange 2010 to 2016 or migrate from one exchange server to another. If you are on an older version of exchange, you can move to a newer version with EdbMails exchange migration tool. Whether you are performing whole server upgrade or want to move users between forests, EdbMails can handle all such scenarios with ease and precision. Keep your servers up to date as EdbMails supports direct migration from Exchange 2003/2007 to 2013/2016 without needing to install Exchange 2007 or 2010 as an intermediate thus ensuring cost-effective migration.
    More info visit link :- https://www.edbmails.com/pages/upgrade-exchange-2010-to-2016.html
    Please visit official website :- https://www.edbmails.com

    ReplyDelete
  3. Exchange EDB to PST Export

    Exchange Server is the storage area for whole Exchange mailbox data. It houses all the user information. Many unforeseen reasons make these data get corrupted, which is laborious to access these valuable data. To have full access, one should need to switch over to third party Exchange server recovery tool. EdbMails EDB to PST Export tool stands top in this scenario.
    1. Recovery of accidentally deleted mailboxes:-
    In case the Microsoft Exchange turns into offline and you should regain a mailbox which is deleted by mistake, then EDB to PST tool assist you in recovering the deleted mailbox form EDB file. Browse the EDB file and in EdbMails application and load the mailboxes. Choose the deleted mailboxes and export to outlook PST. Then you can migrate the recovered mailboxes to Exchange Server
    2. Preview of Mailboxes:
    Prior to export operation, the tool provides the preview of all the mailbox items. Click on any mailbox and its folders, you can view all the E-Mails, Contacts, Calendars, Journals, Tasks etc. in the preview window.
    3. Selective EDB to PST export:
    Using this tool you can export either individual or multiple mailboxes/folders to PST. And also you have an option to apply filters based on After / Before Date, Subject, Attachment, From / To Address, CC Address, BCC Address etc.
    4. No restriction on number of mailboxes and size:
    The software allows you to export any number of mailboxes. No matter of size of the database or mailbox. You can recover and export even large sized mailboxes.
    5. No dependency of Exchange Server services or Active directory:
    Recovery process doesn’t require Exchange server services or active directory. It supports all latest Exchange versions.
    6. Life time license, upgrade:
    License is for lifetime with free software upgrades with 24/7 Technical support.
    7. Free Trial Version:
    You can have the facility to test your EDB file using “Free Trial’ version which permits you to export 30 items from each and every folder of all the mailboxes.
    software link:- https://www.edbmails.com/pages/ost-to-pst-converter.html
    EdbMails Features:-
    EDB to PST
    Free EDB to PST
    Convert EDB to PST
    EDB Recovery
    EDB to PST Converter
    OST to PST
    OST to PST Converter
    More info visit link:- https://www.edbmails.com

    ReplyDelete
  4. You can also use the OST to PST Converter tool by Data-recovery-solutions.
    The tool is capable of migrating multiple and bulk offline OST files to Outlook PST format. The OST files to PST conversion tool comprises so many unique features that make it an exclusive product among others like Bulk conversion facility, Search, Preview, Filter, Fastest Conversion, etc. In the case that user’s offline Outlook (.ost) data files are corrupted, user can fully export them as our software supports the damaged or corrupted OST files and converts them into desired file formats like PST, DBX, EML, MBOX, Archive, and MSG.
    For more info: https://www.data-recovery-solutions.com/ost-to-pst-file-converter.php

    ReplyDelete