• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 293
  • Last Modified:

Remove 2nd Primary Domain in Recipient Policy - Exchange 2003

We are in the process of sending our Exchange server offsite. Our future host is configuring our Exchange 2010 server and having issues because we have two domains marked as primary in our recipient policy.

@domain1 and @domain2 are both selected as primary in our default recipient policy.

If we attempt to remove @domain2 the Exchange server automatically adds @domain3 as a primary.

In order to complete the Exchange 2010 migration we have to have @domain1 as the only selected primary domain in our recipient policy.

How do we make this happen?
  • 2
  • 2
1 Solution
Simon Butler (Sembee)ConsultantCommented:
You must have multiple policies, as you cannot have two domains of type SMTP as primary.
It may well be that you need to recreate the recipient policy and create a new one.
Note that removing a domain from recipient policy does not remove the addresses from mailboxes, you have to use something else to do that.

CJones46Author Commented:
You are correct. Now it makes sense.

Policy #1 - has complete domain list and has @domain1 as primary
Policy #2 - only has @domain2 listed. @domain2 is listed as primary

Can policy #2 be deleted? @domain2 is also listed in Policy #1 so it isn't being removed entirely, it's just being designated as a secondary domain.

Is there benefit to deleting Policy #2 and recreating it with @domain1 as primary as well?

My inclination is to simply delete it since it only contains one domain but I'm leery to do so without some further information.
Simon Butler (Sembee)ConsultantCommented:
Are you sure that the Recipient Policy is being used for email address and isn't being used for Mailbox Management? That could be why you have the second policy.

Check the filter of the policy to see if it is being used to apply the address to specific users. However deleting it is probably going to be the best option, but you need to look carefully at how it is being used.

CJones46Author Commented:
We were able to remove the incorrect entry via ADSI edit.

Issue is resolved.  Thank you
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now