Re: Licensing Fileservers?



My advice to you is think long and hard before using device licencing.

Every single device including printers, plotters, PDA's, or any other device
shared or otherwise, requires licencing. Per server provides seat based
licencing. ie: add 20 printers to the 25 workstations and only need 25 CAL's
whereas in device mode you would need 45 CALS.

The servers require at least 1 CAL to be compliant however the CAL, as the
name suggests is the Client Access License. Therefore a server which
connects to another server is acting as a client and needs to be licensed.

in device mode you would need at least 1 CAL for each server. 1 CAL for each
workstation. Some devices which will be attached to the workstation will
also require its own CAL.

AFIK you can move your CALS between servers without violatung the EULA. A
quick call to your local MVP should get you off in the right direction.

Cheers

"Jay Becker" <JayBecker@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9524F665-6463-4B5F-812B-AA805AAD32E8@xxxxxxxxxxxxxxxx
Hello everyone.

We are having some licensing confusion and were hoping someone could help
us
out. We just purchased a new Windows Server 2003 Domain Controller to
replace our old Windows Server 2000 DC.

So, we have approximetely 25 devices in our office, so we purchased 25
CALs
and figured we would go into Per Device mode. Also, we have 2 file
servers
running Windows Server 2003, each with 5 CALs set to per/server mode.

Our goal is to have everything per device, so all licensed clients can
have
access to all the servers. So far that is working great. The question is
about the licensing on the 2 Fileservers. Right now they are set to 5
per/server on each. Can I remove those CALs and attach them to the
Enterprise licensing? Meaning, I have the 25 we just purchased, can I
remove
the 10 from the file servers, and add them to the 25, so we have 35 CALs?
And if I do so, can the fileservers talk to each other file and to the
DCs?

I guess the confusion is really about the servers. Am I right in assuming
that each server needs a single CAL, just like a desktop client?

We really appreciate any feedback.


Jay Becker


.



Relevant Pages

  • Re: Terminal Services 2003 temporary licenses issue
    ... server itself. ... You also need a normal 2003 server CAL for each client (also Per ... you need to buy and install TS CALs. ... > According to your information from the Licensing Manager, ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing model
    ... SBS doesn't do concurrent licensing. ... Historically speaking, in the Windows server world ... CALs for each server on our network, and the number of CALs on a given ...
    (microsoft.public.windows.server.sbs)
  • Re: License Service
    ... Q. What are the differences between user CALs and device CALs? ... A user CAL permits one user to access the server ... No. SBS 2003 R2 CALs are not concurrent. ... details the licensing mode is set to per server for x concurrent ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 License Disappears - Now shows 1 as Maximum
    ... to use the Licensing module in Server Management to back up the CALs. ... are built-in wizards there to backup and restore your CALs. ...
    (microsoft.public.windows.server.sbs)
  • RE: unable to login to sbs03 domain with 2 unused CALs on server
    ... For the problem why the CALs were reset, it can be caused by following ... the licensing checks that are performed by the Windows Small Business ... Server license service will fail because the license check or the Active ... Worldwide customers can use the Guide to Worldwide Microsoft Licensing ...
    (microsoft.public.windows.server.sbs)