Migrating Win 2011 SBS to Win 2019 Std when Exchange is not an issue.

Question

Hello All
I have a Win SBS 2011 server and Exchange has been moved to MS 365 so I do not have to worry about moving Exchange from the SBS 2011 to the 2019 server. Should I go thru a migration or just start fresh on the 2019 server . If migration path is the choice what would be the best process to go about this when migrating the following:

FSMO roles
Active Directory Domain Services
DNS
DHCP
Folders, folders and shares
Users
Computers
Security and/or permissions

Thank you for any thoughts

Answer 1

For the domain controller. 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.

I'd suggest asking the DHCP migration question here
https://learn.microsoft.com/en-us/answers/topics/windows-dhcp-dns.html

and the storage migration question here
https://learn.microsoft.com/en-us/answers/topics/windows-server-storage.html

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

Answer 2

Just checking if there's any progress or updates?

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

Answer 3

I feel foolish because I missed a step

Has the FRS->DFSR migration been completed?

Answer 4

Then you'll nee to remove the 2019 domain controller then confirm health is 100% if all is good then do the FRS->DFSR migration
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405
and after completion check health is 100% again, then you can raise DFL to at least 2008 level, then you can introduce a 2019 domain controller. (follow the detailed steps in my reply above)

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

Answer 5

• I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations.
• Migrate sysvol replication from older FRS technology to DFSR
  https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405
  • Raise DFL to 2008 or higher
• 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 upvote and Accept as answer if the reply is helpful--