Key steps for Windows Server 2012 migration

Have you noticed that Microsoft has not released a service pack for Windows Server 2012 as it did before, and it is implemented once a month to "update summary". It contains hot fixes that address performance and likelihood issues. Unfortunately, these summaries don't accumulate, so you may end up needing to install multiple summaries to get the latest kernel, drivers, and dynamic link libraries.

You may have noticed how fast Microsoft released Windows Server 2012 R2 —— the first version was released only one year later. Is R2 the new name for SP1? Admittedly, R2 brings a lot of heavyweight new features, such as cluster-shareable virtual disks, but it also means that the first hot fix since Windows Server 2012 was released.

The Windows Server operating system continues to grow in function, performance and reliability. The important enhancements in Windows Server 2012 make you feel good. But perhaps the driving force for moving to Windows Server 2012 made Microsoft decide to end mainstream support for Windows Server 2008 in January 2015.

The goal of the migration is to rebuild the same roles, features, and settings in the environment using this new operating system. By updating and cleaning the installation on new hardware, you can ensure that there are no legacy in the new version, providing the best stability and performance. If you originally implemented a full set of backups on an existing server, you can recover if there is a problem with the system.

First, make sure your hardware meets the minimum requirements

Microsoft maintains the Windows Server Directory website to help you quickly determine if an existing or planned server is on the Windows Server 2012 list.

For example, most HP ProLiant server requirements are 7th or 8th generation to take advantage of new power management features. The same is true for specific hardware models. So be sure to check the list. If you plan to use a failover cluster, make sure all devices have Windows Server 2012 certification.

Second, upgrade the server's BIOS (ie system ROM)

In order to support the new power management features and other hardware-specific enhancements, most manufacturers will release a new BIOS with the mainstream operating system. version. An outdated BIOS can cause intermittent system crashes, so take a moment to browse your vendor website to make sure you are running the latest version.

Before migrating to Windows Server, another best practice is to check the list of installed software products, as sometimes you may need to install the latest version. In particular, some kernel-mode filter drivers, such as anti-virus software, quota management, or third-party backup software, require an upgrade to support major releases.

You may also need to update the microport drivers, such as the host bus adapter, network interface card, and corresponding device firmware. Typically, your vendor's website has the latest version of drivers and firmware updates and upgrade guides.

III. Guides and Tools

Microsoft has prepared a comprehensive set of migration guides and tools (such as PowerShell scripts) to assist you with roles, features and settings from Windows Server 2003/R2 or Windows Server 2008 R2 is migrated to Windows Server 2012 R2. The tool supports cross-architecture (x86/x64), physical to virtual, and server core to GUI migration.

IV. Failover Clusters

Another useful resource is the Cluster Migration Wizard, which helps you migrate cluster roles (services and applications) from Windows Server 2008 R2 to 2012. However, Windows Server 2003 R2 cluster migration is not supported. There are two options when migrating a cluster. You can create a brand new cluster and then copy the roles. Or you can perform an in-place migration, remove a node from an existing cluster and then re-install to create a new node, copy the role, clean it up, and then re-add the removed node by reinstalling.