Terminal Server Licensing

[Art Billings]

Okay this is a bit complicated to explain but I will try. Environment:
W2K3
SBS, 1 W2K3 server running Terminal Services in Application mode. SBS
server
is the licensing server. Initially the Term Server was configured for per
device licensing, but I have changed it to per user, as the
temporary device licenses are about to expire.

I have noticed that in the Licensing Manager that the server is not issuing
user CALS. Also in the System log I get the following entry:

Terminal Server Licensing on server BIGGUY has not been activated. Terminal
Server Licensing will only issue temporary licenses until the server is
activated.

I first noticed this error message after reactivating the Licensing server,
which I reactivated because my user were getting the message about their
licenses expiring. It concerns me that this event is in the system log,
along with the fact that I do not see any CALs issued in the Terminal Server
Licensing console. The users are no longer getting the expiry notice, but
it
just doesn't feel right.

Am I right to be concerned, or is this normal behaviour? Is there something
else I should do to get the licensing correct. This is a mission critical
function for my users, so any and all help will be very much appreciated,
especially if I can fix it prior to them losing connectivity.

TIA,
Art Billings

[Patrick Rouse]

Per-User TSCALs are unmanaged,so they are not issued to specific users. When
a 2003 TS is in Per-User Mode, it simply checks the TSLS for installed
Per-User TSCALs. If they exist, the session is granted.

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com

Post by Art Billings
W2K3
SBS, 1 W2K3 server running Terminal Services in Application mode. SBS
server
is the licensing server. Initially the Term Server was configured for per
device licensing, but I have changed it to per user, as the
temporary device licenses are about to expire.
I have noticed that in the Licensing Manager that the server is not issuing
Terminal Server Licensing on server BIGGUY has not been activated. Terminal
Server Licensing will only issue temporary licenses until the server is
activated.
I first noticed this error message after reactivating the Licensing server,
which I reactivated because my user were getting the message about their
licenses expiring. It concerns me that this event is in the system log,
along with the fact that I do not see any CALs issued in the Terminal Server
Licensing console. The users are no longer getting the expiry notice, but
it
just doesn't feel right.
Am I right to be concerned, or is this normal behaviour? Is there something
else I should do to get the licensing correct. This is a mission critical
function for my users, so any and all help will be very much appreciated,
especially if I can fix it prior to them losing connectivity.
TIA,
Art Billings

[Art Billings]

Thanks Patrick.

Post by Patrick Rouse
Per-User TSCALs are unmanaged,so they are not issued to specific users.
When
a 2003 TS is in Per-User Mode, it simply checks the TSLS for installed
Per-User TSCALs. If they exist, the session is granted.
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com

Post by Art Billings
W2K3
SBS, 1 W2K3 server running Terminal Services in Application mode. SBS
server
is the licensing server. Initially the Term Server was configured for per
device licensing, but I have changed it to per user, as the
temporary device licenses are about to expire.
I have noticed that in the Licensing Manager that the server is not issuing
Terminal Server Licensing on server BIGGUY has not been activated.
Terminal
Server Licensing will only issue temporary licenses until the server is
activated.
I first noticed this error message after reactivating the Licensing server,
which I reactivated because my user were getting the message about their
licenses expiring. It concerns me that this event is in the system log,
along with the fact that I do not see any CALs issued in the Terminal Server
Licensing console. The users are no longer getting the expiry notice, but
it
just doesn't feel right.
Am I right to be concerned, or is this normal behaviour? Is there something
else I should do to get the licensing correct. This is a mission critical
function for my users, so any and all help will be very much appreciated,
especially if I can fix it prior to them losing connectivity.
TIA,
Art Billings