

























|
 |
 |
 |
Licensing Frequently Asked
Questions For
Windows
Server 2003 Terminal Server and
Windows
2000 Server Terminal Services
|
 |
 |
| |

Windows Server 2003 Terminal Server 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.
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.
This article contains information that can help you
understand and successfully deploy Terminal Services on
computers that are running Microsoft Windows Server
2003.
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.
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:
-
Delete this registry key on the client that
can't connect:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
Reboot the client computer
Assign the local users group "Full Control"
permissions to the registry key you just
deleted (it's automatically recreated when
you reboot)
Attempt to logon to the Citrix Server.
|
Windows 2000 Server Terminal Server Licensing
 |
Microsoft Support WebCast, Windows 2000
Terminal Services Licensing, March 15,
2001
This document is based on the original
spoken WebCast transcript. It has been
edited for clarity.
|
 |
Description of Terminal Services License
Server Discovery
This article describes the discovery
process used by Windows 2000-based
computers that are running Terminal
Services to locate Windows 2000-based
Terminal Services Licensing Servers.
|
 |
Windows 2000 Terminal Services Requires
Licensing Service
Windows 2000 Terminal Services uses a
license-management feature called
Terminal Services Licensing. This
feature is used to manage license
quantities for Windows 2000 Terminal
Services Client Access Licenses (CALs)
and Windows 2000 Terminal Services
Internet Connector. No other licenses
(such as Microsoft Office CALs or
Windows 2000 File and Print CALs) are
managed by Terminal Services Licensing.
|
 |
How to Activate a Terminal Services
License Server and Install CALs Over the
Internet
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 2000
Terminal Services Client Access Licenses
(TS CALs) or Windows 2000 Terminal
Services Internet Connector licenses
(ICs). To deploy TS CALs or ICs you must
enable and activate a Terminal Services
"License Server" and then install the TS
CALs or ICs onto it. Terminal Services
Licensing supports four connection
methods to the Microsoft Certificate
Authority and Clearinghouse to the
activate your license server and install
licenses; Internet, World Wide Web(WWW),
Telephone, and Fax. This article
discusses the Internet method; which is
the fastest and easiest method to
complete the process.
|
 |
Establishing Preferred Windows 2000
Terminal Services License Server
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.
|
 |
Licenses Required When Using Terminal
Services Client Software
The following licenses are required when
you deploy a Windows 2000-based server
running Terminal Services in Application
Server mode on your network
|
 |
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.
|
 |
Terminal Services Licensing Does Not
Accept a Valid License Key Pack
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 with a valid license key, and you
may receive the following error message:
One or more license codes were not
validated. To view the status of your
license codes, click Back. Correct or
remove any invalid license codes, then
resubmit your requests. If the problem
persists, contact Microsoft Technical
Support.
|
 |
HOW TO: Run the Terminal Services
Licensing Tool from Another Computer
You may want to run the Terminal
Services Licensing tool from another
Windows 2000 client, for remote
administration or troubleshooting
purposes. This article describes how to
do this.
|
 |
Terminal Services Licensing for MSDN
Versions of Windows 2000
This article describes how to activate
Terminal Services Licensing and acquire
Terminal Services Client Access Licenses
(CALs) for MSDN versions of Windows
2000.
|
 |
Terminal Services License Server Status
Appears as UNKNOWN
When you try to activate a Terminal
Services Licensing Server, you may
receive the following error message:
The licensing wizard cannot connect to
the selected License Server. Make sure
the licensing service is installed and
running.
Also, when you select the licensing
server, the Activation Status appears as
"UNKNOWN".
|
 |
Cannot Revoke Windows 2000 Terminal
Services License from Client
After a test Terminal Services client
connects to a Terminal Services-based
server and obtains a valid Terminal
Services Client Access License (TSCAL),
the certificate license cannot be
revoked and reallocated to the license
pool.
|
 |
Terminal Services Licensing Technology
for Application Service Providers
This article provides detailed
instructions for licensing Terminal
Services in a Windows 2000 environment.
These licensing steps are required only
if you have configured the Terminal
Services server in Application Server
mode. Terminal Services servers that are
configured in Remote Administration mode
do not require these licensing steps.
|
 |
Terminal Services Licensing Wizard May
Not Work
The Terminal Services licensing wizard
may not work when you try to activate
the license server and you may receive
the following error message:
The Licensing Wizard cannot connect to
the License Server Registry. Check the
Network Connection and retry the
Operation. Message = 0x35
|
 |
Terminal Server Licensing Service
Failure
After you install Terminal Server
Licensing on a server, in a Windows 2000
domain, 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:
Event ID 29
Terminal Services Licensing can only be
run on Domain Controllers or Server in a
Workgroup. See Terminal Server Licensing
help topic for more information.
Event ID 7024
The Terminal Services Licensing service
terminated with service-specific error
29.
|
 |
Terminal Services Licensing Enhancements
This article describes two enhancements
to Windows 2000 Terminal Services
Licensing for Windows 2000 that are
available as an update in Microsoft
Security Bulletin MS01-052. These
enhancements are Post Logon License
Token Issuance and Automatic License
Token Re-issuance.
|
 |
Terminal Services Licensing Server
Required for Windows Server Terminal
Services Clients
According to the end-user license
agreement (EULA), if you are using a
licensed version of Windows 2000, you do
not have to purchase a Windows Server
Terminal Services Client Access license
to connect to a server that is running
Windows 2000 Server Terminal Services.
However, you must still deploy and
activate a server that is running
Terminal Services Licensing.
|
 |
Terminal Services Licensing Enhancements
Frequently Asked Questions
Terminal Services Client Access Licenses
(CALs) are not changed after you apply
the Terminal Services Licensing
Enhancements fix for Windows 2000.
Terminal Services CALs (and Server or
Microsoft BackOffice CALs) are still
allocated on a per-device (per-seat)
basis. This list of frequently asked
questions (FAQ) provides information
about some Terminal Services CAL items
(including the "one-time transfer"
clause) and describes some common
scenarios that may occur after the fix
is applied.
|
 |
HOW TO: Deactivate or Reactivate a
License Server 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 2000 Server or
Windows 2000 Advanced Server. 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. Terminal Services Licensing has
already been installed and activated on
the server.
|
 |
Terminal Services License Database Size
Increases
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:
The Terminal Services licensing server
for the entire domain is taken offline
for maintenance, and another temporary
server is brought online for a long
period of time.
The original Terminal Services licensing
server is brought back online, and the
temporary server is removed.
|
 |
HOW TO: Use the Terminal Services
Licensing Reporter Tool (Lsreport.exe)
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.
|
 |
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:
-
Delete this registry key on the
client that can't connect:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
Reboot the client computer
Assign the local users group
"Full Control" permissions to
the registry key you just
deleted (it's automatically
recreated when you reboot)
Attempt to logon to the Citrix
Server.
|
|
 |
|


|