Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

June 20, 2001 12:00 AM

A Licensing Problem

Windows IT Pro
InstantDoc ID #21535
Rating: (0)

Our company upgraded its client machines to Windows 2000 Professional, and we decided to upgrade from Windows NT Server 4.0, Terminal Server Edition (TSE) to Win2K Server Terminal Services at the same time. Now, however, when some users try to access the terminal server from Win2K Pro machines, they can't connect. According to the Event Viewer, the temporary licenses have expired. I didn't think that Win2K Pro clients needed terminal services client access licenses (TSCALs). What am I missing, and how do I fix this problem?

Win2K Pro clients have TSCALs built-in. Nevertheless, if you don't have a Terminal Services licensing server set up and registered on your network, your Win2K Pro clients might still experience the problems you described. The first time the clients connect, they grab 90-day temporary licenses. The next time they connect, they try to upgrade those temporary licenses to full TSCALs. Consult the Terminal Services licensing tool to see what licenses your terminal server has issued.

To fix the problem, you must edit the registry to clear the temporary licenses from your Win2K Pro clients. (If you're not working with Win2K Pro clients, be careful when deleting licenses—if you delete a valid TSCAL, you'll have a hard time replacing it.) Start a registry editor (I recommend regedit.exe because you can analyze registry values more closely than you can with regedt32.exe). Open the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\Store\, and look for a subkey or subkeys called LICENSExxx (e.g., License002). The LICENSExxx subkey contains four values, ClientLicense, CompanyName, LicenseScope, and ProductID, which you can examine to identify the subkey that contains the temporary license information. Once you have identified the temporary license's subkey, right-click that LICENSExxx subkey and delete it. The client machine should now be able to connect to the terminal server without any problems. Make sure that your licenses server is configured correctly and that it issues proper licenses to your clients. Then, everything should work out well.

For more information, see Christa Anderson’s Microsoft Offers TSCAL Licensing Fix. If your problem persists, consult Microsoft Support. Good luck.

Related Content:

ARTICLE TOOLS

Comments
    There are no comments to display. Be the first one!
You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.