SBS 2008域控制器直接迁移至Server 2019 STD的可行性咨询及注意事项询问

Hey there, great question—let me break this down for you from hands-on experience, since I’ve handled a few SBS 2008 to 2019 DC migrations before.

First off: you absolutely can migrate directly from SBS 2008 to Server 2019 without jumping through 2012 R2/2016—no middle versions needed. The catch is that SBS systems have some unique legacy quirks even when they’re only acting as a DC, so you need to prioritize a few key checks and steps to avoid headaches.

Let’s start with the critical pre-migration prep work (this is where most SBS migration issues pop up):

• Audit your AD for Exchange leftovers: Since this SBS 2008 used to handle email, it’s almost guaranteed to have Exchange 2007 remnants in AD—even if you migrated all mail to M365. These leftover objects/properties can break AD prep or cause weird post-migration glitches. First, try properly uninstalling Exchange 2007 from the SBS box using the official wizard. If that fails (super common with old SBS), use ADSI Edit to manually clean up the Exchange organization node in the Configuration partition, and strip Exchange-specific attributes from user objects.
• Validate SBS DC health completely: Run dcdiag /c /v and repadmin /showrepl on the SBS server. Fix every single error before moving forward—even small replication or DNS issues can snowball during migration. Since it’s your only DC right now, make sure all 5 FSMO roles are active and error-free.
• Check AD schema level: SBS 2008 defaults to Windows Server 2008 schema. Server 2019 supports upgrading directly from this level, but you’ll need to run adprep /forestprep and adprep /domainprep from the Server 2019 media on the SBS DC first. Wait for these to finish completely (no errors!) before proceeding.

Now for the migration steps and things to watch for:

• Join the 2019 server to the domain first: Set the 2019 server’s primary DNS to the SBS DC, then add it as a member server. After that, promote it to a DC using either the Server Manager wizard or the Install-ADDSDomainController PowerShell command. When prompted, choose to replicate AD data from the SBS DC—make sure your network is stable during this replication, don’t interrupt it.
• Transfer FSMO roles carefully: Once replication is done, move all 5 FSMO roles from the SBS DC to the 2019 server. You can use the AD GUI tools, but I prefer the PowerShell command for reliability:

  Move-ADDirectoryServerOperationMasterRole -Identity "Your2019DCName" -OperationMasterRole 0,1,2,3,4
  

  (The numbers 0-4 correspond to all 5 FSMO roles: PDC Emulator, RID Master, Schema Master, Domain Naming Master, Infrastructure Master)
• THE BIG SBS CAVEAT: Here’s the non-negotiable rule—you have 7 days to downgrade and remove the SBS 2008 DC after transferring FSMO roles. SBS has a built-in restriction: if a non-SBS DC holds all FSMO roles, the SBS server will lock itself out of AD services after 7 days. Mark this on your calendar, set alarms—don’t let this slip!
• Validate the new DC thoroughly: On the 2019 server, run dcdiag /c /v and repadmin /showrepl to confirm no replication errors, DNS is functioning correctly, and all AD data copied over. Test a few client machines: restart them, log into the domain, and run gpresult /r to confirm group policies are pulling from the new DC.
• Downgrade and retire the SBS 2008: Once you’re 100% sure the new DC is stable, run dcpromo on the SBS server to demote it from a DC to a member server, then remove it from the domain. Double-check that no clients or services are still pointing to the SBS server for DNS or authentication before you decommission it.

Post-migration cleanup:

• After a day or two of monitoring (no replication errors, all clients are working smoothly), you can upgrade the domain and forest functional levels to Windows Server 2019. This unlocks modern AD features and fully removes any lingering SBS-related limitations.

Hope this helps—let me know if you hit any specific snags!

备注：内容来源于stack exchange，提问作者PrinceKufreAkai