A while back I was looking for a way to convert the VHD file to VHDX format. We had a situation where the initial build of FSLogix was using VHD files as we did not change the Group Policy to use VHDX. I found this article that refers to the FSLogix Utility FRX.EXE.
https://www.vcloudinfo.com/2020/07/best-ways-to-shrink-and-optimize-fslogix-profile-vhd-files.html
In the blog is states you can migrate a large container to a smaller size. So for example we have some 30Gb containers but can migrate the contents to a smaller size. This go me thinking, “Can I migrate a VHD to VHDX?”
I decided to test. As you can see we have a FSlogix profile for test account jbond. It is a VHD file…..
Based on the syntax in the article I applied it to the Test profile jbond….
PS C:\Program Files\FSLogix\Apps> .\frx.exe migrate-vhd -src \\<FileServer>\Profiles\FSLogix\jbond\W10St andard\jbond_S-1-5-21-839522115-682003330-2147125571-227461\Profile_jbond.VHD -Dest \\<FileServer>\Profi les\FSLogix\jbond\W10Standard\jbond_S-1-5-21-839522115-682003330-2147125571-227461\Profile_jbond.VHD
|
As you can see it executed but had an error message. I cannot find what the error message means….
that said, I looked in the path and found that we had in fact created a VHDX file.
Once the file is created you have to grant the user access and full control…
Then grant them ownership….
Testing
I needed to apply a GPP or a reg hack so not to disrupt the production GPO that defined the VHD extension. So in the PVS gold image I applied the hack to use VHDX files to our test based on ….
https://docs.microsoft.com/en-us/fslogix/profile-container-configuration-reference
HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles
I logged in and the VHDX profile worked….
To be sure I had all the previous settings…background picture, small taskbar and desktop icons….
.\trevor