Windows 2003 Terminal Service Issuing Temporary Licenses

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Hi,

Hope someone can help me. I have a windows 2003 Terminal Service
Licensing server and 2 Windows 2003 Terminal Servers. My licensing
server continues to hand out temporary licenses. We have 150 User
CALs. All three servers are set to "per user" for their licensing
mode. I have followed this document to manually configure each server
to discovery the license server.
http://support.microsoft.com/kb/279561/EN-US/
This did not help. Is there a way to know if the Terminal Servers are
actually finding the Licensing server?

We currently have 256 temporary licenses. On the Terminal Service
Licensing Server I get the following event entry.
Event Type: Warning
Event Source: TermServLicensing
Event Category: None
Event ID: 21
Date: 5/12/2005
Time: 4:17:18 PM
User: N/A
Computer: <server-name>
Description:
The Terminal Server Licensing server <server name> has no permanent
licenses for product 'Windows Server 2003 - Terminal Server Per Device
CAL Token'. Use Terminal Server Licensing administrative tool to
register more licenses.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Any ideas? I'm at the end of my rope so to speak. If you need more
information please let me know.

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

This line reveals the cause of the problem:
> .. has no permanent licenses for product 'Windows Server 2003 -
> Terminal Server Per Device CAL Token ...

The TS is looking for Per Device TS CALs, not Per User TS CALs.

I know that you wrote that the TS is using the Per User licensing
mode, but have you checked if that is still true? There is a bug in
2003 which can make it switch licensing mode. If that's your
problem, get the hotfix.

834651 - Terminal Services licensing mode changes from Per User or
from Per Device to an invalid value after you add or remove a
Windows component
http://support.microsoft.com/?kbid=834651

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

"b33gopher" <b33gopher@gmail.com> wrote on 13 maj 2005 in
microsoft.public.windowsnt.terminalserver.connectivity:

> Hi,
>
> Hope someone can help me. I have a windows 2003 Terminal
> Service Licensing server and 2 Windows 2003 Terminal Servers.
> My licensing server continues to hand out temporary licenses.
> We have 150 User CALs. All three servers are set to "per user"
> for their licensing mode. I have followed this document to
> manually configure each server to discovery the license server.
> http://support.microsoft.com/kb/279561/EN-US/
> This did not help. Is there a way to know if the Terminal
> Servers are actually finding the Licensing server?
>
> We currently have 256 temporary licenses. On the Terminal
> Service Licensing Server I get the following event entry.
> Event Type: Warning
> Event Source: TermServLicensing
> Event Category: None
> Event ID: 21
> Date: 5/12/2005
> Time: 4:17:18 PM
> User: N/A
> Computer: <server-name>
> Description:
> The Terminal Server Licensing server <server name> has no
> permanent licenses for product 'Windows Server 2003 - Terminal
> Server Per Device CAL Token'. Use Terminal Server Licensing
> administrative tool to register more licenses.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Any ideas? I'm at the end of my rope so to speak. If you need
> more information please let me know.

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Vera Noest,

thanks for the reply. I did check this on all servers prier to
writing the to this group. The values on both terminal servers are
corerct as well as on the terminal server licensing server. That's why
this is so confusing to me. According to microsoft there is no way to
track the "per user" licenses used right? And if you h appen to run
out of licenses there is no notification or restriction from Microsoft
letting you know. The license management is on the honor system. So,
the possiblity of us running out of licenses I presume is out of the
question. Any other thoughts?

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

So the value of HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
\TerminalServer\Licensing Core\PolicyAcOn on the Terminal Servers
equals 4?

If that's the case, I have no idea what is going on, because your
TS is definitively looking for Per Device TS CALs.
I would call Microsoft Support.

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

"b33gopher" <b33gopher@gmail.com> wrote on 16 maj 2005 in
microsoft.public.windowsnt.terminalserver.connectivity:

> Vera Noest,
>
> thanks for the reply. I did check this on all servers prier to
> writing the to this group. The values on both terminal servers
> are corerct as well as on the terminal server licensing server.
> That's why this is so confusing to me. According to microsoft
> there is no way to track the "per user" licenses used right?
> And if you h appen to run out of licenses there is no
> notification or restriction from Microsoft letting you know.
> The license management is on the honor system. So, the
> possiblity of us running out of licenses I presume is out of the
> question. Any other thoughts?

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Yes, the registry entry on all servers show 4. Does anyone else have
any ideas?