Forum Discussion

Roger Critz's avatar
Roger Critz
Copper Contributor
Oct 22, 2019
Solved

Convert UPD to FSLogix container

We are wanting to move our users from RDS to WVD without losing or redoing the the profiles. Is there a way to convert the traditional RDS UPD profile (VHD) to a FSLogix profile container (Would like...
  • Doug_Coombs's avatar
    Doug_Coombs
    Oct 29, 2019

    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!

jerrywilkinson's avatar
jerrywilkinson
Copper Contributor
Dec 06, 2019

Doug_Coombs yes ive gone through all of that, and our FSLogix settings are correct. the errors im seeing are:

 

VirtualDiskAPI::CreateFormattedDisk failed to create vhd(x):

LoadProfile failed. User: ndtest. SID: S-1-5-21-4174114073-886831968-143637270-1216. (A device attached to the system is not functioning.)

 

i think there is an issue in the conversion process, it creates the new VHDX but if i try to mount it with the FSLogix Mount tool i get errors related to permissions. but ive compared the permissions to a new FSLogix container VHDX and they are the same. So just scratching my head on the root issue 

Doug_Coombs's avatar
Doug_Coombs
Icon for Microsoft rankMicrosoft
Dec 06, 2019

jerrywilkinson Sorry if these are remedial questions, but I need to understand the scenario.

 

1- I assume that the user can manually mount the VHDX, from the same machine as is being used for FSLogix, and traverse?

2- What is the result of the error, a new VHDX, temp profile, local profile, etc?

3- What process did you use to convert?

 

Thanks!

  • jerrywilkinson's avatar
    jerrywilkinson
    Copper Contributor
    Dec 06, 2019

    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 ! 

    • adamsi175's avatar
      adamsi175
      Copper Contributor
      Dec 09, 2019

      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>\.

       

      jerrywilkinson 

      • jerrywilkinson's avatar
        jerrywilkinson
        Copper Contributor
        Dec 09, 2019

        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

         

        adamsi175 

Resources