Windows 2000 CAL's 1

[neaxtester2000]

I have a few questions about CAL's. You purchase a CAL for each workstation access's a windows 2000 server. But I noticed there are SQL CAL's and Exchange CAL's. So if i had exchange 2000 running on a server 2000 box, would I require a CAL for both Server 2000 and Exchange 2000? Or if I had MSSQL 2000 running on a Server 2000 box, would I need a CAL for both? Thanks for your time...

 

[danno74]

You would need a CAL for both Exchange and Windows 2000. Same applies for SQL. You can increae and decrease the CALs via Licensing tool under Admin tools. Not sure if SQL keeps track, I don't believe so, but W2k and Exchange does and will cap it.

 

[trusted]

There are two ways to license MS SQL. You can purchase CALs for every connection to the SQL server or you can purchase per processor licensing. Depending on the size enterprise the licensing costs will very. Yes with Microsoft size does matter. If you have a relatively small number of users who concurrently access the SQL server then the per connection method will be cheaper. If you have a large number of people concurrently accessing the SQL server pre processor licensing is the way to go.


JC

 

[neaxtester2000]

What about workstations that are not using exchange or sql but are in the domain. Do they require a server 2000 cal because they talk to the DC?

 

[NortonES2]

They will just need a server CAL

-------------------------------

If it doesn't leak oil it must be empty!!

 

[trusted]

neaxtester2000

In that case all you would need for the users who do not access SQL or Exchange are server CAL's like NortonES2 pointed out.

Do you know if you server licensing is per-seat or per-server?

If you are licensed for per-seat server CALs you will need one for every user on your network. Per-seat is more expensive then per-server, but is ideal in situations where you have a large number of servers to connect to.

If you are licensed for per-server server CALS you will need CALS for the total number of connections into each server. While per-server CALS are less expensive they should only be used in environments where there are one or two servers. Anything bigger per-seat is the way to go.

 

[neaxtester2000]

we are setup per seat. now i need a cal per workstation or per employee?

 

[aco636]

Have you considered MS CoreCals that give you Network Cal, Exchange Cal, Sharepoint, All in one. As the other guys suggested, additionally, you will also require MS SQL cals

To answer tha last question, you need a Cal for each workstation not for every user account (I nearly did that before talking to MS Advisor.

regards ACO

 

[trusted]

With 2000 you will need one CAL for every computer that logs on to the domain. In 2003 Server MS started Per-user CALs to address the needs of companies who have users who access the Domain through multiple computers.

 

[kmcferrin]

You forgot device CALs. Windows 2000 Server CALs can be device CALs or user CALs. You need a device CAL for every device that connects to the server, so technically each network printer that has a queue on the server is supposed to have a CAL too. So if you go with only device CALs, you'll need one per workstation/printer/hardware device that connects to the server. Of course, if you have users outside of your environment who access that particular server from machines that do not have device CALs, you should have user CALs for them as well.

As you see, this rapidly gets very expensive and ridiculously confusing. It's also quite profitable, if you're selling CALs.