Re: Windows 2003 Terminal Licensing Server not issuing licenses
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 07 Jan 2006 11:24:47 -0800
I assume that your clients are *not* running W2K Pro or XP Pro, but
an older Windows OS, Linux, Macintosh, or are thin clients?
All of your 3 points are true, and you *do* have a problem.
In chronological order:
3. Yes, your clients will still have a valid license, and can
connect because of that.
1. When those existing licenses expire, the clients will *not*
receive a temporary license, and they will *not* be able to renew
their permanent licenses, since W2K Terminal Servers cannot use Per
user TS CALs. The clients will be refused a connection.
If you have Software Assurance on your TS CALs, you can phone the
Clearinghouse and get your licenses re-issued as Per Device
licenses. Event if you do not have SA, it is worht a try, since it
has been reported here that the Clearinghouse often replaces
licenses even if you officially don't have the right to switch
them.
2. Is also true, Per User licenses are unmanaged, and therefor you
don't see the number of available licenses decrease, but this
applies only to a 2003 TS.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?cks=?=" <rK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 07 jan
2006 in microsoft.public.windows.terminal_services:
> Hi,
>
> Previously I had 3 Windows 2000 Terminal Servers with each one
> running their own Terminal Services Licensing Server on the same
> machine. These were all member servers in an NT domain. After
> upgrading to Windows 2003 AD, I realised that the licensing
> servers need to be installed on the domain controllers because I
> could no longer see the licensing servers after the domain
> upgrade.
>
> I installed Terminal Services Licensing on the Windows 2003
> Domain Controller and re-activated all the TS CALs again. The
> CALs were registered as USER CALs in the Licensing server.
>
> However, the amount of CALs shown in the Terminal Services
> Licensing Manager does not decrease even when users connect. I
> am now worried because I believe either of these is happening:
>
> 1. The 3 Windows 2000 Terminal Servers only uses Device CALs and
> does not recognize user CALs like Windows 2003 TS. Therefore the
> users are now only using temporary CALs which will expire. If
> this is so, do I need to change all my CALs to device CALs
> instead on the Windows 2003 Terminal Licensing Server? Can this
> be done? Cos the purchased product is user CALs when I tried to
> re-activate the CALs.
>
> 2. I'm not too sure about this but user CALs do not decrease the
> count like device CALs when users connect?
>
> 3. The users are still using the cached licenses as the lease
> may not have expired yet?
>
> I really don't know which one is the most probable cause. Really
> really appreciate any help on this. Many thanks in advance!
.
- Follow-Ups:
- Prev by Date: Awake My Desktop
- Next by Date: Re: How to control the Scanner which connect with a Thin Terminal?
- Previous by thread: Awake My Desktop
- Next by thread: Re: Windows 2003 Terminal Licensing Server not issuing licenses
- Index(es):
Relevant Pages
|
