Small Business Server is an often misunderstood package and this has lead to a number of myths on what SBS can or cannot do. SBS MVP Calvin McLennan and TechNet Canada's own Damir Bersenic recently put on a seminar debunking these myths and they have agreed to let me post them here!

Myth #1 - It is not possible to connect other Windows Servers to the SBS domain. This is FALSE! There are no limits on the number or type of servers that can exist in a Windows Small Business Server 2003 domain, with the following exceptions: - Only one computer in a domain can be running Windows Small Business Server 2003. - Windows Small Business Server 2003 must be the root of the Active Directory forest. - Windows Small Business Server 2003 cannot trust any other domains. - A Windows Small Business Server 2003 domain cannot have any child domains. - A Windows Small Business Server 2003 domain can have no more than 75 CALs. You can use CALs for each user or for each device.

Myth #2 - SBS 2003 will not work in an environment where multiple offices are linked over slow WAN links. This is also FALSE! SBS 2003 will support remote offices over a WAN link. One way is to install Windows Server 2003 at the remote site, and then configure it as a replica domain controller. This enables Active Directory information to replicate at the remote site, so that authentication requests do not have to travel over the slow data link. Also, using Outlook 2003 in Cached Exchange mode minimizes the amount of e-mail traffic between remote clients and the server.

Myth #3 - I cannot run Terminal Services in Application Mode on Small Business Server 2003. This is true, however there are workarounds. It is not possible to run Terminal Services in Application Server mode on Windows Small Business Server 2003. This is a change from Small Business Server 2000. Running Terminal Services in Application Server mode on a domain controller may present a security risk to your network. If you want to use Terminal Services in Application Server mode, we recommend that you purchase an additional Windows Server 2003 license and install an additional server running Windows. Note: This is an ideal situation to use Virtual Server 2005 R2 on the SBS server to host a virtual machine that acts as the terminal server.

Myth #4 - I can use my SBS CAL to access other Exchange 2003 and SQL Server 2000 servers on my network. This is true, however SBS 2003 R2 is going to change this. The Windows Small Business Server 2003 CAL only covers you for the single Windows Small Business Server 2003 server and additional Windows Server System servers. Additional CALs will be required for Exchange, terminal server, or SQL servers in the network. SBS 2003 R2 will allow for connections to other Exchange 2003 servers in the SBS domain, as well as any SQL 2005 Workgroup Edition servers in the domain.

Myth #5 - I want to have additional Windows-based servers in my Windows Small Business Server 2003 domain. I need CALs for those servers. This is FALSE! Your Windows Small Business Server 2003 CALs cover you for any additional Windows-based servers in the domain. You do not need to buy additional CALs for them.