Terminal services Client Connection Manager

             Hi jskfan
                *Once you setup Terminal server, you wont need additional settings on TS. Only step you have to take is adding users which you want them to connect TS, to Remote desktop users group. In clientside, type mstsc to Start>Run. Then you can save this connection clientside.
               *Without installing licenses, only 3 or 5 clients may connect at the same time. You have to install Terminal server CAL (Client access license). Following microsoft article will guide you through entire process
http://www.microsoft.com/windowsserver2003/techinfo/overview/quickstart.mspx

Regards

<<<In clientside, type mstsc to Start>Run>>
this will open RDP.

Both MrHusy and jskfan are right on.  If you want to make a shortcut to a specific server, you can also add a switch to the mstsc executable.  ex:  mstsc /v:servername  This will automatically open an RDP connection to the server.  You will want to install the client license pack as soon as possible as well.  The microsoft site MrHusy sent you to has all the information you should need.  If you are running Windows 2000, the licensing is slightly different and you may want to contact Microsoft Licensing support to ensure your licenses are installed alright.  I've got a Win2K terminal server, and when I went to Win2003 on the domain controllers, I had quite a bit of trouble getting my Win2K TS licenses to install on the new licensing server (which is supposed to reside on a DC).   Good Luck
mltets
(james)

             Yes it opens RDP, type the servername there and connect to Terminal Server. This is what Terminal Server is for. If you have questions in theory or practics, feel free to ask.

1- When you open RDP client, you can click on options and put the information you want (ex. User, Password, Domain, etc.). You can then save this connection as a RDP file. The only thing you have to do is to create a RDP file with the options you want and copy that file to all the users you want them to connect with a login script or manually. If the pc all have WinXP, double-clicking on the file will open mstsc.exe and will connect to TS with the options you specified earlier.

2- It depend what version of Windows Server you are configuring to be TS server. If it's Win2k server and that all the client are using Win2k or WinXP to connect to it, you don't need licenses since the TSCAL are included with those 2 OS for Win2k server. If you have others OSes that connect to the TS Server, you need to buy licenses. If your TS server is Win2K3 server, you need to buy licenses for your clients to be able to connect to it although you have a 90 days grace period where the clients will be able to connect even if no licenses are installed.

#2- I have windows 2000 Terminal Server and the clients are windows 2000 professional, the TS server is activated and switched to application mode. Now do you think 5 or 10 clients(w2k pro) can connect to the terminal server without installing CALs?

         For W2k pro, answer is yes. Here is related article from microsoft.
http://www.microsoft.com/technet/prodtechnol/win2kts/evaluate/featfunc/tslicens.mspx

Taken from this Microsoft Link http://support.microsoft.com/kb/244749

Windows 2000 Professional or Microsoft Windows XP Professional License: This license permits the installation of Windows 2000 Professional or Windows XP Professional, in addition to providing the legal right to access Terminal Services on a Windows 2000-based server. A computer that is running a licensed copy of Windows 2000 Professional or Windows XP Professional does not require a Terminal Services Client Access License.

So you don't need to buy TSCALS if the clients connecting to your Server run Win2K OR WinXP Pro to connect. Here's how the Server will treat the connection.

Windows 2000 Built-In CALs - Clients that are running Windows 2000 Pro or Windows XP are issued a token from the built-in pool of license tokens when connecting to a terminal server running Windows 2000 Server Terminal Services.

Taken from http://thelazyadmin.com/index.php?/archives/305-Terminal-Services-Licensing-Primer.html

To answer your question jskfan,  you won't have to buy TSCALs since all your clients use Win2K.

All the evidence points to the fact that you don't need additional TSCALs.  I'm not sure why my server wouldn't allow any connections until I loaded some onto my Licensing server.  The only thing I can come up with is the addition of the Windows 2003 domain controllers I have on my network...  Hopefully, you're pure Win2K.  Good Luck

        Well it was not the complete answer. Here is the last phrase :)

you won't have to buy TSCALs since all your clients use Win2K if your Terminal server is installed on Win2k server.

I will check this later after I reboot the server.

Because I have switched to application mode and it prompted me to reboot the server and I didn't.
I tried to connect more than 2 users and it says it reached the maximum.

Now after I reboot the server then I will try it and keep you updated.
thanks

it worked fine guys.... I managed to connect with 4 user connections.
I wonder for how long I don't need CALs.

         Hi jskfan
           I don't think that you will need CALs

Regards