Re: Terminal Services 2003 temporary licenses issue

From: Vera Noest [MVP] (vera.noest_at_remove-this.hem.utfors.se)
Date: 04/03/04

  • Next message: Vera Noest [MVP]: "Re: File Types and Windows Server 2003 Terminal Server"
    Date: Sat, 03 Apr 2004 12:39:24 -0800
    
    

    You do need a license for the server, but that often comes with
    the OS itself (but best to check). You don't need a TS CAL for the
    server itself.
    You also need a normal 2003 server CAL for each client (also Per
    User or Per Device). Those may or may not be present (if there are
    more 2003 servers in your network than only this TS, then the
    clients probably already have a 2003 server CAL. But best to check
    this as well).

    When the temporary licenses expire, the clients will be denied
    further access to the TS until a permanent TS CAL is available on
    the LS.

    Deleting the license from the client to regain access to the TS is
    technically a violation of the EULA (but allowed for
    troubleshooting purposes). It shouldn't work either: it will allow
    you to connect once more, since every first connection gets a
    temporary license, but the second connection attempt should be
    refused (that's when the permanent license must be issued).

    Hard to say what the plan of the previous admins was, maybe they
    weren't aware of the licensing requirements, or just didn't bother
    to install them, since they were leaving anyway...

     --
    Vera Noest
    MCSE, CCEA, Microsoft MVP - Terminal Server
    http://hem.fyristorg.com/vera/IT
     --- please respond in newsgroup, NOT by private email ---

    =?Utf-8?B?Sm9obiBUcmVhbm9y?= <jtreanor@earthlink.net> wrote in
    news:27D75D9C-9D36-4EE7-BA6A-01D0303C6614@microsoft.com:

    > Thanks very much, Vera. I had a feeling that this was the case
    > and checked out the pricing for 2003 TS CAL's today.
    >
    > I don't need an additional license for the server, do I?
    >
    > Also, what will happen when the temporary TS CAL's expire? I've
    > noted that if I delete the appropriate registry key on the
    > client a new temporary 90-day TS CAL is created on the server.
    > I'm just trying to figure out what the previous admin's plan
    > was, or if they had just let it run like that for a while....
    >
    > Thanks again -
    > John Treanor
    >
    >
    > ----- Vera Noest [MVP] wrote: -----
    >
    > In short: you need to buy and install TS CALs.
    >
    > According to your information from the Licensing Manager,
    > your LS is activated and functioning correctly, since it is
    > issueing temporary TS CALs. It contains "Existing W2K TS
    > CALs" because it also can handle licensing for W2K Terminal
    > Servers, but since you run Windows 2003 TS, you cann't use
    > those. The fact that the LS is issueing temporary "Per
    > Device 2003 TSCALs" shows that your 2003 TS is in the "Per
    > Device" licensing mode.
    >
    > What you have to do is:
    > * decide if you need "Per Device" or "Per User" TSCALs
    > (which alternative is cheaper in your organisation depends
    > on if you have more users than workstations, or the other
    > way around). * buy enough TS CALs and install them on the
    > LS * if you buy "Per User" TS CALs, switch your TS to "Per
    > User" licensing. You can change this from Administrative
    > Tools - Terminal Services Configuration - Server Settings
    >
    > Further details:
    > Windows Server 2003 Pricing and Licensing FAQ
    > http://www.microsoft.com/windowsserver2003/howtobuy/licensi
    n
    > g/pric licfaq.mspx
    >
    > If you run XP Pro on your clients desktops, you might be
    > entitled to a free TS CAL. Check:
    > Terminal Server CAL Transition Plan FAQ
    > http://www.microsoft.com/windowsserver2003/howtobuy/licensi
    n
    > g/tsca ltransfaq.mspx
    >
    > Check this article as well, it explains that your Per User
    > TS CAL count will not be decremented:
    > 822134 - The Function of Terminal Server CALs in Windows
    > Server 2003
    > http://support.microsoft.com/?kbid=822134
    >
    > --
    > Vera Noest
    > MCSE, CCEA, Microsoft MVP - Terminal Server
    > http://hem.fyristorg.com/vera/IT
    > --- please respond in newsgroup, NOT by private email ---
    >
    > =?Utf-8?B?Sm9obiBUcmVhbm9y?= <jtreanor@earthlink.net> wrote
    > in news:6D344015-4FDF-4F82-9BE5-C9C4FEA06FEF@microsoft.com:
    >
    > > I have "inherited" a Windows 2003 Server network that
    > > currently has Citrix Metaframe XP installed. I can't get
    > > any info from the former admin, so I am trying to figure
    > > out the licensing and have spent hours trying to decipher
    > > what is needed, if anything.
    > >> Currently, when in Licensing Manager, I see two objects:
    > > (1) Existing Windows 2000 Server - Terminal Services CAL
    > > token (per device) This is empty
    > > (2) Temporary Licenses for Windows Server 2003 - Terminal
    > > Server Per Device CAL Token This has a lot of temporary
    > > licenses in it.
    > > Some of them are set to expire soon and the clients are
    > > getting
    > > pending expiration messages.
    > >> I have tried the registry trick (of removing the license
    > >> info
    > > from the registry key
    > > -HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing - on
    > > the client side), which worked, and the machine was given
    > > a new license the next time it logged on to the Terminal
    > > Server.
    > >> I am confused. If the license server was activated in
    > >> the first
    > > place, what was required at that time? What do I need
    > > now? Are the temp licenses going to auto-renew? Any
    > > help would be greatly appreciated!
    > >> Thanks -
    > > John Treanor
    > > jtreanor@earthlink.net


  • Next message: Vera Noest [MVP]: "Re: File Types and Windows Server 2003 Terminal Server"

    Relevant Pages

    • Re: Licensing model
      ... SBS doesn't do concurrent licensing. ... Historically speaking, in the Windows server world ... CALs for each server on our network, and the number of CALs on a given ...
      (microsoft.public.windows.server.sbs)
    • RE: Event 1004 Terminal Server Cannot issue a client license
      ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
      (microsoft.public.win2000.termserv.apps)
    • Re: License Service
      ... Q. What are the differences between user CALs and device CALs? ... A user CAL permits one user to access the server ... No. SBS 2003 R2 CALs are not concurrent. ... details the licensing mode is set to per server for x concurrent ...
      (microsoft.public.windows.server.sbs)
    • Re: SBS2003 License Disappears - Now shows 1 as Maximum
      ... to use the Licensing module in Server Management to back up the CALs. ... are built-in wizards there to backup and restore your CALs. ...
      (microsoft.public.windows.server.sbs)
    • RE: unable to login to sbs03 domain with 2 unused CALs on server
      ... For the problem why the CALs were reset, it can be caused by following ... the licensing checks that are performed by the Windows Small Business ... Server license service will fail because the license check or the Active ... Worldwide customers can use the Guide to Worldwide Microsoft Licensing ...
      (microsoft.public.windows.server.sbs)

    Loading