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 20 Feb., 17:18, i.edelm...@xxxxxxxxxxxxxx wrote:
On 20 Feb., 14:09, i.edelm...@xxxxxxxxxxxxxx wrote:

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 Clie
nt
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\Term
Service \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 an
d 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\TermServi
ce \Parameters
REG_SZ DefaultLicenseServer Name of the Server.
The X509 Cert will be pulled successfully from the server.
Is this parameter right?- Zitierten Text ausblenden -

- Zitierten Text anzeigen -

The other thing i have detect is, that after starting a
published application over a windows XP Prof Clientsystem on a
windows 2000 Server - the client system (winxp) also gets a
temorarily license (LICENSE000) - is this also correct or are
there probs with the license server - (again no information in
the eventlog and i can log on successfully to the app)

Greetz
Casey- Zitierten Text ausblenden -

- Zitierten Text anzeigen -

last but not least - i found the exact comment from ms for using
tscals under winxp pro /w2k

Windows 2000 Professional or Microsoft Windows XP Professional
License: This license permits the installation of Windows 2000
Professional or Windows XP Professional, in addition to
providing the legal right to access Terminal Services on a
Windows 2000-based server. A computer that is running a licensed
copy of Windows 2000 Professional or Windows XP Professional
does not require a Terminal Services Client Access License

From the licensing side means this, i am safe with my
configuration -
will this open licenses be shown as LICENSE000 for me?

Greetz and thanks for your support

This information is a bit misleading. You *do* need a TS CAL for
these clients, but you don't have to purchase it. These clients
receive a free TS CAL from the built-in poll of licenses, as I
wrote in my first reply.

_________________________________________________________
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: Problems with the Windows 2003 License Server
    ... purchased licenses being issued. ... "ExistingWindows2000 Per Device TS CALs Tokens)". ... Now I had downgrade some of the W2k3 Servers for publishing ... server) is started. ...
    (microsoft.public.windows.terminal_services)
  • Re: CAL Q.
    ... > SBS licenses can be organized by user, device, or a combination of user ... Define that entity which you claim the server ... What if both user CALs and device CALs are used? ...
    (microsoft.public.windows.server.sbs)
  • Re: CAL
    ... If you just have the 5 CALs that came with the server, ... So SBS can tell which one you've bought based on the license code? ... You go and you buy 10, 'per user, CALs. ... it's up to you to keep track of the licenses. ...
    (microsoft.public.windows.server.sbs)
  • Re: What is the best licensing option for TS?
    ... which will cost you a lot more than the 2003 TS CALs. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... I don't mind eating the licenses if in the long run I am better ... I have read that XP Pro clients come with a built in TS ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... licenses, I didn't understand that installing your TS CALs in Per ... problem with the XP clients. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)