Problems with the Windows 2003 License Server

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



I have the following problem. I build up a new terminal server farm
based on W2k3 standard SP1 R2. The License server (also W2k3) was
equipped with 400 TS Cals (by user), terminal servers were led by
Registry on some dedicated license server
HKEY_LOCAL_MACHINE \ system \ services \ TermSrv \ parameter \
LicenseServers \ xxxxxxxx)
Now I had downgrade some of the W2k3 Servers for publishing special
application on Windows 2000 Advanced SP4 - I installed further 200
CALS per device, cause the Windows 2000 Server can´t use per user
CALS.
The following Client systems join the farm:
- Published Application on Windows 2000 servers - Windows 2000/Windows
XP Clients
- Published Desktop on Windows of 2003 servers - Windows 2000/Windows
XP Clients/Windows CE Clients
Unfortunately I can´t see any traffic on my license server
(The license server is 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 a license server, since these cannot be indicated (confirmation
comes from ms support an some technical whitpapers)
Also the Windows 2000/Windows XP of devices does not pull a visual
license of the Windows to 2000 servers (published Application) - that
´s also correct, cause each WXP / W2k Client takes a license of the
open license fundus (right? - Information comes also from the
whitepapers)
Only the ThinClient devices (Wyse V30 - Windows CE 5.0) should get a
permanent license from the Server - but I can´t see any use in the
license console
Under W2k3 there is a tool in the resource kit called Lizenztesttool
tsctst.exe - unfortunately there is nothing similar under Windows 2000
-
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 the server pulls only temporary licenses or
something similar (also no reference that the license in xx days runs
off)
b) with the Lsview Tool I see that the right License Server will be
pulled from each Terminalserver
c) Also on the license server no 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 a Windows XP Client to a SecureGateway (presentation
server 4.0)
Via gateway, a published Desktop on a Windows of 2003 server is
started Neither on my Client, nor on the terminal server, a reference
in the Eventlog is shown - only information about successful
FolderRedirections, etc.
Also on the license server shows no entry or a temporary license
(LICENSE00x)
2. Scenario
Connecting at a Wyse ThinClient (Windows CE 5,0) over the
SecureGateway, start a published Desktops on a Windows of 2003 server.
Afterwards a session in session on a published Application (which is
installed on a Windows 2000 Advanced server) is started.
Neither in the Eventlog, nor in the Registry a reference to a
temporary license (neither on the license server, the published
desktop server or the published application server is an entry).
There´s also no entry in the license manager for the use of a
DeviceCAL
All terminal servers are connected by LSView with the correct license
server
The only thing, which I did not make yet (because the server stands
not in my administration), is the registry entry on the site DC
(HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService
\Parameters\LicenseServers\xxxxxxx)
Otherwise I do not get not one information, neither negative nor
positive (even Citrix writes successfully in the Eventlog, that the
license server is successfully addressed by CTX)
Any help would be great
Thank you
Regards
Casey

Actually my problem is, that i´m not sure, if the license server 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 :)

.



Relevant Pages

  • RE: RWW problem on one Client machine
    ... Welcome to SBS newsgroup. ... services licensing service on a Windows 2000 domain controller. ... terminal license successfully. ... messages in the event log saying that "A terminal license server cannot be ...
    (microsoft.public.windows.server.sbs)
  • Re: Anonymous connections.
    ... Windows Server 2003 Licensing Server can control ... you may use the New External Connector License option. ... Microsoft Partner Support ...
    (microsoft.public.windows.terminal_services)
  • Re: Multiple TS license servers in the same domain
    ... We have our own Windows 2003 Terminal Servers, ... there was no Windows 2003 Terminal Services License ... Server in the domain and we set up our own TS License server and added the ...
    (microsoft.public.windows.terminal_services)
  • Re: [SLE] Microsoft Terminal Server access from SuSE 9.3
    ... >> problem by logging on locally and checking the event logs for license ... > Just my friend came to visit me and with his laptop with Windows XP I ... > connected with RDC to my server with my name and passw without trouble...? ... get 2 TSCALs for access, for remote admin only of course. ...
    (SuSE)
  • RE: RWW problem on one Client machine
    ... I think we are looking for something on his client. ... > services licensing service on a Windows 2000 domain controller. ... > terminal license successfully. ... > messages in the event log saying that "A terminal license server cannot be ...
    (microsoft.public.windows.server.sbs)