Create a task sequence to upgrade an OS in Configuration Manager

Applies to: Configuration Manager (current branch)

Use task sequences in Configuration Manager to automatically upgrade an OS on a destination computer. This upgrade can be from Windows 7 or later to Windows 10, or from Windows Server 2012 or later to Windows Server 2016 or later. Create a task sequence that references an OS upgrade package or feature update and any other content to install, such as applications or software updates. The task sequence to upgrade an OS is part of the Upgrade Windows to the latest version scenario.

Starting in version 2103, you can upgrade by using a feature update deployed with the task sequence. This integration combines the simplicity of Windows servicing with the flexibility of task sequences. Servicing uses content that you synchronize through the software update point. This process simplifies the need to manually get, import, and maintain the Windows image content used with a standard task sequence to upgrade Windows. The size of the servicing ESD file is generally smaller than the OS upgrade package and WIM image file.

Prerequisites

Before you create the task sequence, make sure the following requirements are in place:

Required

An OS upgrade package is available in the Configuration Manager console.

Starting in version 2103, you can also use a feature update. In this case, the OS upgrade package isn’t required. For more information, see Requirements for a feature update in a task sequence.

When upgrading to Windows Server 2016 or later, select the Ignore any dismissable compatibility messages setting in the Upgrade Operating System task sequence step. Otherwise the upgrade fails.

Required (if used)

Synchronize software updates in the Configuration Manager console.

Add applications to the Configuration Manager console.

Requirements for a feature update in a task sequence

Synchronize the software update point to include the Upgrades classification. For more information, see Configure classifications and products.

For a deployment package that contains the feature update, distribute it to a distribution point that the client can access. For more information, see Download software updates.

If the feature update isn’t already downloaded, you can manage the deployment package when you deploy the task sequence.

When you deploy the task sequence, you can also select the option of No deployment package for the feature update. When clients run the task sequence, they download the feature update from peers or the Microsoft cloud.

The option to Pre-download content for this task sequence doesn’t apply to feature updates.

Review the configuration of the following client settings in the Software Updates group, which are applicable to this scenario:

Specify thread priority for feature updates: In most instances, set this value to Normal.

Enable Dynamic Update for feature updates: Use this setting to use dynamic update to install language packs, features on demand, drivers, and cumulative updates during Windows Setup. Clients download these other updates from the internet.

Allow clients to download delta content when available: If you use Windows Delivery Optimization, the content that the client downloads may be much smaller.

Known issues with feature updates in a task sequence

Create a new task sequence

If you need to create a new task sequence, you need an OS upgrade package to complete the Create Task Sequence Wizard.

To create a task sequence to upgrade an OS to Windows 10, you typically use the steps in the Process section. The task sequence includes the Upgrade OS step, as well as additional recommended steps and groups to handle the end-to-end upgrade process.

You can create a custom task sequence and add the Upgrade OS step. If you choose this method, also add the Restart Computer step after the Upgrade OS step. Make sure to use the setting for The currently installed default operating system to restart the computer into the installed OS and not Windows PE.

If you have an existing Windows 10 in-place upgrade task sequence, edit or copy it. Then change the Upgrade OS task sequence step to install the feature update.

Export, import, and migrate task sequences

If you export a task sequence with the Upgrade OS step that uses a feature update, the exported task sequence doesn’t include the feature update content. When you import the task sequence, readd the Upgrade OS step with the feature update.

This behavior is similar if you migrate a task sequence with a feature update between hierarchies.

Create prestaged content file

You can’t currently use the action to Create prestaged content file for a task sequence with a feature update.

Create standalone media

Standalone media isn’t supported for a task sequence with a feature update. When you try to create standalone media, it fails with entries similar to the following in CreateTSMedia.log:

Process

To upgrade the OS on clients, create a task sequence and select Upgrade an operating system from upgrade package in the Create Task Sequence Wizard. The wizard adds the task sequence steps to upgrade the OS, apply software updates, and install applications.

In the Configuration Manager console, go to the Software Library workspace, expand Operating Systems, and then select Task Sequences.

On the Home tab of the ribbon, in the Create group, select Create Task Sequence.

On the Create a New Task Sequence page of the Create Task Sequence Wizard, select Upgrade an operating system from an upgrade package, and then select Next.

On the Task Sequence Information page, specify the following settings:

Task sequence name: Specify a name that identifies the task sequence.

Description: Optionally specify a description.

On the Upgrade the Windows Operating System page, specify the following settings:

Upgrade package: Specify the upgrade package that contains the OS upgrade source files. Verify that you’ve selected the correct upgrade package by looking at the information in the Properties pane. For more information, see Manage OS upgrade packages.

Edition index: If there are multiple OS edition indexes available in the package, select the edition index you want. By default, the wizard selects the first index.

Product key: Specify the Windows product key for the OS to install. Specify encoded volume license keys or standard product keys. If you use a standard product key, separate each group of five characters by a dash ( — ). For example: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX . When the upgrade is for a volume license edition, the product key may not be required.

This product key can be a multiple activation key (MAK), or a generic volume licensing key (GVLK). A GVLK is also referred to as a key management service (KMS) client setup key. For more information, see Plan for volume activation. For a list of KMS client setup keys, see KMS client setup keys in the Windows Server activation guide.

Ignore any dismissable compatibility messages: Select this setting if you’re upgrading to Windows Server 2016 or later. If you don’t select this setting, the task sequence fails to complete because Windows Setup is waiting for the user to select Confirm on a Windows app compatibility dialog.

On the Include Updates page, specify whether to install required, all, or no software updates. Then select Next. If you specify to install software updates, Configuration Manager installs only those updates targeted to the collections of which the destination computer is a member.

On the Install Applications page, specify the applications to install on the destination computer, and then select Next. If you select more than one application, also specify whether the task sequence should continue if the installation of a specific application fails.

Complete the wizard.

When the task sequence runs on a device, the Configuration Manager client creates several scripts to control the task sequence behavior in various scenarios. When the task sequence completes, the client doesn’t remove these scripts until the computer restarts. These script files don’t contain sensitive information.

Customize

The default task sequence template for Windows 10 in-place upgrade includes other groups with recommended actions to add before and after the upgrade process. These actions are common among many customers who are successfully upgrading devices to Windows 10. For more information, see In-place upgrade recommendations.

Next steps

The pre-cache feature for available deployments of task sequences lets clients download relevant OS upgrade package content before a user installs the task sequence. For more information, see Configure pre-cache content.

Рекомендации по обновлению и переносу 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 .