|
Originally Posted by stevef
|
Terminal Services is something that was introduced with Windows 2000 server. It is a server product.
Windows XP has a very cut back version that allows one client to connect and provide remote diagnostics/assistance. I believe that you can connect the terminal Services client to this. You must have XP and you have to enable remote Assistance.
I will try this and let you know
|
Windows 2000 Server - Not installed by default.
Windows XP - 'Remote Assistance'
Windows Server 2003 - Sort of installed by default.
There are 2 different 'modes' of opperation for Terminal Server. One costs butt loads of cash for licenses, the other does not.
The first one, which is the expensive one, is (think this is what it's called) 'Application Server' mode. This is where you have one big computer that many users connect to to run their applications.
The other mode is 'Remote Administration' mode, and it's free.
On Windows Server 2003 'Remote Administration' TS is installed by default I believe, and only allows a total of 2 connections at the same time to the TS.
Windows 2000 Server just trusts you to only use a maximum of two at one time.
Windows XP, like stated before, 1 at a time.
If this is a business thing... check your licenses. Anything but 'Remote Administration' requires additional TS licenses.
After using various methods for remote control, from VNC, to Dameware, to Remote Administrator. I must say that Terminal Server is by FAR the best way of connecting to a remote server. Period. Hands down. The others I mentioned, well, for lack of a more descriptive term,
SUCK!
I use it daily to manage about 8 SQL servers. It rocks.