Re: Terminal Server Licensing.
- From: "Simon Harpham" <SimonHarpham@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Oct 2005 04:40:03 -0700
Thanks for that - it didn't solve the problem, but in the process of trying
to figure out what's going on we've noticed the following. The client that's
got this problem connects to a 2003 /and/ a 2000 server simultaneously (via 2
separate sessions). 2003 has given this PC a 2003 license for its 2003
session, and has allocated it a temporary 2000 license for its 2000 session.
1) Why doesn't 2003 TS Licensing just let the client use 1 license for both
sessions? It's a Per Device license, isn't it?
2) I'm guessing that the way we'll have to fix this is to purchase and
install some 2000 TS CALs ... is that correct?
(Incidentally - to answer your prevous points:
1) I checked the Group Policy setting for our Domain controller - it's set
to 'Disabled', which (according to Group Policy Management) means that
default behaviour is being enforced (where "default behaviour" means "2003 TS
licensing will allocate a 2000 TS CAL when no 2000 TSL CALs are available".
2) Local storage of the client license token isn't an issue here. The reason
I think that is that all clients boot from the same Linux bootstrap, and all
operate identically from the point of view of TS / Windows. Thus if one
client's affected, I'd expect them all to be affected. But no other clients
are affected, so the problem's must be unrelated to local storage of the
license token.)
"Vera Noest [MVP]" wrote:
> OK, I've edited your table to make it more readable (see below), and
> it is obvious that you have enough free TS CALs available.
>
> I can see two reasons for your problems:
>
> 1) Your clients connect to a W2K TS. They run Linux, so they need a
> purchased TS CAL. You do *not* have purchased W2K TS CALs (only
> "Existing W2K built-in TS CALs", but you can't use those for your
> Linux clients).
> Now you *do* have enough 2003 TS CALs, and by default, the 2003
> Licensing Server issues a 2003 TS CALs if no W2K TS CALs are
> available. But it is possible to change this behaviour in a Group
> Policy setting. Allthough this is unlikely as a cause for your
> problem (you would probably know it if you had changed the default),
> check to be sure:
>
> Prevent License Upgrade Policy
> Computer Configuration/Administrative Templates/Windows
> Components/Terminal Services/Licensing
>
> If the status is set to Enabled, when a terminal server running
> Windows 2000 requests a license, but no Windows 2000 TS CAL token is
> available, a temporary CAL is issued if the client has not already
> been issued a temporary CAL. Otherwise, no CAL is issued and the
> client is refused connection.
>
> 2) The most likely cause of the problem lies not in the Terminal
> Server or the Licensing Server, but in the clients. You have to be
> able to locally store the license token on the client. I'm not
> familiar with your client type. On Windows clients, the license is
> stored in the registry, and users must have Write permission on that
> particular key.
> On older thin clients, the firmware must be updated to be able to
> store the license.
>
> Maybe someone with more experience with Linux clients will jump in.
> _________________________________________________________
> 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?U2ltb24gSGFycGhhbQ==?="
> <SimonHarpham@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 14 okt 2005 in
> microsoft.public.windows.terminal_services:
>
> > I think the answer is 'yes', but don't just take my word for it
> > - here's what Terminal Server Licensing says:
> >
> > Product Type Total Available Issued
> > Existing W2K TS CALs (per device)
> > Built-in Unlimited Unlimited 1
> > Temporary 2003 TS CAL Token (per device)
> > Temporary - - 3
> > Temporary 2003 Per Device TS CAL Token
> > Temporary - - 26
> > 2003 Per Device TS CAL Token
> > Open 30 21 9
> > 2003 Per Device TS CAL Token
> > Open 2 0 2
> > 2003 Per Device TS CAL Token
> > Open 30 4 26
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> 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 no 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?
>
.
- References:
- Re: Terminal Server Licensing.
- From: Vera Noest [MVP]
- Re: Terminal Server Licensing.
- From: Simon Harpham
- Re: Terminal Server Licensing.
- From: Vera Noest [MVP]
- Re: Terminal Server Licensing.
- Prev by Date: Hotbar - How?
- Next by Date: Re: Bandwidth for a 2003 ts server
- Previous by thread: Re: Terminal Server Licensing.
- Next by thread: Re: Terminal Server Licensing.
- Index(es):
Relevant Pages
|
