Windows Server installation and upgrade

Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008

Extended support for Windows Server 2008 R2 and Windows Server 2008 ends in January 2020. Learn about your upgrade options.

Is it time to move to a newer version of Windows Server? Depending on what you are running now, you have lots of options to get there.

Installation

If you want to move to a newer version of Windows Server on the same hardware, one way that always works is a clean installation, where you just install the newer operating system directly over the old one on the same hardware, thus deleting the previous operating system. That is the simplest way, but you will need to back up your data first and plan to reinstall your applications. There are a few things to be aware of, such as system requirements, so be sure to check the details for Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012.

Moving from any pre-release version (such as Windows Server 2016 Technical Preview) to the released version (Windows Server 2016) always requires a clean installation.

Migration (recommended for Windows Server 2016)

Windows Server migration documentation helps you migrate one role or feature at a time from a source computer that is running Windows Server to another destination computer that is running Windows Server, either the same or a newer version. For these purposes, migration is defined as moving one role or feature and its data to a different computer, not upgrading the feature on the same computer. This is the recommended manner in which to move your existing workload and data to a more recent version of Windows Server. To get started, check the server role upgrade and migration matrix for Windows Server.

Cluster OS Rolling Upgrade

Cluster OS Rolling Upgrade is a new feature in Windows Server 2016 that enables an administrator to upgrade the operating system of the cluster nodes from Windows Server 2012 R2 to Windows Server 2016 without stopping the Hyper-V or the Scale-Out File Server workloads. This feature allows you to avoid downtime which could impact Service Level Agreements. This new feature is discussed in more detail at Cluster operating system rolling upgrade.

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. This is called license conversion. For example, if your server is running Windows Server 2016 Standard, you can convert it to Windows Server 2016 Datacenter. In some releases of Windows Server, you can also freely convert among OEM, volume-licensed, and retail versions with the same command and the appropriate key.

Upgrade

If you want to keep the same hardware and all the server roles you have set up without flattening the server, upgrading is an option—and there are lots of ways to do it. In the classic upgrade, you go from an older operating system to a newer one, keeping your settings, server roles, and data intact. For example, if your server is running Windows Server 2012 R2, you can upgrade it to Windows Server 2016. However, not every older operating system has a pathway to every newer one.

Upgrade works best in virtual machines where specific OEM hardware drivers are not needed for a successful upgrade.

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.

Before you get started with an upgrade, have a look at the tables on this page to see how to get from where you are to where you want to be.

For information about the differences between the installation options available for Windows Server 2016 Technical Preview, including the features that are installed with each option and the management options available after installation, see Windows Server 2016.

Whenever you migrate or upgrade to any version of Windows Server, you should review and understand the support lifecycle policy and timeframe for that version and plan accordingly. You can search for the lifecycle information for the particular Windows Server release that you are interested in.

Upgrading to Windows Server 2016

For details, including important caveats and limitations on upgrade, license conversion between editions of Windows Server 2016, and conversion of evaluation editions to retail, see Supported Upgrade Paths for Windows Server 2016.

Note: Upgrades that switch from a Server Core installation to a Server with a Desktop installation (or vice versa) are not supported. If the older operating system you are upgrading or converting is a Server Core installation, the result will still be a Server Core installation of the newer operating system.

Quick reference table of supported upgrade paths from older Windows Server retail editions to Windows Server 2016 retail editions:

If you are running these versions and editions:	You can upgrade to these versions and editions:
Windows Server 2012 Standard	Windows Server 2016 Standard or Datacenter
Windows Server 2012 Datacenter	Windows Server 2016 Datacenter
Windows Server 2012 R2 Standard	Windows Server 2016 Standard or Datacenter
Windows Server 2012 R2 Datacenter	Windows Server 2016 Datacenter
Hyper-V Server 2012 R2	Hyper-V Server 2016 (using Cluster OS Rolling Upgrade feature)
Windows Server 2012 R2 Essentials	Windows Server 2016 Essentials
Windows Storage Server 2012 Standard	Windows Storage Server 2016 Standard
Windows Storage Server 2012 Workgroup	Windows Storage Server 2016 Workgroup
Windows Storage Server 2012 R2 Standard	Windows Storage Server 2016 Standard
Windows Storage Server 2012 R2 Workgroup	Windows Storage Server 2016 Workgroup

License conversion

You can convert Windows Server 2016 Standard (retail) to Windows Server 2016 Datacenter (retail).

You can convert Windows Server 2016 Essentials (retail) to Windows Server 2016 Standard (retail).

You can convert the evaluation version of Windows Server 2016 Standard to either Windows Server 2016 Standard (retail) or Datacenter (retail).

You can convert the evaluation version of Windows Server 2016 Datacenter to Windows Server 2016 Datacenter (retail).

Upgrading to Windows Server 2012 R2

For details, including important caveats and limitations on upgrade, license conversion between editions of Windows Server 2012 R2, and conversion of evaluation editions to retail, see Upgrade Options for Windows Server 2012 R2.

Quick reference table of supported upgrade paths from older Windows Server retail editions to Windows Server 2012 R2 retail editions:

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

License conversion

You can convert Windows Server 2012 Standard (retail) to Windows Server 2012 Datacenter (retail).

You can convert Windows Server 2012 Essentials (retail) to Windows Server 2012 Standard (retail).

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

Upgrading to Windows Server 2012

For details, including important caveats and limitations on upgrade, and conversion of evaluation editions to retail, see Evaluation Versions and Upgrade Options for Windows Server 2012.

Quick reference table of supported upgrade paths from older Windows Server retail editions to Windows Server 2012 retail editions:

If you are running:	You can upgrade to these editions:
Windows Server 2008 Standard with SP2 or Windows Server 2008 Enterprise with SP2	Windows Server 2012 Standard, Windows Server 2012 Datacenter
Windows Server 2008 Datacenter with SP2	Windows Server 2012 Datacenter
Windows Web Server 2008	Windows Server 2012 Standard
Windows ServerВ 2008В R2 Standard with SP1 or Windows ServerВ 2008В R2 Enterprise with SP1	Windows Server 2012 Standard, Windows Server 2012 Datacenter
Windows ServerВ 2008В R2 Datacenter with SP1	Windows Server 2012 Datacenter
Windows Web ServerВ 2008В R2	Windows Server 2012 Standard

License conversion

You can convert Windows Server 2012 Standard (retail) to Windows Server 2012 Datacenter (retail).

You can convert Windows Server 2012 Essentials (retail) to Windows Server 2012 Standard (retail).

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

Upgrading from Windows Server 2008 R2 or Windows Server 2008

As described in Upgrade Windows Server 2008 and Windows Server 2008 R2, the extended support for Windows Server 2008 R2/Windows Server 2008 ends in January of 2020. To ensure no gap in support, you need to upgrade to a supported version of Windows Server, or rehost in Azure by moving to specialized Windows Server 2008 R2 VMs. Check out the Migration Guide for Windows Server for information and considerations for planning your migration/upgrade.

For on-premises servers, there is no direct upgrade path from Windows Server 2008 R2 to Windows Server 2016 or later. Instead, upgrade first to Windows Server 2012 R2, and then upgrade to Windows Server 2016.

As you are planning your upgrade, be aware of the following guidelines for the middle step of upgrading to Windows Server 2012 R2.

You can’t do an in-place upgrade from a 32-bit to 64-bit architectures or from one build type to another (fre to chk, for example).

In-place upgrades are only supported in the same language. You can’t upgrade from one language to another.

You can’t migrate from a Windows Server 2008 server core installation to Windows Server 2012 R2 with the Server GUI (called «Server with Full Desktop» in Windows Server). You can switch your upgraded server core installation to Server with Full Desktop, but only on Windows Server 2012 R2. Windows Server 2016 and later do not support switching from server core to Full Desktop, so make that switch before you upgrade to Windows Server 2016.

For more information, check out Evaluation Versions and Upgrade Options for Windows Server 2012, which includes role-specific upgrade details.

Схемы обновления до Windows 10 Windows 10 upgrade paths

Относится к: Applies to

• Windows 10 Windows 10
• Windows 10 Mobile Windows 10 Mobile

Схемы обновления Upgrade paths

В этом разделе приведены возможные схемы обновления до Windows 10. This topic provides a summary of available upgrade paths to Windows 10. Выполнить обновление до Windows 10 можно с Windows 7 или более поздней версии операционной системы. You can upgrade to Windows 10 from Windows 7 or a later operating system. Это относится в том числе к обновлению с одного выпуска Windows 10 до более позднего выпуска Windows 10. This includes upgrading from one release of Windows 10 to later release of Windows 10. Также поддерживается миграция между выпусками Windows 10 разной полноты (Корпоративная, Домашняя и т.п.) в пределах одного и того же хронологического выпуска. Migrating from one edition of Windows 10 to a different edition of the same release is also supported.

Если вы также мигрируете в другое издание Windows, см. обновление windows 10 edition. If you are also migrating to a different edition of Windows, see Windows 10 edition upgrade. Методы и поддерживаемые пути описаны на этой странице для изменения выпуска Windows. Methods and supported paths are described on this page to change the edition of Windows. Эти методы требуют ввода лицензии или ключа продукта для нового выпуска Windows перед началом процесса обновления. These methods require that you input a license or product key for the new Windows edition prior to starting the upgrade process. Понижение версии также поддерживается для некоторых путей, но обратите внимание, что приложения и параметры не поддерживаются при понижении версии Windows. Edition downgrade is also supported for some paths, but please note that applications and settings are not maintained when the Windows edition is downgraded.

Обновление версии Windows 10. Вы можете напрямую обновить любую полугодовую версию канала Windows 10 до более новой, поддерживаемой полугодовой версии канала Windows 10, даже если она включает пропуск версий. Windows 10 version upgrade: You can directly upgrade any semi-annual channel version of Windows 10 to a newer, supported semi-annual channel version of Windows 10, even if it involves skipping versions. Работайте с представителем учетной записи, если текущая версия Windows не поддерживается. Work with your account representative if your current version of Windows is out of support. Сведения о доступности и обслуживании см. в листе фактов жизненного цикла Windows. See the Windows lifecycle fact sheet for availability and service information.

Windows 10 LTSC или LTSB: из-за изменения названий версии продуктов, для которых отображается имя Windows 10 LTSB, будут заменены на Windows 10 LTSC в последующих обновлений. Windows 10 LTSC/LTSB: Due to naming changes, product versions that display Windows 10 LTSB will be replaced with Windows 10 LTSC in subsequent feature updates. Термин LTSC используется здесь для указания всех версий с долгосрочным обслуживанием. The term LTSC is used here to refer to all long term servicing versions.

Обновление с Windows 7, Windows 8.1 или Windows 10 полугодовых каналов до Windows 10 LTSC не поддерживается. In-place upgrade from Windows 7, Windows 8.1, or Windows 10 semi-annual channel to Windows 10 LTSC is not supported. Примечание. Для Windows 10 LTSC 2015 этот путь обновления не блокировался. Note: Windows 10 LTSC 2015 did not block this upgrade path. Эта проблема исправлена в выпуске Windows 10 LTSC 2016, в котором теперь доступны только варианта установки: только с данными и чистая установка. This was corrected in the Windows 10 LTSC 2016 release, which will now only allow data-only and clean install options. Можно обновить Windows 10 LTSC до Windows 10 Semi-Annual Channel, если обновление осуществляется до той же или более новой версии сборки. You can upgrade from Windows 10 LTSC to Windows 10 semi-annual channel, provided that you upgrade to the same or a newer build version. Например, Windows 10 Корпоративная 2016 с долгосрочным обслуживанием можно обновить до Windows 10 Корпоративная версии 1607 или более поздней версии. For example, Windows 10 Enterprise 2016 LTSB can be upgraded to Windows 10 Enterprise version 1607 or later. Обновление поддерживается с помощью процесса обновления на месте (с помощью установки Windows). Upgrade is supported using the in-place upgrade process (using Windows setup). Для сохраняемой программы необходимо использовать переключатель Ключ продукта. You will need to use the Product Key switch if you want to keep your apps. Если вы не используете переключатель, параметр «Сохранить личные файлы и приложения» будет серым. Командная строка будет setup.exe/pkey xxxxx-xxxxx-xxxxx-xxxxxx,используясоответствующий ключ продукта Windows 10 SAC. If you don’t use the switch the option ‘Keep personal files and apps’ will be grayed out. The command line would be setup.exe /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx, using your relevant Windows 10 SAC product key. Например, при использовании KMS командная строка будет setup.exe/pkey NPPR9-FWDCX-D2C8J-H872K-2YT43. For example, if using a KMS, the command line would be setup.exe /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43.

Windows N/KN: SkUs Windows «N» и «KN» (выпуски без функций, связанных со средствами массовой информации) следуют тем же путям обновления, которые показаны ниже. Windows N/KN: Windows «N» and «KN» SKUs (editions without media-related functionality) follow the same upgrade paths shown below. Если выпуск до обновления и выпуск после обновления разных типов (как, например, при обновлении с Windows 8.1 Профессиональная N до Windows 10 Pro), в процессе обновления личные данные будут сохранены, однако приложения и параметры будут удалены. If the pre-upgrade and post-upgrade editions are not the same type (e.g. Windows 8.1 Pro N to Windows 10 Pro), personal data will be kept but applications and settings will be removed during the upgrade process.

Windows 8.0. Не удается обновиться непосредственно с Windows 8.0 до Windows 10. Windows 8.0: You cannot upgrade directly from Windows 8.0 to Windows 10. Чтобы обновить Windows 8.0, сначала необходимо установить обновление Windows 8.1. To upgrade from Windows 8.0, you must first install the Windows 8.1 update.

✔ = Поддерживается полное обновление, включая личные данные, параметры и приложения. ✔ = Full upgrade is supported including personal data, settings, and applications.
D = переход на менее полный выпуск; личные данные сохраняются, приложения и параметры удаляются. D = Edition downgrade; personal data is maintained, applications and settings are removed.