Tutorials

What makes this migration kit uniquely valuable for small and medium-sized businesses?

This migration kit is designed for small businesses utilizing Windows Server 2012R2 Essentials on a single, non-virtualized server. As mainstream support for Windows Server 2012R2 Essentials concluded on October 9, 2018, and extended support ended on October 10, 2023, this kit facilitates a smooth transition to a new Windows Server 2019 Essentials on modern hardware, while preserving the original hostname. Consequently, all shared resources will maintain their existing names. For example, if the previous server was accessed via “\server01\redirected folders,” the new server will also recognize this path post-migration. This approach ensures that no modifications are required at the workstation level, allowing for a more seamless and minimally disruptive upgrade.

Windows Server 2019 Essentials is available exclusively through OEM sales channels, typically pre-installed on hardware from suppliers like HP or Dell. When purchasing, it’s recommended to request installation media, such as an ISO file or USB stick, containing the OEM version of Windows Server 2022 Essentials. Interestingly, the Essentials edition uses the same installation media as the Standard edition. Instead of specific Essentials installation media, the Essentials edition is activated by entering a dedicated product key for the Standard edition of Windows Server 2022. This edition is designed for a server with a single CPU and up to 10 cores, and it supports up to 25 unique users or 50 unique devices concurrently.

In this migration we will use the following terms and definitions

If your Source Server was previously migrated from an older SBS 2011 or SBS 2008, there are additional steps that need to be completed before initiating the migration project.

1. The final version of Windows Server that included NTFRS (File Replication Service) as the default for SYSVOL folder replication was Windows Server 2008. Subsequent versions, starting with Windows Server 2008 R2, adopted DFS Replication (DFSR) as the preferred method, although NTFRS remained supported for upgraded systems. From Windows Server 2012 onwards, DFSR became the sole method for SYSVOL replication, with NTFRS being deprecated. Organizations using NTFRS had to transition to DFSR. It is noted that some Windows Server 2016 Essentials instances still operate with NTFRS, despite the migration requirement. To migrate from NTFRS to DFSR, follow the instructions for SYSVOL replication migration https://server-essentials.com/support/migrate-sysvol-replication-from-frs-to-dfsr-replication-before-you-start-your-migration-project. Prior to migration, ensure there are no Journalwrap issues, understand Active Directory Health during migration, and utilize tools such as repadmin and dcdiag https://server-essentials.com/support/understanding-active-directory-health-during-an-active-directory-migration-and-tools-you-can-use-like-repadmin-and-dcdiag
2. The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 170 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. This message sometimes shows up in the DFSR Event Log and is a showstopper for your migration, you must resolve the issue before you continue, read https://server-essentials.com/support/dfs-replication-4012-offline-folder-domain-controller
3. Windows Server 2022 requires both the Domain Functional Level and Forest Functional Level to be set at a minimum of Windows Server 2012. This means that all domain controllers in the domain (for DFL) and the forest (for FFL) must be running Windows Server 2012 or higher. If your environment is running older domain controllers (e.g., Windows Server 2008 R2), you'll need to upgrade them before introducing Windows Server 2022 domain controllers but this is also valid if you migrated from SBS 2011 or earlier in the past. Good chance that the Domain Functional Level (DFL) and Forest Functional Level (FFL) is still at a very low level. Pls use these instructions https://server-essentials.com/support/how-to-raise-domain-and-forest-functional-levels-required-for-the-promotion-of-a-windows-server-2022-or-2025-domain-controller
4. It's crucial to have the correct time across your network. Your primary domain controller (PDC), which is also your only domain controller (DC), should synchronize its time settings from an authoritative source, such as an internet atomic clock. The PDC distributes time settings to all other domain-joined devices, so it's important to follow the guidelines in the article https://server-essentials.com/support/recommendation-to-configure-the-root-pdc-with-an-authoritative-time-source-and-avoid-widespread-time-skew. After applying the Group Policy from the article, time settings will be maintained automatically, even during future migrations. To verify the correct time setting, open a browser and visit https://time.is.