You are currently offline, waiting for your internet to reconnect

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

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
When you run the Manage Your Server Wizard on a Microsoft Windows Server 2003-based computer to select a specific license server to use with Windows Terminal Services servers on a domain or on a site, you may receive the following error message:
No Terminal Services License server was found on the network.
You may receive this error message even if there is a valid Terminal Services License server available on the network.
This problem occurs because the Manage Your Server Wizard does not check in the registry for the manually specified Terminal Services License servers.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name     Platform   ---------------------------------------------------------------------   16-Dec-2003  18:51  5.2.3790.113      220,160  Mys.dll       x86   16-Dec-2003  18:51  5.2.3790.113      345,088  Mys.dll       IA-64
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
823313 Windows Server 2003 Terminal Server licensing issues and requirements for deployment
824684 Description of the standard terminology that is used to describe Microsoft software updates
ts termsrv termserv

Article ID: 831716 - Last Review: 12/08/2015 05:21:46 - Revision: 1.10

Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbwinservperf kbtermserv kbbug kbfix kbqfe kbwinserv2003presp1fix KB831716