Forum Discussion
Ongoing FSLogix Profile Issues
R_AkersI don't believe using an Azure file share is ready yet. We also use a dedicated Azure VM running the file server role and have an OS volume and then a separate Data volume where the profiles are housed.
Here are the reg keys we are using although we are doing full desktops and not remote apps.
jasonhand Thank you for the reply,
The registry currently looks like the below:
Could I ask how you perform your nightly reboots? Do you just use a normal scheduled task or an Azure Automation runbook?
- R_AkersApr 10, 2020Brass ContributorQuick question if you don't mind what VM are you using for your profile storage?
- R_AkersApr 10, 2020Brass ContributorThat might well be it. We have since put together a larger deployment and wen't straight to the D16sv3 and have had no issues like the previous one.
- R_AkersApr 10, 2020Brass ContributorThe experience with Microsoft support was slow and tedious however what does seem to have stabilised it considerably was increasing the resources. I swapped from a B8MS although the resource usage seemed fine and I was accruing plenty CPU credits to a D8 and the issue seems to have gone away,
I'm not sure if this is a coincidence or not, could I ask what VM size you are using? - DP305Mar 02, 2020Copper Contributor
Hey,
Did you get any reply from Microsoft on your issues? We seem to be having the same problems aswell..
- R_AkersFeb 21, 2020Brass Contributor
Hi Jason,
Thanks for checking in, i'm still having a few issues but i'm currently trying to deal with the hell that has become Microsoft support... Its been a month with them and they have been of little help beyond suggesting enabling concurrent sessions on a test account...
Once I get a bit of an update I'll post it here .
- jasonhandJan 24, 2020Brass Contributor
R_AkersThe nightly reboots are handled through a Powershell script that runs from the Azure AD controller. It looks up the pool members by -like {name*} and then uses test-connection to verify each is online before issuing the reboot. Has been working well.
We use scaling sets so this lookup then returns only those that are present since it creates different named instances whenever they are scaled down then back up.
If yours are static a simple remote reboot would work and you can log it into a file as well to keep track of it.