Prev: Finding the rdp port
Next: msrdp object and SendKeys
From: colorado99 on 5 Mar 2007 14:56
I have terminal server licenses that have lifetimes as long as 439 days.

I understand that temporary licenses should be issued for 90 days and
permanent
licenses should be issued for 52-89 days. However, this does not appear to be
happening and is causing failures.

I have 30 Neoware thin clients and 40 TS device licenses (plus 35 Metaframe
FR3
licenses and Windows CALs).

In December of last year (2006) I noticed that I had a large number of
temporary licenses issued. After a quick search I found Q253292 describing a
problem where older TCs failed to retain their license in the WinCE object
store. My units were obtaining a new temporary license each time a user
logged in to the network.

All 40 of my permanent licenses and approximately 750 temporary licenses were
allocated. Numerous licenses were assigned to each device. Reviewing
lsreport output and the Licensing tool, I saw multiple licenses allocated to
"DEFAULT_WINCE" and to each TC by name.

I contacted Neoware and purchased firmware upgrades. This resolved the
problem
of multiple licenses and I expected the problem to work itself out over the
next 90'ish days.

As expected the number of temporary licenses allocated has dropped to 380 over
the past 60'ish days. However, now, I have devices that are unable to obtain
any type of license.

Another detailed review of lsreport output indicates licenses that will not
expire for as much as 439 days. Some, but *NOT* all of these are listed as
"upgraded". The 91+ day licenses that are not "upgraded" are all temporaries.

Lsreport shows the following:
28 active licenses
12 upgraded licenses
380 temporary licenses

Total 420

I see the following errors in my logs:
Event ID 21 on my TS licensing server. This makes senses given that no
permanents are available.

Event ID 1011 and 1004 on the terminal servers (separate machines from license
server). No information is provided at the thin client when these are
logged.

I've reviewed numerous Q articles and CTX articles, including, but not limited
to the following:

Q722499 - Event ID 1028, I had a few of these April 2006, none since then.
My TS programs and DLL files are version 5.2.3790.1830 so this one is ruled
out.

Q917915 - Possible, since this hotfix updates TS programs/DLLs to
5.2.3790.2680
My servers are logging 1004 and 1011 messages. My licensing server has a Gb
Ethernet card. It is running at 100 Mbps and the article doesn't say whether
that matters. None of the terminal servers have Gb Ethernet cards.

Q884570 - Event ID 1004. This describes the problem exactly, however, the
hotfix updates the LServer.exe and Tls236.dll to *OLDER* versions than I have
so this one is ruled out.

Q834651 - Add/Remove windows component causes TS mode to be invalid. The
registry key described does *NOT* exist on my servers. Creating the key makes
no difference. Also, the hotfix would update Tsoc.dll to an *OLDER* version
than I have ruled this one out.

Furthermore, I've reviewed and investigated articles describing similar
symptoms caused by:

the TS license mode set incorrectly, for example Servers=USER and
License=DEVICE. This is not the problem based upon a review of the
appropriate registry entries and the TS configuration panels.

incorrect permissions on HKLM\SOFTWARE\Microsoft\MSLicensing
incorrect permissions on HKLM\SOFTWARE\Citrix\MSLicensing
The key under Citrix did not agree with CTX105657, so I modified the
permissions to match the article. This did not resolve the issue and I have
reset the key to its original ACL

license server discovery problems
The TS Configuration panel indicates the license server is being properly
discovered via AD. However, I set the appropriate registry key (PolicyAcOn
was not present by default) to point to the IP address of the server and
tested. This did not resolve the problem and I removed the key. I copied
LSView to all the TS servers and checked discovery. Despite the fact that
the TS Configuration panel stated the license server was discovered via AD,
LSView was blank. I then used the TS Configuration panel to set the IP
address of the license server and tested again with LSView. LSView indicated
the licensing server could be found. I've left the servers pointed to the IP
address of the licensing server via the TS Configuration panel.

Network communications, invalid MTU
No server or TC has MTU set via registry or control. MTU on my network 1,472
bytes as expected. Furthermore, the TS license is resolvable via AD
integrated
DNS and BIND DNS (AD primary, BIND secondary).

RDP vs. ICA
Testing with the RDP client on the thin clients exhibited the same issues
(event ID 1011). I have ruled out Citrix as the culprit.

Some of the above issues and fixes are referenced in CTX564283 -
"Troubleshooting 1003 and 1004 Terminal Server Licensing Errors".

I have not deployed the RDP v6 client to any of our machines, see CTX112347.

I've watched ProcessMonitor during the login attempts to try to discover the
problem and do not see anything helpful there.

Other key facts:

TS licensing server - Server 2003, PDC emulator with FSMO roles and DFS root
(no files stored here though). This server is in the main office of a hub and
spoke network.

A second DC is the terminal server with Server 2003 R2 and Metaframe XPe FR3.
This machine is the bridgehead for the site (KCC generated).

All branch office terminal servers (7) are identical the main site TS, Server
2003 R2 with Metaframe XPe FR3.

Th Neoware TCs are running:
Win CE 5.0
RDP 5.5
ICA Client 8.33

I'd appreciate some thoughtful guidance on this issue.
From: colorado99 on 7 Mar 2007 15:43
After contacting PSS, it was determined that a hotfix was required
(KB911288) for the TS license server. In addition, the TS licensing database
was corrupt due to the original firmware issue. Recreating the database
(KB283566) fixed this problem.
From: Vera Noest [MVP] on 7 Mar 2007 17:18
Thanks for posting the result here, colorado99!
I hope that your licensing troubles are over now :-)

I assume that you mean KB 273566 - How to rebuild Windows 2000 and
2003 Terminal Services Licensing database
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Y29sb3JhZG85OQ==?=
<colorado99(a)discussions.microsoft.com> wrote on 07 mar 2007 in
microsoft.public.windows.terminal_services:

> After contacting PSS, it was determined that a hotfix was
> required (KB911288) for the TS license server. In addition,
> the TS licensing database was corrupt due to the original
> firmware issue. Recreating the database (KB283566) fixed this
> problem.
From: colorado99 on 11 Mar 2007 01:40
> I assume that you mean KB 273566 - How to rebuild Windows 2000 and
> 2003 Terminal Services Licensing database

Correct! I do mean KB273566
 | 
Pages: 1
Prev: Finding the rdp port
Next: msrdp object and SendKeys