Exchange

[Jawloms]

I have Exchange 2010 SP3 running quite happily. I have installed a new server 2016. The 2010 server doesn't appear to know the new one exists. I assume there's something I'm supposed to do to make it aware? I also can't log in to the EAC on the new server, it just presents me with an Error 500. From Googling I'm wondering if it's because there are no accounts on the new server, but that shouldn't matter I'd have thought if they could see each other? Please help!

 

Thank you

 

Stuart

[Jawloms]

Anyone got any thoughts please?

[HPlum78]

The 500 error on the exch 16 box is going to need fixing in the first place. How do you mean the 2010 box don't know about the 16 box where are you looking? Can you get to the exchange powershell command prompt? (on the 16 box)

 

I am doing this migration right now in our dev test and just got live through CAB so will be doing that next week....

[HPlum78]

Oh and just make sure you observe the ground rules for Exchange nothing in the way of all traffic being able to flow betwee the boxes. (so no firewalls and the likes)

[Jawloms]

I assumed that on the 2010 server that if I wanted to move a mailbox it would offer the new server as a destination and it doesn't. Also in the EMC under "Server Configuration" it only lists the 2010 box.

 

I can get to the Exchange Management Shell on the 2016 server.

[Jawloms]

Strangely, if I type incorrect details in to the login page, it tells me they're wrong so it must be doing something! It's just correct details where I then get the error 500.

[3s-gtech]

It sounds like your new Exchange instance isn't running properly - the process should just give you another ECP running ready to migrate. Have you looked at a guide like https://markgossa.blogspot.com/2015/12/exchange-2013-to-2016-migration-part-1.html - this is a superb write-up and took me right through. There shouldn't be too many changes between 2010 and 2013 as a starting point, but your 2010 server will need to be pretty up-to-date with a later Cumulative Update.

[Jawloms]

Server is on SP3 Update Rollup 21, which is May '18 so should be up-to-date enough. Perhaps I'll try and apply the latest and see if it makes a difference. If not, I may well just wipe the server and start again, the only problem there I assume is if it has entered any info into my existing setup will it like it if suddenly it isn't there anymore and is replaced with another, albeit with the same name? I'm guessing potentially not....

 

Just tried "Get-ExchangeServer" on new and old servers. New server lists both, old server only lists itself.

 

"Get-Mailbox -Arbitration" lists the system, federated and migration mailboxes correctly on both servers so there's obviously some connection in there.....

Edited November 14, 2019 by Jawloms

[Jawloms]

Just tried "Get-ExchangeServer" on new and old servers. New server lists both, old server only lists itself.

 

This seems to be by design. It's to do with version numbers. If I type "Get-ExchangeServer *" on the old server it lists both.

[HPlum78]

Yep that's right, if you can get to the PS exchange prompt I will post some powershell shortly.

[Arthur]

Server is on SP3 Update Rollup 21, which is May '18 so should be up-to-date enough.

SP3 Update Rollup 22 adds support for 2016 Forest Functional Level and Windows Server 2016 DCs if you have those?

 

https://blogs.technet.microsoft.com/rmilne/2018/06/21/exchange-2010-support-for-windows-server-2016-domain-controllers/

[Jawloms]

I have 2x 2016 DCs and 2016 Forest level. I'll install a new rollup.

[Jawloms]

Thanks to @HPlum78 for some PM help which has now got me in