What's involved to have SBS 2011 Standard handle a 2nd domain's emails?

We have an SBS 2011 standard setup with 1 domain for email.

How hard is it / what's involved to have it handle a 2nd domain? The addresses will be different for each domain (not just aliases of the 1st domain).

It'd be something like:

bob@domain1.com
ed@domain1.com
sue@domain2.com
howard@domain2.com

Thanks!
BeGentleWithMe-INeedHelpAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AlanConsultantCommented:
Hi,

You just need to add the second domain as an 'accepted domain' in Exchange:

Exchange Management Console
Organisation Configuration
Hub Transport
Accepted Domains

Add the new domain to the list as an 'authoritative domain' (assuming you are not relaying which I take from your post above).  You probably don't want to make it default (as least not initially).

You might also need to consider your default email address policy.  If a new user is added, the default policy determines which email addresses get automatically created for them (first.last@domain1, last.firstdomain2 etc etc).  It doesn't stop you adding more addresses to a user later, nor from removing them, so not the end of the world if you leave it or change your mind later.


Alan.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jose Gabriel Ortega CastroCEOCommented:
Prior to doing what Alan says, add the suffix to the AD.

https://gallery.technet.microsoft.com/scriptcenter/Add-Suffixes-to-Active-cfa9bb48

So you can actually do the Policy part (not required for the Accepted domain part).
0
AlanConsultantCommented:
@Jose:  I think the author is just wanting to add another email (internet) domain, not an additional Active Directory domain?

Or do I have it wrong?

Alan.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Jose Gabriel Ortega CastroCEOCommented:
he needs to add the full authentication for the domain.
So that end user can login with their "email" instead of using the "domain.local\user" sintax.

Adding the AD to the DC allows you to save the UPN to match the email and this way is taken by the email policy and it's easier for users to login without multiple combinations for email access.
0
AlanConsultantCommented:
Okay - I don't see where you are getting that requirement from.

Its seems like adding complexity where none is required?

Alan.
0
Jose Gabriel Ortega CastroCEOCommented:
It's best practices. If it's complex for you, it's your business I'm not letting to suggest the best practices because it seems too complex for you.

On exchange server, the user is in the center of all of this. Less complexity to them, more for us that's why we are called "experts"
0
AlanConsultantCommented:
Hi Jose,

You seem to have taken offence, and I regret that.

What I mean is that you *seem* to be inventing requirements that I am not seeing in the question.  Where are you getting the idea that the author wants to add a second Active Directory domain, rather than just receive emails from a second internet domain?


Alan.
0
Jose Gabriel Ortega CastroCEOCommented:
One thing *implies* the other.
If they want to receive emails using the second domain in exchange, they can add an "Email Policy" to add an *Alias*. This is your point.

My point is that they would want to create a second domain on the exchange server and also manage the users in this new email. That's why you would create the domain also in the AD and manage your users, and also apply the "Email policy" to create automatically the new domain into a specific Organizational Unit in their AD with their new domain. So users would want to "log in" to the AD to get their emails. This is mine, way more technical.

If it's there or not, I'm not reinventing the wheel sir, the wheel is already created, I'm just suggesting the step to do it the way I would do it following the best practices, more work for us less for clients. Either way is not a good use for this forum to get into specifics points of view, every person would have its own point of view and you should just respect that, not be going there criticizing if it's there or if I'm inventing or not I think that everyone has a point of view and needs to be respected.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.