asked on Exchange 2010 compatibility
I have a client that is running Exchange 2010 on Server 2008 r2. Currently they have one DC running 2008 r2 & one running server 2012. If I upgrade the 2008 DC to Server 2019 (or maybe 2016) will Exchange work? I want to get them on a hosted exchange server but likely that would be after the DC upgrade. I can't find anything that tells me if Exchange will continue to work. Does anyone know?
Thanks in advance!
Thanks in advance!
ExchangeWindows Server 2019Windows Server 2008
Last Comment
Seth Simmons
That should read domain and forest not direct!
P.s. I hope you don’t mean “upgrade” and in fact mean “add a Server 2019 DC” and “demote the 2008r2 DC”!
I don’t like the idea of even attempting an in-place upgrade of a DC.
And I assume that Exchange 2010 is NOT installed on the DC that you’re going to retire or attempt to upgrade.
I don’t like the idea of even attempting an in-place upgrade of a DC.
And I assume that Exchange 2010 is NOT installed on the DC that you’re going to retire or attempt to upgrade.
Your help has saved me hundreds of hours of internet surfing.
fblack61
Yes Exchange2010 t will work but dont forget it is out of support.
And migrate from FRS to DFSR before promoting 2019 or 2016server to DC2019 or DC2016.
ASKER
Awesome. Thanks much. So hard to search on as all the results are about upgrading not compatibility.
It's worse than being out of support - they have wound up with a disjointed name space between their email domain and their LAN. Didn't have any impact until fairly recently. Moving to the cloud will make the issue moot..
It's worse than being out of support - they have wound up with a disjointed name space between their email domain and their LAN. Didn't have any impact until fairly recently. Moving to the cloud will make the issue moot..
ASKER
Need to replace the hardware. Will be ADDING a 2019 server, promote it to a DC then decommission the existing 2008 DC. I find this process to be easier and less of a nailbiter.. Not touching the exchange server at this point.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
-->promote it to a DC then decommission the existing 2008 DC
Promoting a 2019 server to DC before migrating from FRS to DFSR will create replication issue.
I wasn’t giving a step-by-step on how to add a 2019 DC into a 2008r2 domain, just making sure the word “upgrade” wasn’t indicating an attempt at an in-place upgrade, and that the exchange server wasn’t on the DC if an in-place upgrade was going to be attempted (which it shouldn’t).
If you intend to move them to hosted Exchange, why not just do that first? It will save you the step of moving Exchange to a new server just to then move it to hosted.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ASKER
In a perfect world would but there are people that have to agree to this that are far from technical. If I waited for them to be on board with everything, nothing would ever happen.. I have been pushing this for sometime now - ever since disjointed domains became a problem for email.
Also, I am not touching the exchange server - my question was if it would continue to work in a domain with a 2019 DC - that is the box I am replacing.
Also, I am not touching the exchange server - my question was if it would continue to work in a domain with a 2019 DC - that is the box I am replacing.
ASKER CERTIFIED SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a questionSOLUTION
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
According to that document, it’s not supported, however as originally stated, I’ve just done this as part of a migration.
Supported vs possible are two different things.
I would recommend doing a P2V into a segregated test environment and test what you plan to do before doing it in a production environment.
Supported vs possible are two different things.
I would recommend doing a P2V into a segregated test environment and test what you plan to do before doing it in a production environment.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Split:
-- 'Saif Shaikh' (https:#a43019591)
-- 'MAS' (https:#a43019614)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Split:
-- 'Saif Shaikh' (https:#a43019591)
-- 'MAS' (https:#a43019614)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
You can run a 2019 or 2016 DC and still have exchange 2010 - however I didn’t test with the domain and direct level higher than 2008r2.