• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows Terminal Server 2003 Requirements

kazeakuma

Golden Member
Just a quick question. I got asked about a quote the other day on a server for Terminal Services. The server will be running less than 20 users, and the application is a dos based accounting program. I think the server is way overpowered and just want to confirm it, as I haven't worked much with Terminal Services let alone 2003.

Here are the specs:

Dual Xeon 2.8ghz
E7501 Motherboard
1.5GB Ram

The storage subsystem etc. isn't really relevant here so I won't post it.

Now I think a server like that could handle 100 users or so in light terminal sessions (one dos based app) standing on it's head. Or am I being overly optimistic?
 
Since I dont know anything at all about your "little dos based app" I would tend to agree that this server should be plenty, however I dont think that it would be good for 100 users (maybe more like 60). Another thing that makes it hard to say is that it is a "dos based accounting program" which could mean that even though it is running in a dos window it is an encrypted terminal emulation program that eats considerable bandwidth, if that's the case than I wouldnt want more than 20.

-Spy
 
I'm not too sure on the details myself, a friend asked me to look it over. I still find it hard to swallow that running 20 users (assuming this app does encrypt) requires 2 Xeon 2.8ghz processors. I mean seriously, I've seen massive databases run on far less. Is Terminal Services 2003 really that much of a hog?
 
Is Terminal Services 2003 really that much of a hog?
It's not "that much" of a hog, but of course when running a terminal server it would be far better to have a server that is too fast, than one that is too slow so I would error on the side of excess.

-Spy
 
Originally posted by: spyordie007
Is Terminal Services 2003 really that much of a hog?
It's not "that much" of a hog, but of course when running a terminal server it would be far better to have a server that is too fast, than one that is too slow so I would error on the side of excess.

-Spy

Fair enough then. Far cry from the old terminal services 🙂

Thanks for the help.
 
Those specs are WAY over inflated.
I run three terminal servers (windows NT TS Edition)
They are only PIII-600 servers with 1GB of ram and they each run about 60 users using peoplesoft and our export compliance software without a hitch.

Whatever it is he wants to run it should be just fine with that many people, will they be concurrent connections or just up to a 100 people total?
 
Originally posted by: SaigonK
Those specs are WAY over inflated.
I run three terminal servers (windows NT TS Edition)
They are only PIII-600 servers with 1GB of ram and they each run about 60 users using peoplesoft and our export compliance software without a hitch.

Whatever it is he wants to run it should be just fine with that many people, will they be concurrent connections or just up to a 100 people total?

So I thought. There are less than 20 users total. Wouldn't see it going above 30 in 5 years. What I was actually thinking was maybe the servers could be scaled back to save costs. They were quoted same specs as above for the File/Print server! So I thought they might be getting ripped.
 
I run citrix metaframe, 60-70 users on a box concurrently on a Dell Poweredge 1650 / 2GB of ram no problems at all.
look for something in that range and you should be more than fine, you might even be able to get away with buying a Pwoeredge SC server with a P4-2.4ghz cpu in it for less than 1000.
 
Back
Top