Everybody is mostly correct but this is from windowsitpro.com
and really says it all. Note requirement of being the root and
non-SBS domain joining. Also, lack of TS.
"SBS 2003 vs. Windows 2003
For several reasons, you might be better off with the regular
version of Windows 2003 than with SBS 2003. SBS 2003 isn't
intended for a complex network architecture. An SBS server can't
join a non-SBS domain, and an SBS domain must be a root-level
domain. An SBS domain can be in a trusted relationship with
another root-level domain, but it's not truly designed for this
use.
SBS 2003 is similar to Windows 2003 but not entirely. Because
SBS 2003 is intended for smaller networks, and because the SBS
server is meant to be the DC, SBS 2003 doesn't have some
functionality (e.g., Terminal Services) that's useful in larger
networks. (However, you can use Remote Desktop?which is
enabled by default?to remotely administer an SBS 2003 server
from another computer. You can also make an SBS 2003 DC a
Terminal Services license server.)
A final caution about SBS 2003: It's not quite as simple as it
seems. Setup should cause no difficulties for experienced NT
administrators, but a novice would do better to buy a
preinstalled SBS 2003 server. The danger of a reduced-
administration server OS is that administrators can mistake it for
a zero-administration OS. The fact that SBS 2003 is designed to
automatically follow some Microsoft best practices doesn't mean
that it automatically follows all of them. Even if you walk
through all the configuration wizards, you'll still need to install
security patches and service packs and follow safe-computing
guidelines. The audience for which SBS 2003 is designed?the
shop looking for an extremely low-maintenance server?might
balk at SBS 2003's required maintenance."
Also, be aware that SBS and Standard Server family licenses are
different so you will need Server 200x and SBS licenses. The S