<div>
Be sure that your domain and forest functional levels are at 2008 R2, and that you're using DFSR for SYSVOL replication.<br />
<br />
<a href="https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405" rel="ugc">https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405</a><br />
<br />
I don't know what replication you're talking about. Neither AD database replication, nor SYSVOL replication use SMB.
</div>


<div>
SMB 1 should be disabled by default in 2019. &nbsp;Server 2008 and up support v2, and I believe the TCP port is 445.<br />
<br />
You may want to audit other servers in the environment such as Exchange for compatibility as well.
</div>


<div>
Hi&nbsp;<a href="https://www.experts-exchange.com/members/minniejp.html" rel="ugc">minniejp</a>,<br><br>Before going, please refer support ability matrix below,<br><a href="https://techcommunity.microsoft.com/t5/itops-talk-blog/how-to-in-place-upgrade-windows-server-2008-r2-to-windows-server/ba-p/752330" rel="ugc">https://techcommunity.microsoft.com/t5/itops-talk-blog/how-to-in-place-upgrade-windows-server-2008-r2-to-windows-server/ba-p/752330</a>&nbsp;<br><a href="https://filedb.experts-exchange.com/incoming/2020/04_w18/1451574/Windows-Server-Upgrade-Paths-Diagram.png" rel="ugc"></a><a href="https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-overview?WT.mc_id=itopstalk-blog-thmaure" rel="ugc">https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-overview?WT.mc_id=itopstalk-blog-thmaure</a>&nbsp;<br><br>When your are doing in place upgrade, you have to upgrade it into 2012R2 first and then 2019.<a href="https://filedb.experts-exchange.com/incoming/2020/04_w18/1451574/Windows-Server-Upgrade-Paths-Diagram.png" rel="ugc"><br><img src="https://filedb.experts-exchange.com/incoming/2020/04_w18/1451574/Windows-Server-Upgrade-Paths-Diagram.png" class="fr-fic fr-dib"></a><br>Make sure to get backup before proceed.<br>My recommendation is to Migrate the server instead of In place upgrade.(<em>Can be kept your existing server safe</em>)<br><br>Before migration, you need to check forest/domain functional levels and FRS to DFSR conversion as mentioned above by&nbsp;<a href="https://www.experts-exchange.com/members/kevinhsieh.html" rel="ugc">kevinhsieh</a>.<br><br><br><br>
</div>


Windows-Server-Upgrade-Paths-Diagram.png

<div>
SMB = networking file share protocol. It has nothing to do with AD replication. SMB1 is disabled on WS2016/2019 by default. It's not recommended to enable SMB1 on WS2016/2019 due to security. <br />
<br />
For SYSVOL replication, you need DFSR. FRS has been deprecated and is not supported since server version 1709 so if you have DC2019, you must migrate to DFSR. Since you have WS2008R2, it's possible you already use DFSR. You can verify it. Run:<br />

<pre><code class="code-1 nolinks" id="code-20-43074995-1"><span>dfsrmig /getglobalstate</span>
</code></pre>
FRS = DFSR migration has not yet initialized<br />
DFSR = Eliminated state<br />
<br />
The procedure in a short way:<br />
1. Check the current state of your domain - use DCDIAG command and make sure the DC passes all the tests<br />
2. Raise DFL to Windows Server 2008R2 and make sure you use DFSR (see the guides below)<br />
2. Install the DC2019 + install ADDS role<br />
4. Transfer FSMO roles to DC2019<br />

<pre><code class="code-10 nolinks" id="code-20-43074995-2"><span>C:\Windows&gt;ntdsutil</span>
<span>ntdsutil: roles</span>
<span>fsmo maintenance: connections</span>
<span>server connections: connect to server &lt;new_server&gt;</span>
<span>server connections: q</span>
<span>fsmo maintenance: Transfer domain naming master</span>
<span>fsmo maintenance: Transfer infrastructure master</span>
<span>fsmo maintenance: Transfer PDC</span>
<span>fsmo maintenance: Transfer RID master</span>
<span>fsmo maintenance: Transfer schema master</span>
</code></pre>
5. Double-check DNS settings<br />
6. Demote old domain controllers + remove the server form ADSS<br />
7. Raise DFL to 2016 if you have all DCs at least 2016 and higher<br />
<br />
<br />
<br />
FRS to DFSR:<br />
Perform on all DCs: Server Manager -&gt; Manage -&gt; Add Roles and Features -&gt; select the DFS Replication role -&gt; Install<br />
- Then run from the PDC:<br />

<pre><code class="code-1 nolinks" id="code-20-43074995-3"><span>Dfsrmig /setglobalstate 1</span>
<span>Dfsrmig /getmigrationstate</span>
<span>Dfsrmig /setglobalstate 2</span>
<span>Dfsrmig /getmigrationstate</span>
<span>Dfsrmig /setglobalstate 3</span>
<span>Dfsrmig /getmigrationstate</span>
</code></pre>
<br />
How to raise DFL or FFL:<br />
For Domain: Active Directory Users and Computers -&gt; Right-click on your domain -&gt; Raise Domain Functional Level<br />
For Forest: Active Directory Sites and Trusts -&gt; Right-click on Active Directory Domains and Trusts -&gt; Raise Forest Functional Level
</div>


<div>
thanks all for your feedback - I’ve just read a number of articles stating disabling SMB breaks AD and that it is used to replicate between the existing Windows 2008 R2 DC and the new Windows 2019 DC.
</div>


<div>
is it used by sysvol and netlogon for servers etc to access these shares?
</div>


<div>
That is for clients accessing SYSVOL when logging in and applying group policy, which is different than replication. You shouldn't have any issues not having SMB1 since everything thing Windows Vista and 2008 onward support at least SMB 2.
</div>


<div>
what about sites and services, what does it use?
</div>


<div>
Sites and services is based on information stored in the AD database, as is DNS.
</div>


<div>
I see you are worried. But keep in mind that you don't disable SMB for good, you continue using SMB but you just disable the old version. Nothing won't be affected. <br />
<br />
Today, SMB1.0 is not needed and it's not much safe to use it. Use SMB2/3. <br />

<blockquote>
SMB1 isn’t usually necessary. There are far fewer cases left in modern enterprises where SMB1 is the only option. Some legit reasons:<br />
1. You’re still running XP or WS2003 under a custom support agreement.<br />
2. You have old management software that demands admins browse via the so-called ‘network' aka 'network neighborhood’ master browser list.<br />
3. You run old multi-function printers with old firmware in order to “scan to share”.
</blockquote>
<a href="https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858" rel="ugc">https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858</a><br />
<br />
If you don't need it for any of the reasons above, don't enable it.
</div>


<div>
yes....I am a bit, I’m getting conflicting advice with my colleagues and from the research I’ve done I agree with what you’ve said. &nbsp;however, they are pretty adamant that it is used for replication in sites and services, which I just don’t understand how this is the case.
</div>


minniejp

<div>
Apologies for not getting back in touch, I haven't been working due to an illness. Hello there, you are correct, I've spoken to them re this and it was indeed the replication.<br><br>cheers for the help!<br><br>
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
We are introducing Windows 2019 into our existing Windows 2008 R2 environement, with the plan to upgrade the 2019 servers to be Domain Controllers and to finally remove the out dated 2008 R2 Servers. &nbsp;I know replication happens over SMB but can I use SMB v2.0 instead of 1.0?<br />
<br />
Cheers
</div>
</div>


Hi,

We are introducing Windows 2019 into our existing Windows 2008 R2 environement, with the plan to upgrade the 2019 servers to be Domain Controllers and to finally remove the out dated 2008 R2 Servers.  I know replication happens over SMB but can I use SMB v2.0 instead of 1.0?

Cheers

Introducing Windows Server 2019

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.