Migrate to Windows Server 2019 from Small Business server 2011

John Fessel 1 Reputation point
2022-01-25T21:16:47.39+00:00

I'm looking for a document to Migrate to Windows Server 2019 from Small Business server 2011 (no exchange).

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,499 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Tom Jacob Chirayil 121 Reputation points
    2022-01-25T21:41:48.39+00:00

    You can start preparing for the migration scenarios. You might need to look at migrating each role. I don't think there is any one-click wizard to migrate over from SBS 2011.

    SBS 2011 is running Exchange 2010. When you say Windows Server 2019, I am assuming that your migration scope includes Exchange 2019 as well. In that case, unfortunately, there is not direct path. You will have to go to 2016 first and then go to 2019.

    1. Prepare Active Directory - Install Exchange updates for Exchange 2010 and it is on the latest updates for EX 2010 (atleast Update Rollup 11 for Exchange 2010 SP3). EX2010 supports domain controllers running Windows Server 2016. So install Windows Server 2016, promote it as a domain Controller, GC, Transfer FSMO roles, DNS, DHCP
    2. Install Exchange 2016 - Install Exchange 2016, migrate mailboxes to Exchange 2016
    3. Remove SBS 2011 - Demote SBS 2011
    4. Install Exchange 2019 - Install Exchange 2019, migrate mailboxes to Exchange 2019
    0 comments No comments

  2. Dave Patrick 426.2K Reputation points MVP
    2022-01-25T21:50:50.51+00:00

    The two prerequisites to introducing the first 2019 or 2022 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 or 2022, 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--