Getting started with FSLogix profile containers on Azure Files in Windows Virtual Desktop

sarahpotrick2573 The VHDs are not mountable (I tried right from the beginning). While I am no FSLogix expert (and neither is the support team from my experience so far), my observations are that the profiles sync locally over time, and as as user is or does log out, it syncs back to the VHD and removes the local files to keep disk impact at a minimum. That being said, you will now want to undo everything you have done for FSLogix. I'm sure you missed my earlier post. It turns out, it is not yet capable of properly functioning in a Windows 10 environment. It is not FSLogix, but instead modern apps that they began pushing with Windows 8.1. They are not capable of running in a roaming profile. What eventually ends up happening is it breaks the profile, and causes a new one to be started every time. Any local user customization are lost and the profiles stop syncing back to the VHD. It won't be obvious at first. It was almost 3 weeks before a user reported it to us, and then we saw one by one, they were all breaking, as I checked the VHDs and saw that many had not been written to as long as 3 weeks earlier. Microsoft is currently working on a fix for the OS, but there is no timeline on it. To be clear, NO roaming profile solution will work. Our current solution was to disable the service in production and keep the secondary server in the hostpool turned off (as you cannot control availability in a multi-server hostpool, and users would need a configured profile on either machine). I still had my test environment up, and it has been converted to prod, and I am split assigning users. If you need the multi-server to work, you can copy the profiles and Profile list registry entries to the other server to make sure all current users have a profile on both (I have tested with a single profile and this did work).