Comments on: Performing a Like for Like Exchange Server Migration

By: sai kumar

sai kumar — Tue, 30 Mar 2021 23:48:44 +0000

Team , i want a exchange 2013 , now i want to add another 2013 server and remove the other 2013 server , can someone suggest how can i achieve this , very confusing for me whether i need to go DAG or just normally move the mailbox databases , we have 10 mailbox in same server . please suggest me on how can i add another server and decommision old one.

By: Ben

Ben — Wed, 03 Mar 2021 03:28:50 +0000

Hi Paul, have replied to an existing comment, this is a new one as I’m unable to find info on schema changes. You mention like for like doesn’t need to be the same CU, we have 2016 CU5 along with some 2010 too, can we introduce 2016 CU19 without issue and migrate to that, any issue with AD schema changes?

By: Ben

Ben — Tue, 16 Feb 2021 06:44:35 +0000

In reply to

Paul Cunningham

. Hi Paul, you mention like for like doesn't need to be the same CU, we have 2016 CU5 along with some 2010 too, can we introduce 2016 CU19 without issue and migrate to that, any issue with AD schema changes?

By: Tim

Tim — Tue, 29 Sep 2020 15:23:42 +0000

In reply to Mike B.. I'm curious as to how this went? I'm going through the exact same thing right now with an inherited Exchange server.

By: Frank

Frank — Tue, 31 Dec 2019 06:22:45 +0000

In reply to Mike B..

HI Mike,

You can download CU4 from here.
https://www.msexchangeupdates.com/

By: Mike B.

Mike B. — Mon, 09 Dec 2019 15:44:34 +0000

Hi Paul,

Love the article!

Wondering your thoughts on like for like migration between Exchange 2013 SP1(cu4) and Exchange 2013 CU23? I’m way behind on my CU upgrades and only 22 and 23 are currently available. I’m a little worried about the jump because of the .Net Framework upgrade that takes place as a prerequisite. I’ll be upgrading from .Net 4.5.2 to 4.7.2 before I can run CU23 installer. Microsoft’s site says to do it but others have said it’s better to follow an upgrade path where you install .Net and CUs in steps but are never installing a version of either that isn’t compatible with the one you’re on or upgrading to. But I can’t do that because the older CU’s aren’t available. So, I’m hoping a work around would be a like for like migration from 2013 to 2013 but between SP1(CU4) and CU23. Do you think that approach could be successful?

Thanks,
Mike B.

By: Mike B.

Mike B. — Mon, 09 Dec 2019 15:36:58 +0000

Hi Paul,

I was wondering if you have any thoughts on whether a like for like Exchange 2013 migration would work if the first server is on SP1 (aka CU4) and the new server is on the latest CU23? I’m hoping to use a like-for-like migration as a work-around to jumping from SP1 to CU23. Unfortunately I’m way behind on CUs and only the latest 2 are available. Microsoft’s site says to make the jump, but I’ve read elsewhere that there are .Net framework concerns. For example, my Exchange 2013 SP1 is running .Net Framework 4.5.2, which is the correct .Net up to CU15. If older CUs were available there would be a path I could follow to always be upgrading the .Net to a version that’s supported by the current and new CU that I’m upgrading to. Alas, I have to go from SP1 .Net 4.5.2 to .Net 4.7.2 then CU23. The risk lies in that first step of upgrading the .Net Framework while the Exchange CU is still SP1 (CU4). So, a workaround might be to do a like for like mailbox migration in my environment. Any input on if that should work if original mailbox server is SP1 and the new one is CU23? Thanks, Mike B.

By: GP

GP — Fri, 18 Oct 2019 04:13:17 +0000

Hi All,
We are doing a like-to-like migration of Exchange Server 2013 CU23. Our exchange is configured as hybrid (so we can move mailboxes on-prem to online and vice-versa).
After the migration, we cannot anymore move mailboxes either way.
Do we still need to re-run the Hybrid Configuration wizard? If yes, should we run it after we uninstall the old exchange server?

By: tomH

tomH — Sat, 29 Jun 2019 19:54:21 +0000

Hi Paul
I Have an existing exchange 2013 rtm 15.0.516.32 that i am moving to new hardware is it ok to just install exchange 2013 sp1 on the new server then move all mailboxes etc to new server. or should i update existing server to sp1 first

By: Andrew

Andrew — Mon, 03 Jun 2019 16:45:47 +0000

In reply to Andrew. I've installed Exchange on my new servers (went from VMware to HyperV) and added them to the DAG. I completed the virtual directory modifications. and imported the certificates to the new servers. My servers have an identical storage/mount point configuration and are technically ready for the original databases to be seeded over. I understand your guide focuses on migrating the users from the original DB's to net new DB's. Do you foresee any potential issues with creating copies of the databases on the new environment as opposed to migrating?