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

Terminal Services Licensing Problem

Hi all, I've got 2 term servers set up with win 2003 server on the same domain.  company bought 30 user licenses and 30 device licenses.  i set up term server "a" as the license server (enterprise wide) and succesfully activated and installed all 60 licenses (verified twice).  several of my users are getting the message "your terminal services temporary client license will expire in 7 days, please contact sys admin to get permanent license".

further investigation shows no authorized or permanent licenses are being issued.  they all show unauthorized.  both servers recognize term "a" as the license server, and it is activated.

why would term "a" license server not issue any permanent licenses??  docs show once you activate and install licenses, that's it, user connections will be issued licenses as they come in.  

thanks in advance for help.
0
aaalife
Asked:
aaalife
  • 4
  • 4
  • 2
  • +1
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Hi aaalife,
First, your licensing server should not be one of your Terminal Servers.  Also, each Terminal Server must be set to operate in either Device Mode or User Mode, not both... if you have 30 user licenses then configure Server A in User Mode and have those users connect to that server.  The 30 devices can then connect to the other.

More info here:  http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic.mspx
and here:  http://support.microsoft.com/?id=822134



Good Luck!

Jeff
TechSoEasy
0
 
aaalifeAuthor Commented:
not so, with 2003 server, terminal server set up is by "per server" or "per device".  per device now includes per device in addition to per user CALs, which for reasons passed in understanding, we have 30 of each.

this business about not having the license server on a production 2003 server, is ms telling custs to buy another server for license distribution?  if the only concern is the thing going down and not issuing out cals, forget it (not concerned).  but if the problem is the licenses won't be distributed because so much other garbage is going on, then we're hosed.

i don't think that's the source of our problem.



0
 
oBdACommented:
It's best practice to have your terminal services license server running on a DC, but since Server 2003, this is not a "must" anymore. What you'll have to do if it's not a DC, though, is point your terminal servers to the machine that's running the TS license server.

How to Override the License Server Discovery Process in Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You've actually got it backwards... if you are going to mix User & Device CALS then the server needs to be set as "per server".  I realize that this is hella confusing... but this may clarify what I'm saying:  http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/fd7d331b-8857-4f07-9f45-d29488d6ab03.mspx

Mixing CAL types in a small deployment such as yours can be rather grueling to figure out... it's usually better if you stick with per USER CALs if you can for now because they aren't tied to specific AD accounts, but rather simultaneous allocation of the License keys.  Also your licensing server can actually be a workstation (such as a manager's PC... it only requires XP Pro... but as oBdA suggested, it's best to put it on your DC.  

More on licensing servers:  http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/b6c02871-7bef-4e26-9aab-48730511c126.mspx

Jeff
TechSoEasy
0
 
aaalifeAuthor Commented:
our domain controller is a 2000 server.  docs say 2000 servers cannot issue 2003 licenses, and 2003 license servers will not issue 2000 licenses.  ergo, 2003 license server setup had to be on term "a".  i've got the domain controller set up as a 2000 license server for the various 2000 servers in place, which has been fine up to this point.
0
 
oBdACommented:
Then just change your Server 2003 terminal servers' registry to point to your "a" TS as described in the article.
0
 
JasonMcBeeCommented:
I thought this to be of interest.

When running terminal services on Server 2003 and User CAL's, people connect to the server, but they don't show up in your terminal services licensing screen.  This appears to be a bug.  KB article 822134 states the following:

"Currently, Window Server 2003 does not manage User CALs. This means that even though there is a User CAL in the license server database, the User CAL will not be decremented when it is used. This does not remove administrators from End User License Agreement (EULA) requirements to have a valid terminal server (TS) CAL for each user. Failure to have a User CAL for each user, if Device CALs are not being used, is a violation of the EULA. In the future, this behavior will be changed and User CALs will be managed."

For the complete article, go to:
http://support.microsoft.com/?kbid=822134
0
 
aaalifeAuthor Commented:
server was maxed out on device licenses, changed to user (unmanaged) on both terms and no more errors/warnings are occurring.

thanks for the help everybody!
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
That's funny... that was the first KB article I suggested.  Sorry if my explaination was confusing.
0
 
aaalifeAuthor Commented:
sorry, my mistake, i remember thinking, didn't i already read this?  submitted to cust service to see if i can get some points for you.  will pay more attention next time.

thanks
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
no prob..... just was wondering if what I said didn't make sense... (okay... I like being right).  :-)

Thx.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now