1.0 Introduction
1.1 What Is the Terminal Services Advanced Client?
1.2 Overview of Terminal Services Advanced Client Components and Features
1.2.1 Terminal Services ActiveX® Client Control and Sample Web Pages
1.2.2 Terminal Services Connections Microsoft Management Console (MMC) Snap-in
1.2.3 MSI Setup Package and Updated Full Terminal Services Client
2.0 Installation Instructions for the Advanced Client
2.1 Installing the ActiveX Client Control and Sample Web Pages
2.1.1 Before you install the ActiveX Client Control and Sample Web Pages
2.1.2 To Install the ActiveX Client Control and Sample Web Pages
2.2 Installing the Terminal Services Connections MMC Component
2.2.1 To Start the Terminal Services Connections Snap-in
2.2.2 Note on Password Security (Terminal Services Connections Snap-in)
2.3 Installing the Full Terminal Services Client MSI Setup Package
2.3.1 Installing the MSI Setup Files to a Local Computer or Network Share
2.3.2 Before You Deploy the MSI Package to Clients
2.3.3 Running the Full Terminal Services Client MSI Setup Program
2.3.4 Deploying the
MSI Package to Multiple Computers
3.0 User Notes
3.1 Terminal Services Connections Snap-in Might Cause MMC to Fail During Frame Resizing
3.2 Full Terminal Services Client Command-line Syntax
Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. Unless otherwise noted, the example companies, organizations, products, people and events depicted herein are fictitious and no association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2000 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, Active Directory, ActiveX, IntelliMirror, and Visual Basic are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
This document provides information about Microsoft Terminal Services Advanced Client, as well as answers to questions that you might have.
1.1 What Is the Terminal Services Advanced Client?
Welcome to the Microsoft Terminal Services Advanced Client (TSAC). The Terminal Services Advanced Client is an interim release of Terminal Services components and features. The purpose of this release is to extend the functionality of Terminal Services, client side, so that system administrators, Web page designers, and Web administrators can implement Terminal Services client sessions in Web pages or Visual Basic® applications without requiring the user to download or install the full Terminal Services client program. These innovations greatly extend the usefulness of Terminal Services for remote administration of servers, for Web applications, and for management of Terminal server installations.
1.2 Overview of Terminal Services Advanced Client Components and Features
The TSAC consists of three components. Each component has its own installation.
1.2.1 Terminal Services ActiveX Client Control and Sample Web Pages
The Terminal Services ActiveX Client Control is an ActiveX control that provides virtually the same functionality as the full Terminal Services Client, but it is designed to deliver this functionality over the Web. When embedded in a Web page, the ActiveX client control can host a client session with a Terminal server, even if the full Terminal Server Client is not installed on a user's computer.
When you install the ActiveX Client Control, a minimal set of sample Web pages is also installed on your Web server. These pages include: a sample default and connect page that work together to create a Terminal server Web connection, and a page for adminstrators that hosts multiple instances of the ActiveX Client Control.
For more information about the Terminal Services ActiveX Client Control and sample pages, including instructions for embedding the control in a Web page, see the Microsoft Terminal Services ActiveX Client Control Deployment Guide (Webclient.doc), which is installed in the same directory where you installed the ActiveX Client Control.
1.2.2 Terminal Services Connections Microsoft Management Console (MMC) Snap-in
The Terminal Services Connections MMC snap-in provides a tool for system administrators who want to manage multiple remote sessions to individual applications on many servers. This snap-in hosts several Terminal server sessions in an easily navigated tree.
Installing the Terminal Services Connections MMC Component
To Start the Terminal Services Connections Snap-in
1.2.3 MSI Setup Package and Updated Full Terminal Services Client
The Terminal Services Advanced Client MSI Setup package is a tool for deploying the full Terminal Services Client and associated files on computers running any version of Windows 2000, including Windows 2000 Professional. The MSI Setup package can also be placed on a Windows 2000 share for distribution to workstations running Windows 2000 by using Microsoft IntelliMirror®.
Included in the MSI Setup package is an updated version of the Terminal Services Client (mstsc.exe). This version contains all of the functionality of the previous versions as well as the following additional features:
Installing the Full Terminal Services Client MSI Setup Package
Full Terminal Services Client Command-line Syntax
The Advanced Client components are packaged in three self-extracting executable files.
Installing the ActiveX Client Control and Sample Web Pages
Installing the Terminal Services Connections MMC Component
Installing the Full Terminal Services Client MSI Setup Package
2.1 Installing the ActiveX Client Control and Sample Web Pages
2.1.1 Before you install the ActiveX Client Control and Sample Web Pages
The Terminal Services ActiveX Client Control is designed to be installed on a Web server running Windows NT 4.0 Server or later and Internet Information Server 4.0 or later. To use the sample pages, Active Server Pages (ASP) must be enabled on the Web server.2.1.2 To Install the ActiveX Client Control and Sample Web Pages
The ActiveX Client Control and sample pages are contained in a self-extracting executable file called Tswebsetup.exe. This executable file is located in the <cdroot>\Valueadd\TSAC directory of the Microsoft Windows 2000 Service Pack 1 CD. The Setup program installs all files in the directory that you specify on the local computer.
Important The ActiveX Client Control and sample pages are designed to be installed on a Web server running Windows NT 4.0 Server or later and Internet Information Server 4.0 or later. If installed on a computer that does not meet these requirements, the components will not function as described.
To install the ActiveX Client Control and sample Web pages
<cdroot>\ValueAdd\TSAC\Tswebsetup.exeThe ActiveX Client Control Setup program installs the files in the directory you specify on the target computer (Default = C:\Inetpub\Wwwroot\Tsweb).
For more information about the Terminal Services ActiveX Client Control and sample pages, including instructions for embedding the control in a Web page, see the Microsoft Terminal Services ActiveX Client Control Deployment Guide (Webclient.doc), which is installed in the same directory where you installed the ActiveX Client Control and sample pages (Default = C:\Inetpub\Wwwroot\Tsweb).
2.2 Installing the Terminal Services Connections MMC Component
The Terminal Services Connections MMC Component is contained in a self-extracting executable file called Tsmmcsetup.exe. This executable file is located in the <cdroot>\Valueadd\TSAC directory of the Microsoft Windows 2000, Service Pack 1 CD. By default, the Terminal Services Connections MMC Snap-in Setup program installs the Terminal Services Connections .dlls into the Program Files\Terminal Services MMC Snap-in directory of your hard disk.
Important The Terminal Services Connections component should be installed on the computer from which you administer Terminal servers. This component is only supported on computers running Windows 2000.
To install the MMC Component
<cdroot>\ValueAdd\TSAC\Tsmmcsetup.exe2.2.1 To Start the Terminal Services Connections Snap-in
After you install the Terminal Services Connections MMC component, you can open it in your MMC console with the following procedure.
To start the Terminal Services Connections snap-in
2.2.2 Note on Password Security (Terminal Services Connections Snap-in)
When you create a connection in the Terminal Services Connections snap-in, you have the option of supplying your user information, including your password, for automatic logon to the Terminal server. If you choose to enter password information in the connection dialog, your password is saved in encrypted form in the .MSC file. This encrypted password is protected, and can only be accessed by your user credentials.
If you choose not to supply your password in the connection dialog, the standard Windows logon dialog will appear when the session begins, and you can manually log on to the Terminal server. In this case, your password is not stored on your local computer in any form.
2.3 Installing the Full Terminal Services Client MSI Setup Package
The MSI Setup package for the full Terminal Services Client is contained in a self-extracting executable file called Tsmsisetup.exe. This executable file is located in the <cdroot>\Valueadd\TSAC directory of the Microsoft Windows 2000 Service Pack 1 CD. This executable file places the files on the share you designate on the local computer.
Note Tsmsisetup.exe only copies the Terminal Services Client MSI installation files to the specified share; it does not install the client on the computer. To perform the actual installation, see Running the Full Terminal Services Client MSI Setup Program.
Important The MSI Setup package for the full Terminal Services Client is designed to install the full Terminal Services Client and associated files on computers running any version of Windows 2000, including Windows 2000 Professional. For information on using MSI Setup to install the Terminal Services Client on other computers, see Before You Deploy the MSI Package to Clients. The MSI Setup package can also be placed on a Windows 2000 share for distribution to client computers with Change and Configuration Management software such as Microsoft IntelliMirror. See Deploying the MSI Package to Multiple Computers for more information.
2.3.1 Installing the MSI Setup Files on a Local Computer or Network Share
To install the MSI Setup Package
<cdroot>\ValueAdd\TSAC\Tsmsisetup.exe2.3.2 Before You Deploy the MSI Package to Clients
Before you can install Windows Installer Setup packages on a client computer, the client computer must first have the Windows Installer (MSI) service installed. Windows 2000 comes with Windows Installer already configured. To install Windows Installer on computers running Windows NT 4.0, Windows 98, or Windows 95, use the Windows Installer Setup program (InstMSI.exe). You can download a copy of this Setup program from the following Web location: http://www.microsoft.com/msdownload/platformsdk/instmsi.htm. You will be prompted to select the Setup file for installing Windows Installer on Windows 95 and Windows 98 or the Setup file for installing Windows Installer on Windows NT 4.0. You can also use this Setup program to update older versions of Windows Installer.
2.3.3 Running the Full Terminal Services Client MSI Setup Program
To install the full Terminal Services Client from the MSI setup package (local computer)
Note If the computer is not running Windows 2000 Professional or later, make sure that Microsoft Windows Installer (MSI) service is installed. See Before You Deploy the MSI Package to Clients for more information.
Setup creates a Program Files/Terminal Services Client program group on the Start menu with a shortcut to the Client Connection Manager and the Terminal Services Client. To create a new connection to an existing Terminal server, click Client Connection Manager.
Note When you run the MSI Setup program, the installation program automatically replaces the existing Terminal Services Client on your computer.
2.3.4 Deploying the MSI Package to Multiple Computers
If you are deploying the Terminal Services Client to many users in a large organization, you can use a tool such as Microsoft Systems Management Server (SMS) to deploy the Terminal Services Advanced Client MSI Setup package. SMS version 2.0 can deploy Windows Installer-based software to computers running Windows 2000 Professional, Windows NT 4.0, Windows NT 3.51, Windows 98, and Windows 95.
For more information about deploying software with SMS, see http://www.microsoft.com/smsmgmt/deployment/.
Note If the client computer is not running Windows 2000 Professional or later, make sure that Microsoft Windows Installer (MSI) service is installed. See Before You Deploy the MSI Package to Clients for more information.
If you are deploying the Terminal Services Client to many users in a large organization, and all of the workstations are using Microsoft Windows 2000 Professional and Microsoft Active Directory directory services, then you can use Windows 2000 Group Policy and IntelliMirror to deploy the Terminal Services Advanced Client MSI Setup package.
For more information about deploying software with IntelliMirror, see http://www.microsoft.com/technet/win2000/inmnwp.asp#b, or see the "IntelliMirror Tips and Tricks" page http://www.microsoft.com/technet/win2000/inttips.asp.
If you are running Windows 2000 Server, you can also see the topics on IntelliMirror in Windows 2000 Server online Help.
For information about using Microsoft Windows Installer (MSI), see the MSI online Help (WinInstl.chm), which is installed automatically in the <Windir>\help directory on computers running Windows 2000 Server. In particular, see the topic on Best Practices.
3.1 Terminal Services Connections Snap-in Might Cause MMC to Fail During Frame Resizing
There is a known problem with the Microsoft Management Console in Windows 2000 whereby certain snap-ins, such as the Terminal Services Connections snap-in, can cause the MMC to fail under certain conditions. This can happen if the system focus is on the Terminal Services Connections snap-in, and you attempt to resize the MMC frame (that is, move the splitter bar that separates the contents pane from the topic pane). Upgrade to SP1 to resolve this issue.
3.2 Full Terminal Services Client Command-line Syntax
The new version of the full Terminal Services Client contains updated syntax. You can now run the client and connect to specified servers from the command line.
For Terminal Services Client syntax, type the following in a command line:
Mstsc.exe /?
The syntax for the Terminal Services Client is as follows:
Mstsc.exe ["session"] [-v:server] [-f] [-w:width -h:height ]
where: