Right now I'm running SBS2000 as DC, about 40 clients. (T1 hookup) I've got another 7 workstation peer-to-peer in a remote location (DSL hookup).
The Server serves websites, email & dns - plus the DC.
I recently got a new server to put Exchange on (ontop of w2k3 standard). As I will be needing to run both email servers for awhile I figure I'll need to put the exchange on it's own public IP address.
Here are the questions.
-Should I join the Exchange server to the existing domain?
-If Not - then that would mean creating a new domain right for AD.
-How would the remote office connect up taking advantage of Exchanges Store - would I need to set up VPN's or can they do it with the remote connection by just putting in the Exchange server's IP Address?
Eventually I'd like to move websites also over to the exchange server if possible - get stuff off that DC as much as I can - I just have virtually no budget to work with.
And if there is anything else you can think of ?
many thanks.
Stuart
The Server serves websites, email & dns - plus the DC.
I recently got a new server to put Exchange on (ontop of w2k3 standard). As I will be needing to run both email servers for awhile I figure I'll need to put the exchange on it's own public IP address.
Here are the questions.
-Should I join the Exchange server to the existing domain?
-If Not - then that would mean creating a new domain right for AD.
-How would the remote office connect up taking advantage of Exchanges Store - would I need to set up VPN's or can they do it with the remote connection by just putting in the Exchange server's IP Address?
Eventually I'd like to move websites also over to the exchange server if possible - get stuff off that DC as much as I can - I just have virtually no budget to work with.
And if there is anything else you can think of ?
many thanks.
Stuart