Managing Windows Servers with Terminal Services

As a side note, whenever you add or remove Windows components, you will always be prompted to configure which Terminal Services mode is required, regardless if you haven’t made any changes to Terminal Services. This is by design, and does not affect any of your current Terminal Services settings and configurations.

In Remote Admin mode, you are only allowed to make 2 concurrent connections to your server. Just keep that in mind if you’re sharing remote admin responsibilities with your co-workers, and suddenly this error pops up: “The Terminal Server has exceeded the maximum number of allowed connections“. In Application Server mode, as long as you have a valid Terminal Services Client License, or are connecting from a Windows 2000/XP Professional workstation, you can make a connection. If you have any concerns on the performance impact your server might experience by installing Terminal Services, when installed, it uses up very little system resources and won’t degrade performance.

Once Terminal Services is installed on your server, you’re now ready to make a client connection. There are several client connection options available to you, which makes connectivity from multiple devices and platforms possible, and quite frankly, pretty easy. Microsoft provides a Terminal Services Advanced Client, which is a Win32-based ActiveX control (COM object) that can be used to run Terminal Services sessions within Internet Explorer (IE 5 or later); a standard 16-bit and 32-bit Windows Client; an enhanced 32-bit Windows Client, called Remote Desktop Client, which was released with Windows XP, and finally a handheld client, developed for Windows CE, which allows you to remotely administer your server using a Pocket PC. Using Third-Party Add-ons, you can administer your Win 2K server from non-Windows clients as well.