question

EnterpriseArchitect avatar image
0 Votes"
EnterpriseArchitect asked ·

Procedure for replacing the existing Hybrid Exchange 2013 with Exchange 2016?

Hi People,

I'm running Hybrid Office 365 and Exchange 2013.

I plan to install Windows Server 2016 with Exchange 2016 to run Hybrid Configuration (HCW) to replace the existing aging 2x Windows Server 2012 R2 & Exchange 2013.

There is already a namespace called email.domain.com

What are the steps I need to take to avoid downtime to the user connecting the Outlook OnPremise?

office-exchange-server-administrationoffice-exchange-server-connectivityoffice-exchange-hybrid-itprooffice-exchange-server-itprooffice-exchange-server-deployment
· 1
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@EnterpriseArchitect
I am writing here to confirm with you any update about this thread now?
If the suggestion below helps, please be free to mark it as an answer for helping more people.

0 Votes 0 ·
AshokM-8240 avatar image
1 Vote"
AshokM-8240 answered ·

Hi @EnterpriseArchitect ,

If you have planned to change only the Hybrid configuration, then you can install Exchange 2016 and re-run the Hybrid configuration wizard and configure accordingly.

https://jaapwesselius.com/2015/11/22/upgrade-hybrid-server-to-exchange-2016/

If you planned to upgrade mailboxes/services to Exchange 2016 from Exchange 2013 including Hybrid, then I would suggest to check the Deployment assistant

https://assistants.microsoft.com/
https://practical365.com/exchange-server/migrating-exchange-server-2016/

If the above suggestion helps, please click on "Accept Answer" and upvote it.

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KyleXu-MSFT avatar image
1 Vote"
KyleXu-MSFT answered ·

@EnterpriseArchitect

The DNS switch will cause at least a little impact, but the impact will not be long. Exchange on-premise mailbox will disconnect and reconnect to new Exchange server automatically.

Here are suggestions for you:

  1. Deploy Exchange 2016 coexist with Exchange 2013.

  2. Configure service URLs(such as OWA, EWS, ECP) for Exchange 2016, internal URL using "ExchangeComputerName.domain.com", external URL using "email.domain.com".

  3. Switch internal and external DNS record(email.domain.com, autodiscover.domain.com, MX record) from Exchange 2013 to Exchange 2016. (Exchange on-premise mailbox may reconnect during this step)

  4. Enable MRS Proxy on Exchange 2016 and rerun HCW to choose Exchange 2016 as end point.

Here are some article which may be useful to you:

  1. Exchange Server supportability matrix

  2. Exchange/Office 365 Hybrid Configuration Wizard – step by step guide

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

EnterpriseArchitect avatar image
0 Votes"
EnterpriseArchitect answered ·

OK, Thanks all, I've just successfully deployed new Exchange Server 2016 using the latest .ISO file from Microsoft portal: SW_DVD9_Exchange_Svr_2016_CU_19_MultiLang_Std_Ent_.iso_MLF_X22-47606.ISO

So this is my current Exchange version according to ECP:
74671-image.png

Do I still need to apply this patch: Security Update For Exchange Server 2016 CU19 (KB5000871)

or not needed?



image.png (4.3 KiB)
· 2 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Absolutely!

0 Votes 0 ·

Yes, it is needed. If there still exist Exchange 2013 in your organization, you also need to update it to CU 23, then apply KB5000871 for Exchange 2013 on it.

First update the Internet facing Exchange server, then update the others.


0 Votes 0 ·