Upgrade Options for Windows Server 2012 R2

Applies To: Windows Server 2012, Windows Server 2012 R2

This topic includes information about upgrading to Windows ServerВ® 2012 R2 from a variety of previous operating systems using a variety of methods.

The process of moving to Windows Server 2012 R2 might vary greatly depending on which operating system you are starting with and the pathway you take. We use the following terms to distinguish among different actions, any of which could be involved in a new Windows Server 2012 R2 deployment.

Installation is the basic concept of getting the new operating system on your hardware. Specifically, a clean installation requires deleting the previous operating system. For information about installing Windows Server 2012 R2, see System Requirements and Installation Information for Windows Server 2012 R2. For information about installing other versions of Windows Server, see Windows Server Installation and Upgrade.

Upgrade means moving from your existing operating system release to a more recent release, while staying on the same hardware. For example, if your server is running Windows Server 2012, you can upgrade it to Windows Server 2012 R2. You can upgrade from an evaluation version of the operating system to a retail version, from an older retail version to a newer version, or, in some cases, from a volume-licensed edition of the operating system to an ordinary retail edition.

License conversion in some operating system releases, you can convert a particular edition of the release to another edition of the same release in a single step with a simple command and the appropriate license key. We call this “license conversion.” For example, if you are running Windows Server 2012 R2 Standard, you can convert it to Windows Server 2012 R2 Datacenter.

Migration means moving from your existing operating system to Windows Server 2012 R2 by transferring to a different set of hardware. Migration, which might vary considerably depending on the server roles you have installed, is discussed in detail at https://technet.microsoft.com/windowsserver/dn458795.

Depending on your scenario, you might encounter a variety of different upgrade pathways.

Upgrading previous retail versions of Windows Server to Windows Server 2012 R2

The table below briefly summarizes which already licensed (that is, not evaluation) Windows operating systems can be upgraded to which editions of Windows Server 2012 R2.

Note the following general guidelines for supported paths:

In-place upgrades from 32-bit to 64-bit architectures are not supported. All editions of Windows Server 2012 R2 are 64-bit only.

In-place upgrades from one language to another are not supported.

In-place upgrades from one build type (fre to chk, for example) are not supported.

If the server is a domain controller, see https://technet.microsoft.com/library/hh994618.aspx for important information.

Upgrades from pre-release versions of Windows Server 2012 R2 are not supported. Perform a clean installation to Windows Server 2012 R2.

Upgrades that switch from a Server Core installation to the Server with a GUI mode of Windows Server 2012 R2 in one step (and vice versa) are not supported. However, after upgrade is complete, Windows Server 2012 R2 allows you to switch freely between Server Core and Server with a GUI modes. For more information about these installation options, how to convert between them, and how to use the new Minimal Server Interface and Features on Demand, see https://technet.microsoft.com/library/hh831786.

If you do not see your current version in the left column, upgrading to this release of Windows Server 2012 R2 is not supported.

If you see more than one edition in the right column, upgrade to either edition from the same starting version is supported.

If you are running:

You can upgrade to these editions:

Windows ServerВ 2008В R2 Datacenter with SP1

Windows Server 2012 R2 Datacenter

Windows ServerВ 2008В R2 Enterprise with SP1

Windows Server 2012 R2 Standard or Windows Server 2012 R2 Datacenter

Windows ServerВ 2008В R2 Standard with SP1

Windows Server 2012 R2 Standard or Windows Server 2012 R2 Datacenter

Windows Web ServerВ 2008В R2 with SP1

Windows Server 2012 R2 Standard

Windows Server 2012 Datacenter

Windows Server 2012 R2 Datacenter

Windows Server 2012 Standard

Windows Server 2012 R2 Standard or Windows Server 2012 R2 Datacenter

Hyper-V Server 2012

Hyper-V Server 2012 R2

Windows Storage Server 2012 Standard

Windows Storage Server 2012 R2 Standard

Windows Storage Server 2012 Workgroup

Windows Storage Server 2012 R2 Workgroup

Per-server-role considerations for upgrading

Even in supported upgrade paths from previous retail versions to Windows Server 2012 R2, certain server roles that are already installed might require additional preparation or actions for the role to continue functioning after the upgrade. Consult the specific TechNet Library topics for each server role you intend to install for details of additional steps that might be required.

Converting a current evaluation version to a current retail version

You can convert the evaluation version of Windows Server 2012 R2 Standard to either Windows Server 2012 R2 Standard (retail) or Datacenter (retail). Similarly, you can convert the evaluation version of Windows Server 2012 R2 Datacenter to the retail version.

Before you attempt to convert from evaluation to retail, verify that your server is actually running an evaluation version. To do this, do either of the following:

From an elevated command prompt, run slmgr.vbs /dlv; evaluation versions will include “EVAL” in the output.

From the Start screen, open Control Panel. Open System and Security, and then System. View Windows activation status in the Windows activation area of the System page. Click View details in Windows activation for more information about your Windows activation status.

If you have already activated Windows, the Desktop shows the time remaining in the evaluation period.

If the server is running a retail version instead of an evaluation version, see the “Upgrading previous retail versions of Windows Server to Windows Server 2012 R2” section of this topic for instructions to upgrade to Windows Server 2012.

For Windows Server 2012 Essentials: You can convert to the full retail version by entering a retail, volume license, or OEM key in the command slmgr.vbs.

If the server is running an evaluation version of Windows Server 2012 Standard or Windows Server 2012 Datacenter, you can convert it to a retail version as follows:

If the server is a domain controller, you cannot convert it to a retail version. In this case, install an additional domain controller on a server that runs a retail version and remove AD DS from the domain controller that runs on the evaluation version. For more information, see https://technet.microsoft.com/library/hh994618.aspx.

Read the license terms.

From an elevated command prompt, determine the current edition name with the command DISM /online /Get-CurrentEdition. Make note of the edition ID, an abbreviated form of the edition name. Then run DISM /online /Set-Edition: /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula, providing the edition ID and a retail product key. The server will restart twice.

For the evaluation version of Windows Server 2012 Standard, you can also convert to the retail version of Windows Server 2012 Datacenter in one step using this same command and the appropriate product key.

Converting a current retail version to a different current retail version

At any time after installing Windows Server 2012, you can run Setup to repair the installation (sometimes called “repair in place”) or, in certain cases, to convert to a different edition.

You can run Setup to perform a “repair in place” on any edition of Windows Server 2012; the result will be the same edition you started with.

For Windows Server 2012 Standard, you can convert the system to Windows Server 2012 Datacenter as follows: From an elevated command prompt, determine the current edition name with the command DISM /online /Get-CurrentEdition. Make note of the edition ID, an abbreviated form of the edition name. Then run DISM /online /Set-Edition: /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula, providing the edition ID and a retail product key. The server will restart twice.

Converting a current volume-licensed version to a current retail version

At any time after installing Windows Server 2012, you can freely convert it between a volume-licensed version, a retail version, or an OEM version. The edition remains the same during this conversion.

To do this, from an elevated command prompt, run:

slmgr /ipk

Where is the appropriate volume-license, retail, or OEM product key.

Обновление Windows Server 2008 R2 до Windows Server 2012 R2 Upgrade Windows Server 2008 R2 to Windows Server 2012 R2

Если вы хотите сохранить существующее оборудование и все роли сервера, которые вы настроили, без сжатия сервера, необходимо выполнить обновление на месте. If you want to keep the same hardware and all the server roles you’ve already set up without flattening the server, you’ll want to do an in-place upgrade. При обновлении на месте вы переходите с более старой версии операционной системы на более новую, сохраняя свои параметры, роли сервера и данные. An in-place upgrade allows you to go from an older operating system to a newer one, while keeping your settings, server roles, and data intact. Эта статья поможет вам перейти с Windows Server 2008 R2 на Windows Server 2012 R2. This article helps you to move from Windows Server 2008 R2 to Windows Server 2012 R2.

Чтобы выполнить обновление до Windows Server 2019, сначала используйте сведения из этой статьи, чтобы выполнить обновление до Windows Server 2012 R2, а затем выполнить обновление с Windows Server 2012 R2 до Windows Server 2019. To upgrade to Windows Server 2019, use this topic first to upgrade to Windows Server 2012 R2, and then upgrade from Windows Server 2012 R2 to Windows Server 2019.

Подготовка к обновлению на месте Before you begin your in-place upgrade

Перед началом обновления Windows Server рекомендуется выполнить сбор данных с устройств для диагностики и устранения неполадок. Before you start your Windows Server upgrade, we recommend that you collect some information from your devices, for diagnostic and troubleshooting purposes. Так как эти сведения предназначены для использования только в случае сбоя обновления, необходимо убедиться в том, что вы храните информацию в расположении, доступ к которому можно получить с вашего устройства. Because this information is intended for use only if your upgrade fails, you must make sure that you store the information somewhere that you can get to it off of your device.

Сбор данных To collect your info

Откройте командную строку, перейдите в c:\Windows\system32 , а затем введите systeminfo.exe. Open a command prompt, go to c:\Windows\system32 , and then type systeminfo.exe.

Скопируйте, вставьте и сохраните полученные сведения о системе в любом расположении на устройстве. Copy, paste, and store the resulting system information somewhere off of your device.

Введите ipconfig /all в командной строке, а затем скопируйте и вставьте полученные сведения о конфигурации в то же расположение, что и ранее. Type ipconfig /all into the command prompt, and then copy and paste the resulting configuration information into the same location as above.

Откройте редактор реестра, перейдите в куст HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion, а затем скопируйте и вставьте значения BuildLabEx (версия) и EditionID (выпуск) для Windows Server в то же расположение, что и выше. Open the Registry Editor, go to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion hive, and then copy and paste the Windows Server BuildLabEx (version) and EditionID (edition) into the same location as above.

После получения всех данных, относящихся к Windows Server, мы настоятельно рекомендуем создать резервную копию операционной системы, приложений и виртуальных машин. After you’ve collected all of your Windows Server-related information, we highly recommend that you backup your operating system, apps, and virtual machines. Кроме того, необходимо завершить работу, выполнить быструю миграцию или динамическую миграцию всех виртуальных машин, выполняющихся в данный момент на сервере. You must also Shut down, Quick migrate, or Live migrate any virtual machines currently running on the server. Во время обновления на месте виртуальные машины не могут работать. You can’t have any virtual machines running during the in-place upgrade.

Выполнение обновления To perform the upgrade

Убедитесь, что значение BuildLabEx указывает, что используется Windows Server 2008 R2. Make sure the BuildLabEx value says you’re running Windows Server 2008 R2.

Найдите установочный носитель Windows Server 2012 R2 и выберите setup.exe. Locate the Windows Server 2012 R2 Setup media, and then select setup.exe.

Выберите Да, чтобы начать процесс установки. Select Yes to start the setup process.

На экране Windows Server 2012 R2 выберите Установить сейчас. On the Windows Server 2012 R2 screen, select Install now.

Для устройств, подключенных к Интернету, выберите Установить обновления из Интернета (рекомендуется) . For internet-connected devices, select Go online to install updates now (recommended).

Выберите выпуск Windows Server 2012 R2, который требуется установить, а затем нажмите кнопку Далее. Select the Windows Server 2012 R2 edition you want to install, and then select Next.

Выберите Я принимаю условия лицензии, чтобы принять условия лицензионного соглашения, исходя из вашего канала распространения (например, розничная, многократная, OEM, ODM версия и т. д.), а затем нажмите кнопку Далее. Select I accept the license terms to accept the terms of your licensing agreement, based on your distribution channel (such as, Retail, Volume License, OEM, ODM, and so on), and then select Next.

Выберите Upgrade: Install Windows and keep files, settings, and applications (Обновление: установить Windows и сохранить файлы, настройки и приложения), чтобы выбрать обновление на месте. Select Upgrade: Install Windows and keep files, settings, and applications to choose to do an in-place upgrade.

Программа установки напоминает вам, что вы должны убедиться, что ваши приложения совместимы с Windows Server 2012 R2, используя информацию из статьи Установка и обновление Windows Server, а затем нажмите кнопку Далее. Setup reminds you to make sure your apps are compatible with Windows Server 2012 R2, using the information in the Windows Server installation and upgrade article, and then select Next.

Если отображается страница с уведомлением о том, что обновление не рекомендуется, можно проигнорировать его и нажать кнопку Подтвердить. If you see a page that tells you upgrade isn’t recommended, you can ignore it and select Confirm. Она предназначена для того, чтобы предлагать чистую установку, но это не обязательно. It was put in place to prompt for clean installations, but it isn’t necessary.

Начнется обновление на месте, в котором отображается окно Обновление Windows с информацией о ходе выполнения. The in-place upgrade starts, showing you the Upgrading Windows screen with its progress. После завершения обновления сервер перезапустится. After the upgrade finishes, your server will restart.

Действия по завершении обновления After your upgrade is done

После завершения обновления необходимо убедиться, что обновление до Windows Server 2012 R2 прошло успешно. After your upgrade completes, you must make sure the upgrade to Windows Server 2012 R2 was successful.

Проверка успешности обновления To make sure your upgrade was successful

Откройте редактор реестра, перейдите в куст HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion и просмотрите запись ProductName. Open the Registry Editor, go to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion hive, and view the ProductName. Вы должны увидеть выпуск Windows Server 2012 R2, например Windows Server 2012 R2 Datacenter. You should see your edition of Windows Server 2012 R2, for example Windows Server 2012 R2 Datacenter.

Убедитесь, что все приложения работают, и что подключения клиентов к приложениям выполняются успешно. Make sure all of your applications are running and that your client connections to the applications are successful.

Если вы считаете, что во время обновления возникли проблемы, скопируйте и создайте архив каталога %SystemRoot%\Panther (обычно C:\Windows\Panther ) и обратитесь в службу поддержки Майкрософт. If you think something might have gone wrong during your upgrade, copy and zip the %SystemRoot%\Panther (usually C:\Windows\Panther ) directory and contact Microsoft support.

Дальнейшие действия Next steps

Вы можете выполнить обновление на месте для перехода с версии Windows Server 2012 R2 на Windows Server 2019. You can perform one more upgrade to go from Windows Server 2012 R2 to Windows Server 2019. Подробные инструкции см. в статье Upgrade Windows Server 2012 R2 to Windows Server 2019 (Обновление Windows Server 2012 R2 до Windows Server 2019). For detailed instructions, see Upgrade Windows Server 2012 R2 to Windows Server 2019.