Hi experts! I'd really appreciate some advice/direction on best practices, if there are any, to deploying our SBS 2003 domain controller across a SPN network. SPN is being piped in by our ISP, Cox Communications. It is T1 via cable modem that connects to our main corporate office. That cable modem is connected to a Cisco fast ethernet router. That router is connected to identical routers at our two remote sites via cable modems on the 3mb synchronous loop called "SPN". We currently have basic windows workgroups set up and are preparing to deploy our domain controller across all 3 sites. My specific questions are:
1) SBS 2003 generally wants to be the DHCP server, but if I assigned static IPs to all of our clients, would I run in to trouble? Reason being, once this is deployed, if the server were to go down, I need the clients to be able to communicate both inside and outside our network. DHCP and routing is currently handled by the location-specific Cisco routers.
2) Is there a better way to handle IP assignments across multiple sites? Users at all locations can currently interact and share files and resources and this needs to continue.
3) Exchange: We have 40 users and I'd like to deploy exchange and outlook web as part of the SBS. Are there any considerations or risks I need to weigh considering all of this is meant to run on a single box? Again, the wizard-driven SBS 2003 likes to be the end-all be-all solution, but the absence of redundancy scares me to death. We currently use 3rd party-hosted pop mail, so setting up a contingency plan in the event of SBS crash would be optimal. I just have no idea where to start...
I've attached a screenshot of a whittled down topology to illustrate the SPN network.