How Do I Install W Server 2003 CALs?

Discussion in 'Server Setup' started by razor, May 5, 2005.

  1. razor

    razor Guest


    Really dumb question, but we just bought 10 CAL licenses to add to our
    Windows Server 2003 Enterprise edition domain controller, and I don't know
    how to install them. They are a per device type.

    I've installed Terminal Server CAL licenses in the past, but not W Server

    razor, May 5, 2005
    1. Advertisements

  2. Start - Help - Administering and tracking licenses:

    For Enterprise licensing:
    Start - Administrative tools - Licensing

    For single server licensing:
    Start Control Panel - Licensing
    Vera Noest [MVP], May 5, 2005
    1. Advertisements

  3. razor

    razor Guest


    Thanks for the reply. I've actually done that, and it never asks for the
    Authorization or Account numbers. I also keep getting the licensing errors
    that we've exceeded our number of licenses.

    Should there be a step that requires me to enter the license authorization
    and account numbers?

    Any links/white papers on this?
    razor, May 5, 2005
  4. Check out here:

    Hope this helps.
    Arek Iskra [MVP], May 8, 2005
  5. razor

    razor Guest


    Thank you for the reply. Are you saying that I install W Server 2003 CAL
    licenses the same way as Terminal Server CAL licenses?

    I have installed TS CAL licenses before...but I thought that was just for
    razor, May 9, 2005
  6. It's similar. Just that you use Licensing snap-in from within the server
    where you want to add CALs.
    Arek Iskra [MVP], May 9, 2005
  7. razor

    razor Guest

    OK--thank you!

    razor, May 9, 2005
  8. razor

    razor Guest

    Me again--

    Sorry to be a pest, but all this article talks about it installing W Server
    2003 "Terminal Server" CAL licenses.

    I thought that maybe you just go through the same steps to install W Server
    2003 (non TS) CAL licenses, but no, it wont work.

    When you wrote, it is similar and you use the licensing snap-in, could you
    be more specific? I have tried the llsmrg.msc and it will not let me add
    licenses there--again, it doesn't ask for the authorization number nor the
    license number and is not recording the purchase history.

    What am I missing here?

    Anyone else have any ideas?

    razor, May 9, 2005
  9. razor

    Kerry Brown Guest

    I'm not certain but I think the License Logging service has to be started
    before you can add licenses. Once it's running you should be able to add
    them via Licenses in the Contorl Panel.

    Kerry Brown, May 9, 2005
  10. razor

    Henrik Guest

    If you dont want them, do as Vera told you, that is, start the license
    logging service on the domain controller responsible for the licence logging
    (Can be seen using AD Sites and Services, and clicking on your site, and
    then viewing the properties for "Licensing Site Settings".

    The thing is though, that in Windows Server 2003, a warning is not an error,
    and you can safely disregard the warning saying you are out of licences
    (this might NOT be the case if you have legacy software like Exchange 5.5,

    Your programs, if they are of a newer version won't cease to function just
    because your are out of licenses.

    The License Logging Service won't be a part of the next version, and the
    fact is that service does not function especially well in Windows Server
    The reason, as stated in the article below, is that the LLS tool cannot keep
    up with the fact that license terms and the licenses themself change all the
    time. The tool was thought to be a help for Admins to keep track of
    licenses, and their usage, which is no longer possible.

    See the following article in which LLS is explained for Windows Server 2003,
    and a list of programs which will work regardless if your are in violation
    of licenses or not:

    I know about all this since the licensing service no longer replicates the
    licensing information in Win2K3, which led me to believe I had a faulty AD
    or something, but after some hunting on Google, and an incident logged with
    MS (which was deemed free of charge due to the new, nearly undocumented
    nature of license handling in Win2K3), we found that the "crappy" way WIN2k3
    handles licenses is
    1) By Design
    2) Not well documented

    // Henrik
    Henrik, May 10, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.