Earlier today I asked:
> I'm seeing this on a Windows 2003 Terminal Server. My
> license server
> is an activated Windows 2003 DC. Odd thing: Note the date of the
> event, and the date of expiration noted in the Event Description.
>
> So is this a red herring, or a real problem? (I have done License
> server discovery registry trick as per the MS KB article).
>
>
> Event Type: Warning
> Event Source: TermService
> Event Category: None
> Event ID: 1009
> Date: 10/25/2004
> Time: 11:35:15 AM
> User: N/A
> Computer: TULCTX1
> Description:
> The terminal server licensing grace period is about to expire on
> 10/22/2004 and the service has not registered with a license server
> with installed licenses. A terminal server license server
> is required for continuous operation. A terminal server can operate
without a
> license server for 120 days after initial start up.
After talking with MS (free call, btw, since it's a licensing issue. I
guess MS feels too guilty to charge $$ to fix problems with their weird
licensing scheme)
This error is actually a false alarm. It occurs because of the way that
Windows 2003 handles (or doesn't handle, actually) per-user TS CAL's.
Although you can set up per-user TS 2003 CALs in a license server, they
are not actually handed out or tracked. This functionality was rumored
to be added in perhaps in Service Pack 1 for Windows 2003 server, but
the MS guy I talked with today said definitely not in SP1, and probably
not for quite a while after that.
In the meantime, the TS 2003 Terminal Server, which has been set to use
Per User licensing as well, is simply reporting that it cannot find a
license server with Per User CALS on it. This is both true and false,
since there really IS an activated 2003 license server with Per User
CALs on it, but those CALs are not actually managed/tracked by the
license server. In reality the Terminal Server should not be issuing
this error message. The MS guy acknowledged this is a bug in Windows
2003 Terminal Services but did not offer a timeframe for a hotfix or
general fix.
He gave me a registry entry to prevent the message from appearing any
further:
In HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters, create
a DWORD value called LicensingGracePeriodEnded, and set the value to 0.
This will prevent the license expiration warning message from appearing
in the Event Log.
Hope that helps someone in the future!
********************************************************
This Weeks Sponsor Emergent Online ThinCity Conference
Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology
Conference
http://www.ThinCity.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
