Migrate FSLogix Profiles to a new Region

Dave Stephenson 56 Reputation points
2023-02-15T20:22:30.18+00:00

Because of the lack of available resources in the West US 2 Region, we're needing to move our AVD environment to a different region.

We've been able to migrate everything except the FSLogix Profile disk(s).
When we try to logon after migrating the profile disk, users are getting either Cannot open virtual disk or Cannot find virtual disk at the provided location errors.

As far as I know, we're not doing anything non-standard.
We're using Microsoft Documentation to move the Storage Account and Azure Storage Explorer to move the profiles.

Has anyone been able to successfully migrate FSLogix storage to a new region?

User's image

User's image

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,104 questions
Azure
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
1,164 questions
Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,517 questions
FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
488 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Stephenson 56 Reputation points
    2023-02-15T21:58:50.6433333+00:00

    I believe I was able to find the issue.

    It looks like Azure Storage Explorer isn't copying the SMB permissions when it's doing the copy.
    I found THIS blog post that talks about using the --preserve-smb-permissions=true parameter with AzCopy.

    When I used Azure Storage Explorer to generate the command for me, added the --preserve-smb-permissions=true to the command and ran the AZCopy command manually, it made the error go away.

    Granted, I could have started by writing the AzCopy command from scratch, but where's the fun in that? 🤦‍♂️User's image

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.