Posted by Barbara Brazil on April 08, 2014 at 14:44:02:
In Reply to: CAW Terminal Services posted by Doug Pegg on April 07, 2014 at 15:27:46:
Doug:
I think we'll need to see some logs to get a better idea of what might be going on. The only problem we've heard of recently that could have eaten up memory is in remote printer handling for Comet16. This has been eliminated for the .480 Comet release which we will make this Friday. One symptom of this problem was a ntvdm crash.
If that doesn't sound like your problem, I'd suggest sending the Comet.log from the CA host from a time when the user is hung. The CFAM.log might help also. It would be helpful to know the name of the .exe that appears to be eating up memory. Comet consists of several .exes. Check the Windows Task Manager to get the name of the offending program.
You probably know that we aren't big fans of RDP. Is your other Win 2008 Server using RDP also?
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.