Keeping things thin since 1997.....
 

CCAHeaven.com
 

Home
Citrx Study Guides
Presentation Server 4.0
Virutal Desktop
Citrix Access Gateway
Philadelphia Citrix Training
Search
ANTI-SPAM
Lookup tools
Home Page
Metaframe
Terminal server
TSE profiles
Terminal server Licensing
Win 2003 TSE
Rdp load balancing
Win 2000 TSE
Links
Free Software
Certification
CSG
Citrix Printing
Nfuse
Downloads
Wireless

 

 

 
The wonderful world of TS licensing. Please fasten your seat belts and keep you hands in the car at all times.

CCAheaven not responsible for sudden changes in MS licensing or mass hysteria as a result of trying to comprehend the following documents <grin>

 

 

 

 

 

 

 
   
Terminal server Licensing

Windows Server 2003 specific

What's New in Windows Server 2003 Licensing

Licensing Terminal Server in Windows Server 2003

Windows Server 2003 Pricing and Licensing FAQ

Terminal Server CAL Transition Plan FAQ - if you owned XP Pro before April 24, 2003

Windows Server 2003 Terminal Server Licensing White paper - highly recommended reading, especially if you have a mixed 2003/W2K environment!

Guidelines for Deploying Terminal Server

823313 - Windows Server 2003 Terminal Server licensing issues and requirements for deployment

822134 - The Function of Terminal Server CALs in Windows Server 2003

301932 - Terminal Services Licensing service discovery - 2003

279561 - How to Override the License Server Discovery Process in Windows Server 2003 Terminal Services

325869 - HOW TO: Activate a License Server by Using Terminal Server Licensing in Windows Server 2003

814593 - HOW TO: Deactivate or Reactivate a License Server Using Terminal Services Licensing - 2003

818023 - Licenses are listed as either "Windows 2000 Server-Terminal Services CAL Token (Per-Device)" or "Windows 2000 Terminal Services Client Access License" in the Terminal Server licensing tool on Windows Server 2003-based computers

Troubleshooting Licensing Error Messages

832917 - "A Product ID was not generated during installation" error message when you try to activate a Terminal Server license server

310122 - Terminal Services Licensing Service May Not Start and Event ID 43 May Be Logged

831716 - You receive a "No Terminal Services License server was found on the network" error message when you run the Manage Your Server Wizard on a Windows Server 2003-based computer - fixed in SP1

885013 - Event ID 1009 is logged on a Terminal Server License server in a Windows Server 2003-based domain

834651 - Terminal Services licensing mode changes from Per User or from Per Device to an invalid value after you add or remove a Windows component - fixed in SP1

884570 - Event ID 1004 is logged when a thin client tries to obtain a license from a Windows Server 2003-based terminal server -

837321 - You cannot connect to a Windows 2000 Terminal server if your Windows Server 2003 Terminal Services license is expired - fixed in SP1

 

Description of Terminal Services License Server Discovery Microsoft Knowledge Base Article: 232520 - Describes the discovery process used by Windows 2000-based computers that are running Terminal Services to locate Windows 2000-based Terminal Services Licensing Servers. (updated 1/19/2000)

Establishing Preferred Windows 2000 Terminal Services License Server
Microsoft Knowledge Base Article: 239107 - To select a specific license server for use with various Microsoft Windows 2000 Terminal Services servers in a domain or site, you can modify the registry to point to a particular license server. You can do this to specify that all Terminal Services servers work with a particular license server for accounting purposes, or if a Terminal Services server and the license server reside in different domains. (updated 1/18/2001)

How to Activate a Terminal Services License Server and Install CALs Over the Internet
Microsoft Knowledge Base Article: 237811 - The process of deploying and tracking licenses within an organization is enhanced in Windows 2000 Terminal Services. Terminal Services Licensing now includes a Licensing wizard to download license packs and manage license quantities for Windows (updated 1/31/2000)

HOW TO: Activate a License Server by Using Terminal Services Licensing 
Microsoft Knowledge Base Article: 306622 - This article describes how to activate a license server by using Terminal Services licensing. (updated 1/21/2002) 

How to Locate a Phone Number for the Microsoft Clearinghouse
Microsoft Knowledge Base Article: 291795 - This article describes how to locate the appropriate phone number for the Microsoft Clearinghouse for your country or region by using the Terminal Services Licensing tool. (updated 3/14/2001)

How to Transfer Terminal Services CAL from One Client Computer to Another  
Microsoft Knowledge Base Article: 315262 - This article describes how to transfer a Terminal Services (TS) client access license (CAL) internally from one client computer to another in the same company within Terminal Services Licensing. (updated 1/23/2002) 

HOW TO: Use the Terminal Services Licensing Reporter Tool (Lsreport.exe) 
Microsoft Knowledge Base Article: 317592 - This step-by-step article describes how to use the Terminal Services Licensing Reporter tool (Lsreport.exe) to display and analyze the license information that is contained in the database of Terminal Services license servers. (updated 312002) 

Reclaiming Terminal Server Client Licenses for Windows 95 or 98 Computers Upgraded to Windows 2000 Professional
Microsoft Knowledge Base Article: 287679 - This article tells how you can reclaim Microsoft Windows NT 4.0, Terminal Server Edition, client licenses for computers that have been upgraded from Microsoft Windows 95 or Windows 98 to Microsoft Windows 2000 Professional. (updated 2/16/2001)

Terminal Services Internet Connector License and ASPs
Microsoft Knowledge Base Article: 288379 - The Terminal Services Internet Connector license allows for 200 concurrent, anonymous, non-employee connections to a Windows Terminal Server through the Internet. This license is useful for organizations that want to demonstrate Windows-based software to Internet users without making the software Web-based. Application Service Providers (ASPs) cannot use this type of license to provide a pay-for service. Furthermore, ASPs cannot offer any Microsoft products for rental or leasing in any situation without having a signed and accepted an Application Services Agreement (ASA) that is in place with Microsoft. This agreement allows Terminal Services Client Access licenses (CALs) and licenses for other Microsoft products to be allocated on a per-subscriber basis, rather than on a per-seat basis. (updated 372001)

Terminal Services Licensing Enhancements
Microsoft Knowledge Base Article: 287687 - This article describes two enhancements to Windows 2000 Terminal Services Licensing for Windows 2000 that are available as a hotfix. These two enhancements, Post Logon License Token Issuance and Automatic License Token Re-issuance, are described below. (updated March 29, 2001)

Terminal Services Licensing Enhancements Frequently Asked Questions
Microsoft Knowledge Base Article: 294655 - Terminal Services Client Access Licenses (CALs) are not changed after you apply the Terminal Services Licensing Enhancements fix for Windows 2000.(updated 5/26/2001) 

Windows 2000 Terminal Services Issues in an Active Directory Domain Environment
Microsoft Knowledge Base Article: 250776 - Windows 2000 Terminal Services provides increased functionality for Windows 2000 domain environments, and affects all aspects of the domain environment. This article describes the affected areas, and provides links to Microsoft Knowledge Base articles (updated 472000)

Windows 2000 Server Evaluation Version and Terminal Services Licensing
Microsoft Knowledge Base Article: 248650 - The Windows 2000 server family evaluation product End User License Agreement (EULA) provides the customer with 10 Terminal Services Client Access Licenses (TS CALs), together with 10 Server Client Access Licenses. (updated 7/12/2001) 

Known Bugs and Issues
Cannot Revoke Windows 2000 Terminal Services License from Client
Microsoft Knowledge Base Article: 271245 - After a test Terminal Services client connects to a Terminal Services-based server and obtains a valid Client Access License (CAL), the certificate license cannot be revoked and reallocated to the license pool. (updated 9/28/2000) 

Cannot Start the Terminal Server Licensing Service and Events 7024 and 37 Occur 
Microsoft Knowledge Base Article: 312028 - On a computer that runs Windows 2000 Server, you may not be able to start the Terminal Server Licensing service. The following information may be logged in Event Viewer: (updated 1/30/2002) 

Clients with an Expired Temporary License May Be Unable to Connect to Terminal Services Microsoft Knowledge Base Article: 315404 - New Terminal Server clients, Terminal Services clients, or Remote Desktop Connection clients may connect to Terminal Services correctly, but some existing clients that could previously connect may be unable to connect. If an existing client cannot connect, the following error message may be displayed on the client computer: (updated 142002) 

Terminal Services Clients Consume Multiple Terminal Services CALs Because of Storage Issues
Microsoft Knowledge Base Article: 294729 -  Windows-based terminals or Windows clients may consume multiple Terminal Services CAL tokens because of local storage issues. (updated 672001) 

Terminal Services License Database Size Increases 
Microsoft Knowledge Base Article: 313567 - If the following conditions exist, the Terminal Services license database may continuously increase, and you may receive an "Event ID 43: Work Manager error can't create work item, error code 87" entry in the Event log: (updated 3/28/2002) 

Terminal Server Licensing Service Failure 
Microsoft Knowledge Base Article: 277917 - After you install Terminal Server Licensing on a server, servers may not be listed in the Terminal Services Licensing tool, and you may receive a warning message that indicates that no license servers were detected. In the System event log,  TermServLicensing may report an error with Event ID 29, and Service Control Manager may report an Event ID 7024 (updated 10/17/2001)

Terminal Services Licensing Problems After Upgrade to Release Version of Windows 2000
Microsoft Knowledge Base Article: 248409 - After you upgrade an existing installation of a prerelease version of Windows 2000 to the release version of Windows 2000, the following problems may occur: (updated 6/21/2000)

Cannot Start the Terminal Server Licensing Service and Events 7024 and 37 Occur 
Microsoft Knowledge Base Article: 312028 - On a computer that runs Windows 2000 Server, you may not be able to start the Terminal Server Licensing service. The following information may be logged in Event Viewer: (updated 1/30/2002) 

Terminal Services Licensing Does Not Accept a Valid License Key Pack
Microsoft Knowledge Base Article: 258045 - The Terminal Services Licensing server does not accept the license key pack after being activated. The activation process functions normally, however the installation of license key packs may not work when you configure the License Server (updated 1042000)

Terminal Services License Server Status Appears as UNKNOWN
Microsoft Knowledge Base Article: 269349 - When you try to activate a Terminal Services Licensing Server, you may receive an error message: (updated 8/15/2000)

Terminal Services OEM License Server Activation Does Not Validate PIN or Recognize License Server ID
Microsoft Knowledge Base Article: 256854 - The Windows 2000 update, "Terminal Services OEM License Server Activation Failure", addresses a license server activation problem that occurs only on servers obtained through Microsoft Original Equipment Manufacturers (OEMs) and configured (updated 7/31/2000)

Windows Base Terminal Devices Take Multiple Terminal Services Client Access Licenses
Microsoft Knowledge Base Article: 253292 - When you are using some Windows Base Terminal (WBT) devices, additional Terminal Services licenses may be taken when the devices restart and reconnect to the Terminal Services server. (updated 6/30/2000)

Frequently Asked Questions About Terminal Services Licensing

The Definitive Q&A for Terminal Services Licensing - by Christa Anderson
 

HOW TO: Activate a License Server by Using Terminal Server Licensing in Windows Server 2003

This step-by-step article describes how to activate a Terminal Services license server by using Terminal Server Licensing in Microsoft Windows Server 2003.
 

HOW TO: Deactivate or Reactivate a License Server By Using Terminal Services Licensing

This step-by-step article describes how to either deactivate or reactivate Terminal Services Licensing on a server that is running Windows Server 2003. You must activate a license server before it can issue licenses to Terminal Services client computers. Use Terminal Services Licensing to activate a license server. When you activate a license server, Microsoft provides the server with a digital certificate that validates server ownership and identity. If you use this certificate, a license server can make subsequent transactions with Microsoft to receive client licenses for the servers that have Terminal Services enabled.

Licensing Terminal Server in Windows Server 2003

This article describes Terminal Server Licensing Requirements and Terminal Server Client Access Licensing Mode
 

Terminal Server CAL Transition Plan: Frequently Asked Questions

The plan describes which TS customers are eligible for the transition plan around the discontinuation of desktop operating system equivalency and what steps customers can take to receive complimentary TS Client Access Licenses (CALs) under the transition plan.
 

Licensing Terminal Server in Windows Server 2003

This step-by-step article describes how to activate a Terminal Services license server by using Terminal Server Licensing in Microsoft Windows Server 2003.
 

Windows Server 2003 Terminal Server Licensing Whitepaper

This white paper provides an introduction to Terminal Server Licensing, the client license management service for the operating systems in the Microsoft Windows Server 2003 family. The Terminal Server Licensing service works with Terminal Server to provide, catalog, and enforce license policy among Terminal Server clients. This paper examines the key features and components of Terminal Server Licensing and explains how this service affects computing in an enterprise
 

How to Override the License Server Discovery Process in Windows Server 2003 Terminal Services

This article describes how to override the license server discovery process in Microsoft Windows Server 2003 Terminal Services.
 

What's New in Windows Server 2003 Licensing

These changes to the Microsoft licensing program will first be available with the Microsoft Windows Server 2003 product release.
 

Microsoft Terminal Server Licensing Changes and Transition Plan

Acquired Windows XP Professional license before April 24, 2003.

Have active Software Assurance (SA) or Upgrade Advantage coverage as of April 24, 2003, covering their Windows desktop operating system.

Windows Server 2003 Terminal Server Licensing Issues and Requirements for Deployment

This article contains information that can help you understand and successfully deploy Terminal Services on computers that are running Microsoft Windows Server 2003.

Support WebCast: Microsoft Windows Server 2003 Terminal Server Licensing

This Support WebCast will present an overview of Microsoft Windows Server 2003 Terminal Server Licensing. It will describe how it works, the different types of licenses, the different modes of license server, and how to install it correctly. The presentation is designed to answer frequently asked questions about licensing.

How to Transfer Terminal Services CAL from One Computer to Another

This article describes how to transfer a Terminal Services (TS) Client Access License (CAL) internally from one client device to another in the same company within Terminal Services Licensing.

Event Message 1004 Terminal Services Licensing When You Use the Citrix ICA Client

When you connect to a Windows 2000 Terminal Server that has Citrix Metaframe installed, clients may receive the following error message:

Network or dialup problems are preventing communication with the Citrix server. An attempt to automatically restore the connection will begin after a delay to let the network recover. If the problem persists please contact your System Administrator.
-or-

Error in connection. The Citrix server is not available, please try again later.
-or-

Terminal Server has ended the connection.
You may also receive Event ID 1004 message on the Terminal Server in the application event log:

Event ID 1004
Source: TermService
Description: The Terminal Server cannot issue a client license.

If the Terminal Services Licensing Service is issuing licenses to other clients, but yours can connect, and this error is logged on the terminal server, do the following:

  1. Delete this registry key on the client that can't connect:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
  2. Reboot the client computer
  3. Assign the local users group "Full Control" permissions to the registry key you just deleted (it's automatically recreated when you reboot)
  4. Attempt to logon to the Citrix Server