Share via

Migration from Exchange 2013 to 2019 while changing virtual directories URL

Caspar - ABO 201 Reputation points
2023-03-27T12:48:31.5433333+00:00

Hi, we are assisting one of our clients to migrate from Exchange 2013 to Exchange 2019.

Usually I would just install a new server, point DNS to the new server and move mailboxes then decommission the old server, like I've done before. The situation I have now is a bit unique and annoying.

Server configuration: (as an example)

servername: DCEX.company.com (Primary Domain Controller AND Exchange 2013 on the same server)

Internal AND external virtual directory URLs for Outlook and mobile devices dcex.company.com

servername: DC02.company.com (Second Domain Controller)

Plan on setting up new server:

servername: MAIL.company.com (Dedicated 2022 server with Exchange 2019 only)

The problem here is that I don't think I will be able to preserve the FQDN for exchange as all existing devices point to "dcex.company.com". I cannot point the internal DNS records of "DCEX" to the new mailserver using that same name as I think this will break all sort of stuff domain related (authentication/dns).

Is there any way to add a second mailserver and just setup a completely different URL (mail.company.com) and have that coexist with the current Exchange 2013 server? I'm not sure this is possible.

I have never seen such a setup so I'm a little lost on what would be the best practice here. Any advice?

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,162 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,461 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
442 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andy David - MVP 144.2K Reputation points MVP
    2023-03-27T12:53:57.6233333+00:00

    Sure, absolutely.

    For the new server, just ensure you have a valid trusted certificate applied with subject names that reflect the URLs on the 2019 client virtual directories and the Autodiscover SCP.

    Clients will find that new server and use it and as long as the cert is trusted, with no errors.

    Ensure the new remote FQDNs are reachable externally as well

    1 person found this answer helpful.
  2. Andy David - MVP 144.2K Reputation points MVP
    2023-03-27T13:10:11.29+00:00

    Yep, that will work as well!:

    https://techcommunity.microsoft.com/t5/exchange-team-blog/client-connectivity-in-an-exchange-2016-coexistence-environment/ba-p/603925

    as far as the mobile devices, if you can't point to the new Exchange Server, then yes, users will need to update their profiles to access the new servers. Not elegant but it will work.

    1 person found this answer helpful.
    0 comments