How can I migrate local user profiles to Azure Files and FSLogix?

You can migrate local user profiles to Azure Files and manage them with FSLogix. This enhances performance, scalability, and reliability of user profile management in cloud environments.

Overview

Migrating local profiles to Azure Files and managing them with FSLogix provides a scalable, reliable, and high-performance solution for user profile management in cloud environments. This guide outlines various strategies and tools to facilitate migrations, from small-scale to complex enterprise scenarios.

With careful planning, automation, and best practices, organizations can minimize downtime and enhance user experience during the transition. Choosing the right approach depends on your organization's specific needs and infrastructure.

As cloud technologies evolve, regularly updating migration strategies and troubleshooting methods is crucial for maintaining efficiency and addressing new challenges. By following these guidelines and staying informed about new tools and best practices, organizations can ensure secure, accessible, and well-managed user data.

Consider the following migration methods:

• Method 1: Migrate local profiles using the FSLogix command-line utility

• Method 2: Migrate local profiles using the FSLogix migration PowerShell module

• Method 3: Migrate local profiles using the SharePoint Migration Tool or other third-party tools

• Method 4: Migrate specific datasets

Prerequisites

Ensure the following prerequisites are met.

Preparation and assessment

• Verify that you have proper backups of your data. A fallback option is crucial in case something goes wrong during the migration process.

• Evaluate the current local profiles and determine the requirements for the migration.

• Confirm that Azure File storage is properly configured to handle profiles, with considerations for redundancy and access permissions.

Azure Files setup

• Create an Azure Files share to store FSLogix profile containers.

• Configure the share with appropriate network access and security settings. For details, see Manage Azure Files shares.

• Ensure the Azure environment is properly set up for SMB connections, which are required for FSLogix.

For more details, see What Are Azure Files and FSLogix Profile Storage Options?.

FSLogix configuration

• Install and configure FSLogix on all user systems being migrated. This includes setting up the FSLogix agent to redirect user profiles to the Azure Files share.

• Configure FSLogix rules and settings based on your organization's needs, such as redirections, permissions management, and performance optimization.

For more details, see FSLogix settings and configuration.

Tools and scripts

When migrating local profiles to Azure Files, consider using the following tools and scripts:

• Using the built-in FSLogix command-line utilities: The built-in FSLogix command-line utilities offer a solid solution for profile migration. However, the current documentation does not cover bulk actions. The frx copy-profile command is designed for migrating a single profile and should be incorporated into proper scripting for automation. When using this tool, a best practice is to set the RobocopyLogPath registry key. For details, see FSLogix Configuration Setting Reference.

  Registry Hive: HKEY_LOCAL_MACHINE

  Registry Path: SOFTWARE\FSLogix\Logging

  Value Name: RobocopyLogPath

  Value Type: REG_SZ

  Default Value: None

  Specifies a log file name and path where the output of the robocopy commands (for example, during mirroring of data in or out of a VHD) are stored. If the value is nonexistent, then the robocopy results aren't logged at all. This setting is recommended for troubleshooting only.

  Example Value: C:\NMM\Logs\FSLogixRoboLogs.txt

• FSLogix migration PowerShell module: This PowerShell module is actively supported and maintained, providing a reliable way to convert user profiles and UPD disks to FSLogix containers.

  Note: This module is a fork of the Microsoft FSLogix Migration Private Preview Module (linked below).

• Microsoft FSLogix Migration Private Preview Module: This is a script maintained by Microsoft engineers. When downloading the module, follow the steps outlined in the ReadMe document.

Scenarios

When migrating profiles, consider the following scenarios:

• Scenario 1: Migrating local machine profiles to Azure Files with FSLogix.

• Scenario 2: Migrating profiles from an on-premises file server to Azure Files with FSLogix.

• Scenario 3: Migrating User Profile Disks (UPD) from an RDSH environment to FSLogix.

Method 1: Migrate local profiles using the FSLogix command-line utility

For smaller-scale migrations, such as when migrating only a handful of profiles, FSLogix frx copy-profile command offers a straightforward alternative, especially if you're less familiar with PowerShell. Ensure FSLogix is installed on the machine where the command will be executed.

For guidance on installing FSLogix on machines that aren't managed in Nerdio Manager, see Install FSLogix Applications.

To migrate a user profile using the FSLogix command-line utility:

1. Open PowerShell as Administrator.

2. Navigate to the FSLogix Apps directory: cd 'C:\Program Files\FSLogix\Apps'

3. Run the following command to copy and configure the profile:

   frx copy-profile -filename C:\Profile.vhdx -username CONTOSO\msmith -size-mbs 30000 -dynamic 1 -verbose

   This command completes the following tasks:

   • Saves the FSLogix profile container as C:\Profile.vhdx.

   • Converts the domain profile for user CONTOSO\msmith.

   • Sets the VHDX file to dynamic, allowing the disk to automatically resize up to 30GB.

Method 2: Migrate local profiles using the FSLogix migration PowerShell module

This migration approach is typically preferred for larger environments due to its automation capabilities, which help reduce human error and improve efficiency.

Main functions

• Convert-RoamingProfile: Converts a roaming profile to an FSLogix profile container.

• Convert-UPDProfile: Converts a User Profile Disk (UPD) to an FSLogix profile container.

• Convert-UPMProfile: Converts a UPM profile to an FSLogix profile container.

  Note: UPM conversion has undergone minimal testing in small environments.

For details and troubleshooting guidelines, see FSLogixMigration repository on GitHub.

Syntax and examples

For more information about what syntax switches are supported, see FSLogixMigration repository on GitHub.

Method 3: Migrate local profiles using the SharePoint Migration Tool or other third-party tools

For larger-scale migrations, especially when dealing with multiple users and complex environments, migration tools like the SharePoint Migration Tool (SPMT) or similar third-party tools can be beneficial. These tools offer advanced features for managing user profiles, including scheduling, reporting, and error handling.

Microsoft provides detailed guidance on using SPMT for migrating user profiles to Azure Files or Microsoft 365 (M365). For details, see Overview of the SharePoint Migration Tool (SPMT).

Other third-party tools:

• MigrationWiz: A popular migration tool that supports a wide range of migration scenarios, including user profile migrations to Azure Files. MigrationWiz offers advanced features for managing large-scale migrations, such as scheduling, reporting, and error handling.

  For details, see:

  • BitTitan MigrationWiz

  • MigrationWiz YouTube video series

• AvePoint Fly: Offers advanced features for managing large-scale migrations, such as scheduling, reporting, and error handling.

  For details, see:

  • AvePoint Fly

  • How to Fly YouTube series

Method 4: Migrate specific datasets

When migrating user profiles to Azure Virtual Desktop (AVD), considerations vary based on the number of users and the specific data involved. In some cases, starting with a fresh profile may be beneficial, especially when deploying a new AVD environment. This approach is commonly favored by MSPs and IT teams.

Consider the following options:

• File migration to OneDrive: For user data such as documents, images, and desktop files, migrating to OneDrive is efficient. Use migration tools to transfer this data in the background, then perform a final delta sync on migration day to ensure all files are available when users sign in to their new AVD desktop.

• Browser settings migration: Automate the backup and migration of browser settings. A common practice is setting Microsoft Edge as the default browser, transferring settings from the previous browser, and enforcing Entra SSO sign-in. This ensures that browser settings are synchronized with the user’s profile. Enable Enterprise State Roaming in the Entra portal to support this process.

• Email signatures: Instead of relying on manual email signatures, consider a managed solution like Exclaimer Cloud to simplify signature management. Alternatively, guide users to configure signatures in Outlook on the web, allowing them to roam with their Microsoft 365 profile.