Never done this, but it's should be straight forward. https://learn.microsoft.com/en-us/powershell/module/hyper-v/convert-vhd?view=windowsserver2019-ps https://learn.microsoft.com/en-us/answers/questions/314588/convert-existing-vhd-to-vhdx.html

I know this says HyperV but it's a microsoft technology VHDX,VDH https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831446(v=ws.11)

i thought i was missing something so thats why i asked.

do you use vhd or vhdx for your deployments?

But many years ago, 6 to be extract I did deploy VHD. But I stick to VHDX now.

Out of all the FSLogix guys out there, I would think someone has done this migration. It's no light task, for sure.

From how I understand it, and I could be wrong. I would setup another File share location. Use some sort of tool that can copy the Folder NTFS permissions that are a match for the destination. Example robocopy "source" "destination" /e /z /SEC /xf * Setup the GPO to the new location, Set VHDX in that setup. Make sure the share is setup too. Then take a couple of test users(could be created for the Test approach) use the " c:\Program Files\FSLogix\Apps\frx.exe migrate-vhd -src \\server_one\usrname\<username.vhd> -Dest \\server_two\username\<username.vhdx>" (never tested that personally) but a general Idea. Once migrated, have a test user login and see what happens.

I think you shared this before? I remember it, but I could not remember. But it’s awesome of you

Current script uses same path for both files. Have considered making changes to have a separate destination path, but never got round to it. If you need to use a different VHDX destination path, feel free to modify it, or just robocopy the VHDs to the new location before running it assuming enough space.