First off, thanks to all who have already assisted me. I really appreciate the help of the folks on this board.
We are ready to deploy Exchange 2003. Currently we are running a POP3 mail server (Gordano product). This mail server's mx record is pluto.scld.org.
We want to add our Exchange 2003 server to our 2003 AD domain and test before we "go live" with all of the users. We are considering the following options:
1. The Exchange 2003 server is currently set up on an internal test domain, seperate from our live domain. We own the domain name scld.net and are thinking of adding a mx and DNS record for exhange.scld.net and testing the server on the test network. This way we can test transparent to our live users.
2. Add the Exchange server to our live domain and add a second mx record for scld.org. Seems harder to test this way as pluto.scld.org (the pop3 server) will handle all initial mail requests from the internet and if its down mail will get delivered to exchange.scld.org (the new mx record for scld.org) and that could result in a loss of email.
3. Go for broke. Turn off the pop3 server and install the new Exchange server to our live AD network and give it the same name and IP address as the old pop3 server. That way its already resolved on the internet, clients are already set to receive mail from the server name. BUT there really is no testing. It may work. It may not. Scary to take that chance. Has anyone else?
Any advice on how to deploy in our environment (10 sites, around 200 users, Windows Server 2003/AD) would be GREATLY appreciated.
Thanks in advance!
Tony LaSoya
Spokane County Library District
We are ready to deploy Exchange 2003. Currently we are running a POP3 mail server (Gordano product). This mail server's mx record is pluto.scld.org.
We want to add our Exchange 2003 server to our 2003 AD domain and test before we "go live" with all of the users. We are considering the following options:
1. The Exchange 2003 server is currently set up on an internal test domain, seperate from our live domain. We own the domain name scld.net and are thinking of adding a mx and DNS record for exhange.scld.net and testing the server on the test network. This way we can test transparent to our live users.
2. Add the Exchange server to our live domain and add a second mx record for scld.org. Seems harder to test this way as pluto.scld.org (the pop3 server) will handle all initial mail requests from the internet and if its down mail will get delivered to exchange.scld.org (the new mx record for scld.org) and that could result in a loss of email.
3. Go for broke. Turn off the pop3 server and install the new Exchange server to our live AD network and give it the same name and IP address as the old pop3 server. That way its already resolved on the internet, clients are already set to receive mail from the server name. BUT there really is no testing. It may work. It may not. Scary to take that chance. Has anyone else?
Any advice on how to deploy in our environment (10 sites, around 200 users, Windows Server 2003/AD) would be GREATLY appreciated.
Thanks in advance!
Tony LaSoya
Spokane County Library District