Riguy Index and Archive:
Microsoft Windows Terminal Services (Part 3)Terminal Services Client Install
Ø With the floppy disks created on the previous page in hand, insert Disk 1 into the workstation from which a remote connection is desired:
Ø Enter the TS Client Installation:
Ø Simply enter the user name and company:
Ø Read the License Agreement, which informs that this software can only be used to connect to an NT Server 4.0, Terminal Server Edition and Windows 2000 Server, Advanced Server, or Datacenter Server:
Ø To start:
Ø Begin, select Yes or No according to needs. For a bit more security, it may be best to keep it for the current user only:
Ø Installation begins:
Ø Go with the default install Directory, and witness the need for Disk 2:
Ø The installation continues easily and quickly enough. When finished, put the 2 TS client install floppy disks in a safe storage place for another install on another workstation. Then, it is time to go into the Program and connect to the Terminal Server!
Ø Go to Start/Programs/Terminal Services Client/Client Connection Manager:
Ø Go into File/New Connection:
Ø After selecting Next, the TS Server descriptive name and specific host or IP need to be typed in. Browse if needed:
Ø Then the option to log in automatically is given. This means that as soon as the TS session is activated, log on is automatic, no need to type in a username or password. For security reasons (i.e. a stolen laptop), even long shot ones, it is best to fill in the log in credentials for authentication each time.
Ø Otherwise, anyone who magically jumps onto your workstation will be able to simply click the connection and, voila, access to the server! A long shot, but I bet it's happened. So, I left blank/Next:
Ø Also, keep in mind that "Log on Locally" permissions always apply to a Windows 2000 Server. So, if you DO choose this option, the User name must be a User who has the proper permissions. Logging on to the domain is different than logging on to a Server:
Ø The next step concerns the windows screen size. This will be the window to work within while connecting to the Terminal Server. I chose 800x600 here:
Ø Self-explanatory items, compression and bit maps, etc These options depend on type/speed of the network or connection:
Ø Do you want or need a program to run upon connecting to the TS?
Ø Choose a different Program Group and icon, if needed:
Ø Finished! I have created a connection to a server named, "Rhody"/Finish:
Ø Back to the TS Connection Manager, double click the connection icon made moments ago, and a log on prompt should come up after a few seconds (unless the not recommended "Log on automatically" was configured:
Ø As an aside, on the workstation I installed TS Client on, I also have Zone Alarm installed. This port (3389) is generally only used for TS. As a result, I got the following prompt, and I selected Yes (or connection would not work!):
Ø That's about it. At this point, the Windows Server can be managed remotely from the workstation. If it is a laptop, for example, it is feasible to connect from any where within a building, or via a VPN /and or dialup (they should go together) connection from home or a hotel.
Ø It is important to be certain that the log off is visible on the remote server. It is not wise to simply click the "X" of the Terminal Service window to close/log off. That may leave the session technically open. And likely you do not want the server to be shut down either. So, do the following if you do not know: right-click Task Bar/Properties/Advanced. And check "Display Logoff".
Ø An interesting tidbit, although not needed at all for TS to function:
"The Terminal Services Advanced Client (TSAC) is a Win32®-based ActiveX® control (COM object) that can be used to run Terminal Services sessions within Microsoft® Internet Explorer.
The TSAC Web package includes the downloadable ActiveX control and sample Web pages that can be used as a starting point for running Windows®-based programs inside Internet Explorer. Developers can also use the TSAC to develop client-side applications that interact with applications running on a terminal server."
That's it!