Published: May 2003

Download 0,85 Mb.
bet	2/5
Sana	26.12.2019
Hajmi	0,85 Mb.
	#5286

1 2 3 4 5

Contents i

Introduction iv

The Terminal Server Licensing Model 1

License Server 1

Terminal Server 2

Supported Licenses 2

Summary of Features and Benefits 4

Service Deployment 4

Terminal Server Grace Period 4

Licensing Service Installation 5

Licensing Service Activation 5

Upgrading a Windows 2000 License Server 6

License Purchase 6

License Installation 7

Licensing Service Discovery 7

Workgroup/Non-Active Directory Domain Discovery 8

Active Directory Discovery 8

Configuring License Servers for High Availability 8

License Token Announcement 10

Terminal Server Licensing Mode 10

Licensing Process 11

Client License Distribution Per Device 11

Client License Distribution Per User 12

Client License Distribution for External Connector 12

Additional Server Configuration 12

License Server Backup 12

Prevent License Upgrade Policy 13

License Server Security Group Policy 13

Administration 14

Terminal Server Licensing Tool 14

Terminal Server License Reporting Tool 15

Terminal Server Client License Test Tool 16

Terminal Server License Server Viewer Tool 17

Preferred License Server WMI Scripts 17

Glossary 19

Summary 19

For More Information 19

Introduction

The Windows Server 2003 operating system family provides a client license management system known as Terminal Server Licensing. This system allows terminal servers to obtain and manage terminal server client access license (TS CAL) tokens for devices and users connecting to a terminal server. Terminal Server Licensing is a component service of Microsoft® Windows Server™ 2003, Standard Edition; Windows® Server 2003, Enterprise Edition; and Windows Server 2003, Datacenter Edition. It can manage unlicensed, temporarily licensed, and client-access licensed clients, and supports terminal servers that run Windows Server 2003 as well as the Microsoft Windows® 2000 Server operating system. This greatly simplifies the task of license management for the system administrator, while minimizing under- or over-purchasing of licenses for an organization. Terminal Server Licensing is used only with Terminal Server and not with Remote Desktop for Administration.

Terminal Server for Windows Server 2003 (known as Application Server mode in Windows 2000 Server) provides application deployment and management for users on a variety of devices through its application server mode. Each device or user who initiates a session on a terminal server running Windows Server 2003 must be licensed with one of the following:

Windows Server 2003 Terminal Server Device Client Access License.
Windows Server 2003 Terminal Server User Client Access License.
Windows Server 2003 Terminal Server External Connector.

Note that additional licenses might be needed, such as Microsoft or other application, operating system, and Client Access licenses. The licenses in the preceding list are required even if other add-on products are used on top of Windows Server 2003.

The Terminal Services Licensing service is only associated with licensing for a terminal server client. It is not used to license any other application or service, and does not replace or interoperate with the licensing service for any other component, or alter your rights and obligations under any End User License Agreement (EULA). The Terminal Server Licensing service is not a replacement for purchasing a TS CAL by using the appropriate sales channels.

TS CAL tokens are electronic representations of real licenses, but they are not actual licenses themselves. Therefore if a license token is lost, it does not mean that you have lost an actual license. If you have the documentation to prove that you have bought an actual license, the license token can be re-issued. Conversely, just because you have a license token does not mean that it necessarily maps to an actual legal license.

Terminal Services Licensing is designed to manage these license tokens to allow an administrator to more accurately assess an organization’s licensing requirements. However, there are a few situations in which a license token will not map to an actual license. The administrator should make his best effort to determine if this is the case, and if necessary, purchase extra licenses (but not install the corresponding license tokens) to account for this discrepancy.

The Terminal Server Licensing Model

Terminal Server Licensing operates between several components as shown in Figure 1. The Terminal Server Licensing-enabled license server, the Microsoft Certificate Authority and License Clearinghouse, one or more terminal servers, and terminal server clients. A single license server can support multiple terminal servers. There can be one or more license servers in a domain, or throughout a site.

Figure 1 The Terminal Server Licensing model

Microsoft Certificate Authority and License Clearinghouse

The Microsoft Clearinghouse is the facility Microsoft maintains to activate license servers and to issue client license key packs to license servers. A client license key pack is a digital representation of a group of client access license tokens. The Microsoft Clearinghouse is accessed through the Terminal Services Licensing administrative tool. It might be reached directly over the Internet, through a Web page, or by phone.

License Server

A license server is a computer on which Terminal Server Licensing is installed. A license server stores all TS CALs license tokens that have been installed for a group of terminal servers and tracks the license tokens that have been issued. One license server can serve many terminal servers simultaneously. A terminal server must be able to connect to an activated license server in order for permanent license tokens to be issued to client devices. A license server that has been installed but not activated will only issue temporary license tokens.

Terminal Server

A terminal server is a computer on which the Terminal Server service is installed. It provides clients access to Windows–based applications running entirely on the server and supports multiple client sessions on the server. As clients connect to a terminal server, the terminal server determines if the client needs a license token, requests a license token from a license server, and then delivers that license token to the client.

Supported Licenses

A license server that runs Windows Server 2003 supports the following types of licenses and manages their corresponding tokens associated with Windows Server 2003 Terminal Server and Windows 2000 Terminal Services as of this writing:

Windows Server 2003 Terminal Server Device Client Access Licenses. These licenses are purchased for known devices that connect to a terminal server running Windows Server 2003.
Windows Server 2003 Terminal Server User Client Access Licenses. These licenses are purchased for known users that connect to a terminal server running Windows Server 2003.
Windows Server 2003 Terminal Server External Connector Licenses. These licenses are purchased to allow unlimited connections to a terminal server running Windows Server 2003 by external users (for example, business partners). It is important to note that there is currently no support for installing External Connector tokens on a license server.
Windows 2000 Terminal Services Client Access Licenses. These licenses are purchased for known devices that connect to a terminal server running Windows 2000.
Windows 2000 Terminal Services Internet Connector Licenses. These licenses are purchased to allow up to 200 simultaneous anonymous connections to a terminal server running Windows 2000 by non-employees across the Internet.
Note
All devices connecting to a terminal server running Windows Server 2003 are required to have a Windows Server 2003 TS CAL. No operating system, including Windows 2000 Professional or successor operating system(s) will be issued a token from the built-in pool.
Windows 2000 Built-in Licenses. Clients that are running Windows 2000 Professional or its successor operating system(s) are issued a token from the built-in pool of license tokens when connecting to a terminal server running Windows 2000.
Temporary Licenses. When a terminal server running Windows Server 2003 requests a Windows Server 2003 Per Device TS CAL token, or when a terminal server running Windows 2000 requests a Windows 2000 TS CAL token, and the license server has none to give, it will issue a temporary token to the connecting client (if the client device has no existing token). The license server tracks the issuance and expiration of these. These temporary tokens are designed to allow ample time for the administrator to install license tokens on the license server. They are not designed to provide for a period of “free” access to the terminal server. Per the Windows Server EULA, licenses are required to be purchased to access a terminal server. There is no provision in the EULA for accessing a terminal server without the appropriate licenses.

Important

Although it is possible to install all the preceding license token types on a terminal server running Windows Server 2003, the token types for Windows 2000 are only valid for use by clients connecting to a terminal server running Windows 2000. Windows Server 2003 tokens are required for connecting to a terminal server running Windows Server 2003.

Download 0,85 Mb.

1 2 3 4 5

Download 0,85 Mb.