2019 Domain Controller upgrade, application compatibilty

Yankee30 206 Reputation points
2021-05-13T08:36:24.877+00:00

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

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,346 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,578 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 426.2K Reputation points MVP
    2021-05-13T13:43:54.607+00:00

    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--

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Dave Patrick 426.2K Reputation points MVP
    2021-05-13T12:30:49.99+00:00

    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--


  2. Vicky Wang 2,636 Reputation points
    2021-05-14T09:34:01.187+00:00

    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

    1. Which is the specific application?
    2. Is this program a tripartite program?

    According to these questions, analysis can be carried out
    Best wishes
    Vicky


  3. Dave Patrick 426.2K Reputation points MVP
    2021-05-14T12:15:49.213+00:00

    Just checking if there's any progress or updates?

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  4. Vicky Wang 2,636 Reputation points
    2021-05-17T08:50:00.31+00:00

    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

    0 comments No comments