Solved

recipient policy

Posted on 2009-04-15
12
214 Views
Last Modified: 2012-05-06
Hi,

I have two exchange servers and they are installed as member servers to the main DC. I was gonna setup one exchange handling NY.mydomain.com and the other to hadle JP.mydomain.com

What's happening now is everytime I change the smtp address from one exchange server, the other follows it..what m I missing?


Cheers!

0
Comment
Question by:mikesteven
  • 6
  • 6
12 Comments
 
LVL 58

Accepted Solution

by:
tigermatt earned 500 total points
ID: 24149961

They're doing what they're meant to do. "Global" settings in Exchange will be mirrored by all Exchange Servers in the same domain.

You need to use some other way of filtering on your recipient policies, such that each policy only applies to the appropriate accounts. I would suggest using an attribute on each user account, to designate whether they should receive an @NY or @JP email address. You can then filter based on this in the Recipient Policies.

The other option is to simply configure the recipient policies to give any mailbox on a particular server or in a particular mailbox store to receive either an @JP or @NY address. I tend to avoid this situation though, as it can cause issues when users are migrated between servers.

-Matt
0
 

Author Comment

by:mikesteven
ID: 24151051
worked like a charm, i place a filter in the office category, NY and JP. then like you said creted a new recipient policy.

I was looking at the public fodlers and contact on each server and everything was being in sync, are there any other entity that's being sync that I do not know of? liek a useful feature?
0
 

Author Comment

by:mikesteven
ID: 24151080
matt,

more importantly is this a good setup? would you recommnd this? or this has a single point of failure?
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 24151338

With proper configuration, you won't have a single point-of-failure in your environment. You can configure MX records on both the @JP and @NY email domains so they point to Exchange Servers in both sites, with the intended site (NY for @NY and JP for @JP) with highest priority. That way, if the server in one site goes down, you can queue mail at the other end for up to 48 hours while the issue is resolved.

>> I was looking at the public fodlers and contact on each server and everything was being in sync, are there any other entity that's being sync that I do not know of? liek a useful feature

I'm not sure what you're mentioning there. The best way to check Public Folder Sync is in ESM.

-Matt
0
 

Author Comment

by:mikesteven
ID: 24151443
I turned off the AD and the web mail wasn't working for both sites. Did I do something wrong?
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 24151494

You didn't do anything wrong. Exchange depends on Active Directory for everything; if it has no Domain Controller to communicate with, everything will fall over. Ideally, you'd be installing at least 2 Domain Controllers on your network for resilience purposes in the event one failed.

-Matt
0
Too many email signature changes to deal with?

Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

 

Author Comment

by:mikesteven
ID: 24152013
matt thank you so much for everything. you are one amazing guy. So sorry to be off topic. but I'd like to learn more on the proper configuration you mentioned earlier, this is very very important, how can I go about the configs?

>>With proper configuration, you won't have a single point-of-failure in your environment. You can configure MX records on both the @JP and @NY email domains so they point to Exchange Servers in both sites, with the intended site (NY for @NY and JP for @JP) with highest priority. That way, if the server in one site goes down, you can queue mail at the other end for up to 48 hours while the issue is resolved.
<<
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 24152162

The MX records are what control which server(s) are responsible for receiving email for your network. Since your Exchange Servers are going to be part of the same Active Directory domain (and therefore the same Exchange organization), you can use each server as a temporary 'backup' server, where mail can queue if the other server is offline.

What you need to do is create two A records, say nymail.domain.com and jpmail.domain.com, and map them to the public static IP at that location.

Then, configure the MX records for jp.domain.com with jpmail.domain.com as the preferred server (lower cost number, which = highest preference), and nymail.domain.com as an additional MX with a higher cost. Use, say, costs of 5 and 10 respectively, as an example. Repeat, but in reverse for the ny.domain.com domain.

This essentially means all mail destined for NY will attempt to be delivered direct to NY first, but can be delivered to JP and queued there until NY becomes available if necessary (and the same, in reverse, for the JP domain).

Thanks for the kind words BTW :-)

-Matt
0
 

Author Comment

by:mikesteven
ID: 24155651
what do you meant by "queued" until the other one comes up? does this mean, email sent to the site that's having problems wont be lost but users wont also be able to open them until everything comes online?
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 24155861

Pretty much. Queued email is like email in storage; it's not reached its final delivery point (where user mailboxes are located), but it is held within your system. There is a limit on the queues and email will be returned to the sender as undeliverable if the email sits queued for too long without being delivered.

-Matt
0
 

Author Comment

by:mikesteven
ID: 24156436
is there a posibility to have a realtime back in place? like when NY goes down, users will automatically be routed to jp with their mailboxes there also, everything would be seemless to the users?
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 24158840

For that, you'd need some form of cluster. You could either implement an Exchange-based cluster (very costly) or use third-party software. DoubleTake is the commonly recommended product for doing this. It will replicate mailboxes between the two servers, and failover automatically if one goes down.

http://www.doubletake.com

-Matt
0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

"Migrate" an SMTP relay receive connector to a new server using info from an old server.
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now