Exchange 2010 SP3 - Upgrade Issues

David McMorris
David McMorris used Ask the Experts™
on
Hi,

In preparation for our Office 365 move, I am upgrading our Exchange 2010 to SP3 and then installing the latest roll up. Currently we are on SP2.

I attempted the install for SP3 and it has come up with an error about it not being able to locate a domain controller which is 2003 or later during the readiness check. We recently upgraded our domain controllers to 2019 and demoted the 2008 R2 controllers. We still have one of the 2008 R2 vm's. The domain forest level is 2008 R2. Turns out 2019 isn't compatible with Exchange 2010 as i believe the schema needs to be updated.

Would i be OK joining the 2008 R2 server back to the forest as a controller and then performing the Exchange SP3 upgrade. Then demoting the controller again?

Thanks,

David
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Saif ShaikhServer engineer

Commented:
Please post the complete error when upgrading SP3.

remove and company information you would like..
Server engineer
Commented:
Yes 2019 is not compatible with exchange 2010, you should have read the instructions first.

Would i be OK joining the 2008 R2 server back to the forest as a controller and then performing the Exchange SP3 upgrade. Then demoting the controller again?

Yes this is the only choice. OR you will have to bring a new exchange 2013 or 2016 and then move the mailboxes from 2010, but even for that SP3 upgrade would be required. It is not a must but you never know what errors might come up during move mailboxes.
Saif ShaikhServer engineer

Commented:
Second option is export all mailboxes first from exchange 2010 server.

Then also export X500 addresses from all mailboxes.

Decomission exchange 2010 gracefull using control panel.

Install a new exchange 2019 in the environment,

Create new mailboxes on 2019 server and import all PST's.

Then also import X500 addresses for all mailboxes.

and you are good to GO....
Saif ShaikhServer engineer

Commented:
Make sure port 25 and 443 on firewall are pointed to new exchange 2019 public IP after the migration.

Also all internal DNS records like host A and autodiscover must be changed to new 2019 server internal IP..
Saif ShaikhServer engineer

Commented:
Single SAN certificate is an issue since all outlook 2013 or 2016 clients will connect to exchange 2019 using autodiscover.

Purchase a multi- SAN cert for exchange 2019 i.e.

mail.domain,com
autodiscover.domain.com

Install the new cert on exchange 2019 server.

change all VD's to mail.domain.com on 2019 server.

Also make sure autodiscover host A record is updated in public DNS pointing to exchange server public IP.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial