Hello,

We have 4 terminal servers. 2,5gb memory in the servers.
Windows 2003 WTS; RDP
On each server we have 15 users.

We have 1 very important application, but it's a 16 bit appication.

We have the problem that after a few hours the application is slow, or it
stops working.

Do I have to change something on the servers ?
What's the best option to tune the server ?

Regards,

Henk

Henk, 16 bit apps are notorious for wreaking havoc on Windows NT based OS, so
this is not a problem thats specific to Terminal Server. The reason you
notice it on a terminal server is becasue there are multiple people running a
memory & CPU hungry app, which doesn't cause a problem on a single user
system, because only one person is running the app.

There are several programs that can be used to help "tame" the 16 program so
it doesn't thrash your systems. Some are free any w/o any bells and
whistles, some do very specific things, and some are enterprise management
apps. There are surely more, so no one get mad if I didn't mention your app.

Free add-ons:
http://www.workthin.com/tsdown.htm
Threadmaster (no GUI, but works)

Not free add-ons:
http://www.workthin.com/tsao.htm
WM Software Relevos - Used this before, works great, inexpensive
TMULimit
Appsense Performance Manager - Used before, works great (more features, but
more pricey)
TScale
Tame DOS

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com




"Henk Lohuis" wrote:

> Hello,
>
> We have 4 terminal servers. 2,5gb memory in the servers.
> Windows 2003 WTS; RDP
> On each server we have 15 users.
>
> We have 1 very important application, but it's a 16 bit appication.
>
> We have the problem that after a few hours the application is slow, or it
> stops working.
>
> Do I have to change something on the servers ?
> What's the best option to tune the server ?
>
> Regards,
>
> Henk