Re: Client Access Licenses

Tech-Archive recommends: Fix windows errors by optimizing your registry



Search this group for CAL and you'll find quite a few articles about CALs. But basically it breaks down like this:
You need 1 server license for each server OS and app (i.e. Windows Server 2003, Exchange and SQL).
You need Windows CAL and 1 Application CAL for each client machine.
You need 1 OS for each XP machine (they probably have OEM licenses).

The exception is for per-processor licensing on SQL which doesn't required CALs.

So for your situation you'd need (forgetting about the appliances because I'm not sure about their licensing models)
4 x Windows Server Std edition licenses
2 x Windows Server Ent edition licenses
2 x Exchange 2003 ent edition licenses
1 x SQL Server license
35 Window Server 2003 CALs
35 Exchange CALs
35 SQL CALs

You don't ALWAYS get 5 CALs when you buy WS03, it depends on the license you bought, but for retail or OEM you generally get 5 CALs

Cheers,
Jeremy.

PS

If you want to be sure just ring the MS licensing number in your country and they will give you the low down, they are pretty good.

<egaskill@xxxxxxxxx> wrote in message news:1181863830.353992.247510@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
So I took over the network here at this office, after putting out
several fires stability-wise I started checking out the legality of
the network. Then I started wondering how exactly CALs worked and
what requires them.

As the network stands right now, we have the following:
2 Windows 2003 Server Standard machines acting as Domain Controllers
2 Windows 2003 Enterprise Server machines with a copy of Exchange 2003
Enterprise on each
3 Windows 2003 Appliance edition file servers by Iomega
1 Windows 2003 Appliance edition ISA 2006 Server
1 Windows 2003 Server Standard acting as the web server for our
intranet and internet sites
1 Windows 2003 Server Standard hosting SQL

We have roughly 35 users and I'm still trying to find out whether or
not the previous IT guy actually bought a corporate license for XP pro
or not.

Now my question is how many CALs and for which products will I be
needing to get everything nice and legal?

Also I heard from someone that Windows 2003 includes 5 CALs when you
buy it, is that true?


.



Relevant Pages

  • Re: How to add a user with very limited rights
    ... The Windows Server 2003 External Connector license is an optional ... An EC license is not applicable to Web Edition or Windows Small Business ... For more information about External Connector License, ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW problem on one Client machine
    ... Welcome to SBS newsgroup. ... services licensing service on a Windows 2000 domain controller. ... terminal license successfully. ... messages in the event log saying that "A terminal license server cannot be ...
    (microsoft.public.windows.server.sbs)
  • Re: Anonymous connections.
    ... Windows Server 2003 Licensing Server can control ... you may use the New External Connector License option. ... Microsoft Partner Support ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: terminal service tempory cals
    ... In Windows 2003 per user CAL's are never issued. ... Just because the license server has per user cals doesn't mean the terminal server will try for per user cal's. ... Some how the 5 user cals they paid for are not being issued and when users try to logon they it says their cal is expired. ...
    (microsoft.public.windows.terminal_services)