RE: Memory usage with Win Terminal server
- From: Patrick Rouse <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Apr 2006 06:45:01 -0700
When using a DOS application on any Terminal Server, whether NT4 TSE, 2000 or
2003, you should look at using a CPU management program like Aurema Armtech,
WM Software Relevos, Threadmaster... as a few instances can easilly dominate
the CPUs due to constant keyboard polling by the DOS app.
http://www.sessioncomputing.com/add-on.htm#performance
TameDOS exists, but I'm not a fan of using such a DOS specific program, when
I can purchase a product that addresses all processes.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.sessioncomputing.com
"Joe McHae" wrote:
I have a similar CPU utilization problem. I recently moved to 2003 Termial.
Services from 2000. Since I moved the CPU Utilization has been a t 100%. The
users are emoting in to use a dos application on a 2000 server. Whe I open
task manager on the terminal server machine each user has opened the 'NTVDM
executable' I am only able to get 3 to 4 users in when on the 200 server I
had 12 users up at all times.
Any ideas would help
"Patrick Rouse" wrote:
I don't know, but if you give me the reference tho the statement you made
I'll check, otherwise I have to do the same googling you did.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.sessioncomputing.com
"PN" wrote:
Thanks Patrick - was there a solution for this problem
"PN" wrote:
We have 2 Windoes 2003 servers. In one of the servers there were some
services that did not loaded when booted up. After investigating on the
Events
Log, it was found to be run out of resources and memory, thus causing some
required services not be loaded properly. A second look at the memory
utilization, it was found to be OK. But the CPU utilization for both
processors were 100% at all time. After checking on all the processes, it
was found to be the wmiprvse.exe of Windows Management Instrumentation had
held up all the CPU power. It was also found from Internet that it was a
known issue that caused memory leak when calling on Terminal Services on
W2K3 servers. Does any one have a solution for this/
- Follow-Ups:
- RE: Memory usage with Win Terminal server
- From: Joe McHae
- RE: Memory usage with Win Terminal server
- References:
- RE: Memory usage with Win Terminal server
- From: Patrick Rouse
- RE: Memory usage with Win Terminal server
- Prev by Date: 2000 to 2003 terminal services (RDP) glitch
- Next by Date: Can't reconnect from anywhere after Disconnect
- Previous by thread: RE: Memory usage with Win Terminal server
- Next by thread: RE: Memory usage with Win Terminal server
- Index(es):
Relevant Pages
|