Forum Discussion
Convert UPD to FSLogix container
Roger Critz we will be starting a private preview for a PowerShell script to accomplish this. I will post the specifics here when available. The Private Preview will be for those moving from on-prem to WVD, which is the use case you describe. The current plan is for this PowerShell to ultimately move to an open source repo to be extended by the community. Thanks!
i was using the script that's listed in this forum post,
ive signed up for the private preview, ill wait for that before i move ahead.
Thanks for the reply !
The script I posted uses 2 settings that are not the default for FSLogix. Perhaps that explains your issue?
1) It uses a .vhdx suffix. The default that FSLogix tries to load on an RDSH is .vhd
2) It creates the folders using SAM_SID rather than the default of SID_SAM
In the script change it to .vhd and SID_SAM if you want to use the defaults that are configured with a basic install of the FSLogix app in an RDSH. If you want to use the defaults of .vhd and sid_sam then the parts you want are on lines 113 and 222 of the attached file.
The requirements in a .vhd* file itself for FSLogix are 2 things
1) Files are in "\Profile" rather than the root of the UPD.
2) A few registry keys for FSLogix. The script has code there to create the info and add to their registry
Attached is a more recent update that has an extra bit to not move files for a profile that fails to mount. The process to move and rename the UPD file itself is unmodified. I've used it to convert 500+ UPD .vhdx files from D:\UPD to D:\FSLogix\<SAM>_<SID>\.
There are lost files that are not found. I am not able to understand the exact causeracook
Is it possible for you to come on call, so that we can troubleshoot. It would be great help if you can
- racook
Microsoft
jerrywilkinson the log file will show why it didn't attach. %programdata%\FSLogix\logs\Profiles is where to look.
ive checked permissions, and everything matches to when a FSLogix VHDX gets created. ive even tried logging in so a FSLogix VHDX gets created, then renaming the converted one to match the newly created one and the same issue happens. FSLogix doesnt mount the VHDX it just creates a local user profile on the RDSH. im still digging into the issue adamsi175
"(The file exists.)" as in the file already exists that it would want to create? Can it not read it due to permissions? The computer AD account presumably has permissions to the share and parent folder. After running the conversion script if you then rename the file slightly and try to log in do you end up with a new file based on the template VHD or the DefaultUser for the RDSH and can use that file? jerrywilkinson
Thanks for the reply, originally i did change the defaults in the script to match my FSlogix GPO settings. It creates the new VHDX without any issues but when i try to login with the test user it doesnt attach the FSLogix VHDX , and i get the errors in the fslogix log
VirtualDiskAPI::CreateFormattedDisk failed to create vhd(x):
(The file exists.)
Status set to 9: Cannot create virtual disk
