Рекомендации по обновлению и переносу Windows Windows upgrade and migration considerations

Файлы и параметры приложений можно перенести на новое оборудование под управлением операционной системы Windows® или сохранить их во время обновления операционной системы на том же компьютере. Files and application settings can be migrated to new hardware running the Windows® operating system, or they can be maintained during an operating system upgrade on the same computer. В этом разделе подводятся ® microsoft® которые можно использовать для перемещения файлов и параметров между установками в дополнение к особым соображениям для выполнения обновления или переноса. This topic summarizes the Microsoft® tools you can use to move files and settings between installations in addition to special considerations for performing an upgrade or migration.

Обновление из предыдущей версии Windows Upgrade from a previous version of Windows

Вы можете обновить предыдущую версию Windows, что означает, что вы можете установить новую версию Windows и сохранить приложения, файлы и параметры, как это было в предыдущей версии Windows. You can upgrade from an earlier version of Windows, which means you can install the new version of Windows and retain your applications, files, and settings as they were in your previous version of Windows. Если вы решите выполнить настраиваемую установку Windows вместо обновления, приложения и параметры не будут поддерживаться. If you decide to perform a custom installation of Windows instead of an upgrade, your applications and settings will not be maintained. Ваши личные файлы и все файлы и каталоги Windows будут перемещены в папку Windows.old. Your personal files, and all Windows files and directories, will be moved to a Windows.old folder. Вы можете получить доступ к данным в папке Windows.old после завершения установки Windows. You can access your data in the Windows.old folder after Windows Setup is complete.

Перенос файлов и параметров Migrate files and settings

Средства миграции доступны для переноса параметров с одного компьютера с Windows на другой. Migration tools are available to transfer settings from one computer that is running Windows to another. Эти средства передают только параметры программы, а не сами программы. These tools transfer only the program settings, not the programs themselves.

Дополнительные сведения о совместимости приложений см. в набор средств application набор средств ACT. For more information about application compatibility, see the Application Compatibility Toolkit (ACT).

Средство миграции состояния пользователя (USMT) 10.0 — это приложение, предназначенное для администраторов, которые выполняют крупномасштабные автоматизированные развертывания. The User State Migration Tool (USMT) 10.0 is an application intended for administrators who are performing large-scale automated deployments. Для развертывания на небольшом количестве компьютеров или для индивидуально настроенных развертывания можно использовать Windows Easy Transfer. For deployment to a small number of computers or for individually customized deployments, you can use Windows Easy Transfer.

Перенос с помощью Windows Easy Transfer Migrate with Windows Easy Transfer

Windows Easy Transfer — это мастер программного обеспечения для передачи файлов и параметров с одного компьютера с Windows на другой. Windows Easy Transfer is a software wizard for transferring files and settings from one computer that is running Windows to another. Это помогает выбрать, что переместить на новый компьютер, позволяет определить, какой метод миграции использовать, а затем выполняет передачу. It helps you select what to move to your new computer, enables you to set which migration method to use, and then performs the transfer. По завершению переноса отчеты windows Easy Transfer показывают, что было передано, и предоставляют список программ, которые можно установить на новом компьютере, а также ссылки на другие программы, которые можно скачать. When the transfer has completed, Windows Easy Transfer Reports shows you what was transferred and provides a list of programs you might want to install on your new computer, in addition to links to other programs you might want to download.

С помощью Windows Easy Transfer файлы и параметры могут передаваться с помощью сетевой доли, usb-флеш-накопителя (UFD) или кабеля Easy Transfer. With Windows Easy Transfer, files and settings can be transferred using a network share, a USB flash drive (UFD), or the Easy Transfer cable. Однако для передачи файлов и параметров с помощью Windows Easy Transfer нельзя использовать обычный универсальный кабель серийного автобуса (USB). However, you cannot use a regular universal serial bus (USB) cable to transfer files and settings with Windows Easy Transfer. Кабель Easy Transfer можно приобрести в Интернете, у производителя компьютера или в магазине электроники. An Easy Transfer cable can be purchased on the Web, from your computer manufacturer, or at an electronics store.

Миграция с помощью средства миграции состояния пользователя Migrate with the User State Migration Tool

Вы можете использовать USMT для автоматизации миграции во время больших развертывание операционной системы Windows. You can use USMT to automate migration during large deployments of the Windows operating system. USMT использует настраиваемые файлы правила миграции (.xml), чтобы точно контролировать, какие учетные записи пользователей, файлы пользователей, параметры операционной системы и параметры приложений переносились и как они переносились. USMT uses configurable migration rule (.xml) files to control exactly which user accounts, user files, operating system settings, and application settings are migrated and how they are migrated. Можно использовать USMT ** для обеих однобоких миграций, где заменяется одно оборудование, или миграций стирки и загрузки (или обновления) при обновлении только операционной системы. You can use USMT for both side-by-side migrations, where one piece of hardware is being replaced, or wipe-and-load (or refresh) migrations, when only the operating system is being upgraded.

Соображения обновления и миграции Upgrade and migration considerations

При обновлении или переходе на новую версию Windows необходимо знать о следующих проблемах и соображениях: Whether you are upgrading or migrating to a new version of Windows, you must be aware of the following issues and considerations:

Совместимость приложений Application compatibility

Дополнительные сведения о совместимости приложений в Windows см. в материале Использование готовности к обновлению для управления обновлениями Windows. For more information about application compatibility in Windows, see Use Upgrade Readiness to manage Windows upgrades.

Многоязычные обновления изображений Windows Multilingual Windows image upgrades

При выполнении многоязычных обновлений Windows межязычные обновления не поддерживаются USMT. When performing multilingual Windows upgrades, cross-language upgrades are not supported by USMT. При обновлении или переносе операционной системы с несколькими языковыми пакетами можно обновить или перейти только на язык пользовательского интерфейса по умолчанию. If you are upgrading or migrating an operating system with multiple language packs installed, you can upgrade or migrate only to the system default user interface (UI) language. Например, если по умолчанию установлен пакет испанского языка, можно обновить или перейти только на английский. For example, if English is the default but you have a Spanish language pack installed, you can upgrade or migrate only to English.

Если вы используете одноязычное изображение Windows, которое соответствует языку пользовательского интерфейса системы по умолчанию вашей многоязычной операционной системы, миграция будет работать. If you are using a single-language Windows image that matches the system default UI language of your multilingual operating system, the migration will work. Однако все языковые пакеты будут удалены, и после завершения обновления их придется переустановить. However, all of the language packs will be removed, and you will have to reinstall them after the upgrade is completed.

Errorhandler.cmd Errorhandler.cmd

При обновлении из более ранней версии Windows, если вы собираетесь использовать Errorhandler.cmd, необходимо скопировать этот файл в каталог %WINDIR%\Setup\Scripts на старой установке. When upgrading from an earlier version of Windows, if you intend to use Errorhandler.cmd, you must copy this file into the %WINDIR%\Setup\Scripts directory on the old installation. Это позволяет убедиться, что при ошибках на этапе установки Windows на уровне ниже уровня будут запускаться команды в Errorhandler.cmd. This makes sure that if there are errors during the down-level phase of Windows Setup, the commands in Errorhandler.cmd will run.

Перенос ACL диска данных Data drive ACL migration

Во время прохода настройки установки Windows корневой список управления доступом (ACL) на дисках, отформатированные для NTFS, которые, как представляется, не имеют операционной системы, будет изменен в формат ACL Windows XP по умолчанию. During the configuration pass of Windows Setup, the root access control list (ACL) on drives formatted for NTFS that do not appear to have an operating system will be changed to the default Windows XP ACL format. AcLs на этих дисках изменены, чтобы позволить пользователям, уверяемым в подлинности, изменять доступ к папкам и файлам. The ACLs on these drives are changed to enable authenticated users to modify access on folders and files.

Изменение acLs может повлиять на производительность установки Windows, если acLs Windows XP по умолчанию применяются к разделу с большим объемом данных. Changing the ACLs may affect the performance of Windows Setup if the default Windows XP ACLs are applied to a partition with a large amount of data. Из-за этих проблем с производительностью можно изменить следующее значение реестра, чтобы отключить эту функцию: Because of these performance concerns, you can change the following registry value to disable this feature:

Эта функция отключена, если это ключевое значение реестра существует и настроено на 1 . This feature is disabled if this registry key value exists and is configured to 1 .

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.