Terminal services
Discussion
Hi
We use terminal services with several clients and have never had any major issues with it. The service and support requirment has reduced mainly due the the user not being able to do anything other than their work tasks by locking down their profiles. Only real down side is the initial costs are comparable to other solutions but the long term savings can be good.
We use terminal services with several clients and have never had any major issues with it. The service and support requirment has reduced mainly due the the user not being able to do anything other than their work tasks by locking down their profiles. Only real down side is the initial costs are comparable to other solutions but the long term savings can be good.
If you use ts in Win 2003 there are some additional costs involved in licensing. Also - you should really install TS licensing on one W2003 Server (domain controller would be good) and install ts on another W2003 server (member server so that it does not have DC overhead).
MS has some good and helpful stuff in their technical documents about ts.
If you have any specific questions? We just rolled out TS to use with the new version of ACT.
ErnestM
MS has some good and helpful stuff in their technical documents about ts.
If you have any specific questions? We just rolled out TS to use with the new version of ACT.
ErnestM
ErnestM said:
If you use ts in Win 2003 there are some additional costs involved in licensing. Also - you should really install TS licensing on one W2003 Server (domain controller would be good) and install ts on another W2003 server (member server so that it does not have DC overhead).
MS has some good and helpful stuff in their technical documents about ts.
If you have any specific questions? We just rolled out TS to use with the new version of ACT.
ErnestM
It's not only Windows 2003, it's all versions of the product. You need to have a TSCAL for every machine accessing the server, though some clients ship with an inbuilt license.
The main issue you're going to have is around application compatability. Do you know the product you want to run actually works with TS?
Other things to consider are:
1) Security. There's additional costs associated with locking the machine down
2) Resilience (more than 1 server may be required)
3) Printing (it's a PITA with TS)
4) Application suitability. Even if the application works, it may not give the required user experience (animations etc are a no-no).
6) Scalability. It quickly gets expensive in terms of hardware if you're using a CPU/memory intensive application
7) User training. Are users comfortable using a TS session (it's easy to confuse a TS session and a normal desktop session). If one application links to others on the desktop losing that transparency could be an issue.
8) Support. Will the software vendor support their app on TS?
And I'm sure there are a load more!
D
>> Edited by _DeeJay_ on Friday 18th March 12:51
DeeJay...
Under the MS licensing for TS/2003, you must acquire a license if you are going to connect to a 2003 server machine. Win2000 licenses are only supported if 2000 workstation connects to a 2000 server. They've done away with inbuilt client licenses for XP->2003 or even 2000 ws->2003.
They've also solved the printer redirection and even audio/sound redirection in ts 2003.
Cheers
ErnestM
Under the MS licensing for TS/2003, you must acquire a license if you are going to connect to a 2003 server machine. Win2000 licenses are only supported if 2000 workstation connects to a 2000 server. They've done away with inbuilt client licenses for XP->2003 or even 2000 ws->2003.
They've also solved the printer redirection and even audio/sound redirection in ts 2003.
Cheers
ErnestM
As an example we run one site which has 24 users all who run 2 MS Access apps and MS Office.
One Access app is 250MB and the other around 50. They run these all day every day and run endless reports and mail merges etc. They run on a W2003 Server dual XEON with 1GB RAM.
Performance wise the system runs brilliantly. Only get the occasional slow down when a user may run a v.large report.
) machine featuring dual Nocona (Xeon) processors, a "tumwater" chipset motherboard, raid and 4GB of PC3200 RAM. This thing absolutely rocks! You may also wantto consider WinConnect ServerXP.
www.thinsoftinc.com/purchase.php
All you need is XP home/Pro and the above software, 3 user version at £150. Very easy to use and works off the Windows XP RDP. Up to 21 users can connect at any one time.
www.thinsoftinc.com/purchase.php
All you need is XP home/Pro and the above software, 3 user version at £150. Very easy to use and works off the Windows XP RDP. Up to 21 users can connect at any one time.
ErnestM said:
DeeJay...
Under the MS licensing for TS/2003, you must acquire a license if you are going to connect to a 2003 server machine. Win2000 licenses are only supported if 2000 workstation connects to a 2000 server. They've done away with inbuilt client licenses for XP->2003 or even 2000 ws->2003.
They've also solved the printer redirection and even audio/sound redirection in ts 2003.
Cheers
ErnestM
All that is correct to some degree:
1) Printers are still a PITA. No universal print driver, so still instability through dodgy print drivers that must be installed on the server, incorrect matching of other OS printers etc.
2) Licensing. Kind of true, however if you bought XP before the launch of 2003 you get a free CAL (or at least the enterprise agreement customers do) - see their transition plan at www.microsoft.com/windowsserver2003/howtobuy/licensing/overview.mspx#transition
D
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff