move an exchange 2010 on premises server running in a hybrid configuration to a new server running exchange 2016

Robert Wills 20

I need to move off exchange 2010 running in a hybrid configuration with exchange online to a new server running exchange 2016 as i believe this is the only supported configurationI installed exchnage 2016 on a new windows server but it fails

4 answers

Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-02T09:25:09.8833333+00:00

Hi，

Thanks for posting your question in the Microsoft Q&A forum.

Based on your description, I have a few questions to confirm with you.

Did you get errors when installing Exchange 2016? If so, could you please provide the screenshot of the error? If not, please provide more details.

You could refer to the following document for migration.

Exchange On-Premises Best Practices for Migrations from 2010 to 2016 - Microsoft Community Hub

In order to better upgrade Exchange, we recommend that you use the Exchange Deployment Assistant.
Please sign in to rate this answer.
Robert Wills 20 Reputation points

2024-05-03T02:19:28.7533333+00:00

Hi Bruce thank you for your response and I realise I am late (very) to the party to get off 2010.. The install seemed to work okay, I used the cmd line with setup.exe and options to prep AD and then ran setup on the ISO to install. Didn't get any errors - once I had figured the correct switches out. I will have a look through that link and see if I can find my mistakes. I have been following this https://www.linkedin.com/pulse/migrating-exchange-server-2010-2016-existing-hybrid-office-sharif/

CU levels are all good I need to move Exchange to another server and run Exchange 2016, partly to get to a newer version also to try and tidy up the environment. The exchange deployment assistant doesn't allow me to select Exchange 2010 only 2013 or 2016, unless there is an old version out there.

I have errors in Event viewer similar to this

Cmdlet failed. Cmdlet test-SetupPrerequisites, parameters -DomainController "dc-name" -ExchangeVersion "15.1.2507.6" -Roles ("Mailbox","UnifiedMessaging","ClientAccess","Bridgehead","FrontendTransport","Cafe") -ScanType "PrecheckUninstall" -SetupRoles ("Mailbox","UnifiedMessaging","ClientAccess","Bridgehead","FrontendTransport","Cafe","AdminTools","LanguagePacks") -TargetDir "C:\Program Files\Microsoft\Exchange Server\V15" -HostingDeploymentEnabled "False".

Appreciate any suggestions you or any have to get this moving and off the todo list.

Robert

Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-06T09:57:04.0466667+00:00

Hi，

Based on your description, I would like to confirm:

1.Is your Exchange 2016 server installed successfully? Is it working properly?

"CU levels are all good I need to move Exchange to another server and run Exchange 2016" Can you explain it in detail? Did you install Exchange Server 2016 on another computer? Or move Exchange Server 2010 to another computer and then upgrade to Exchange Server 2016?

Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-09T10:03:09.4266667+00:00

Hello, it's been a long time since I've heard from you, did my previous reply help you, if it was useful, you can mark it as an answer. Thank you for your understanding and support.

Robert Wills 20 Reputation points

2024-05-09T21:41:12.0866667+00:00

Hi Bruce apologies i checked back but didn't see any comments previously and had another task that needed closing.

In answer:

1-It is installed but not running properly, I have run updates across it to see if that helps but i am getting these errors in Event Viewer so I am working through them. I believe the first one is acceptable as CA is turned off as part of the hybrid config, the others not 100%

[Owa] Marking ClientAccess 2010 server ClientAccess 2010 server <servername> (https://servername/OAB) as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. --->

[Ews] Marking ClientAccess 2010 server ......Basically same details as above.

[RpcHttp] Marking ClientAccess 2010 server .....Basically same details as above.

2-I checked the existing Exchange server CU was at or above the minimum level to to upgrade to Exchange 2016 and I used Exchange 2016 CU 23 iso. I created a new VM running Windows server 2019 and installed the Exchange 2016, from what i had read it is not supported to do an in place upgrade from Exchange 2010 to 2016. When I attempt to start EAC on the new server at the server i get Access to localhost denied error. Exchange Mgmt Shell Opens though. There is obviously something i am missing and it makes me think of shutting down the Existing Exchange server and manage email via powershell, but that will give me another series of headaches i am sure.

Thank you for any help Bruce

Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-14T09:45:45.0566667+00:00

Hi，

According to your replies, you should now be in a 2010 hybrid environment, and you have added Windows 2019 to this environment. Exchange 2016 has been installed in the Windows 2019 environment.

Is my summary of your current environment correct? If not, please point it out.

I still have a few questions to confirm with you:

"CA is turned off" Can you clarify what this CA is?

After you installed Exchange 2016, does Exchange 2010 not work properly?

"When I attempt to start EAC on the new server at the server i get Access to localhost denied error. Exchange Mgmt Shell Opens though." Does this sentence mean that you cannot open EAC, but you can use Exchange Server PowerShell?

according to the error message “denied error”, it seems to be permission issue, you could try to create a new admin for test.

Robert Wills 20 Reputation points

2024-05-14T20:44:55.3466667+00:00

Hi Bruce as follows

Is my summary of your current environment correct? If not, please point it out.

I still have a few questions to confirm with you: -Yes

"CA is turned off" Can you clarify what this CA is? - Client Access as we are in hybrid client machines have to go to MS365

After you installed Exchange 2016, does Exchange 2010 not work properly? - Exchange 2010 is working okay but I am trying to get onto Exchange 2016 and decommission 2010

"When I attempt to start EAC on the new server at the server i get Access to localhost denied error. Exchange Mgmt Shell Opens though." Does this sentence mean that you cannot open EAC, but you can use Exchange Server PowerShell? - Yes that is correct

according to the error message “denied error”, it seems to be permission issue, you could try to create a new admin for test. - Okay I will give that a try and report back

Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-17T05:47:08.9366667+00:00

Hi，@Robert Wills

I'm glad to hear from you.

Since you are able to use EMW, this suggests that the Exchange 2016 functionality is not compromised. Based on the information you provided, there seems to be an error in the EAC configuration.

Start IIS Manager on the server and navigate to Exchange Backend website > ECP Virtual directory.

Select Application settings > BinsearchFolder，and check the paths to the Exchange directories that are listed

Navigate to a folder that includes Exchange Server scripts in Exchange Management Shell

Run the following scripts：.\UpdateCas.ps1

Run .\UpdateConfigFiles.ps1

6.Exit Exchange Management Shell and open a Command Prompt window as an administrator. Run iisreset.

Restart the server.

You can refer to this URL for detailed steps: OWA or ECP stops working after you install a security update - Exchange | Microsoft Learn
Sign in to comment
Robert Wills 20 Reputation points

2024-05-14T22:59:38.2366667+00:00

Hi Bruce a new admin did not work, trying to give application permissions to folder as some suggest online.

Robert
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Robert Wills 20 Reputation points

2024-05-21T04:34:29.25+00:00

Hi Bruce went through all the above, even went to the linked article when it didn't work to see if i had overlooked something. Same error

Thanks Robert
Please sign in to rate this answer.
Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-23T09:00:40.0766667+00:00

Hi，@Robert Wills

According to your current situation, the installation of Exchange 2016 was not very successful, and many problems occurred. Considering that Exchange2016 was recently installed and doesn't have user data, you may consider reinstalling Exchange2016.It is recommended to go by the official documentation to avoid many problems.

You could refer to the following document for migration.

Exchange On-Premises Best Practices for Migrations from 2010 to 2016 - Microsoft Community Hub

In order to better upgrade Exchange, we recommend that you use the Exchange Deployment Assistant

If my answer is helpful to you, please mark it as the answer so that other users can refer to it. Thank you for your support and understanding.

Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-28T01:18:10.63+00:00

Hello,

It's been a long time since I've heard from you, did my previous reply help you, if it was useful, you can mark it as an answer. Thank you for your understanding and support.
Sign in to comment
Robert Wills 20 Reputation points

2024-05-28T04:58:55.6033333+00:00

Hi Bruce as previously noted the Exchange Deployment Assistant does not allow me to select Exchange 2010. I am slowly working through the docs you have linked to and I did try to reinstall Exchange 2016 but the installer insisted that it was already installed and stopped. I will see if there is a /force like cmd that i can use to over write existing installation.

Thanks for your help to date i will report back once I have finished just for completion
Please sign in to rate this answer.
Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-28T08:53:11.1433333+00:00

Hi，@Robert Wills

I'm glad to hear from you.

I will answer your questions in turn.

I checked out the version selection in Exchange Deployment Assistant and it is letting you select the version you want to upgrade to instead of your own current version.

"It was already installed and stopped" is probably due to the fact that you did not clean up the last installation.

I would recommend completely cleaning it up before reinstalling it.

Finally, I look forward to the good results of your successful installation.

If my answer is helpful to you, please mark it as the answer so that other users can refer to it. Thank you for your support and understanding.

Bruce Jing-MSFT 1,380 Reputation points Microsoft Vendor

2024-05-31T06:57:15.5166667+00:00

Hello, @Robert Wills

It's been a long time since I've heard from you, have you solved your problem yet? Did my previous reply help you？ If it was useful, you can mark it as an answer. Thank you for your understanding and support.
Sign in to comment

Share via

move an exchange 2010 on premises server running in a hybrid configuration to a new server running exchange 2016

4 answers