Hey All, trying to figure out a mystery here.
Horizon 7.13. Windows 10 20H2. Have a file share on Server 2019. FSLogix 2.9.7654.46150
Currently setting FSLogix via local policy/regedit. In HKLM\Software\FSLogix\Profiles I have the following:
Enabled: 1
NoProfileContainingFolder: 1
SetTempToLocalPath: 3
VHDLocations: <file share path>
VolumeType: VHDX
I create an instant clone pool. If I set it to be a desktop pool and log in it creates my profile VHDX and works as expected. Logging out and back in unmounts and remounts the profile VHDX as expected.
If I set the pool to be an application pool, then publish an application (in this case Google Chrome pointing at a specific URL), if I log in without an existing FSLogix Profile a profile VHDX gets created, but it isn't used. On subsequent logons it is marked as corrupted and a new VHDX is created then not used. In the FSLogix logs it shows the equivalent of:
- No profile disk found
- Creating the profile disk
- Formatting the profile disk
- Successful
- Unmounting the profile disk
- Mounting the profile disk
- Unable to read the profile disk
- Create a local profile
If I look at the share with an admin account the VHDX is created, then gets to a files size around 167MB and never gets any larger. When configured as a full desktop it grows larger than that.
If I have the pool set to Desktops & Applications, and sign into the desktop first, then loading the published app also uses the existing VHDX successfully.
So it appears that only when in published application mode creation of FSLogix profiles are failing. Has anyone else come across this and found a solution?
