This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 25%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Dear Forum,
I inherited a network that the DC where upgraded to a mix of Windows 2019 and Windows 2016.
Domain level and Forest level are set to Windows 2016.
I was tasked with the upgrade of Exchange 2013 to Exchange 2019.
During the pre-requirement checks I notice that Exchange 2013 does not support Domain controllers 2019.
However in the current environment it is already running.
Now my questions is, is it safe to introduce the Exchange 2019 to the network seeing that the Domain Controllers are already a mix of 2019 and 2016?
What other alternatives do I have for this upgrade?
Thank you in advance for your feedback
Well, at this point, its moot right? :)
I would continue moving forward and get 2019 in there and move the mailboxes to it.
Hi @Sherlon Martina ,
Yes the Exchange 2013 will not support Windows server 2019 as the domain controller, but you still have 2016 mixed.
I think the question is the schema master, that refers to the first Windows server you've installed.
But as you said, it is running, so I think you could go on migrating.
Oh you can export the mailboxes to pst files to backup, and you can follow the deploy assistant to do the migration.
Regards,
Lou
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Sherlon Martina ,
Do the suggestions above help? If the issue has been resolved, please click “Accept as answer” to mark helpful reply as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
Regards,
Lou
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Sherlon Martina ,
It has been a long time since last reply, did these suggestions help you? If the above suggestion helps, please click “Accept as answer” to mark helpful reply as an answer.Your action would be helpful to other users who encounter the same issue and read this thread.
Regards,
Lou
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 91%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJT%3C/text%3E%3C/svg%3E)
Thanks for valued information.
I have terribly broken (production) Exchange 2013 in topology with 3 AD servers upgraded to WS2019 Std (domain functional level WS2016). Exchange recovery always failed, so after reading Your post I've add 4th AD server with WS2016 Std to support dissaster recovery - now it should met this requirements, but recovery is still failing.
Is there any help from this (Exchange vs AD) hell without loss of about 120 mailboxes an tons of messages?
Thank you, BR
Dear All,
Thank you for your feedback.
What I will do is replicate the scenario in a test lab. Then introduce the Exchange 2019 is simulate a migration.
It that goes well I will do the same into he production environment.
Thank you again for you input.