Exchange Server Forums

Edge server installation

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2010] >> Installation >> Edge server installation

Page: [1]

Message

<< Older Topic Newer Topic >>

Edge server installation - 4.Apr.2013 6:29:43 AM

scott.mcgrath

Posts: 56
Joined: 9.Mar.2006
Status: offline

Hello,

We need some advice on a procedure for a piece of work we are doing.

We currently have four Edge servers. They are basically smarthosts in that our HT Servers have send connectors setup to send email to them.

There are * send connectors for all external email as well as a few specific namespace connectors. The Edge servers then have send connectors that send * to MessageLabs (Symantec.cloud). The Edge servers then also have some specific namespace connectors to send to domains with enforced TLS etc�

We want to replace this with four new Edge servers and have edge subscriptions setup between the HT and Edge servers.

We are doing it in a two phase approach. I.e. do two of the servers one week and do the other two servers two weeks later, to ensure continued service.

We are concerned about the following:

1. When the two new edge servers are installed, and before we setup the edge subscription, how do we implement the connectors on the edge servers to make sure they work on the new ones as well? So do we install them manually on the two new edge servers and then let the edge subscription process copy them in? or should we create them on the Hub Transport servers before the edge subscription process.
2. For a short period, we�ll have two servers using the �smarthost� config and two using the edgesync process. Is this OK? Keeping in mind the edgesync connectors will be setup on the HT servers and they will also be setup on the old servers.

Thanks.

Post #: 1

Featured Links*

RE: Edge server installation - 4.Apr.2013 1:30:25 PM

de.blackman

Posts: 3542
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline

Hi Scott,

One thing to remember is that edge subscription is a one-way replication from your active directory to the edge servers. Whatever changes you make on the edge servers will remain local and will NOT replicate back to the internal network.

"EdgeSync is a collection of processes that are run on a computer that has the Hub Transport server role installed to establish one-way replication of recipient and configuration information from Active Directory to the AD LDS instance on an Edge Transport server"
http://technet.microsoft.com/en-us/library/bb124701(v=exchg.141).aspx

So you do not need to create the connectors on the edge. Edgesync will replicate them from your hub transport servers from the site you subscribe the edge servers to.

_____________________________

Ibrahim Benna - Microsoft Exchange MVP
Forum Moderator
Navantis
@IbrahimBenna

(in reply to scott.mcgrath)

Post #: 2

RE: Edge server installation - 5.Apr.2013 4:17:00 AM

scott.mcgrath

Posts: 56
Joined: 9.Mar.2006
Status: offline

Hi Ibrahim,

Thanks for you reply. That's a helpful link.

I'm still concerned about one thing though.

Once we commission the two new servers, and set-up the EdgeSync process, there will be two new Edge Servers using the Edge Sync process, and for a short time two old servers still using the old 'Smarthost' type config.

So that means the connectors to the outside world will be set-up on the HT Servers for the EdgeSync process, and also on two Old Edge servers. I'm not sure if this is OK, or should we be planning to turn off the two old servers at the same time we commission the new two servers?

Basically the HT Servers will have the current * connector to the two old Edge, and the two EdgeSubscriptions to the two new Edge, plus for the EdgeSubscription we'll have the Connectors setup on the HT's as well. Sorry bit confusing.

Eventually we'll be turning the two old servers off, and replacing them too so that's fine as we'll have all four servers will have Edge Subscriptions so that's fine.

But for the time of the change over, there'll be connectors configured on the HT Servers and the two old Edge. Do you have any thoughts on this?

(in reply to de.blackman)

Post #: 3

RE: Edge server installation - 5.Apr.2013 7:58:42 AM

de.blackman

Posts: 3542
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline

I would recommend that you actually deploy the connectors on the HT servers not directly on the edge transport servers. This way once you enable a new subscription, you don't need to worry about things like this in the future.

Why do you have 4 edge servers? Are they in different locations?

_____________________________

Ibrahim Benna - Microsoft Exchange MVP
Forum Moderator
Navantis
@IbrahimBenna

(in reply to scott.mcgrath)

Post #: 4

RE: Edge server installation - 5.Apr.2013 8:32:40 AM

toybits

Posts: 8
Joined: 22.Jan.2009
Status: offline

Yeah we have two production data centres. Each one has been fitted with enough kit to run the entire email infrastructure. However during production time they share the load about 50/50.

We were going to be configuring the connectors on the HT's before doing the Edge subscription.

But we currently have a * connector to send to the current Edge servers. Then those two Edge Servers have the various connectors to the internet.

So this is where I'm wondering. When we setup the connectors to the internet on the Hub Transport servers, and then the Edge Subscription to the NEW edge servers, we'll have the following.

1. Old * Connector from Hub to the old Edges.
2. The old Connectors to the Internet on the old Edges.
3. The connectors on the HT for the Edge Subscriptions
4. the Two new Edge Servers with Edge Subscriptions setup.

So I'm not sure if that's a good idea.

I'm thinking maybe when we enable the Edge Subscriptions, we disable the * Connectors to the old edge and shut down the old edge. But my boss wants to run in parallel for a while.

We've logged a call with Microsoft PSS too to see what they think.

Thanks again for your input.

(in reply to de.blackman)

Post #: 5