This is also done by OSOT, so disable that from there.Īlso are you also running Vmware App Volumes ? Because there are things you have to make sure are excluded from the snapvol.cfg when using FSLogix. Make sure you do NOT have these services disabled (These are VERY important):Īre you removing apps using Remove-AppxPackage and Remove-AppXProvisionedPackage. I had this issue also, but I went through a lot (which I will list below), to get it to work. Don't know if you are using FSLogix CCD or just VHD Location, butĪparently there have been a lot of bug fixes to the CCD side of it, so should be working better now.Īlso make sure the remote volume you are putting the VHDX files on is a formated ReFS volume. We put the main site first in each GPO, you probably don't have to but I am pendantic). We have GPOs specifically just for FSLogix on a per site basis (mainly because of the CCD Locations. May conflict with what you are trying to implement in Horizon. Also try with limited GPOs and maybe split out GPOs to be Horizon specific, as this environment will behave differently to a physical one and settings from a physical setup
Worth checking what GPOs you have in place, because there may be some there that are causing this type of behaviour.ĭefinitely have a look at the techzone document and build a new one from scratch. He had for the apps (Like putty, chrome, winscp. So if we ever have to remove a corrupted profle the user does not lose the settings It purely just makes copies of the settings users have on their Os/desktops and profiled applications. Our setup of DEM will not affect the availibility of apps on an OS. We disabled them initially, but have enabled them back again as they are needed. There is also a document on vmware tech zone for optimising and image which is excellent (just be careful if you are using App Volumes also - do NOT add the devices.hotplugĭo not disable those two Services. The tool is fantastic and really speeds up the VM. I would not recommend stopping use of OSOT. We also run DEM for application and desktop/OS profiling (gives resilience when a profile needs to be deleted if it gets corrupted). We are running 1909 with the latest FSLogic Agent. Since doing all three of these all the apps have come back. As a result packages only installed on first login (profile creation), butĪlso the following services had been disabled (which we enabled once again): What had happened is we mistakenly excluded C:\Users\\AppData\Local\Packages from the FSLogix profile using a Redirections.xml file.
0 kommentar(er)
