• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Attn Admins --> MSDN or Small Business Server?

trilks

Golden Member
I am an IT intern at a small consulting company, and I am in charge of basically redesigning the entire IT infrastructure. I am going to replace the current peer-to-peer network of Win 98SE machines with a domain-based network running a Windows Server (2000 or 2003), Exchange, SQL Server, etc., as well as upgrading all desktops to XP Pro.

My question is whether or not I should go with MS Small Business Server, or a MSDN subscription. SBS would fit the company, as it is less than 10 people, but it does not include some of the applications that we would really like to have, such as CRM and SharePoint Portal. Also, it locks us in with the 2000 versions of all the software, and we would have to pay to upgrade to the later version (SBS 2003 is due out in 3rd or 4th quarter, I believe). On the other hand, a MSDN Universal subscription would give me all the software I could ever need, as well as updates, betas, and support. However, would this be too much for such a small business? I'm trying to get the best system I can, but I don't want to waste money.

Anyway, if anyone has had experience with either of these, I'd appreciate your thoughts/comments/advice/ramblings.

Cheers in advance.
 
You can't legally use MSDN for production servers, just development, so if the business is at all concerned about obeying license terms you need to go with MS Small Business Server.
 
DaveSimmons is 100% correct, MSDN is NOT for production systems, it is for development only. If my arse was on the line, I wouldn't recommend MSDN for anything that involves something MS may check up on.

Maybe trying Linux/Samba/POP for the backend and XP Pro on the desktops? Sure, some of the configuration may take some time, but the savings would be tremendous over Server and Exchange licenses.

vash
 
Back
Top