Troubleshooting Terminal Services


Objective:

Troubleshoot Terminal Services

  • Diagnose and resolve issues related to Terminal Services security.

  • Diagnose and resolve issues related to client access to Terminal Services.

Windows Terminal Services is dependent on the common services on the network, such as TCP/IP and domain services. If you are having problems with Terminal Services, make sure no other functions on the network are failing.

A common problem with Terminal Services involves connecting to the server with the older RDP 5.0 client instead of the RDC 5.0 client, which is included with Windows 2000, or the RDC 5.1 client, which is included with Windows XP and Windows Server 2003. The clients look and function in a similar manner; however, the advanced functionality that is enabled in RDC 5.1, such as improved encryption, audio support, and keyboard mapping, are not available with the older RDP clients.

The multiple-monitor support in Windows XP/2003 can cause problems when you're connecting to one of these machines. If the application that you want to work with was last displayed or is currently displayed on the secondary monitor, you will not be able to see it.

To move the application to your RDC session, use the procedure outlined in Step by Step 11.6.

Step by Step

11.6 Moving an application to your RDC session

1.

Select the application's icon on the taskbar.

2.

Hold down the Alt key and press the spacebar to open the Window menu. (You won't be able to see it.)

3.

Press the M key (Move) and use the arrow keys to move the application window into your RDC session, as shown in Figure 11.19.

Figure 11.19. Moving a window back onto the viewable desktop.


4.

After the application window is within your session window, press the Enter key to lock it down.

When trying to diagnose a possible Terminal Services problem, sometimes you need to know what mode the server is in. To determine which mode a Terminal Services server is using, follow the procedure outlined in Step by Step 11.7.

Step by Step

11.7 Determining the Terminal Services mode

1.

Select Start, All Programs, and then click Administrative Tools.

2.

Select Terminal Services Configuration.

3.

Select Server Settings.

4.

Locate the Licensing entry in the right pane. The mode is listed in the Attribute column, as shown in Figure 11.20.



Figure 11.20. Identifying the Terminal Services mode.


There are many applications, including some from Microsoft, that you cannot install on the Terminal Services computer from a Remote Desktop session. You have to install these programs from the server console connection. This includes SQL, most of the service packs for Windows, and other Microsoft applications.

Challenge

You are putting together a business plan for a startup company. Your goal is to run a small application service provider (ASP) that caters to several local small businesses that can't afford to have their own server farm and IT staff. You plan for all your clients to access your server farm over the Internet, either through a VPN or via one of the web servers.

You are, in effect, running the business for a number of small companies. It is essential that you provide these companies with reliable access to their data as well as ensure that their data is not accessible by other companies, both those sharing your resources and those external to your network.

Try to complete this exercise on your own, listing your conclusions on a sheet of paper. After you have completed the exercise, compare your results to those given here.

  1. You should set up a cluster of load-balanced Windows Server 2003 Terminal Services servers, with identical applications installed on each server. These load-balanced Terminal Services servers should have the Session Directory Service enabled so that a disconnected user (common over Internet connections) will be automatically routed back to her existing session.

  2. To ensure that users from one company cannot access the data of another, you should set up different user groups for each company. Each company should be configured with its own file shares and folders. Each company's file shares should grant Deny Read permission to the groups from the other companies.





MCSA. MCSE 70-290 Exam Prep. Managing and Maintaining a MicrosoftR Windows ServerT 2003 Environment
MCSA/MCSE 70-290 Exam Prep: Managing and Maintaining a Microsoft Windows Server 2003 Environment (2nd Edition)
ISBN: 0789736489
EAN: 2147483647
Year: 2006
Pages: 219
Authors: Lee Scales

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net