Discussion Locked

How to install 2 exchange servers with 1 domain

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello out there.

My question is this. I have a question which I know will be easy to answer but I just wanted to confirm my thoughts on how this could be done.

Let?s just say that I have 1 public domain called xyzusa.com which is in Texas and my email addresses are using user@xyzusa.com. I do have an exchange server in Texas but my exchange server is just acting like a storage for all email. We have a hosting company that pops email to the exchange server and then the clients pull down via exchange their email. I understand how the change the MX record to point to the exchange box so we are not relying on the hosting co to get mail.

The domain controller in Texas is a windows SBS 2003 and the FQDN of that server is xyz.city.local. I Would like to create a sub domain called xyz.utah.local and have that domain controller in Utah offsite. Then through AD setup users and the domain policy for those users to be able to login. Those users currently pop their email from the same hosting company that we use so that we all can have the same user@xyzusa.com email address.

The two offices would need from time to time access to files that are on each other?s servers, so a trust would have to be setup.

What would be the best way of accomplishing this. The ultimate goal would be to the exchange server deliver mail to both locations, or to have 2 exchange servers that act jointly , but are in physically to locations.

Can someone help me in this regard and thanks in advance for taking the time to look at this for me.

JKL

1 reply

by churdoo

The problem is that you're using Small Biz Server at the Texas site, and SBS will NOT allow you to create a child AD, nor will it allow you to create a trust to another AD. Furthermore, I don't think it will allow you to add another exchange server into the same exchange organization, although I'm not certain of this particular point.

First, how many peeps in Utah, and file sharing between sites notwithstanding, do you really need its own exchange server in Utah, versus Outlook RPC/HTTP from the Texas exchange server?

Do you have any dedicated bandwidth between the sites? If so, how much? Otherwise, what bandwidth do you have at each site and do you / will you have a VPN tunnel?

Given the SBS limitations, this is your greatest chance for success if you need a dedicated exchange server in Utah:

Upgrade the SBS in Texas with the SBS Transition Pack; add a W2K3 server to Utah and DCPromo as a separate or child AD with appropriate trusts in place;

add exchange server to Utah, and also specify this exchange server to be responsible for email delivery to @xyzusa.com.

Change your MX records, say to deliver email to your Texas site and get rid of your hosted POP mailboxes; then configure your Texas mail server's "forward all mail with unknown recipients to" setting (in ESM/your org/servers/texas server/protocols/smtp/default smtp virtual server/properties/the third tab I think) to specify your Utah exchange server.

This discussion is closed to new replies.