Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Microsoft CAL info

  • 10-11-2004 4:21pm
    #1
    Stky10
    Registered Users, Registered Users 2 Posts: 1,165 ✭✭✭


    Just checking something.

    How exactly do Microsoft CAL's work??

    If you buy a Microsoft Server package with eg 10 CAL's,
    and have 10 clients attached to the domain, do the clients
    have to have a legal license, or is that taken care of by the
    CAL.

    Or is it as I presume that you have to have a legal license
    for all clients, and the CAL's just permit you to attach them
    to a domain...

    Or is it something completetly different...


Comments

  • #2
    Nuttzz
    Registered Users, Registered Users 2 Posts: 3,777 ✭✭✭Nuttzz


    Stky10 wrote:
    Just checking something.



    Or is it as I presume that you have to have a legal license
    for all clients, and the CAL's just permit you to attach them
    to a domain...

    Thats it, CAL is client access licence not a windows OS licence


  • #3
    Capt'n Midnight
    Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 92,385 Mod ✭✭✭✭Capt'n Midnight


    10 clients allowed to connect at any one time - license on the server - cheapest if only one server.

    if you do the non-reversable change to per seat licencing then the license goes to the client, this works out cheaper if you have lots of clients connecting to lots of servers.

    The license does not "float" between machines in per seat licensing , if you have 20 PC's then you need 20 CAL's , if you replace the machines then you can move the CAL's (don't quote me on that M$ licensing is a complete head wrecker and uses terms that aren't normal english usage or explained clearly on their site.)

    RANT
    If you want to email someone a database report then you could be looking at..
    one windows license on PC
    one server license
    one CAL to connect to server
    one license for M$Access
    one license for SQL Server
    one CAL for the Device not per concurrent connection - if you didn't get the per processor license above
    one Exchange server license - if it's not on the SQL server you need a second windows server license, if you want to store more than 8GB of email in a web accessible format or 16GB in total you need the enterprise version and that means you need a windows enterprise server license.
    one CAL for Exchange, this allows you to use a copy of outlook (but outlook comes with office so not really giving anything away)

    If you want to do that through terminal services 2003 then you need a TS Cal license , or maybe not depending on when you bought the copy of windows, and to run it in you need a license on the client for each microsoft app you use on the TS, it's fun buying an MSAccess license for a MAC....

    then there are OEM licnesnes / upgrade licenses / volume licenses / software advantage and they all have different rules for transfer and downgrade rights .

    And since they change the licensing schemes about as often as the user interface (every 5 years) once you have got your head around it, it's obsolete

    t'wood drive you to open source,
    Excel used to cost more than buying a copy of works and upgrading it to Office
    /RANT


Advertisement