Forum Discussion

Deleted's avatar
Deleted
Apr 30, 2023

Exchange 2013/2019 coexistence and client connectivity to new 2019 problem

Hey all,   Some details first: Forest/Domain functional level: 2012 R2 (only one domain) 2 x Exchange 2013 CU 23 Servers in a DAG (both on Server 2012) 1 x Exchange 2019 CU 12 server (Server 202...
2013
2019
Exchange Server
outlook
Deleted's avatar
Deleted
May 01, 2023

Thanks for the reply Dan_Snape 

 

I had gone through the Deployment Assistant you linked.

 

I have also run the Test Autodiscover and it shows successful.  It was showing this even when itself Outlook wasn't connecting.

 

Strange.  I decided to let Outlook run for a while and it seems to be connected now and stable.

 

Is it perhaps normal for it to not connect initially as it perhaps searches for my mailbox, seeing as my mailboxes database isn't on the server I am connecting to?  It took a while though (I wasn't watching it so not sure exactly how long, but at least 20 minutes).  I have a couple of shared mailboxes attached so that may increase the time of the search?

 

Is there a way to confirm Outlook is definitely using the 2019 server for client access?  I flushed my dns after changing the hosts file and pinging our namespaces returns the IP of the 2019 server.

 

I assume the version displayed below is for the mailbox rather than the client access part?

 

thanks

Dan_Snape's avatar
Dan_Snape
Bronze Contributor
May 02, 2023
Generally client connectivity is controlled by DNS. The version does give a good indication though. Try the test email configuration utility and that will show you what URLs are returned to the client for connectivity.
  • Deleted's avatar
    Deleted
    May 02, 2023

    Dan_Snape 

    Definitely connected to the correct url's, just want to be sure that I am using 2019 for client access.

     

    There was that issue with random disconnects after first changing my hosts file so I'm not sure what was happening in the background (maybe that ol' black magic like the Send Connectors :smile:).

     

    EDIT: Test Email AutoConfiguration and Connection Status all show https://webmail.domain.com/XXXXX for all connections.  Browsing to https://webmail.domain.com/ecp shows the 2019 console.

     

    The version in Connection Status shows the 2013 server version.  Do we know if this is because my mailbox is still on 2013 (and this is the mailbox database version), or does it show this because 2019 is transparently proxying the request and Outlook assumes it is connected directly to a 2013 server?

     

     

    • Dan_Snape's avatar
      Dan_Snape
      Bronze Contributor
      May 03, 2023
      I'd say it was the latter...but not 100% sure
      • Deleted's avatar
        Deleted
        May 04, 2023
        I had another user change their hosts file and their Outlook just worked like normal, no disconnections. They also have a few shared mailboxes linked.

        I can see their username and pc ip in the iis logs of the 2019 server so they are connecting through it.

        Next test is migrating the mailbox of my test user on 2013 to 2019 and see how that goes!