one domain, two sites with two SMTP address spaces

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

e2k3 - 29 May 2006 14:45 GMT

Hi Exchange Experts,
I would appreciate your advices for this:
Let's say in site 1 we currently have one AD domain ABC and one exchange
server receiving email to SMTP address spaces xyz.com and zyx.com.
Now we want to set up another server in site 2 and join the AD domain ABC.
We want to set up an exchange server in site 2 in such a way that the
exchange server in site 1 still receives email to both address spaces but
route email addressed to zyx.com to exchange server in site 2.
How should I implement this?
1. should the organization name in site 2 be the same as site 1?
2. should I use routine group connector or smtp connector? and how to
configure it?

Reply to this Message

Bharat Suneja [MVP] - 30 May 2006 17:55 GMT

Inline.

Signature

Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------

> Hi Exchange Experts,
> I would appreciate your advices for this:
[quoted text clipped - 5 lines]
> route email addressed to zyx.com to exchange server in site 2.
> How should I implement this?

> 1. should the organization name in site 2 be the same as site 1?

There can only be 1 Exchange Org in an AD Forest, so yes Organization name
will be the same for the entire Forest. However, this does not at all relate
or map to SMTP domains/email addresses -think of it as just a placeholder
within the Configuration naming context of an AD Forest.

> 2. should I use routine group connector or smtp connector? and how to
> configure it?

You could use either, but RGC recommended.

Setting up new SMTP Domain:
1. Setup External DNS zone for xyz.com
2. Point MX to the A record/fqdn of Exchange server in ABC domain
3. Setup Recipient Policy to generate email addresses for xyz.com
4. Create Routing Group Connector both ways between both Routing Groups
- in General tab, select the appropriate remote Routing Group from the
"Connects this routing group with:"
- select local Bridgehead (default: all servers in this Routing Group can
send over the Connector)
- in "Remote Bridgeheads" tab, select appropriate remote Bridgehead
- Look at any other options you may want to configure depending on your
requirements.

Reply to this Message

e2k3 - 31 May 2006 03:41 GMT

Thanks very much Bharat. This is very helpful.

That means all incoming mail will be passed on to the server in site 1 as
before, but for those to the zyx.com address space the server will route
them to the server in site 2 via the routine group connector and eventually
delivered to the end users' mailboxes in site 2. Is it correct?

Should I use one administrative group for two routine groups or one for
each?

> Inline.
>
[quoted text clipped - 30 lines]
> - Look at any other options you may want to configure depending on your
> requirements.

Reply to this Message

Bharat Suneja [MVP] - 31 May 2006 04:13 GMT

Correct on the first assumption.

Re 2 Administrative Groups - AGs are for separating administrative
responsibilities. If you had a separate IT dept./admin in the other location
and you wanted to restrict administration of that server/all servers in that
"site"/location, you would create a separate AG.

Routing Groups are for message routing - servers within the same RG can talk
SMTP to each other directly, no Connectors required. Between RGs you need
(RG) Connectors, and messages are routed from sending server in a site to
the server designated as the local "Bridgehead" on the Connector - which
then forwards it to the Bridgehead on the other end of the remote RG, and on
to the receiving server.

In this case, it appears you don't require to separate administration, so a
single AG should suffice.

Signature

Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------

> Thanks very much Bharat. This is very helpful.
>
[quoted text clipped - 41 lines]
>> - Look at any other options you may want to configure depending on your
>> requirements.

Reply to this Message

e2k3 - 31 May 2006 07:05 GMT

Thanks again.
I am clearer.
So it would be one AG two RG topology.
I heard that with mixed mode only one RG per AG is supported.
If this is true I would have to change current mode (mixed) to the Native,
right?
It should be all right as both echange servers are 2003.
Would this change cause any side effects? Can I do the change at any time
while users are online?
--

> Correct on the first assumption.
>
[quoted text clipped - 59 lines]
>>> - Look at any other options you may want to configure depending on your
>>> requirements.

Reply to this Message

Bharat Suneja [MVP] - 31 May 2006 07:49 GMT

Where did you hear that?

As a sidenote, Exchange mixed mode simply means you can/may have Exchange
5.5 servers in the Org.
If you don't, you can switch the Org to native mode without anyone noticing.

Signature

Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------

> Thanks again.
> I am clearer.
[quoted text clipped - 70 lines]
>>>> - Look at any other options you may want to configure depending on your
>>>> requirements.

Reply to this Message

e2k3 - 02 Jun 2006 02:49 GMT

Thanks again, Bharat.

I have one more question - even though it might be a setup question:
If this new DC/Exchange server on a new site of the same domain, same
organisation, but different routine group,
how can I ensure the OWA and Outlook over HTTP work? During the exchange
installation do I have chance to install a windows certificate on this new
server?

Thanks in advance.

> Where did you hear that?
>
[quoted text clipped - 77 lines]
>>>>> - Look at any other options you may want to configure depending on
>>>>> your requirements.

Reply to this Message

Bharat Suneja [MVP] - 02 Jun 2006 14:46 GMT

- OWA works out-of-the-box.
- You will need to configure RPC over HTTP.
- Cert can be installed before or after Exchange installation - the cert is
issued to the computer, not to an individual application. As such, it can be
installed at any time, and the default web site configured to use the cert.

Signature

Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------

> Thanks again, Bharat.
>
[quoted text clipped - 89 lines]
>>>>>> - Look at any other options you may want to configure depending on
>>>>>> your requirements.

Reply to this Message

newserver - 03 Jun 2006 00:14 GMT

Thsnk!
I do not have a third party certificate so that want to just install one
provided by Windows.
How should I do this?

>- OWA works out-of-the-box.
> - You will need to configure RPC over HTTP.
[quoted text clipped - 96 lines]
>>>>>>> - Look at any other options you may want to configure depending on
>>>>>>> your requirements.

Reply to this Message

Bharat Suneja [MVP] - 03 Jun 2006 02:12 GMT

Windows does not provide a certificate as such. What it does have is the
Certificate Services component.

However, if you haven't set up CertSvc before, rather than deal with the
hassle of setting up a CA I'd look into the option of purchasing a 3rd party
cert - there are some very inexpensive CAs out there that will issue you a
cert for as low as under $50 (some even as low as $30, iirc). Look for a CA
that's trusted by Windows - you can check the list of trusted Root CAs from
the Certificates MMC snap-in or from IE.

You'll end up spending more time (which does have a cost... :) setting up
Certificate Svc yourself - not worth it for a single certificate, imo.

Signature

Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------

> Thsnk!
> I do not have a third party certificate so that want to just install one
[quoted text clipped - 101 lines]
>>>>>>>> - Look at any other options you may want to configure depending on
>>>>>>>> your requirements.

Reply to this Message

e2k3 - 03 Jun 2006 06:38 GMT

Thanks for the advice.
I didn't realize this.
My had an Windows server 2003 SBS on which it has a certificate called
CertSBS. I thouht all windows come with something like this.

> Windows does not provide a certificate as such. What it does have is the
> Certificate Services component.
[quoted text clipped - 116 lines]
>>>>>>>>> - Look at any other options you may want to configure depending on
>>>>>>>>> your requirements.

Reply to this Message

Michael Books - 08 Jun 2006 20:49 GMT

You can only have 1 Exchange org per forest. You situation sounds very
simple. Join new server to the domain, install Exchange part of the same
organization and place in a seperate routing group if needed. If both
servers are part of the same org, mail will flow to server 1 and if the user
is on Server 2, Server 1 will route the mail through the MTA or routing group
connector depending on your configuration.

Signature

Michael

> Hi Exchange Experts,
> I would appreciate your advices for this:
[quoted text clipped - 8 lines]
> 2. should I use routine group connector or smtp connector? and how to
> configure it?

Reply to this Message