license questions

[Guest]

Hi,
I started out with one server running licensing for another Win2k term
application server . They are both Win2k. I added a new Win2003 terminal
application server in January, and did not change any of the licensing at
that point because I did not want to disrupt the existing win2k term server.
I did purchase 25 CALs in January. Yesterday users could not access the
win2003 term server, ther error message said a licensing server could not be
reached. I checked into the win2k licensing server, tried to
deactivate/reactivate the server, but recieved errors. So...I then stopped
the term licensing service on the win2k server, and installed terminal
service license service on the win2003 server, activated and installed the 25
user CALs. Now on the licensing server (win2003, also the new term
application server) I have 3 license groups. 1 - Existing win2k per device -
built in -unlimited. 2 - Temp licenses win2003 server per divice temporary.
3 - Win2003 perr user CAL tokin - quantity 25. All of the users that are
connecting are going under the temporary group, not in the 25 CAL user group.
What do I need to do before they expire? Why do the not get issued a CAL
from the 25 user pool? Does this have something to do with them usiing the
other server before and having an existing license?
Thanks - Sorry for all the details, but I am not sure what is revelant.

 

[Guest]

OK - now I have MORE trouble...I reviewed KB 822134 from an earlier post, and
checked the win2003 terminal server properties, and it was set up for
per-device. I changed it to per-user, and then users on a remote site - not
part of the domain yet - could not connect. Even an enterprise admin account
could not connect. The error message was that "they do not have permission
to connect". I then changed the win2003 terminal server properties back to
per-device, and the users can connect - However - they now get a message that
the temp license will expire in 5 days. HELP !!!!!!!

 

[Vera Noest [MVP]]

You definitively have to put the 2003 Terminal Server into the "Per
User" licensing mode, otherwise your purchased Per User licenses
will never be issued.
So concentrate on solving the permission problem.

Have you checked the EventLog on the 2003 TS? It will probably give
you more details. How about users on the local subnet (the same
subnet as the TS is on)? Can they connect when the TS is in Per
User licensing mode?
Try if removing the existing temporary Per Device TS CAL from the
registry of the client helps:

187614 - Removing Terminal Server Licenses from an RDP Client
http://support.microsoft.com/?kbid=187614

 

[Guest]

Hi
I verified that I was unable to connect on the local subnet, while in the
"user cal" mode. As soon as I change it back I can get in. I checked the
access properties for the connection, and they are OK. I do get a couple of
strange messages in the event log while in "user cal" mode. Event id 1010 -
The terminal server could not locate a license server... and 1008 - The
terminal server licensing grace period has expired and the service has not
registered with a license server with installed licenses...When I switch the
mode back the messages go away. I ran lsreport and it did find the license
server (which is on the 2003 member server running treminal server also). I
think I ran this while it was in "device cal" mode, not user cal mode... I
will try and run it in "user mode" tomorrow, and I can try removing the
client license also. I did some checking and found the start of the problem
- I did not install a license server on the 2003 box, which we set up 120
days ago yesterday.
Thanks again

 

[Vera Noest [MVP]]

This should help:

279561 - How to Override the License Server Discovery Process in
Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

 

[Guest]

Hi,
Well, I changed the mode back to "user cal" and ran Lsview and it found the
license server. I then the added the server name per KB 279561, rebooted,
and am now able to get in from the local subnet, while the server is in "user
cal" mode. I am not sure if just rebooting after I changed the mode to "user
cal" would have worked, I was not able to try that yesterday. The
documentation says you should be able to change the mode without a restart,
but...Anyway, now on to another issue with this. When I ran RDC and got into
the terminal server from 2 machines that had not been on before, they were
not issued temp cals like all the rest had been. I have noticed in previous
posts you do not see who a cal is issued to, but there is nothing in the
license section under user cal on the license server, so how do I track
usage?
Thanks for your help - Wayne

 

[Vera Noest [MVP]]

OK, you seem to have solved the licensing problem.

Currently, Per User licenses are unmanaged, and you have to keep
track of the usage manually.
Check this article, it explains that after you have switched
licensing mode on the TS, your Per User TS CAL count will not be
decremented:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---