This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 81%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGH%3C/text%3E%3C/svg%3E)
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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 30%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
Hi,
Could you please clarify more about how you migrate the VHDx file? Are you using the way mentioned in below two links or any other way to expand the FSlogix VHDx size.
How to resize the current VHD(x) in FSLogix
Expanding an FSLogix profile disk
I've successfully migrated all but one subject VHDx
What do you mean by "subject VHDx"?
Does the issue occur on one user or all users whose profiles have been migrated?
What if we move back the VHDx files?
Thanks,
If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.
Hello!
I am expanding VHDx using frx.exe -migrate-vhd method: frx.exe migrate-vhd -src \\<file-server>\<disk path>\Profiles\<username>\<username-SID>\OLDProfile_<username>.vhdx -dest \\<file-server>\<disk path>\Profiles\<username>\<username-SID>\Profile_<username>.vhdx -size-mbs=61440 -dynamic=1
This has worked well for all users but one. I also tried with two versions of frx.exe - the 2004 version and the most recent 2009 HF_01. Both versions produced a VHDx that errored out as described.
If I rename the files and use the original VHDx, all logins work as desired. That's what we're doing now to keep the user running.
I'm researching into VHD analysis to see what parameters might be different between the two disk instances.
Thanks!
Hi,
Since only one user has the problem, how about comparing the parameters between the problematic user's and other normal user's VHDx file for both original and new ones.