trying to understand Windows Server CALs

[ZippyDan]

yes, i did google and wiki it, but i need more concrete instead of general explanations

if i have a windows server running a server application, do any clients connecting to the server application require a CAL? (example: Quickbooks or Inventory server software)

if i have a windows server that is just sharing folders and printers do i need a CAL for each workstation that has access to the shares (not necessarily on a domain)?

if i have a windows server acting as domain controller, do i need a CAL for every workstation on the domain?

if i have a windows server running exchange, i think i need an Exchange CAL for every workstation using outlook... but not necessarily a normal CAL?

then there are terminal services CALs which i suppose i need for remote desktop and VPN connections... does this only apply to external RDC or RDC on the LAN too?

basically, my planned network infrastructure will be like this:

1. Win2k8 Server: Domain Controller, WINS, and Folder/Printer Shares
2. Win2k8 Server: Running Exchange 07
3. Win2k3 Server: Running Citrix Access Essentials for remote access to Quickbooks and Inventory Software Clients, and possibly also handling external RDC connections
4. Win2k8 Server: Running Inventory Server
5. Win2k8 Server: Running Symantec Backup Exec
6. Win2k8 Server: Running NOD32 AV Server

NonWindows
7. Linux Server running QuickBooks Server
8. Linux Server running HylaFax Server
9. Linux Server running ClarkConnect

If I hypothetically have 10 workstations, then I assume I need

Server 1

10 CALs for the workstations + 5 more CALs for each of the other servers that will be joining the domain?

Server 2

10 Exchange CALs for my workstations running Outlook?

Server 3

Only need Terminal Services CALs equal to number of concurrent Citrix or RDC users?

Server 4

10 CALs for the workstations all running Inventory Client software?

Server 5

Assuming Backup EXEC is only backing up other Windows servers, then I'd need 5 CALs? If I'm backing up Linux Servers and individual workstations then I need a CAL for each device that's being backed up.

Server 6

I need a CAL for every computer running the A/V client?

 

[ZippyDan]

anyone?

 

[bob4432]

i hate to disappoint, but i had recently set up just 1 server and called ms multiple times asking them what i needed for cals, and everytime i called i got a different answer. i would give them a call, record it if legal in your state and go w/ what they say.

 

[GeekDrew]

MS Licensing is horrible. This is how *I* think that you'd be compliant for licensing, but I'm just another forum user... I don't represent Microsoft. (I am not a lawyer, don't take my advice, I'm not liable, etc.) I'm talking about per device CAL mode here, not per user CAL mode, as per device CAL seems most appropriate for your situation.

http://www.microsoft.com/windowsserver2008/en/us/client-licensing.aspx:
"A separate Windows CAL (of either type) is required for each user or device that accesses or uses the server software on any of your servers."

You need one CAL for each device that will be access *any* server. Device being a desktop PC, laptop, another server, etc. That is to say, if you have 10 desktops, 6 windows servers, and 3 linux servers, and they each have the potential of accessing any windows server for any reason, then you need a grand total of 19 device CALs. If you're connecting any phones, laptops, remote users, etc. - anything else - you'll need an additional device CAL for that. These device CALs are good for any server in your organization, so you need a grand total of 19 Windows CALs.

Exchange CALs are per-user, not per-device or per-mailbox. Therefore, the number of devices you have, and the number of Windows CALs you have, is wholly irrelevant. If you have 90 users using those 10 desktop PCs, you're going to need 90 Exchange CALs.

TS CALs are, like Windows CALs, either per-device or per-user. If you go with per-device, you'll need an appropriate number of CALs to cover however many devices will need to use terminal services in your organization. This is not concurrent. If 8 of your 10 desktops will need to use Terminal Services, regardless of whether or not they are using it concurrently, you will need 8 TS CALs.

 

[ZippyDan]

that makes much more sense GeekDrew, thanks!