• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 449
  • Last Modified:

No permanent License in Terminal Services after 90-days temporary license expiring

After the 90 days temporary license for Windows 2000 Terminal Services expire the clients does not get a permanent license. The clients are mostly Windows XP, but the same is happening with Windows Server 2003 as client against the same Windows 2000 TS. What could be the reason and does somebody  know of a solution?
0
TorfinnM
Asked:
TorfinnM
1 Solution
 
dis1931Commented:
If the 90 days are over you either need to discontinue using or get licenses.

Dis
0
 
oBdACommented:
Is your license server activated?

Windows 2000 Terminal Services Requires Licensing Service
http://support.microsoft.com/?kbid=237801

HOW TO: Activate a License Server by Using Terminal Services Licensing in Windows 2000
http://support.microsoft.com/?kbid=306622

How to Activate a Terminal Services License Server and Install CALs Over the Internet
http://support.microsoft.com/?kbid=237811
0
 
harleyjdCommented:
XP clients should not have a temporary licencem as under 2000 they have an in-built TS CAL. If it was a 2K3 Terminal server, then they'd need a seperate TS CAL.

Just for grins try these links:

You cannot connect to a Windows 2000 Terminal server if your Windows Server 2003 Terminal Services license is expired
http://support.microsoft.com/default.aspx?scid=kb;en-us;837321

MS01-052: Clients with an Expired Temporary License May Be Unable to Connect to Terminal Services
http://support.microsoft.com/default.aspx?scid=kb;en-us;315404

Hmm- reading that first one a bit more definately sounds fishy...
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
quail99Commented:
The permanent licenses on a Win2K TS shouldn't be getting consumed by Windows XP clients; as harleyjd said, they don't need one, as there is already a client license built into Windows XP (the same is true for Windows 2000 clients, as well). The only reason that you should need for licenses to be assigned to machines on a permanent basis is if you were using some pre-W2K operating system, like Windows 98.

I believe that Microsoft came out with a patch that changed this behavior, but by default, once a machine is assigned a permanent license, it is forevermore assigned to that machine. If that machine goes away or is rebuilt, you are allowed to reassign that license, at least once, but the only way you can do it is by calling Microsoft and having them reissue you licenses for however many machines you've replaced/rebuilt.

As for the XP machines, unless you're being refused a connection, I wouldn't worry about the licensing for them. If you are being refused a connection from those machines, then there's other things we'd need to look at.
 
0
 
TorfinnMAuthor Commented:
I am aware of the fact that we should not need license on XP-computers, but by some reason the take a license and it expires after 90 days, resulting in refused connection. The terminal server - including the license server - we're connecting to is at a vendors site and they say the license server has reserved licenses for all the computers. When the licenses expires we have to delete the license key in registry and then receiving a new temporary license.
0
 
harleyjdCommented:
Torfinn - did you read the MS KB 837321 up above? That hints at what you are seeing - a Licensce server issuning 2003 CALS, but trying to use a 2000 TS...
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now