windows 2000 server: what the hell is a CAL?


Recommended Posts

I was trying to install a (legit) copy of windows 2000 server... the documentation that came with it said that I have 5 Client Access Licenses (CALs)

but what the hell is it?

secondly, i dont know if this is related or not, but I lied and said I had 1000 of the "CAL"s when it asked me for how many i had, and then in components setup, it rebooted itself when i clicked "cryptosomething services" (second one down)

does anyone have any answers for me? TIA :)

Link to comment
Share on other sites

Client Access Licence:

There are two licensing models to consider: payment per server with each concurrent connection requiring a client-access licence; or payment per device or user.

Link to comment
Share on other sites

5 concurrent connections meaning that i can only have 5 apps (like msn messenger) access the net at one time, 5 users can be logged on at a time, 5 people can access IIS at a time, 5 users can access file and printer sharing at a time, if i were to install apache- only 5 users at a time? what exactly does that mean?

or i will have to send $ to microsoft everytime someone accesses the server, simular to how WPA works?

Link to comment
Share on other sites

Its how many people can access the server at once, you can have 5 people access your server concurrently, if you want to allow more each connection needs a licence, this is per server licencing.

Per seat licence is where each user has access to all servers, the user has the licence not the server.

If you had 50 users and only need to give access to 10 at a time you would have per server licencing, if you had 100 servers and each user had access to all servers you would use per seat licence.

You have to work out which is the cheapest as each licence costs money.

Link to comment
Share on other sites

what i need to know is will IIS be only limited to 5 users? why is the licensing different in xp?

and if i were to just say "25" in the box, would it work fine?

Link to comment
Share on other sites

that's right, i havn't used a server before... so confusing :wacko:, maybe if you know of an article that explains it quite clearly, that would help ;)

Link to comment
Share on other sites

This is a good topic because I've been puzzled with all this awell, and I don't fancy reading through pages and pages of tech sites. Just something in a couple of paragraphs that can explain things simply. I do have a couple of questions on this:

Win2K Server (5 CALS):

Say now I hosted my own website on my own machine with a static IP etc. etc. now, how many people can view my site at the same time? Because there's an option in IIS to allow 'x' amount of concurrent connections per virtual directory.

WinXP Pro:

I'm guessing this can handle more than 5 concurrent connections (whatever this really means), so hosting a website on this would be perfect. I know it won't be as secure as the server but would it get past the CAL problem.

There are two ways of looking at these concurrent connections to a server (either in uni on a LAN that handles all students storage spaces on the server, and the other method is via a web server), so these CALs get's even more confusing.

Link to comment
Share on other sites

CAL is Client Access License, sorry to offend you but if you don't know that you shouldn't be installing it.

no offense taken, I need to learn about servers for school, what better way then testing one at home to learn about it ;)

Link to comment
Share on other sites

No, IIS isn't affected by CAL's. You can have as many connections to your website as you can handle.

I don't really know how to explain a CAL or a concurrent connection other than think about what it stands for. Client Access License. In this case a Client is a workstation. Each server purchase comes with 5 CAL's included. So that means you can have up to 5 workstations on your domain (this is where AD comes into play) at any one given time. If you have more than 5 workstations on your domain, then you can purchase CAL's in blocks of 5.

Now typing this made me think of something...

If your not running a DC and your server is acting as a fileserver only (meaning no AD is running) then can you have as many connections as you want or are you still limited to 5?

Link to comment
Share on other sites

CAL is Client Access License, sorry to offend you but if you don't know that you shouldn't be installing it.

why do people bother posting things like this?

is there some infused knowledge that you have? were you born knowing what CALS are?

let the dude try and learn, sometimes the best way to learn something is to figure it out on your own.

and although xp pro doesn't have cal, the server is still limited to 5 connections, right?

Link to comment
Share on other sites

I concur, don't waste our time and yours typing in useless posts. I myself tend to learn a hell of a lot more outside Uni than in, and this is a great resource for learning.

And yet again, I'm learning more - I'm glad IIS don't require CALs, but CALs is a very tricky subject and we're all learning.

Link to comment
Share on other sites

OK. They really should give some examples on the MS website. If you're unsure, contact MS Licencing. This is how I understand it.

Per Seat CAL - number of separate workstations (this is in total, not just concurrently) allowed to have authenticated access the server or other servers in the domain.

Per Server CAL - number of concurrent connections for authenticated access to the individual server.

If you are accessing across the internet to an anonymous website hosted on the server, you don't need any licences.

If you are accessing across the internet to an authenticated website hosted on the server, you can buy a single internet connector licence for unlimited connections across the internet.

Windows XP Pro has a maximum of 10 connections. This cannot be upgraded.

p.s. This changes slightly in Windows Server 2003.

Link to comment
Share on other sites

I'm slowly understanding it aswell, but I am researching into it on the net and here's what I've learnt so far.

Example:

1 Server (S) with 5 CALs

1 Domain Controller (DC)

6 Workstations (W1-6)

W1 wants to access files on S;

S sends a request to DC;

DC authenticates/authorises this user and sends a license to W1 "Authentication License";

So, W1 has a CAL (there are 4 left);

W2 wants to access files on S;

Another CAL is provided (there are 3 left);

W3-5 repeats the process (all 5 CALs are being used);

W6 wants to access files on S;

Uh-Oh, sorry, you're not allowed because all of the 5 licenses are being used;

W6 is forced to wait until any of W1-5 signs off, a CAL is returned and W6 can now login.

Hey cool, typing all of that out helped my understand it a lot more (mind you I have Enya in the background, lol). All I got to do now is research into:

- Active Directory (done this)

- Understanding AD, Forests, Trees, Domain Controllers etc.

Question: Why is necessary to use CAL's? the only reason I can think of is that M$ can do with the money, but I honestly cannot think up a reason why CAL's are required (is it a security or performance issue?), otherwise I've just got to understand the differences between per seat & per server.

Link to comment
Share on other sites

Thanks Xeron, per seat & per server makes sense to me now. I did misread it the first time, I didn't give the word domain any thought, but christ - what a mistake to make.

Link to comment
Share on other sites

Hehe... Try installing Apache... No CAL in the way... ;) And safer(?)!!!

But ok... For learning how to expand MS power over the world, no better way than installing their server stuff and pay for licences... ;)

Link to comment
Share on other sites

Question: Why is necessary to use CAL's?

So M$ will get money from an enterprise with 50 CALS, easily. Other then that it's pretty useless.

Link to comment
Share on other sites

50 CALs, true true.

Apache - you're drifting in the wrong direction, IIS & Apache have nothing to do with CALs, lol.

Question: In university, are they likely to have a lot of CAL's then? considering 50 for an enterprise, but whenever I access my student drive and others do the same at the same time, isn't this using CALs.

Link to comment
Share on other sites

You are describing a per server situation so the licences are held on each server, therefore you'd need 6 licences on your fileserver.

What I'm not sure of is whether your DC would need any. I guess not as you're not using any file, print, remote access or terminal services from it. Plus, if you have multiple DCs you will connect to one randomly for authentication, and I can't see how that could be licenced in per server mode.

Edited by Xeron
Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.