Solved

Server 2008 R2 RDP licensing and issues

Posted on 2010-08-18
7
904 Views
Last Modified: 2013-11-21
I have a question regarding Microsoft Licensing and a problem regarding Windows Server 2008.
The scenario is... there are several time clocks that connect back to a server through an RDP connection. Also, there are several users that connect back to that Server through an RDP connection. The server is loaded with Server 2008 R2. There are 50 Server 2008 Remote Desktop device cals for all of the time clock and business software users. At most there are only 40 users that could possibly ever connect to the server. Almost immediately the time clocks stopped working correctly. Most all of the time clocks will disconnect at night and when they do come back up they are showing the previous day’s times. There is a message from the server saying the Remote Desktop manager is out of licenses. There are never any more than 30 connections at any given time. It’s almost like the server is remembering every Remote Desktop connection and has used the 50 licenses up and it’s just letting users on temporarily and then at night it’s disconnecting them.  
0
Comment
Question by:bytespeed
[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
7 Comments
 
LVL 32

Expert Comment

by:Rodney Barnhardt
ID: 33469651
How are the licenses installed? Per device or per user?
0
 

Author Comment

by:bytespeed
ID: 33469666
They are per device.
0
 
LVL 32

Assisted Solution

by:Rodney Barnhardt
Rodney Barnhardt earned 100 total points
ID: 33469739
Have you checked your session time limits for things like inactivity? I have seen where a client disconnects, but the server still holds the connection open, especially if the disconnect is not clean, as in a wireless client dropping.
http://technet.microsoft.com/en-us/library/cc753112(WS.10).aspx
 
0
Office 365 Training for IT Pros

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.

 
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 200 total points
ID: 33469865
That is correct once a device or user connects these CALS get allocated they do NOT come back to the licensing server to be used again. These are NOT concurrent licenses which means that just because only 30 users are connected doesn't mean you are only using 30 CALS. How TS\RDS CALS work is once a device or user connects it gets a licensed allocated to it which does not get reallocated back to the licensing server.
0
 
LVL 3

Expert Comment

by:pmaribeiro
ID: 33473300
The allocation by device are not concurrent so the first 50 devices that connect are licensed , all the different devices that try to connect afterwards the connection is refused because the license limit has been reached.

If you also can check the inactivity time so the session can be disconnected this can also be a factor to grab too many licenses if some users are idle for many time and dont disconnect or are not forced to disconnect.

I believe that you issue is relate to my first statement so check that out.

PR
0
 
LVL 31

Accepted Solution

by:
Cláudio Rodrigues earned 200 total points
ID: 33476484
Your problem is simple.
You need to determine what makes more sense in terms of RDS CAL licensing for your environment. If you have multiple shifts for example, where workers share the same computers (meaning more users than devices) it makes sense to license per device. If users connect from several locations (home, multiple office PCs, laptops, etc meaning more devices than users) you should have per user licenses.
As pointed out these are NOT concurrent.
The other thing to keep in mind is per DEVICE licensing is ENFORCED what means if you run out of licenses you do not connect. Simple as that (you actually get a temporary RDS CAL and after 90 days with no RDS CALs available that one expires and you get screwed).
As a workaround until you get more licenses you can simply delete the registry key HKLM\Software\Microsoft\MSLicensing on the device that cannot connect and it will get a new temporary RDS CAL good for 90 days.
For more information about licensing please download and read the guide I wrote, "Terminal Services A to Z" available at no cost at http://www.wtslabs.com. It explains all that and much more.

Cláudio Rodrigues
Microsoft MVP - Remote Desktop Services
Citrix CTP
0
 

Author Closing Comment

by:bytespeed
ID: 33476723
Thanks for the info everyone regarding the licensing and also regarding the session time limits.
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

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

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

695 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