Exchange 2010 with multiple domains
We have a domain that spans several different physical locations with a few hundred users and client machines. We were set to upgrade our Exchange 2003 server to Exchange 2010 when we learned we could not move forward as scheduled because the domain name was not acceptable to Exchange 2010 because it contains an underscore, such as DOMAIN_1 (this was set up by a previous IT staff and we wanted to change it at some point.)
Instead of delaying the project and creating a lot of chaos by trying to rename the entire domain in a hurry, we came up with the following idea: create a new domain controller for the new domain name we want to use (DOMAIN2) and set up two-way trusts between DOMAIN2 and DOMAIN_1. Then we can build the new Exchange 2010 server on a member server in DOMAIN2, import the mailboxes from the exchange server on DOMAIN_1. If users can authenticate across both domains, I think this should work.
Can anyone think of any reasons why it wouldn't, or other trouble we might hit along the way? Any 'gotchas' in this scenario?
Instead of delaying the project and creating a lot of chaos by trying to rename the entire domain in a hurry, we came up with the following idea: create a new domain controller for the new domain name we want to use (DOMAIN2) and set up two-way trusts between DOMAIN2 and DOMAIN_1. Then we can build the new Exchange 2010 server on a member server in DOMAIN2, import the mailboxes from the exchange server on DOMAIN_1. If users can authenticate across both domains, I think this should work.
Can anyone think of any reasons why it wouldn't, or other trouble we might hit along the way? Any 'gotchas' in this scenario?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
YOu will need to set up a connector between the exchange boxes so that mail can route from one to the other while you are in the process of migration your users.
why dont u go for zimbra.
your scenario makes perfect sense you can do it you don't even need a trust between them
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi everyone,
Thanks for the comments. There were two ways to progress with this project: rename the domain and put the Exchange upgrade on hold, or try to install exchange on a new domain that was accessible to the old one.
I decided to rename the domain first as this is something that needs to be done eventually regardless of the exchange server's upgrade. I will then upgrade the exchange server in the renamed domain without the additional layer of complexity the reverse would involve.
JuusoConnecta and DrUltima had the two responses that best represented what each path would involve. I have split the points between the two.
Regards,
Ad-Apex
Thanks for the comments. There were two ways to progress with this project: rename the domain and put the Exchange upgrade on hold, or try to install exchange on a new domain that was accessible to the old one.
I decided to rename the domain first as this is something that needs to be done eventually regardless of the exchange server's upgrade. I will then upgrade the exchange server in the renamed domain without the additional layer of complexity the reverse would involve.
JuusoConnecta and DrUltima had the two responses that best represented what each path would involve. I have split the points between the two.
Regards,
Ad-Apex
ASKER
Thanks for the assistance.