Quote:
Originally Posted by johnhook
spec_r,
One more thing - what are you currently running on SBS 2003? Is there some reason you picked SBS2003 instead of S2k3? Not sure if your ERP and Veritas apps use the SQL-Server database that's bundled into SBS2003. Are you using Sharepoint on SBS2003? Obviously you're using Exchange. What about MS Office? Is that installed on each client desktop or is it installed/shared from a fileserver?
Based on my personal application issues with SBS 2003 - I'm thinking that you should consider replacing it with S2K3 in either a single large server configuration as well as a 2-server configuration. I'm having concerns about the lack of expandability with SBS2003 and potential conflicts we may not know about down the road. Your environment/company size is right on the edge of being too large for SBS2003 anyways. If you expand or add employees, PCs, etc. You might be forced to replace SBS2003 anyways. It might make more sense in you're going through the science fair project of a complete domain/server migration - to eliminate SBS2003 now rather than be forced to do this later.
I personally LIKE SBS2003 and would keep it in my small office environment if it were not for the ridiculous S2K3 requirements of our medical software. In YOUR environment - I can easily see you outgrowing SBS2003's capacity and being force to migrate to an ALL S2K3 environment anyways.
- John
|
Hi John,
SBS2003 was already here when i join. I think reasons we are using SBS2003 bcoz there's a built in Exchange Mail server. The MS office are not shared among users. As for our Oracle ERP they are in another server manage by IBM AIX OS so i guess it was not bundle with SBS2003 SQL-Server Database?
You are right having to consider the growing size of the company, we don't mind getting W2K3 and adding an additional Exchange server too. Our size is about around 80 users +/- currently.
Thanks