Re: Terminal Server Licensing.
- From: "Vera Noest [MVP]" <Vera.Noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 14 Oct 2005 07:04:41 -0700
You leave out one vital piece of information:
do you have any free Windows 2000 or Windows 2003 TS CALs
installed on the TS Licensing Server?
A device can only *once* receive a temporary license. When the
temporary license has expired (after 90 days) you must have a
permanent (purchased) TS CAL available on the Licensing Server.
You cannot renew a temporary license.
There's not hotfix for this :-)
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
"=?Utf-8?B?U2ltb24gSGFycGhhbQ==?=" <Simon
Harpham@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 14 okt 2005:
> Hi. We run a mixed Windows and Linux network and are having a
> problem with terminal licensing.
>
> First off, some details about our operating environment:
>
> We have three servers:
>
> 1) Windows 2003 Server domain controller (no SP) running
> terminal services in Per Device mode.
>
> 2) Windows 2000 Server (SP 4) running terminal services in
> Application mode.
>
> 3) Red-Hat Linux version 2.6.5-1.358
> (bhcompile@xxxxxxxxxxxxxxxxxxxxx) (gcc version 3.3.3 20040412
> (Red Hat Linux 3.3.3-7))
>
> All dumb-terminals PXE-boot from Linux, which starts 'X' and
> redirects the terminal to windows terminal services running on
> server #2 (above). At which point terminal services logs both an
> information and warning message to Server#2's event log with
> same event ID, viz: event ID 1004 "The terminal server cannot
> issue a client license."
>
> I've checked terminal server licensing on the Windows 2003
> computer (the server that's doing terminal server licensing for
> our domain), and the terminal in question has been allocated a
> "Temporary License for Windows 2000 Server - Terminal Services
> CAL Token (Per Device)" - this license has now expired.
>
> I've had a look at the various licensing tools provided with
> Windows but none of them give me the option of renewing these
> temporary licensing, and don't provide much information as to
> why the problem's happening in the first place.
>
> I've searched on Microsoft.com for help to do with this issue
> but the help has left me more confused than when I started.
> Apparently I can fix my problem by either:
>
> 1) Restarting terminal server licensing on the licensing server,
> waiting 15 minutes for the licensing clear-up thread to run, and
> then retrying. This didn't work.
>
> 2) Ringing Microsoft for a hotfix. This hotfix applies to
> Windows 2000 servers however, so I have my doubts it'll do the
> job as the server that's running the T/S licensing service is a
> Windows 2003 server.
>
>
> Does anyone have any other ideas I can try before I ring the MS
> helpline?
.
- Follow-Ups:
- Re: Terminal Server Licensing.
- From: Simon Harpham
- Re: Terminal Server Licensing.
- Prev by Date: Re: mapping drive letter to local user's home directory
- Next by Date: Re: Changing from Remote Admin Mode to Application Mode
- Previous by thread: printer permissions and auditing in win2000 TS?
- Next by thread: Re: Terminal Server Licensing.
- Index(es):
Relevant Pages
|
Loading
