RDP licensing

70yearsyoung
70yearsyoung used Ask the Experts™
on
I have a client with an SBS 2003 domain controller (5 user license) and a server 2008 R2 domain member with 10 cals and 10 rdp cals.

The server 2003 is old and is only used for domain controller, one app and document storage so there is never more than 5 users on it.  The server 2008R2 is used for another app which will only work thru RDP to it. When ever they try to connect to the server 2008 RDP, the first 5 connect fine but from 6 they get a message "cannot connect to remote computer".

Examining the licensing on 2008 all appears to be correct and shows 10 RDP cals installed.

I have thought of taking the server 2008 off the domain and making it a workgroup system as it is possible that the SBS 2003 licensing (5 users ) is screwing up the connections.


Can any one offer any other solutions or confirm that my proposed solution would work?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
On your Server 2008 R2 Remote Desktop Session Host (RDSH) server you need to configure it to point to your RD Licensing server.  This is done in RD Session Host Configuration (tsconfig.msc).  It is okay to run RD Licensing on the same server as your RDSH, but you still need to point it to itself.  Server 2008 R2 RDSH requires a licensing server running on either Server 2008 R2 or Server 2008 (with a hotfix).

Also make sure that the licensing mode matches the type of RDS CALs that you installed on the RD Licensing server.  For example, if you purchased and installed Per User RDS CALs, then make sure that you have set the RDSH server to Per User licensing mode in RD Session Host Configuration.

Wayne

Author

Commented:
I have all that done. however one thing I just noticed was in RDSH, RDP-TCP properties, It shows limit connections to the network adaptor to 5 and the option to change is greyed out
Top Expert 2016

Commented:
that means that it is being set somewhere by group policy probably the s2k3 group policy

Computer Configuration, Administrative Templates, Windows Components, Terminal Services,
http://technet.microsoft.com/en-us/library/cc784146%28WS.10%29.aspx
Rowby Goren Makes an Impact on Screen and Online

Learn about longtime user Rowby Goren and his great contributions to the site. We explore his method for posing questions that are likely to yield a solution, and take a look at how his career transformed from a Hollywood writer to a website entrepreneur.

Technology and Business Process Advisor
Most Valuable Expert 2013
Commented:
You need more SBS CALs.  Windows CALs DO NOT cover SBS access.  SBS being your authenticating DC requires a CAL per user. or END device.  I would call MS first to verify you can still get CAL codes for SBS 2003 (it really should be replaced - running 11 year old unsupported software is not wise) but it used to be you would buy SBS 2011 CALs and contact MS for keys to install on 2003.
Jeffrey Kane - TechSoEasyPrincipal Consultant
Most Valuable Expert 2016
Top Expert 2014

Commented:
What Lee says is correct.  However since you suggested you may just remove the Server 2008 from the domain and make it a workgroup, then that would be your best course of action.  Removing it would mean that you don't need SBS CALs for it.

Jeff
Seth SimmonsSr. Systems Administrator

Commented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial