We are currently attempting to migrate Roaming Profiles to FSLogix Profile Container Profiles utilizing the following the instructions provided here:
https://www.christiaanbrinkhoff.com/2020/02/14/youtube-how-to-migrate-from-upd-to-fslogix-profile-container-profiles-to-windows-virtual-desktop/
Convert-RoamingProfile
Convert-RoamingProfile -ParentPath <String> -Target <String> -VHDMaxSizeGB <UInt64> -VHDLogicalSectorSize <String> [-VHD][-IncludeRobocopyDetail] [-LogPath <String>] [-WhatIf] [-Confirm] [<CommonParameters>]`
Our user roaming profiles are stored on the Domain Controller @ \dc\rdsprofiles$\ - however, profile folders are: <username>.domain.v6. This inherently causes issues using that command as it results in the following error:
"Profile \dc\rdsprofiles$\fstest3.domain.v6 Could not resolve to AD User. Cannot copy."
What I've done to get around this is grant ownership and full permissions on the user's v6 folder, copy it to a temp location, rename it (remove "domain.v6") then copy it back.
Convert-RoamingProfile -ParentPath \dc\rdsprofiles$\user -Target \fileserver\profile_containers$\ -VHDMaxSizeGB 100 -VHDLogicalSectorSize 512 -IncludeRobocopyDetail -Verbose -LogPath C:\Temp\LogixConversion.log
This works for the most part, except for by the end of the script where it mounts the converted .vhdx to then apply NTFS permissions and subsequently fails...
If that user were then to login, nothing works for them (browsers, start menu, any apps, etc). I can go and mount the .vhdx and apply the permissions myself but there's no way we can do this manually for 300+ users (and I haven't given scripting that a thought yet).
I can provide any further details if needed.