Migrate users from Windows 10 to Windows 11 AVD host pools with FSLogix continuity

Avatar
Nerdio Product Support

This article provides a recommended workflow for moving users from an existing Windows 10 Azure Virtual Desktop (AVD) host pool to a new Windows 11 host pool, while preserving user profile continuity with FSLogix. It covers staged host pool migration, pilot validation, and rollback planning.

The guidance applies to pooled dynamic or static host pools that use Windows 10 Enterprise multi-session or Windows 11 Enterprise multi-session, with FSLogix profile containers on Azure Files, Azure NetApp Files, or another supported storage path.

Note

In most AVD environments, create a new Windows 11 image and host pool, apply the validated FSLogix configuration, pilot with a limited group, and then phase users over. Don't treat pooled session hosts like traditional in-place desktop upgrades.

How profile continuity works

FSLogix profile containers store the user profile outside the session host. At sign-in, the profile container is attached to the session host and appears to Windows as the local user profile. This allows profile data and user personalization to follow the user across compatible AVD session hosts.

For a Windows 10 to Windows 11 migration, the usual design is to build a clean Windows 11 host pool and use the same validated FSLogix profile path when profile continuity is required. Treat the migration as an application, policy, and user experience validation project as well. Profile continuity doesn't guarantee application compatibility.

The migration follows these stages:

  1. Review and document the current Windows 10 host pool configuration.

  2. Create, clone, or update a Windows 11 desktop image.

  3. Create a new Windows 11 host pool that uses the validated image.

  4. Apply the correct FSLogix profile configuration to the Windows 11 host pool.

  5. Pilot with a limited user group.

  6. Validate profile behavior, applications, OneDrive, Teams, Outlook, printing, and performance.

  7. Move users in controlled waves.

  8. Maintain rollback access until the migration is stable.

  9. Retire or repurpose the Windows 10 host pool after the approved rollback period.

Planning considerations

Confirm Windows 11 application compatibility

Before you move users, validate all required applications on the Windows 11 image. Don't assume that an application that works on Windows 10 behaves identically on Windows 11 across the full user workflow. Validate:

  • Line-of-business applications

  • Microsoft 365 Apps

  • Teams and meeting functionality

  • OneDrive sync behavior

  • Browsers and browser extensions

  • Printers and print drivers

  • Security, VPN, ZTNA, or endpoint agents

  • ODBC drivers, middleware, runtimes, and application dependencies

Confirm the FSLogix version and configuration

Confirm that the Windows 11 image has a supported FSLogix version, and that the intended FSLogix profile configuration is applied to the new host pool. In Nerdio Manager, this configuration can come from a reusable FSLogix profile, a host pool profile, or a per-host-pool customization. For details, see FSLogix settings and configuration, Manage host pool profiles, and FSLogix per-host pool customization.

Confirm storage access and permissions

If the Windows 11 host pool reuses the existing profile containers, the new session hosts must be able to resolve and reach the same storage path, and users must have the required access. Validate:

  • Share permissions and NTFS permissions

  • Storage firewall or private endpoint rules

  • DNS

  • Identity configuration

  • The configured VHDLocations or Cloud Cache path

Avoid concurrent profile access

Important

Don't intentionally allow a user to keep active sessions in both the Windows 10 and Windows 11 host pools when both pools use the same single-user FSLogix profile container. Have the user sign out of the old session before you test or move them to the new host pool.

Decide whether to reuse or replace the profile path

Use the following comparison to decide whether the Windows 11 host pool should reuse the existing profile path or use a new one:

Reuse the existing profile path when

Create a new profile path when

The same user population is moving to Windows 11.

Existing profiles are bloated, inconsistent, or intentionally being reset.

The same identity model and storage backend remain in use.

The customer is changing the storage platform or identity model.

Profile continuity is the priority.

Pilot isolation, profile redesign, or a clean profile start is required.

Application and OS changes have been validated.

User data migration and communication are acceptable.

Migrate the users

Step 1: Document the current Windows 10 host pool

Record the current production configuration before you build the Windows 11 pool. This record becomes the comparison baseline and rollback reference. Capture:

  • Workspace and host pool name

  • Host pool type and image version

  • VM size, disk type, and disk size

  • Auto-scale, Start VM on Connect, and session limit settings

  • RDP properties

  • FSLogix profile source and storage path

  • Cloud Cache configuration, if you use it

  • Application delivery method

  • Published desktops or RemoteApps

  • User and group assignments

  • Intune policies, GPOs, scripted actions, tags, monitoring, and alerts

Step 2: Prepare the Windows 11 image

Create, clone, import, or update a Windows 11 image in Nerdio Manager. For details, see Clone Desktop Images, Refresh desktop images from the Azure Marketplace, and Management and lifecycle tasks for imported desktop images. Validate the image before you assign it to production. Check:

  • First sign-in

  • FSLogix profile attach

  • OneDrive sign-in and sync behavior

  • Outlook profile behavior

  • Teams launch and meeting join

  • Browser launch and extensions

  • Printing

  • Primary LOB application workflows

  • Security agent status

  • AVD agent status

  • Intune enrollment or policy application, where applicable

Step 3: Create the Windows 11 host pool

Create a new Windows 11 host pool and select the validated Windows 11 image. For details, see Create dynamic host pools. Apply the appropriate FSLogix configuration. Where possible, use a host pool profile to reduce manual configuration drift. For details, see Manage host pool profiles.

If you need profile continuity, confirm that the selected FSLogix profile points to the same validated storage location that the Windows 10 host pool uses.

Step 4: Configure pilot assignments

Create a pilot group that represents real workloads. Start with a small group, and expand after validation. Include:

  • IT administrators and help desk

  • Power users

  • Users of critical LOB applications

  • Users with heavy Outlook, Teams, or OneDrive usage

  • Users from each major department or role

Step 5: Validate profile behavior

Have pilot users sign out of the Windows 10 host pool before they sign in to the Windows 11 host pool. Validate that the expected profile attaches, and that user settings persist after sign-out and sign-in. Confirm that:

  • The expected desktop and profile data are present.

  • Documents and known folders are available.

  • OneDrive starts correctly.

  • Outlook and Teams launch correctly.

  • The user doesn't receive a temporary profile.

  • The profile container isn't locked by another session.

  • Logon times are acceptable.

Step 6: Validate applications and the user experience

Track application validation separately from profile validation. A successful FSLogix attach means that the profile loaded, not that every Windows 11 application workflow is ready. Use the following categories to classify issues:

Issue category

Examples

Image issue

Missing dependency, outdated app, incorrect agent, bad default setting

FSLogix issue

Wrong path, profile lock, temporary profile, version mismatch

Application issue

Windows 11 compatibility, missing plugin, bad installer behavior

Policy issue

Different Intune or GPO behavior between pools

Storage or network issue

Latency, DNS, firewall, private endpoint, permission problem

Step 7: Move users in waves

Move users in the following waves:

  1. Wave 0: IT and help desk

  2. Wave 1: Friendly users or low-risk departments

  3. Wave 2: Standard users

  4. Wave 3: Power users and complex application users

  5. Wave 4: Remaining users and cleanup

Before each wave, confirm that no critical pilot issues remain, notify users, ask users to sign out of the old environment, and update assignments. During each wave, monitor sign-in, profile attach, application launch, and support tickets.

Step 8: Maintain rollback access

Keep the Windows 10 host pool and the previous image available through the approved rollback period. If a user must roll back, make sure they fully sign out of Windows 11 before they sign in to Windows 10. This reduces the risk of a profile lock.

Step 9: Retire or repurpose the Windows 10 host pool

When you retire or repurpose the Windows 10 host pool:

  • Remove old user assignments.

  • Disable or scale down the Windows 10 host pool.

  • Confirm that no active sessions remain.

  • Retain old resources through the rollback window.

  • Review profile storage after the migration.

  • Remove unused session hosts and images only after rollback is no longer required.

  • Update monitoring, documentation, and help desk procedures.

Common issues and remediation

Symptom

Likely causes

Recommended checks

Temporary profile

FSLogix isn't applied, incorrect path, permission issue, profile lock, or storage is unreachable.

Review the FSLogix logs, profile path, storage access, and file handles. See Troubleshoot FSLogix Profile Mount Errors.

Expected data is missing

The new pool points to a different profile path, or the user signed in with a different identity.

Validate VHDLocations, identity, and OneDrive Known Folder Move.

OneDrive or Outlook behaves differently

Different image, policy, cache, or Office configuration.

Validate Microsoft 365 Apps, OneDrive policy, and FSLogix settings.

Application settings don't follow the user

The application stores settings outside the profile or requires machine-level configuration.

Review application packaging and vendor support for Windows 11.

Best practices

  • Use a new Windows 11 host pool rather than upgrading pooled session hosts in place.

  • Pilot with real users before broad rollout.

  • Use the same validated FSLogix profile configuration when you need profile continuity.

  • Avoid concurrent sign-ins to different host pools that use the same single-user FSLogix profile.

  • Keep rollback access until the new pool is stable.

  • Validate applications separately from profile behavior.

  • Document each migration wave and user-impacting change.

Related articles

Need help?

Raise a support ticket for this item.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Related articles

Comments (0 comments)

Article is closed for comments.