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

BBoozer1968, I appreciate the inherent problems with "Insider's Preview" in a production environment. There are work arounds that can be employed, however they cause issues with performance and they have to be applied each time the user logs in, especially for those using non-persistent VDI solutions. 

Relating to getting a standalone patch, this is something that would require a case being opened with the Windows Operating system team directly. The FSLogix team does not have direct access to request this on your behalf since it is a completely different team. 

You are correct, we have seen a sharp increase of cases on the FSLogix team relating to this issue and while this is actually an underlying issue in the Operating System, the FSLogix Engineers do have two workarounds that I have starting last week asked them to discuss with customers as viable options. 

We are also currently receiving numerous cases around OneDrive and credential prompts. This is a result of multiple unique session IDs being created which OneDrive currently does not support. While the underlying issue is with OneDrive's ability to support the configuration, I am actively encouraging my team to work with the customers to see if we can help a "best practice" on how OneDrive can be configured with the product. If you are facing this issue, I encourage that you engage a case directly with OneDrive. Please make sure the description is about "multiple unique session IDs". This will help ensure proper focus is placed on your case and you are not transferred back to the FSLogix team.

Final note, we have discussed this forum with the owner, he wanted to discuss that this article was designed for a "Preview" release. While it is only a few months old, we are no longer in "Preview", which means in the current versions this article no longer applies. The team that built this article is currently creating an updated article to be released. Many of the items in this article that did not work have reportedly been resolved. For customers that open cases with us relating this article, we will not be able to resolve this specific article, but will work diligently to resolve individual issues and ensure the updated article does not contain the same issues.

Thank you for your patience.