Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
Terminal Server on separate machine
Name: mvandek2 Date: January 30, 2005 at 16:00:19 Pacific OS: Windows 2003 CPU/Ram: 1024
Comment:
Is it really necessary to install a Terminal Server on a separate machine?
I just want to give a few users remote access to a few applications. I understood that you need to install the applications you want to use via TS again to make them work for TS and that this could conflict with the applications installed for normal (client-server) use.
Name: jefro Date: February 1, 2005 at 16:29:22 Pacific
Reply:
I think you can run it any thing 2003 offers all on one machine. The speed issue is the reason that you select more than one machine.
Seems that what I read was that you should uninstall and re-install all applications that you wish to run in TS. While it might work it also may not at all. When installed again there should be no issue as to local or TS. (pretty sure on that)
0
Response Number 2
Name: mvandek2 Date: February 2, 2005 at 00:57:05 Pacific
Reply:
I understood that some applications are installed differently for TS, so you either install for TS or client/server (say it is a client server app). To make them work on both you therefore need TS on a separate machine.
Summary: Is it possible to implement Windows 2003 Terminal Service on a current Windows 2003 File Server? I am looking into implementing Windows 2003 Terminal Service within my domain; however, I don't want t...
Summary: I'm having a problem with a 2003 terminal server on a Domain, where all Domain users on winterms using a rdp client can't connect to the server if the Domain connection is broken. error"System cannot ...
Summary: I want to use Terminal Server on SBS 2003. Do I need additional licenses for this? I heard something about TS CAL's needed for each user/client connecting. ...
0 
