![](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(262.40000000000003, 4%, 35%)' 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)
Microsoft System Center | Other
Additional System Center tools and components for managing infrastructure, applications, and services
Upgrading the AD DS domain controllers’ OS from Windows Server 2012 R2 to Windows Server 2019 while keeping the domain functional level at Windows Server 2012 is supported in general AD terms and does not introduce any specific incompatibility in the provided documentation for System Center Configuration Manager (SCCM) 2012 R2.
From the compatibility matrix around upgrading domain controllers, Configuration Manager (current branch) is documented as supporting Windows Server 2012 domain controllers and higher, via the “Supported operating systems for Configuration Manager site system servers” guidance. The same AD DS upgrade article shows that Windows Server 2012 and later domain controllers are supported for other server workloads (Exchange, SQL, etc.) with domain functional levels as low as Windows Server 2003, which aligns with the requirement previously seen for SCCM 2012 R2 (domain functional level not lower than 2003).
The context does not list any breaking changes or known issues for AD DS when domain controllers are upgraded beyond Windows Server 2012 that would specifically affect SCCM 2012 R2, as long as the domain functional level remains at or above Windows Server 2003. It also notes that new domain and forest functional levels exist in newer versions, but existing domains can continue to run at older functional levels while adding newer OS domain controllers.
Therefore, based on the provided documentation:
- Keeping the domain functional level at Windows Server 2012 is supported.
- Upgrading domain controller OS from 2012 R2 to a newer version (such as 2019) is not documented as introducing SCCM 2012 R2 incompatibility, provided the functional level requirement (≥ 2003) is met.
Normal AD DS upgrade best practices (introduce new DCs, transfer FSMO roles, decommission old DCs, verify replication and DNS, etc.) still apply, but no SCCM‑specific incompatibility is indicated in the referenced material.
References: