Adding a second exchange domain
Early next year I need to add a second exchange domain. Currently our setup is like this:
Site A - DC and Exchange are on seperate boxes
Site B - DC and Exchange are on same box (wasnt me)
We only have one logon domain and will stay like that. As of now everyone is setup with @maincompany.com email but I need to add @secondcompany.com email to only the exchange box at site B.
I checked routing groups > first routing group > members, and the box at site A is listed as "Master" and the box at site B is listed as "Member". Will adding a second email domain be feasible with our current config?
Site A - DC and Exchange are on seperate boxes
Site B - DC and Exchange are on same box (wasnt me)
We only have one logon domain and will stay like that. As of now everyone is setup with @maincompany.com email but I need to add @secondcompany.com email to only the exchange box at site B.
I checked routing groups > first routing group > members, and the box at site A is listed as "Master" and the box at site B is listed as "Member". Will adding a second email domain be feasible with our current config?
Comments
-
Claymoore Member Posts: 1,637It's easy to add email addresses to existing users with recipient policies in 2003:
How to use recipient policies to control e-mail addresses in Exchange 2003 and in Exchange 2000
Of course you will need to make sure that the MX records are set up as well so the Exchange box can send and receive mail. -
phoeneous Member Posts: 2,333 ■■■■■■■□□□Do I need to be concerned about the master vs member relationship between the two servers?
-
Claymoore Member Posts: 1,637No, email addresses have nothing to do with the routing groups and connectors. When Exchange receives an email for someone@newdomain.com, it will look up their mail server and database and send the mail on its way.
Only one recipeint policy can apply to an object, and the default policy has the lowest priority. When the Recipient Update Service runs (and RUS has a scheduling mind of its own), it will process the policies until it finds a match for that object and then stop. If you filter the policy by msExchHomeServerName, you can restrict the new address policy to only those users on that server.
Verifying the Required Active Directory Attributes -
phoeneous Member Posts: 2,333 ■■■■■■■□□□This is old but I'm bumping it to say thanks again. Finally got to do this project and works great!