Troubleshooting Session Slowness Complaints on RDS server

Posted by EmicationLikely@reddit | sysadmin | View on Reddit | 10 comments

We have a pretty new RDS server at a clients that will eventually be supporting about 12 simultaneous users. We currently have 3 users on the server and are getting slowness complaints. This is a Hyper-V VM and is currently the only VM on the host. Both the host and the VM are running Server 2022 (currently at 21H2). The specs on the host (Dell R940) are: * 4 x Xeon Gold 6140 (72 Cores total) * 1.1TB RAM * 2 x 2TB SSDs in RAID1 for OS drive (800GB free) * 6 x 4TB SSDs in RAID10 for Data drive (where the redirected user folders are) * 4 x 25Gb Mellenox NIC, using 2 ports bonded for 50Gb to the main aggregation switch * No graphics card The specs of the RDS VM are: * 180GB OS drive (130GB free) * 9TB Data drive for the redirected user folders (8.75TB free) * 40 processor cores assigned (average usage 8%, spikes to 12 or 15%) * 800GB RAM assigned (average usage 30-40GB) * NIC usage 300-600Kbps average, haven't really seen spikes above that Only the RDS session host and Licensing roles are installed - No connection broker, RD Gateway or session collection. This is a run of the mill business - Outlook, Word & Excel are the main apps, plus a couple of SQL LOB apps (Separate AppServer for SQL is a VM on a different physical host with a 20Gb connection to the aggregation switch). There are about 40 employees total, with a dozen remote workers. The office has 800Mbps fiber connection (so up and down) and a Sonicwall TZ500 at the edge. A speed test on the RDS server just now showed 660 down and 620 up. The only adjustments I've made in the GP for Remote Session Environment is to limit the number of monitors available to 2. All 3 current users have dual monitors on the machines they use to connect to the server. I have considered getting a graphics card, but that's a project and don't want to go down that path without some obvious diagnostics pointing to that as a need. With these specs, this thing should NOT be slow, IMO. Since I see no resource bottlenecks, how can I troubleshoot these complaints?