Quote:
Originally Posted by johnhook
spec_r,
I'm not sure what kind of hardware you're currently running (make/model/RAM/processor/storage space, etc). Knowing this would help me provide more sound advice. While I DO believe that you could potentially roll both of your server's functions, apps, etc. onto a single SBS or S2K3 server - I'm thinking you be looking at a larger, faster server to handle all of that. I'm thinking a Quad Core Xeon server with 4-8GB RAM and a hardware RAID 5 disk array. In this case, I would also recommend that you go with S2K3 Enterprise and forget about SBS 2003. I say this because SBS2003 really limits you in terms of future expansion.
If you aren't able to invest in a high-end single-server solution and wish to keep your existing hardware (not sure what that is), I would break the environment up onto two servers - the SBS 2003 as the domain controller running Exchange, DHCP, Print & File Server - and put the remaining APPS on the second server running S2K3 - making it a member of the SBS2003 domain established from migrating over your old NTv4 domain environment.
- John
|
Hi John,
Hardware currently using:
WinNT on IBM Server Xseries200 P3, 1.13GHZ 512MB RAM Storage:100GB
SBS2003 on IBM Server Xseries206 P4, 2.8GHZ 1GB RAM Storage: 36GB
Actually we don't really need a fast server bcoz the actual server usuage are not so high & we need it to provide administration & MS Exchange + the list below:
Currently using WinNT for:
- domain server
- streamserve application
- printer server
- file server
Currently using W2K3 SBS for:
- Veritas
- Microsoft Exchange
- XmediusFax
- DHCP
The main purpose is to allow communication & share domain between 2 compatiable OS like SBS2003 & W2K3 to trust each other' bcoz of NT limitations.