Exchange migration

[Jawloms]

I can find hundreds of tutorials for migrating Exchange, but none I can actually work through successfully.

 

I have Exchange 2010 SP3 running on a Server 2008 R2. It's had an initial hybrid setup config done, but nothing actually moved anywhere.

 

I want to go to Exchange 2016 on Server 2019, I'm not going cloud as I have a 35mb Internet connection and can't currently pay for a quicker connection.

 

The ones I can find either don't take into consideration the hybrid bit so I stumble when the setup notices that exists, or say things like "Now do this bit where you've extracted the setup to" but at no point told you to extract the setup files. There just seem to be bits missing. I got frustrated and just tried running setup.exe off the Exchange 2016 disc on the new 2019 server to see how far I'd get and it said "Enter the credentials of an office 365 account that's a member of the organization management role". Looking in the admin centre, I can't see a role of "Organization Management", so I used credentials for a Global Admin and it didn't like it.

 

Can anyone help please?

 

Stuart

[HPlum78]

First thought would be to get to the latest cu/ ru whatever we are calling them these days for 2010 before you do anything more. I think it 23 maybe... (26 at first glance). Then you should be able to get a 2016 box in making sure you get the latest installer, from memory having the hybrid configuration should not stop you installing a later version of exchange with the roles that you require, although you should probably make sure you rerun the HCW again as this is updated all the time. Don't think that it tied to cu/ ru/ version.... Edited June 14, 2019 by HPlum78

[Jawloms]

I've made quite a bit of progress on this now having battled with it most of the day. Even though the PROXY was set, I had to set it using netsh winhttp as well. Then had some PowerShell things to run, and a command line setup.exe with a lot of switches and eventually came across another error. I Googled that one and found that Exchange 2016 isn't supported (and won't install) on Server 2019! Argh! I know I should have checked that to begin with, but the amount of results I found I clearly am not the only person.

 

I start again on Monday on Server 2016.....

 

Stuart

[HPlum78]

Ah that will slow you up... :-p

[3s-gtech]

Sorry, I’ve not piped up with any help here even though I did similar earlier this year - but from 2013. Yes, your netsh proxy settings are a requirement, as is making sure your logged on user for the upgrade is a member of all the requires security groups. I put it on Server 2016 as I hadn’t done anything with 2019 at that time - it’s a real pain that you have to start again but best to just shrug it off.

 

I used this guide, which will have some minor differences due to 2013 but plenty will be relevant. I can’t stress enough how comprehensive this is https://markgossa.blogspot.com/2015/12/exchange-2013-to-2016-migration-part-1.html?m=1

[2097]

I recently went from 2010 - 2013 and planning to do the next jump to 2016 in the summer.

 

I used quite a few guides to do the push and only experienced one day downtime. Most of the problems i experienced was the previous office/exchange 2010 build didn't use SMTP auto discover so the URL was hardcoded into the setup which meant scripting to remove the old profile etc.

 

Another thing to watch out for is Domain Admin rights to OWA . I was trying to test OWA with my domain admin account which exchange 2013+ now does not like.

 

Last problem i had was setting up a Outlook anywhere reverse proxy for exchange access outside of the local network. Yet again totally different to 2010 , and requires multiple DNS entrys like "autodiscover" accessible on the outside so make sure you get all your dns sorted first !.

[Jawloms]

After quite a battle, I've got it installed. Yay!!

 

Well actually, no, not "Yay"!

 

If I try and open the Exchange Administrative Center, it asks for a username and password (which says "wrong" if I enter incorrect details so must be working to a point) but then gives an error 500 as soon as I sign in.

 

Please, any suggestions anyone? I don't have an out of the ordinary install as far as I'm aware, why is it such a struggle?

 

Stuart

[supportman]

I want to go to Exchange 2016 on Server 2019, I'm not going cloud as I have a 35mb Internet connection and can't currently pay for a quicker connection.

 

Office 365 works fine with a 0.5mbit connection, let alone a 35mbit one! Bandwidth is no reason to discount the cloud in my opinion.

 

I couldn't imagine working with onsite exchange servers any more, complete waste of admins time for such a simple task as using email. Best thing we ever did was more to Office 365 from onsite Exchange. Back then we had a 5mbit internet line.

 

Please, any suggestions anyone? I don't have an out of the ordinary install as far as I'm aware, why is it such a struggle?

 

Because nobody really uses onsite exchange any more, the future has been cloud for years.

[Jawloms]

Office 365 works fine with a 0.5mbit connection, let alone a 35mbit one! Bandwidth is no reason to discount the cloud in my opinion.

 

I find this a little unlikely. I can't see a 0.5mb feed coping with a class of 30 kids all trying to use OWA on top of all the staff dotted about the place already using it, also on top of all the other classes using the Internet for general things.

 

Because nobody really uses onsite exchange any more, the future has been cloud for years.

 

The struggle I was referring to was Microsoft making a product work in the first place, not getting help for it when it doesn't, but point taken too! Perhaps if I can get some people to say "We have x users and y internet speed" I can look at going 365 instead of moving to 2016 as I really haven't got very far down that line......

 

Stuart