I have been reading some conflicting information regarding the limitations placed on SBS 2003 and 2008 by MSFT. We are planning a 2-server environment for our 35 users with plans to take it to as many as 50. Obviously, there is quite a price jump, not with just Windows OS, but also 3rd party software like Backup Exec - buying for SBS is MUCH cheaper! I would like some feedback and write-ups from you guys pertaining to a multi-server environment where both servers are AD controllers and one of them is an SBS box.
I have read and heard that although SBS will allow another server as a domain controller, it does not play well and starts fighting for control. I would like to know if there is any truth to this.
We currently have SBS 2003 running on our domain and our 2003 Std server is joined like a workstation (member-server) and does not hold the domain info. Problem is, when the SBS box goes down (and man, those damn things that FOR EVER to reboot), nobody is able to authenticate to the domain - Quickbooks flips out and various other softwares that we have don't like it. I want out new server config to be resiliant - in the even that the Exchange box is booted, everything else should continue to work normally; likewise if the Exchange server tanks, I need to have our users be able to log on and perform other work. Each hour of downtime costs our company over $2000 and I need to limit our exposure as much as possible.
As for redundancy, if each our of downtime is costing your company $2000 then you REALLY should look into server mirroring products such as NeverFail or DoubleTake - they are expensive... but two hours of downtime should pay for them.