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.
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:
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:
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.
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:
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
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:
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:
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
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:
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
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.
|