Terminal Server Licensing Problem

I have 2000 running Terminal Services.  The server is set up with 99 Per Seat licenses and Terminal Server Licensing service is started.  However, not one can connect via RDP using their Terminal Server Client to my server -the server is not issuing temporary client licenses to them.  Am I missing something here?  Does it need to be set up for Per Server?  Can I go back?
SilasAsked:
Who is Participating?
 
elischConnect With a Mentor Commented:
Do you have a licensing server?  If this is your first/only terminal server you need to install the Terminal Server Licensing piece.  YOu will then need to connect to Mirosoft and register your terminal server.  They will then e-mail you an activation code which you will need to enter on the server.  This will enable the server to issue a seat license when someone logs on.
0
 
geoffrynCommented:
Did you register the licensing service with AD and setup the licenses?
0
 
SilasAuthor Commented:
AD is not set up on this server -it is a stand-alone.
0
 
HousenetCommented:
-Did you active the server & give your license authorization number etc to MS for a lisence code ?
0
 
SilasAuthor Commented:
The problem is the actual 2000 licensing.  It is my understanding that Terminal Server licensing gets its temporary licenses from the per server license pool and then hands them out -the problem is, the server is set to per-seat, therefore, no licenses are available.  What do I do?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.