Forum Discussion
R_Akers
Jan 13, 2020Brass Contributor
Ongoing FSLogix Profile Issues
Hi, We have recently gone live with a WVD setup of 2 Session hosts using FSlogix's profiles on an Azure File Server VM. It's not a massive deployment. Maximum of 38 users with general usage ...
jasonhand
Jan 13, 2020Brass Contributor
R_AkersCan you post what registry keys you have under your FSLogix/Profiles reg key? There are several that should be considered here. Also, are you just using the profile container VHD or are you using the Office container?
R_Akers
Jan 13, 2020Brass Contributor
- knowliteJan 13, 2020Iron ContributorHi,
Can you tell me which FSLogix agent version you are using (I suppose the latest version?)
Which type of disk are you using for the profile storage on the Azure VM?
Any reason you added the DisableRegistryLocalRedirect entry?
Can't seem to find this in the current documentation but I found that it idd may help with stability.
Which Windows 10 version did you deploy?
I deployed an environment of similar size last year and they are working fine.
We could go over the environment together to find the differences.- R_AkersJan 13, 2020Brass Contributor
knowlite Thanks for the reply:
Can you tell me which FSLogix agent version you are using (I suppose the latest version?): I've just updated to 2.9.7237.48865 after reading this post https://techcommunity.microsoft.com/t5/windows-virtual-desktop/workaround-for-non-responsive-windows-10-enterprise-multi/m-p/1017828
I can't remember what it was on prior but I did update it a few weeks ago when we first started having issues. I'll see if I can find out.
Which type of disk are you using for the profile storage on the Azure VM?127gb Premium SSD
Any reason you added the DisableRegistryLocalRedirect entry?
Can't seem to find this in the current documentation but I found that it idd may help with stability.I read somewhere that on Win 7 or over you can add DisableRegistryLocalRedirect and set it to 1 to force FSLogix to keep the NTUSER.dat and associated files in the profile container. Its apparently used to reduce profile corruption.
Which Windows 10 version did you deploy?It's currently running Windows 10 Enterprise for Virtual Desktops 1903 It was the deployment package if I remember right with O365 Pro Plus from the market place.
I deployed an environment of similar size last year and they are working fine.
We could go over the environment together to find the differences.- knowliteJan 13, 2020Iron ContributorAre you using an 127GB SSD to house 38 profiles? That is like 3.3GB average per user, isn't that kinda small? Hower this is not the cause of your issue I think.
Do I understand correctly that you updated your FSLogix agent just now after reading the post above?
What is the exact experience, do users get an error message or can't they login at all?
Did you also disable the BrokerInfrastructure scheduled task from the post above?
schtasks /change /tn "\Microsoft\Windows\BrokerInfrastructure\BgTaskRegistrationMaintenanceTask" /disable