Good afternoon!
We're running FSLogix in a customer's small Server 2019 farm. Some of the users are nearing or hitting the 30 GB default VHDx size limit. I've successfully migrated all but one subject VHDx; that one has two results, depending on the session server.
The migration completes successfully, according to the result from the command line. However, when we log in to RDS1, the doesn't mount and FSLogix creates a new, local profile. On RDS2, the profile fails to attach with an unknown error. The original VHDx mounts fine in either server.
I'd like to fix the VHDx so we don't have to go through saving files and recreating the profile from scratch. Does anyone have guidance on inspecting and perhaps fixing these VHDs in an FSLogix environment?
Thanks!
Gregg