Usage guide: Windows 11 migration

This workflow will automate the process of assessing whether pre-Windows 11 devices are ready to be compatible with Windows 11, attempt to automatically resolve common incompatibility issues, report incompatible or partially compatible devices using an ITSM tool, and interact with users to determine the appropriate time to update.

Ensure your workflow is properly configured by following the steps highlighted in its configuration guide: Configuration guide: Windows 11 migration

Workflow Structure

This section describes the key steps in this workflow. The first two queries with a condition after them are designed to check whether the device is already part of a migration group. This part helps to re-validate the input to ensure that any individual device has not been assessed and scheduled for multiple upgrades to Windows 11.

The next group of thinklets is designed to assess the device for compatibility with Windows 11. This assessment is performed using the Get Windows 11 Readiness remote action. This remote action verifies that devices meet the Microsoft requirements for Windows 11 listed on the following page:

https://learn.microsoft.com/en-us/windows/whats-new/windows-11-requirements

The following decision matrix explains which component incompatibilities are considered upgradeable (partially compatible) and which are considered not upgradeable (replacement candidates):

Incompatible hardware componentUpgradableNot upgradable

CPU

X

TPM module

X

RAM

X

Storage

X

SecureBoot

X

DirectX

X

WDDM

X

In case of incompatibility or partial compatibility, these devices will be reported to the ITSM tool in one of the predefined tickets for storing incompatible and partially compatible devices.

Details of devices considered partially compatible or candidates for replacement will be added to predefined ITSM tickets. This information includes the following: device name, and incompatible hardware components of these devices.

If the device is considered eligible for an update, the workflow interacts with the user to check if it is the right time to update. The user can defer the update up to three times for a specified period, after which the device will be added to the migration group and the Intune policy update will be triggered.

Once a device becomes a member of a migration group, content download begins in the background based on Intune deployment settings.

After the update contents are downloaded, the user receives a standard Windows notification indicating that the updates are ready to be installed and that a reboot is required to complete the update.

Depending on your Intune deployment settings, the user may have the option to delay this update or schedule when it should be installed.

The duration of the update may vary depending on the specific device hardware, user data volume, and number of applications. On average it takes about 1.5 hours. Once the update is complete, the user will be able to log in with the same account. User data, applications, and settings remain in place.

Related topics

For more information on Windows 11 migration progress in your organization, Nexthink has released the pack, Windows 11 Readiness and Migration. This pack enhances your ability to monitor and report on Windows 11 migration progress at various stages, assess device readiness for Windows 11 by component, assess device and application stability after migration, and compare before and after DEX scores.

Last updated