What servers can we use with a SBS 2003 CAL

Here is what we currently have :-

30 SBS 2003 CAL's

Microsoft partner program where we have the following server products available :-
SBS 2003 R2 Premium
Server 2000 standard
SBS 2008 Standard
Server 2008 standard

The original plan was to install SBS server as the main domain authentication server and link a Linux Samba server to it to be the main file server. No problem with that as that is the exact CAL's we purchased.

We would like a 2nd server to be a backup incase the first failed so that at least people could continue to log in and for authentication to carry on working.
What choices do we have for the backup server without having to buy more CAL's?

The SBS features are really overkill for what we need as we dont use the firewall feature or exchange.
LVL 36
Who is Participating?
You can add any regular (that is, non-SBS) Windows server to your SBS domain and promote it to DC (except for the Web edition, which doesn't support AD). Access to these member servers will be covered by the SBS CALs.
"Q. Do additional servers in my SBS 2003 R2 network require a CAL to connect to the domain?
A. You do not need a CAL for additional servers to connect to the domain."

So in your case, if your SBS domain is still running in mixed or Windows 2000 native mode, you could add the W2k Standard as DC to your SBS domain (or was that a typo and it should have been Server 2003 standard, since Windows 2000 isn't supported anymore anyway? Then that would be the primary choice).
You could add the W2k8 Standard as well after upgrading the schema, but it leaves the question open whether "until May" refers to "Customers who buy" (that is, if you buy it until May, you may access the W2k8 for however long you feel like) or to "can use" (that is, you can only access it until May 31) in general. You'd probably need to ask Microsoft (several times) to get a clear answer on that. Or you upgrade to SBS 2008 and add the W2k8 as secondary DC.
Q. Does the SBS 2003 R2 CAL allow me to access Windows Server 2008 connected to the SBS 2003 R2 domain?
A. Yes, until May 31, 2009, Windows Small Business Server (Windows SBS) 2003 R2 customers or Windows SBS 2003 Customers who buy a copy of Windows Server 2008 and add it to the Windows SBS 2003 domain can use their Windows SBS 2003 or Windows SBS 2003 R2 CALs to access the Server.

Quotes above from here:
Licensing > Windows Small Business Server 2003 R2: Frequently Asked Questions
Darius GhassemCommented:
You are going to have purchase more CALS because you can't have 2 SBS servers on the same domain. So, you must install a Standard edition or Enterprise edition. So, you will have to purchase CALs there isn't a way around it.
grbladesAuthor Commented:
Thanks for the link. This was the question that I found the most usefull.

Q.      I want to have additional servers running Windows 2000 Server or Windows Server 2003 on my SBS 2003 R2 domain. Do my users need CALs to access those servers?
A.      No. Your SBS 2003 R2 CALs allow your users to access any additional servers running Windows Server software in the domain. You do not need to buy additional CALs for file and print services, or to access additional servers running Exchange Server 2003 or SQL Server 2005 Workgroup Edition. However, you will need to purchase Terminal Server CALs if you have a server running Terminal Services in application mode on your network.

Yes there was a typo earlier. I did mean we have a copy of both SBS 2003 and Server 2003 (not 2000) standard.

We currently have NT4 domain controllers and the plan is to upgrade these to 2003 using the following procedure which have already been tested.

Install 2003 standard as member server in NT domain.
Install virtual server.
Install NT4 server in virtual server.
Separate the networks (so NT4 domain continues to work)
Promote NT4 to PDC
Upgrade NT4 to server 2003 using trial license
Install SBS 2003 into new domain
Migrate roles across using dcpromo
Reconfigure samba on new file server to talk to the new domain.
Switch old samba file server into read only mode
Shutdown old NT4 servers
Reconnect networks
Re-Syncronise data from old to new samba server (already done previously so wont be much changed data to recopy)
Reboot all workstations
Remap drives to the new file server

Its quite a long procedure with all the installing, service packs and updates which need to be performed but it makes it pretty seemless for the clients as they keep their local profile so the settings on the desktops dont have to be re-entered.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.