?
Solved

Per device licensing caveat

Posted on 2008-10-24
4
Medium Priority
?
191 Views
Last Modified: 2013-11-21
Due to a large number of shift workers, we have a per device licensing scheme for terminal services.  However, some offices have switched out a large number of devices in the last few weeks and the lifecycle of the CAL hasn't had a chance to run its course.  So we ran out.

Anyway, it's easy enough to 'reg delete HKLM\Software\Microsoft\MSLicensing /f' on a laptop or workstation to trick it into getting a 90 day temp license till the storm blows over, but what about non-Microsoft clients?.  We are now planning on replacing old linux terminal boxes with new ones in the next two months and I'm not really sure how I would trick them into getting new CALs, since I doubt they store the CAL locally like the windows RDP client, so I assume the info is cached server side, but I don't understand how.  Any tricks?
0
Comment
Question by:Marketing_Insists
[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
  • 2
  • 2
4 Comments
 
LVL 85

Expert Comment

by:oBdA
ID: 22798203
*If* your licensing is correct, replacing your TS clients with new ones should be no problem at all, whether they're Windows based or not.
A TS CAL will be renewed by the client as long as it's connecting to the terminal server. If a client is retired and doesn't connect to the TS anymore, its TS CAL will be returned to the pool of available licenses after 54 to 89(!) days. During that time, a new client replacing the old one can use a temporary license, which is valid for 90(!) days (one day more than the longest possible lifetime of a CAL of a client not connecting anymore).
In other words: if the temporary CALs of the "new" devices ran out before the old ones expired, the new clients have been used *parallel* to the old ones, violating the licensing. You'll need new licenses to cover this situation.
But a one-to-one *replacement* of clients (that is, as soon as the new device has logged on for the first time, the old one will never again access the terminal server) should be no problem at all.
0
 

Author Comment

by:Marketing_Insists
ID: 22798910
I suspect parallel usage, I suppose... salesmen have been known to hang on to their old laptops for a few weeks before sending them back, but it's odd that I'm having as many problems as I am having.

If I were to switch to 'per user' mode for a few weeks on my terminal servers, would I have issues switching back to 'per device' mode?  I'm not really familiar with 'per user', since it's relatively a newish 2003 feature.  I have more users than devices, so I'd be in EULA limbo for a while.
0
 
LVL 85

Accepted Solution

by:
oBdA earned 2000 total points
ID: 22799535
Technically, you can switch back and forth between the modes as often as you feel like it. Legally, ... well, you already mentioned the EULA limbo.
0
 

Author Comment

by:Marketing_Insists
ID: 22800079
Ah, it seems our main office set up a class room for training purposes with the old machines before sending them back.  surprise.  "per user  mode" it is - mum's the word though, nudge-nudge.  

Definitely cutting back on the grace period for device swaps.  
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

Hyper-convergence systems have taken the IT world by storm and have quickly started to change our point of view of how the data center should and could be architected. In this article, I’ll explain the benefits of employing a hyper-converged system …
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses
Course of the Month14 days, 16 hours left to enroll

771 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