How to promote over the primary SMTP address - Exchange 2007

Can someone please remind me....

Our SBS 2008 server has a domain of, say, FRED.COM.

I have a user that works for another organisation on it so I want to promote his e-mail address over the default, user@FRED.COM to  user@WILMA.COM.

When I try this is Exchange Management Colonsole/Recipient Configuration/Mailbox/User Name Properties/E-mail Addresses I get the message:

"Cannot remove the primary SMTP address 'user@FRED.COM'. Please promote another valid SMTP address before removing this one.

Can some kind soul remind me how to do this?

Many thanks...
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Tony JConnect With a Mentor Lead Technical ArchitectCommented:
Ok so the steps would be:

Ensure the new domain is on the accepted domains list within Exchange Management Console;

Edit the default email address policy and add in the new domain.

If it's per user, from the properties of the user account, edit the email addresses and uncheck the box to automatically update from email address policy. Highlight the new address, and click the "reply to" button.
Im not sure if ive got this right, do you just want to add an email address to all of the users and make it a primary address for all the users?

If so all you need to do is creat a new email address policy which will go though all the users SMTP address's and give them a new one. has a really good guide about this..

Please reply back if that is not what your looking for.

Best Regards

Dave J
Probably the best way to do this is to create a second email address policy with the second domain as well as the first (if he needs both).

If his organisation is set on his AD account, make sure that on this new email address policy, there is a filter to apply only to users with the organisation this user has.

This way if another user ever requires the same setup, you only have to create their account with the organisation the same as this user and they will receive the correct address automatically.

If it is only 1 user and will only ever be 1 user, refer to Tony1044.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tony JLead Technical ArchitectCommented:
As I've had pointed out to me recently, backed up by research, that won't work in Exchange 2007 or 2010 as it stops processing them after it finds a match.
Tony1044, which solution are you referring to as will not work?
edhastedAuthor Commented:
To clarify it is only this one user I need to alter.
The rest of the users remain on the default FRED.COM domain.
Tony1044 solution is the one you need.
Tony JLead Technical ArchitectCommented:
CW - it would appear, although I've only looked online and not tried this in my lab yet - that if the EAP's find a match, they stop processing.

So in the above, if there were two EAP's, the first would always match and the second never get processed which is why it's now a necessity to edit the default and not use additional ones.

Now this sounds both crazy, and a step backwards, and I'm eager to get in and try it on my lab but the few articles and blogs etc that I've found thus far do indeed suggest it's true.

That said, I am sure in the past, that configuring an additional EAP would still process, but with the precedence given.

I intend to give it a go at some point this week when I get a chance.
edhastedAuthor Commented:
Yes, it really is that easy. Whilst the system won't allow you to delete the primary or spell out how you promote, all you do is edit the e-mail addresses as you require. The one if BOLD is the primary.

Many thanks,

It works alright as long as you incorporate all addresses you want per policy (duplicates of all others) The hierachy  doesn't seem to work anymore.

Each one needs to be specific enough e.g. If you have a general one for most users then make that the default and for all others, filter by org, OU etc. and no overlap.

At least until the next Service pack!
Tony JLead Technical ArchitectCommented:
What a crock...let's break something that used to work so it, in turn, breaks all the best practices methodology too...

edhastedAuthor Commented:
So this no longer works in Exchange SP3.
We are on SP1.
Tony JLead Technical ArchitectCommented:
It'll work if you follow my way and edit the default EAP.

Not ideal, as you preferably shouldn't touch the default (it gives a clean, delete all the others to get back to basics backout method...when MS don't mess things up, of course).

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.

All Courses

From novice to tech pro — start learning today.