Forum Discussion
Ongoing FSLogix Profile Issues
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
Are 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.
It is but storage is ok at the moment. They are using it primarily to access a couple of applications rather than storing large amounts of data.
Do I understand correctly that you updated your FSLogix agent just now after reading the post above?
That's correct
What is the exact experience, do users get an error message or can't they login at all?
Either they log in with what looks like a local profile despite the reg keys or they get a message advising the fslogix profile container is unavailable. the messages I see in the FXtray app is below
Did you also disable the BrokerInfrastructure scheduled task from the post above?
schtasks /change /tn "\Microsoft\Windows\BrokerInfrastructure\BgTaskRegistrationMaintenanceTask" /disable
I did just this morning.
- Please give feedback end of the week while testing the latest version, looking forward to the results!
Are your users working in a full desktop environment on WVD or launching Remote Apps?
I've seen this error when trying to launch a remote app when another app is already using the FSLogix profile.- I will do. I'm hoping desperately this resolves it! Thnk you for helping.
It's a Remote App setup. These error messages seem to happen when it's trying to sign the user in. So after a week of everything running pretty smoothly with one session host. Something happened over the weekend that has sent it off in a huff again.
Its seems to be working after a reboot of the profile server. Logs below:
From what I can see so far there was no issues with the domain controllers over the weekend.
- Again after running fine for a few days the fslogix service seems to have randomly stopped. I'm looking to see if I can find a reason now. The unreliability is really starting to cause issues.
