Terminal Services Pros and Cons


Please can anyone provide me with Pros and Cons with Terminal Services on Windows Server 2003. More CONS please!!

A package has been bought that needs a 100meg LAN, but has been deployed over a 1meg WAN !!( lol - I was not involved!)

Needless to say - performance is crap!

It has been suggested that TS is used, but it goes completly against our model. I have to build a case for the IT Manager.

Any advice/past experiences would be useful.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You should make sure that the application will run in a muti-instance environment because obvously if you are running a TS server and 3 people log in and open the app, then it will be running 3 times on that one box. apart from that TS should be fine.  You could also consider Citrix, although expensive it is very good.  Once you have deployed a TS you could then also open it up so people can work from home.  Sorry no real con's here, I happen to like Terminal Server.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Have a look at:


They explain a lot of pros and cons of Terminal Server.....
Bare in mind the age of that article and the fact that TS is much better these days.

I'm another happy TS user , sorry.
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

I'm also a happy w2k3s-TS user , sorry.
If you give a little more detail, perhaps the feedback will be more usefull.
Is the argument to be used on IT management or somebody who knows what they are talking about?

I'd be tempted to use good old fashioned b**ls*it if you just want to win the argument. Quote a report in IT weekly, something to do with hacking maybe and throw in a few keywords like "Bankrupt" and "Data Protection" . Never fails.
Yancey LandrumTechnical Team LeadCommented:
Cons: the licensing model is changed for 2K3; you have to have TS CALs in addtion to the server license and the server CALs regardless of the client OS on the connecting machine. (Under 2000 TS, if you had 2000 Pro or XP Pro on the client, it counted as a TS CAL so you did not need to purchase additional TS CALs). So for each machine that will be connecting you'll need to purchase a Windows Server 2003 CAL and a Windows Terminal Services CAL.

If you allow access to any MS apps they will need to be licensed accordingly as well.

You'll need quite a bit of RAM in the server depending on how many clients are going to be connecting concurrently.

I've run into printing issues also when the printer on the terminal server and the printer on the client machine are both connected to the same shared printer; double print jobs or corrupt printouts. Other times we've had print jobs go to another connected user's printer (For example, I may be printing a sensitive payroll report but instead of my printer, it goes to Joe Blow's printer in the mailroom).

Plus the app may not even work as stevoharris noted; it will need to be thoroughly tested ($$). And you can't legally test without buying all the associated software/CALs to start with (more $$).

Citrix/Terminal services has it place in network engineering.  There are some apps that are simply not written to perform well over the WAN.  They make to many calls to a database, or inefficently use network resource, like pulling full data sets over the wan when only a subset will do.  A better approach may be to actually measure bandwidth consumption during the use of specific features in the application, and then return a cost estimate on what it's going to take $$$ wise in new WAN links to achieve various benchmarks of performance, and then evaluate that against what a terminal service/citrix solution will cost in terms of $$$ and bandwidth.  Actual business impact can be spinned many different ways, but before you embark on the internal marketting campaign, make sure you have comprehensive data across the board.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.