Hello Top Notch People,

I’ve got a virtual terminal server 2008 R2 that we P to V in April 2022. It’s been working flawless for the last few months until this week. We have twenty three different properties that have four Users’ at each property that connect to this virtual terminal server. So there’s probably some extra people that also access this virtual terminal server. Lets say 100 to 105 users’

The virtual terminal server itself has the following specs:

  1. CPU AMD EPYC 7313 16-Core Proc 2.99 GHz

  2. Memory- 32 GB

  3. just over 300 GB of hard drive space

The server has Office 2016 installed on it.

The problem, is that the last three consecutive days in the afternoon. This terminal server has had Outlook 2016 become non responsive for a whole bunch of the users’. There are some users’ that can’t log into it the server when its like this. Other users have issues printing. The only thing that seems to resolve people not accessing Outlook 2106 is to restart the server. After restarting the server, ten to fifteen minutes later, users’ are able to log back in and Outlook is back to normal.

I know it’s not our “on-prem exchange server” because I can log into the virtual terminal server as one of our user’s and access OWA w/out any issues.

Any suggestions as to why keeps making this virtual terminal being unresponsive?

12 Spice ups

What’s the storage media? It should be running on SSD.

Windows 2008 R2 at this point should be considered a major security risk. I wouldn’t want it on my network.

3 Spice ups

This virtual terminal server is on a SAN host, which all have SSDs in it.

Are all the applications installed with Terminal Server mode 9MS Office, Browsers, Printers) ?? As in “Change user /install” then installation then “change user /execute” ?

How many users as 32GB RAM seems very low for 5 user TS sessions (OS need approx 8-12GB, then each of the 5 user session have at most 4GB RAM) ? Where are the user profiles saved ?

What hypervisor ?

How many VNICs assigned to the VM ?

Even if the host or SAN is using SSDs…how many VMs are running ?

We had similar issue, we just schedule restart in the morning and all working fine, thinking our issue was memory leakage and applications and users not logging off correctly…