Solved

2003 terminal server by device

Posted on 2006-11-02
6
329 Views
Last Modified: 2010-04-10
I have a server that has 5 device licenses. One of the licenses is not being used anymore. How can I change T/S to recognize the new device?
0
Comment
Question by:mdsmith52
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 18

Expert Comment

by:PowerIT
ID: 17858486
After max. 89 days it becomes available automatically.
If in the meantime when you start a new device, that will get a temporary license which is valid for 90 days.
After those 90 days it will get the now released 'old' license.
So bascically you don't have to do anything.

J.
0
 

Author Comment

by:mdsmith52
ID: 17866126
The temporary license has expired and it has not renewed.
0
 
LVL 18

Expert Comment

by:PowerIT
ID: 17866330
Has the issued license to the old device expired? Look in Terminal Server Licensing, click on your license server, then on 'Windows Server 2003 - Terminal Server Per  Device CAL Token'. To the right you should NOT see the old device. If it is still there then it has not expired, but it should have an expire date in the column 'Expires On'.
If so, what is that date?


J.
0
Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

 

Author Comment

by:mdsmith52
ID: 17908422
All 5 licenses are in use. The license in question expires on 12/29/06. The temp license assigned to the problem cpu expired 10/16/06. I have removed the registry key on the client and renamed the system. The unit still will not connect.
0
 
LVL 18

Accepted Solution

by:
PowerIT earned 250 total points
ID: 17909178
You can temporary solve this by removing the following registry sub-hive on the client:
/HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MSLicensing
Not just a key under there, but this whole hive.

J.
0
 

Author Comment

by:mdsmith52
ID: 17960422
Removing the mslicensing key on the client was the answer. What threw me was the server did not drop an used device and add the lastest device as a permanate client. I guess this is the best fix until the license expires again. Thanks.
0

Featured Post

Why Off-Site Backups Are The Only Way To Go

You are probably backing up your data—but how and where? Ransomware is on the rise and there are variants that specifically target backups. Read on to discover why off-site is the way to go.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Let’s list some of the technologies that enable smooth teleworking. 
If your business is like most, chances are you still need to maintain a fax infrastructure for your staff. It’s hard to believe that a communication technology that was thriving in the mid-80s could still be an essential part of your team’s modern I…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question