You probably already know that Windows 2000 contains a wide variety of tools that you can use to see what’s going on inside your servers. For example, you can use the Event Viewer Console to see if any warnings or errors are present on a server. However, even with all these tools, sometimes there’s no substitute for being able to actually see the server’s screen in real time. Windows 2000’s terminal services will allow you to do just that from a wide variety of clients.
In this series of articles, I’ll explain how to manage your servers through a terminal-enabled client. In Part 1, I’ll discuss the basics of the terminal services. In future articles, I’ll discuss enabling the terminal services on your servers and how to prepare a client to access the terminal services.
It’s often difficult for administrators to grasp the concept of the terminal services, because the terminal services perform more like something from the mainframe world than from the PC world. Dozens of third-party products offer remote-control capabilitiesbut most, if not all, of these third-party remote control products tie up the actual server console during use. If the remote user moves his mouse, anyone who’s sitting at the server console will also see the server’s mouse pointer move. Needless to say, using traditional remote control packages on a server can compromise your network’s security if you aren’t extremely careful about how the remote control capabilities are implemented.
The terminal services work differently than traditional remote control software. When a terminal-enabled client attaches to the server, it doesn’t see the actual server screen, but rather a reproduction of it. Therefore, if a terminal-enabled client is at work, the server screen appears as though no one is using it. Of course, there are ways to check to see if someone is using a terminal session, but the idea is that a terminal-enabled client doesn’t take full control of the server.
To understand exactly how the terminal services work, think of a mainframe environment in which a central computer sends screen updates to dumb terminals. The mainframe itself performs every bit of the processing. Any time a user enters information, the information is sent to the mainframe and processed, and a screen update is passed back to the dumb terminal to acknowledge the processing. This concept is very similar to the way that the terminal services work.
Another similarity is that in a mainframe environment, everyone who’s attached to the mainframe has her own individual session. This makes it possible for everyone to work independently. Just because the mainframe is sending everyone screen updates doesn’t mean all the screens are the same. Instead, the mainframe maintains an independent session for each attached user, which allows users to work independently of each other.
What Are the Terminal Services?
You Decide How to Use the Services
Right about now, you might be getting a little concerned. PC users tend to have a negative image of mainframes, because mainframes are ponderous, cost millions of dollars, and are usually reserved for use as storage systems with millions of records. And let’s face itno one likes to think of their high-end Pentium III as a glorified dumb terminal.
Fortunately, if you decide to use the terminal services, how you use them is up to you. You’re not limited to an all-or-nothing situation. As I’ll discuss in detail in Part 2, when you initially set up the terminal services, you’re asked whether the server will function as a full-blown terminal server, or if you just plan to use the terminal services for administrative purposes.
Even if you decide to use your server as a full-blown terminal server, users will still be able to use the server in the normal way, if you permit them to. However, doing so defeats the entire purpose of having a terminal server. The idea behind running a terminal server is that one (or more) very powerful server runs all the applications. Therefore, users can log in and use any application regardless of how old their PCs are. Another advantage of using a terminal server is that because everything is running on the server, there’s little danger of users damaging their PC configurations or running unauthorized applications. This benefit can greatly reduce calls to your help desk.
Of course, you probably aren’t looking to totally change your network infrastructure. Most likely you just want a good way to manage your servers. This is where administrative mode comes in. Administrative mode allows you to keep everything the same from a client standpoint: It simply adds the capability for a limited number of terminal sessions to also attach to the server.
By enabling this limited capability, you can attach to a server from your desktop PC, notebook, or even a Windows CE device, and interact directly with the server console no matter where you are. For example, in my house, I have 13 servers running in my basement. If I want to look at something on a server while I’m upstairs, I don’t have to go to the basement. Instead, I simply use a palm-top computer and a wireless network link to access a terminal session on whichever server I want to look at. The same technique can easily be applied on a larger scale in just about any office environment. I’ll show you how in the articles that follow. //
Brien M. Posey is an MCSE who works as a freelance writer. His past experience includes working as the director of information systems for a national chain of health care facilities and as a network engineer for the Department of Defense. Because of the extremely high volume of e-mail that Brien receives, it’s impossible for him to respond to every message, although he does read them all.