<div>
You can't, there is no direct Upgrade path from 2003 to 2016, this is fully unsupported. You can even use a desktop, throw 2008r2 on it, then promote that and then decom after you get it to 2016.<br />
<br />
Reading some dodgy how to guide in order to achieve this is playing with fire. Actually no, it's like playing with Gun powder in a building that's on fire.
</div>


<div>
Hi,<br />
<br />
As Alex advised, there is no direct upgrade of AD to &nbsp;WS2016 from WS2003. You could have used the same server (which you had already installed WS2016) to install a WS2012 ADC first, then migrate the file replication from NTFRS to DFS and perform an in-place upgrade of the WS2012 to WS2016.<br />
<br />
Thanks,<br />
Abhi...
</div>


<div>
Thanks for the info. &nbsp;I actually could downgrade the newer server to Win2012, I guess. There is nothing of value on it now anyway.
</div>


Principal Support Engineer

DrDave242

<div>
Alternatively,<br />
<br />
Use a microsoft approved method in order to up your Domain to 2016. <br />
<br />
I'm sorry but I really don't agree with any method to upgrade a domain functional level that is not following microsoft best practice. In the event it goes wrong, you will have zero support in order to rectify the issue. Not only that you don't know what else could possibly happen from this.<br />
<br />
Regards<br />
<br />
Alex
</div>


<div>
Check below thread on same topic<br />
<br />
<a href="https://www.experts-exchange.com/questions/29128981/Steps-to-upgrading-AD-enviroment-that-is-a-mix-of-2003-and-2008r2-DC's.html" rel="ugc">https://www.experts-exchange.com/questions/29128981/Steps-to-upgrading-AD-enviroment-that-is-a-mix-of-2003-and-2008r2-DC's.html</a>
</div>


<div>
I'm not sure where the idea came from that you can't promote a 2016 DC into a domain with only 2003 DCs. You can absolutely do this, and <a href="https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/upgrade-domain-controllers#functional-level-features-and-requirements" rel="ugc">even Microsoft says so</a>:<br />
<br />

<blockquote>
Windows Server 2016 requires a Windows Server 2003 forest functional level. That is, before you can add a domain controller that runs Windows Server 2016 to an existing Active Directory forest, the forest functional level must be Windows Server 2003 or higher.
</blockquote>
<br />
If your domain has only 2003 DCs, there's nothing preventing you from setting the functional levels to 2003 and promoting a 2016 domain controller.
</div>


<div>
As for the issue at hand, check the FRS event log on the 2003 domain controller for errors. It's likely that FRS is in a journal wrap.
</div>


<div>
Refer to the MS article :- [Windows Server version 1709 no longer supports FRS]<br />
<br />
<a href="https://support.microsoft.com/en-in/help/4025991/windows-server-version-1709-no-longer-supports-frs" rel="ugc">https://support.microsoft.com/en-in/help/4025991/windows-server-version-1709-no-longer-supports-frs</a>
</div>


<div>
That articled did not apply to 2016 server OS<br />
<br />
version 1709 (semi releases) and 2016 server are different and its not update version of 2016 server
</div>


<div>
As Mahesh said, Windows Server version 1709 is not the same as Windows Server 2016. 1709 (and 1803 and 1809) are Semi-Annual Channel releases of Windows Server, whereas Windows Server 2016 and 2019 are the Long-Term Servicing Channel releases. More info on these can be found starting <a href="https://docs.microsoft.com/en-us/windows-server/get-started/windows-server-release-info" rel="ugc">here</a>, but most people won't be working with the Semi-Annual Channel releases.<br />
<br />
The confusion is understandable. Microsoft isn't exactly making this clear.
</div>


<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.<br />
<br />
I have recommended this question be closed as follows:<br />
<br />
Accept: 'Mahesh' (<a href="https:#a42766772" rel="ugc">https:#a42766772</a>)<br />
<br />
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.<br />
<br />
seth2740<br />
Experts-Exchange Cleanup Volunteer
</div>


<div>
<div class="content wysiwyg-content">
I have a very small Windows network that is still using a Win2003 DC. &nbsp;I now have a Win2016 server that I would like to promote to DC and finally retire the Win2003 DC. &nbsp;I joined the W2016 server to the domain and it seems happy enough. &nbsp;I know that Microsoft does not support promoting Win2016 within a Win2003 Domain/Forest, but I do not have the resources to build a Win2008 server, so after reading some success stories online I thought I'd give it a try. &nbsp;Other than a few warnings, the promotion went pretty well and completed. &nbsp;DNS seemed to be ok after completion/restarts. &nbsp;Ran a DCDiag and noticed that SYSVOL and NetLogon shares did not exist. &nbsp;I know that I'm now dealing with 2 different replication methods but hoping that someone can help my get past this. Is there a way to manually move them maybe?
</div>
</div>


I have a very small Windows network that is still using a Win2003 DC.  I now have a Win2016 server that I would like to promote to DC and finally retire the Win2003 DC.  I joined the W2016 server to the domain and it seems happy enough.  I know that Microsoft does not support promoting Win2016 within a Win2003 Domain/Forest, but I do not have the resources to build a Win2008 server, so after reading some success stories online I thought I'd give it a try.  Other than a few warnings, the promotion went pretty well and completed.  DNS seemed to be ok after completion/restarts.  Ran a DCDiag and noticed that SYSVOL and NetLogon shares did not exist.  I know that I'm now dealing with 2 different replication methods but hoping that someone can help my get past this. Is there a way to manually move them maybe?

Possible to move SYSVOL tree from Win2003 DC to Win2016 DC when migration does not

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.