Manage and Maintain Access to Resources
These questions are based on 70-290 – Managing and Maintaining a Microsoft Windows Server 2003 Environment
Self Test Software Practice Test
Objective: Manage and maintain access to resources.
Sub-objective: Troubleshoot terminal services.
Single answer, multiple-choice
You are your company’s network administrator. The corporate network consists of a single Active Directory domain. All servers run Windows Server 2003, and all client computers run Windows XP Professional.
The network contains five identically configured member servers that run Terminal Server. You want to configure those terminal servers in a Network Load Balancing (NLB) cluster. First, you enable and configure NLB in the LAN connection properties on each terminal server. What should you do next?
- Enable the Terminal Services Session Directory service on each terminal server.
- Configure one of the terminal servers as a DHCP server.
- Enable the Terminal Services Session Directory service on a server that is not part of the NLB cluster.
- Install DNS Server on each terminal server, and enable the round robin feature.
C. Enable the Terminal Services Session Directory service on a server that is not part of the NLB cluster.
You should enable the Terminal Services Session Directory service on a server that is not part of the NLB cluster. An NLB cluster is a collection of servers that appears to users as a single computer. When a user attempts to establish a Remote Desktop session with the NLB cluster, the user’s request is automatically assigned to one of the servers in the cluster. To configure several terminal servers to operate as an NLB cluster, you should first configure NLB in the LAN connection properties on each server. Next, you should configure the Terminal Services Session Directory service on a Windows Server 2003 computer. This service maintains a database that stores user session information. That information is used to enable users to reconnect to their respective disconnected sessions. If a user disconnects from a terminal server session that is running on a server in an NLB cluster and later attempts to reconnect to that session, the user’s request must be forwarded to the correct server.
It is recommended that the Session Directory for an NLB cluster be created on a server that is not part of the cluster. When the Terminal Services Session Directory service is started on a server, a local group named Session Directory Computers automatically is created on that server. You must manually add the terminal servers in the NLB cluster to that group in order to enable the terminal servers to participate in the Session Directory. Additionally, you must configure each terminal server in the cluster to join that Session Directory. You can use the Session Directory setting in the Terminal Services Configuration console to configure each terminal server individually, or you can place all terminal servers into an organizational unit (OU), configure the appropriate Session Directory policies in a Group Policy object (GPO) and link the GPO to the OU.
It is not necessary in this scenario to install the DNS Server service on the terminal servers, nor is it necessary to configure one of the terminal servers as a DHCP server.
Windows Server 2003 Online Help, Contents, “Software Deployment,” “Terminal Services,” “Terminal Server,” “Concepts,” “Deploying Terminal Server,” “System Planning,” “Load balancing and terminal servers.”