Azure wvd- fslogix

Question

how can we monitor several WVD Hosts that have several FXlogix User profiles where their .vhdx file size keeps growing even though there aren’t much files or software’s installed in the profile. We tested a redirection.xml gp policy to excludes teams data on a specific WVD Pool however it only worked when deleting the current profile. We will need more findings on how to clear the current storage growth issues on fxlogix profiles without deleting the existing user fxlogix user profile .vhdx file.

Answer 1

Can you please share what kind of storage are you using for the user profiles Vhdx files?

In terms of overall profile size, limitations or quotas for FSLogix depend on the storage type used for the user profile VHDx files, as well as the size limitations of the VHD/VHDx format.

For network bandwidth, depending on the type of utilization it is recommended to plan between 5 and 30 MbPS per user.

Requirements can vary widely depending on the user, applications, and activity on each profile, so your actual usage may vary significantly from what is listed here. The table uses an example a single user. Use this to estimate requirements for the total number of users in your environment. For example, you may need around 1,000 IOPS (input/output operations per second) for 100 users, and around 5,000 IOPS during sign-in and sign-out, if a large number of users login during a short period of time creating a login storm.

Storage options for FSLogix profile containers
Azure offers multiple storage solutions that you can use to store your FSLogix profile container. We recommend storing FSLogix profile containers on Azure Files or Azure NetApp Files for most customer scenarios. The article Storage options for FSLogix profile containers in Windows Virtual Desktop compares the different managed storage solutions Azure offers for Windows Virtual Desktop FSLogix user profile containers.

Storage spaces direct (S2D) is supported in conjunction with FSLogix and Windows Virtual Desktop as well. It is a self-managed storage solution that is out of scope for this article. Customers can get most value out of either Azure Files or Azure NetApp Files while simplifying management of Windows Virtual Desktop.

Best practices
The following are general best practices for FSLogix profile containers:

-For optimal performance, the storage solution and the FSLogix profile container should be in the same data-center location.
-Exclude the VHD(X) files for profile containers from antivirus scanning, to avoid performance bottlenecks.
-We recommend to use a separate profile container per host pool, while having two active sessions.

Here is a very detailed document on FSLogix for the enterprise, storage options and performance: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/wvd/windows-virtual-desktop-fslogix#performance-requirements

This document should be able to help you make decisions on the storage side.

For monitoring, please refer to this document:
https://learn.microsoft.com/en-us/azure/virtual-desktop/azure-monitor#install-the-log-analytics-agent-on-all-hosts

Please let me know if you have further questions.