!! Trying to sort this out for implementation this weekend if possible !!
We recently purchased Windows Small Business Server 2003 to replace our two current Win2k servers. Because I've moved some network functionality to Linux servers in the past couple of months, I only want/need one windows server and it's main function will be file and print sharing with appropriate security. I will not be running Fax Services, Exchange, or any of the other added features that come with SBS 2003.
We bought a bunch of Server 2003 CALs at the same time that we ordered SBS 2003. The company through which we ordered the software asked their distributor whether the Server 2003 CALs were the right CALs for SBS 2003 and were told yes, but it seems that is not the case. When I go to add CALs to SBS 2003, it asks for a 25 digit product key and there is no key provided with our Server 2003 CALs.
So then I went to the Internet to try to get more information about SBS client access licensing. Here's what I found on Microsoft's site: (http://www.microsoft.com/windowsserver2003/sbs/howtobuy/CALs.mspx
Client Access Licensing Requirements
Client access licensing requirements have changed for Windows Small Business Server 2003. In previous versions of Small Business Server, CALs were activated when a workstation used particular server services, such as print, remote access, and authenticated access. (Authenticated access is defined as an exchange of user or program credentials between the server software and a user or device.)
With Windows Small Business Server 2003, use of server services does not activate CALs. Instead use of CALs is based on access to and/or use of the server software.
A general exception to Windows Small Business Server 2003 CAL requirements is that CALs are not required when the server software is accessed through the Internet by an unauthenticated user. An example of this exception is unidentified users browsing your public Web site. Windows Small Business Server 2003 CALs are not required for those users.
Now, I'm thoroughly confused by Microsoft's distinction between "server services" and "server software". If I am only using the server as basically a file server for the use of both staff and students at our training facility, am I using server software? We have about 60 student workstations, 7 staff workstations, several local printers on staff machines and one shared printer that is shared through one of the staff workstations. Our email, web services, firewall, and DHCP are handled by the two Linux servers (one running IPCop, one running Trustix with additional services). The students access the servers for their personal data folders and for audio and data files that are part of their courses. The software they use is all installed on their local workstations (Office, Real Player, etc). The staff use the servers for file storage as well, but again all the software is installed locally.
Can some please help me to understand:
1. whether I need more CALs for my network configuration
2. how the CALs are identified to distinguish them from Server 2003 CALs, which I can't seem to use (although maybe I'm missing something)
I think this is everything I need to know in order to move forward. I would appreciate any help I can get as I was planning to put the new server in place this weekend. Our old servers were never properly built (it was before my time), have lots of errors, and are also starting to be cranky on the hardware front. I thought I had everything ready to go, but this licensing issue is a really big hiccup in my plans...
Worst case, I build a new 2000 server until I come up with a better plan, but I really don't want to do that.