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(12.8, 70%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EY%3C/text%3E%3C/svg%3E)
Plan is to upgrade 2008 DC’s to 2019 DC’s in our environment.
We also have Win2003 member servers in out environment, I understand it as a risk but upgrading them as of now is not an option.
So we’ll be enabling Smbv1 on 2019 DC’s.
But my main question is how can we verify application compatibility in our environment with 2019 DC’s?
Can we identify what applications may break on upgrading DC to 2019?
Is there any authentication protocol version change in 2019 DC, compatibility to which should be pre-checked?
Thanks
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The short answer is there's nothing native with windows for application compatibility verification. The slightly longer answer is you can stand it all up in an isolated dev environment and do your own testing. Or the much simpler answer may be to ask the developer about support for the new environment.
--please don't forget to Accept as answer if the reply is helpful--
The highest domain functional level even with 2019 domain controllers is 2016. As to application compatibility the developer will be your best resource for this information.
The two prerequisites to introducing the first 2019 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405
I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
--please don't forget to Accept as answer if the reply is helpful--
I understand the functional level requirements.
But my main question is how can we verify application compatibility in our environment with 2019 DC’s?
Can we identify what applications may break on upgrading DC to 2019?
Is there anything specific we can ask the application guys to check in advance that can determine if it’ll continue working with 2019DC’s?
Is there any authentication protocol version change in 2019 DC, compatibility to which should be pre-checked?
![](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(281.6, 28.999999999999996%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVW%3C/text%3E%3C/svg%3E)
Hi,
Thank you for posting in our forum
In order to better help you solve the problem, I want to confirm some information with you first
According to these questions, analysis can be carried out
Best wishes
Vicky
Well there isn’t any specific application. We are tying to understand if there’s any way to find out if any application in the environment may break by upgrading DC’s to 2019?
how can we verify application compatibility in our environment with 2019 DC’s?
Is there anything specific we can ask the application guys to check in advance that can determine if it’ll continue working with 2019DC’s?
Is there any authentication protocol version change in 2019 DC, compatibility to which should be pre-checked?
how can we verify application compatibility in our environment with 2019 DC’s?
You can stand it all up in an isolated dev environment and do your own testing. If your application has active directory integrated into it the much simpler answer may be to ask the developer about support for the new environment.
Is there any authentication protocol version change in 2019 DC
No, nothing much has changed.
--please don't forget to Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to Accept as answer if the reply is helpful--
Hi，
How are things going? Could you please send me an update so that we can continue to work on this problem and resolve it? Thanks for your help.
Best wishes
Vicky