That said my SBS still wastes one whole processor all day long trying to query OSX computers for it's DCOM information because some Microsoft developer though not to check the Operating system field of the computer object in AD but that's another story - View image here:. I setup SBS2008 3x before I finally didn't fuck it up and then rolled it out to 60% mac/40% PC setup.
You come in with "I know how to set this network" enterprise mentality you will break things. Lots of stuff is scripted/automated through the custom gui/monitoring/reporting for an SBS because it's designed so that no person who has system administrator experience can run it. Usually the following applies for any Administration work: You may be use to doing things the Enterprise way will break the SBS server. ++ and SBS is NOTHING like a 500 user Active Directory evironment. I think the non-premium CALs are like $20/ea? Licensing on SBS will be dirt cheap - the CALs cover all teh services. If you need to get faster hardware, just buy a dell server with sbs 2008 and swing migrate to the new server.
and its a lot cheaper than a full enterprise config. Microsoft puts it out as a fully supported product - it DOES work perfectly fine. It sounds like you are fighting SBS because that is not the way you are used to do things. Sorry for my ignorance, but I'm not really sure how well all those things play together since I'm use to being able to dedicate an entire physical server to them.įor some baseline figures, I think I'll be able to do either two servers ~$3500 or one monster server at ~$7500. Also, I'd be interested to hear different ideas like running something on the main server for now, but moving it to a standalone server later, etc.
So I'm looking for opinions as to how many servers I need (or whether I should do virtual servers) to replace all those SBS functions. You'd think that this would free up the old server to utilize somewhere else, but you wouldn't want this thing in your network! I have a very small budget (around $15,000) to purchase a new server(s) and rack to set up a new domain and bring users into it. I am used to running SQL, Exchange, and ISA on completely separate servers, not to mention my PDC, BDC, File/Print Server, and various app servers. At first, I thought the costs of licensing alone would kill me but Microsoft has a Charity Licensing program that helps substantially. They are currently using Small Business Server 2003 and utilizing Exchange, Sharepoint, ISA, and SQL aspects of it.
I went to work for a church with about 40 users. I came from a company with 500+ users and stacks of servers.