Re: Problems with the Windows 2003 License Server

Tech-Archive recommends: Fix windows errors by optimizing your registry

i.edelmann@xxxxxxxxxxxxxx wrote on 20 feb 2007 in
microsoft.public.windows.terminal_services:

On 19 Feb., 21:07, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
Everything is fine, and you will never see any of the purchased
licenses being issued.

Here's what happens:

* all clients connecting to the 2003 TerminalServerwill use a
Per User TS CAL. Since these Per User TS CALs are not managed,
you will not see them appear in the TS Licensing Manager

* the clients connecting to the W2K TerminalServerare running
W2K Pro or XP Pro, and thus do not need a purchased TS CAL.
They receive a free TS CAL from the built-in pool. Check in TS
Licensing Manager the line that's called "ExistingWindows2000
Per Device TS CALs Tokens)". So there was no need to install
the 200 Per Device TS CALs, since you have no clients who need
them. The only potential clients for these TS CALs would be
yourWindows CE thin clients, but they connect only to the 2003
TS, according to your post.

Hope this reassures you that all is well. And be assured that
licensingproblemsare *always* recorded in the EventLog. No news
is good news, in this case!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - TerminalServer
TS troubleshooting:  http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

i.edelm...@xxxxxxxxxxxxxx wrote on 19 feb 2007 in
microsoft.public.windows.terminal_services:



I have the following problem. I build up a new terminalserver
farm based on W2k3 standard SP1 R2. TheLicenseserver(also
W2k3) was equipped with 400 TS Cals (by user), terminal
servers were led by Registry on some dedicatedlicenseserver
HKEY_LOCAL_MACHINE \ system \ services \ TermSrv \ parameter
\ LicenseServers \ xxxxxxxx)
Now I had downgrade some of the W2k3 Servers for publishing
special application onWindows2000 Advanced SP4 - I installed
further 200 CALS per device, cause theWindows2000Servercan´t
use per user CALS.
The following Client systems join the farm:
- Published Application onWindows2000 servers -Windows
2000/WindowsXP Clients
- Published Desktop onWindowsof 2003 servers -Windows
2000/WindowsXP Clients/WindowsCE Clients
Unfortunately I can´t see any traffic on mylicenseserver
(Thelicenseserveris activated and registered - the CALS are
also registered and activated.
I have the following effect: I see no effect on using user
CALS anyway in alicenseserver, since these cannot be
indicated (confirmation comes from ms support an some
technical whitpapers) Also theWindows2000/WindowsXP of
devices does not pull a visuallicenseof theWindowsto 2000
servers (published Application) - that ´s also correct,
cause each WXP / W2k Client takes alicenseof the
openlicensefundus (right? - Information comes also from the
whitepapers) Only the ThinClient devices (Wyse V30 -WindowsCE
5.0) should get a permanentlicensefrom theServer- but I
can´t see any use in thelicenseconsole
Under W2k3 there is a tool in the resource kit called
Lizenztesttool tsctst.exe - unfortunately there is nothing
similar underWindows2000 -
To be safe, that a licenses will be pulled - Can I make a
test connection with the help of a Tool or "visualize" the
use of licenses on my W2k3 Licenseserver?
Thank you for the assistance
PS: It comes
a) no reference in the Eventlog of the respective terminal
servers, which would show me, that theserverpulls only
temporary licenses or something similar (also no reference
that thelicensein xx days runs off)
b) with the Lsview Tool I see that the rightLicenseServerwill
be pulled from each Terminalserver
c) Also on thelicenseserverno temporary licenses are
contained, which would show me, which is not correct

The Eventlogs on the Clients does not say nothing at all. The
Eventlogs on the terminal servers says only the Eventlog
entry 4193 Ms DTC was started with the following attitudes
(OUT = 0 and = a 1): Safety configuration: Network
administration of transactions = 0, Netzwerkclients = 0,
Detailed one distributed transactions with the help of system
MSDTC minutes = 0, Outgoing distributed transactions with the
help of system MSDTC minutes 0, Transaction Internet Protocol
(TIP) = 0, XA-transactions = 1 Filtering of duplicated events
= 1 Further information about the assistance and support
services receives you

Otherwise I tested the following scenarios today:
1. Scenario
Connection over aWindowsXP Client to a SecureGateway
(presentationserver4.0)
Via gateway, a published Desktop on aWindowsof 2003serveris
started Neither on my Client, nor on the terminalserver, a
reference in the Eventlog is shown - only information about
successful FolderRedirections, etc.
Also on thelicenseservershows no entry or a temporarylicense
(LICENSE00x)
2. Scenario
Connecting at a Wyse ThinClient (WindowsCE 5,0) over the
SecureGateway, start a published Desktops on aWindowsof 2003
server. Afterwards a session in session on a published
Application (which is installed on aWindows2000 Advanced
server) is started. Neither in the Eventlog, nor in the
Registry
a reference to a temporarylicense(neither on thelicense
server, the published desktopserveror the published
applicationserveris an entry). There´s also no entry in the
licensemanager for the use of a DeviceCAL
All terminal servers are connected by LSView with the correct
licenseserver
The only thing, which I did not make yet (because theserver
stands not in my administration), is the registry entry on
the site DC
(HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermServ
ice \Parameters\LicenseServers\xxxxxxx)
Otherwise I do not get not one information, neither negative
nor positive (even Citrix writes successfully in the
Eventlog, that thelicenseserveris successfully addressed by
CTX) Any help would be great
Thank you
Regards
Casey

Actually my problem is, that i´m not sure, if
thelicenseserver works correctly - i have no message, which
tells me, that something is not working, but the statement of
microsoft isn´t really satisfactoring. So i want to be 100%
sure, that everything works fine :)- Zitierten Text
ausblenden -

- Zitierten Text anzeigen -

Cool,
it is now working ï?? i installed some 2003 ts cals per device
and the licenses will be given correctly to the clients.
Only one thing is not working:
I start a session over the thin client (connecting on W2k3
published desktop), after this, I start a session into session
on a Windows 2000 published application.
I got a temporary license on the Windows 2003 Server, where the
published app was started via the desktop. On the W2k Server,
the license server was hardcoded written in the registry under:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService
\Parameters
REG_SZ DefaultLicenseServer Name of the Server.
The X509 Cert will be pulled successfully from the server.
Is this parameter right?

Now you've got me all confused!
Why did you install Per Device licenses? Which type of licenses do
you want? And most important: in what licensing mode is your 2003
Terminal Server? If it was in Per User licensing mode, as I
assumed, given the fact that your 2003 licenses were Per User, then
the LS should *not* issued the newly installed Per device licenses.
And vice versa, if the 2003 TS is configured in the Per Device
mode, it will not "see" the Per User licenses. Mixing 2003 Per User
and 2003 Per Device TS CALs doesn't make sense with a single 2003
TS.

The first connection from any device always gets a temporary
license. This is by design, to avoid that licenses can be taken by
unauthorized access attempts.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
.

Relevant Pages

  • Re:TS Cals ex- und importieren
    ... wie ich unter W2k Server Terminalserver Lizenzen ... Q. How do I move my licenses from one licensing server to another? ... Siehe doch die ganze Aktion als Anlass, ...
    (microsoft.public.de.german.windows.terminaldienste)
  • Re: Problems with the Windows 2003 License Server
    ... purchased licenses being issued. ... "ExistingWindows2000 Per Device TS CALs Tokens)". ... you have no clients who need them. ... server) is started. ...
    (microsoft.public.windows.terminal_services)
  • Re: TS 2000 Workgroup server
    ... The new client PCs are all XP Pro. ... What OS are these new clients running? ... "Existing Windows 2000 TS CALs" on the TS Licensing Server. ... running out of licenses. ...
    (microsoft.public.windows.terminal_services)
  • RE: Some Remote users cant login
    ... Maybe the other clients are running on ... Verify in your TS Licensing Manager which type of licenses have ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Citrix server at another site from the WinXP system. ...
    (microsoft.public.windows.terminal_services)
  • Re: Problems with the Windows 2003 License Server
    ... all clients connecting to the 2003 TerminalServerwill use a Per ... CALs Tokens)". ... W2k3) was equipped with 400 TS Cals, terminal servers ... that a licenses will be pulled - Can I make a test ...
    (microsoft.public.windows.terminal_services)