Configuring Terminal Services Clients Lesson 9

Transcription

1 Configuring Terminal Services Clients Lesson 9

2 Skills Matrix Technology Skill Objective Domain Objective # Planning a TS Licensing Deployment Configuring RDC Options Configure Terminal Services licensing Configure Terminal Services client connections

3 Terminal Services Clients Configuring a terminal server is only half of the equation. To complete a Terminal Services connection, you must configure the client as well. Selecting client hardware. Configuring the RDC client. Deploying a TS Licensing server.

4 Remote Desktop Connection

5 Remote Desktop Connection

6 Remote Desktop Connection

7 Remote Desktop Connection

8 Remote Desktop Connection

9 Remote Desktop Connection

10 Remote Desktop Connection

11 Remote Desktop Connection

12 Remote Desktop Connection Hot Keys

13 Easy Print In previous versions of Terminal Services, for a client to use a printer connected to the client computer in a terminal session, both the client and the terminal server must have the appropriate printer driver installed. In Windows Server 2008 Terminal Services, a new feature called Easy Print eliminates the need for the printer driver on the terminal server. Instead, the terminal server has a generic Easy Print driver based on the XML Paper Specification (XPS) document format introduced in Windows Vista and Windows Server 2008.

14 Easy Print When you open a printer s Properties sheet in Windows, the printer-specific controls you see are provided by the printer driver. When a user in a terminal session tries to print a document, it is accessing a driver on the terminal server. With Easy Print, the driver on the terminal server redirects user interface calls back to the printer driver on the client computer, so the user sees printer-specific controls without having a printer-specific driver on the terminal server. When you print the document, the terminal server creates a print job in the XPS format and transmits it to the client computer, which prints it using the local driver.

15 Easy Print Support for XPS is built in to Windows Server 2008 and Windows Vista but not Windows XP. To use Easy Print on a Windows XP computer, you must use the RDC 6.1 client and install.net Framework 3.0, which provides the support for XPS.

16 RDP File After you configure the settings in the RDC client, you can save them as a file with an rdp extension to avoid reconfiguring them each time you connect to that particular terminal Server.

17 Mstsc.exe Command When you run the Mstsc.exe program with no parameters, the Remote Desktop Connection window appears with its default settings intact. However, you can use parameters on the Mstsc.exe command line to control the behavior of the client. These command-line parameters are as follows: Mstsc [filename] [/v:servername:portnumber] [/admin] [/f] [/w:pixels /h:pixels] [/public] [/span] [/edit filename] [/migrate]

18 Terminal Server Configuration Console In addition to configuring the RDC client interactively, terminal server administrators can set client limitations on the server itself using the Terminal Server Configuration Console.

19 Terminal Services Configuration Console

20 Terminal Services Configuration Console

21 Terminal Services Configuration Console

22 Terminal Services Configuration Console

23 Terminal Services Licensing To facilitate the deployment of your terminal servers and clients, Windows Server 2008 provides a grace period during which clients can connect to a terminal server. It begins when the first client connects to the terminal server and lasts a maximum of 120 days. After the grace period has expired, all clients must have a license to connect to the terminal server.

24 Terminal Services Licensing Windows Server 2008 includes a limited form of Terminal Services that you can use for remote administration, whether you install the Terminal Services role or not. This feature enables up to two users to connect to the server using the Remote Desktop Connection client with no licenses or restrictions.

25 Terminal Server Licensing To use the Terminal Services role for multiple user connections, you must purchase the appropriate number of Terminal Services client access licenses (TS CALs) and install a TS Licensing server to deploy them. A client access license (CAL) is a document that grants a single client access to a specific software program (in this case, a Terminal Services server).

26 Terminal Services Licensing The process of installing a TS Licensing server and preparing it for use consists of the following basic steps: 1. Install the TS Licensing role service. 2. Activate the TS Licensing server. 3. Install the TS CALs on the TS Licensing server. 4. Configure the licensing settings on the terminal servers.

27 TS Licensing Configuration Page

28 Activating a TS Licensing Server An unactivated licensing server can issue only temporary, 90-day Per Device TS CALs or Per User TS CALs. When you activate the server, Microsoft issues it a digital certificate that certifies the identity of the server and its owner.

29 TS Licensing Manager Console

30 Starting the Activate Server Wizard

31 Connection Method Page

32 Company Information Page

33 Web-based License Server Activation Page

34 Telephone-Based License Server Activation Page

35 Completing the Activate Server Wizard Page

36 Installing TS CALs When you purchase TS CALs, you must select either Per Device or Per User licenses and configure your terminal servers accordingly. After you purchase the TS CALs, you must install them on the TS Licensing server so the server can distribute them to your clients.

37 Install Licenses Wizard

38 License Program Page

39 License Code Page

40 License Code Page with License Number

41 Completing the Install Licenses Wizard Page

42 Terminal Services Configuration After you have an operational TS Licensing server on your network, you must configure two elements on each of your terminal servers, as follows: Terminal Services licensing mode Specifies whether the terminal server should issue Per Device or Per User licenses to clients attempting to connect. Licensing server discovery mode Specifies how the terminal server will locate a TS Licensing server.

43 Licensing Tab on a Terminal Server s Properties Sheet

44 Licensing Diagnosis Display

45 Summary The primary platform for a Terminal Services client is a desktop PC running Windows Vista or Windows XP SP2 with the Remote Desktop Connection (RDC) 6.x client installed. To minimize the client hardware requirements, administrators should run all applications not included with the desktop operating system on terminal servers, with the sole exception of the RDC client program.

46 Summary Deploying applications on a large fleet of desktop computers is a complicated undertaking. The simplest and perhaps most time-consuming method is to install each application on each desktop computer manually. For larger networks, automating the application installation process is almost always preferable. Deploying an application using Terminal Services requires you to install it only once on each terminal server, no matter how many clients will be running the application.

47 Summary Deploying applications using Terminal Services can drastically reduce the network bandwidth consumed by client computers. Microsoft Remote Desktop Connection Client for Mac 2.0 is available as a free download, and third-party clients are available for Macintosh and UNIX/Linux computers.

48 Summary Thin clients require an operating system just like any other computer, but they are not designed to run a full Windows installation. Operating system options include proprietary OSs, Windows CE, Window XPe, and Linux. The Remote Desktop Connection 6.1 client included with all versions of Windows Server 2008 supports all of the new Terminal Services features in Windows Server 2008.

49 Summary One of the long-term problems with Terminal Services is the confusion caused by having two separate desktops: one provided by the local operating system and one by the terminal server. You can configure the RDC client to completely overlap the local desktop with the one provided by the terminal server.

50 Summary Over the years, Microsoft has gradually developed the device redirection capabilities of the RDC client. With RDC 6.x, it is possible to use almost any device connected to the client computer in a terminal session. In Windows Server 2008 Terminal Services, a new feature called Easy Print eliminates the need for the printer driver on the terminal server.

51 Summary After you configure the settings in the RDC client, you can save them as a file with an rdp extension. In addition to configuring the RDC client interactively, terminal server administrators can set client limitations on the server. Administrators can also use Group Policy to control many aspects of Terminal Services client behavior.

52 Summary To use the Terminal Services role for multiple-user connections, you must purchase the appropriate number of Terminal Services client access licenses (TS CALs) and install a TS Licensing server to deploy them.

53 Summary To facilitate the deployment of your terminal servers and clients, Windows Server 2008 provides a grace period during which clients can connect to a terminal server. This grace period begins when the first client connects to the terminal server and lasts a maximum of 120 days.

54 Summary When you install the TS Licensing role service, you must specify the server s discovery scope by selecting the Workgroup, Domain, or Forest option. After you install the TS Licensing role service, you must activate the licensing server before it can be fully functional. When you activate the server, Microsoft issues it a digital certificate that certifies the identity of the server and its owner.

55 Summary When you purchase TS CALs, you must select either Per Device or Per User licenses and configure your terminal servers accordingly. After you purchase the TS CALs, you must install them on the TS Licensing server so the server can distribute them to your clients.