Exchange Hybrid Migration
Apologies if this question has been answered before. We are going for Exchange hybrid migration to EOL (Exchange Online). On-premise, we have Exchange 2016 mailbox and Exchange 2016 Edge transport servers, DLP appliance (Forcepoint 8.4) and Cisco Email Security as our mail gateway.
We are enabling Centralised Mail Transport (CMT) because we wish to retain the DLP appliance for now until all mailboxes are migrated.
1) When running the HCW, should I choose the Edge Transport server as the Optimal server or the Exchange 2016 mailbox server? The Edge Transport server is used for address-rewrite for outgoing emails. Incoming emails do not traverse the Edge Transport server.
2) Is there any additional configuration needed on the send/receive connectors, so that email delivered to the online mailbox is routed back to the on-premise Exchange (CMT) without issues. I read somewhere that you should not have anything in between the on-premise Exchange and EOL that modifies the email.
3) Is there any address rewriting capabilities in Exchange Online?
Thank you.
email exchange
asked Jan 26 at 4:42
RNathanRNathan
61
migrated from superuser.com Jan 26 at 22:49
This question came from our site for computer enthusiasts and power users.
add a comment |
Apologies if this question has been answered before. We are going for Exchange hybrid migration to EOL (Exchange Online). On-premise, we have Exchange 2016 mailbox and Exchange 2016 Edge transport servers, DLP appliance (Forcepoint 8.4) and Cisco Email Security as our mail gateway.
We are enabling Centralised Mail Transport (CMT) because we wish to retain the DLP appliance for now until all mailboxes are migrated.
1) When running the HCW, should I choose the Edge Transport server as the Optimal server or the Exchange 2016 mailbox server? The Edge Transport server is used for address-rewrite for outgoing emails. Incoming emails do not traverse the Edge Transport server.
2) Is there any additional configuration needed on the send/receive connectors, so that email delivered to the online mailbox is routed back to the on-premise Exchange (CMT) without issues. I read somewhere that you should not have anything in between the on-premise Exchange and EOL that modifies the email.
3) Is there any address rewriting capabilities in Exchange Online?
Thank you.
email exchange
asked Jan 26 at 4:42
RNathanRNathan
61
migrated from superuser.com Jan 26 at 22:49
This question came from our site for computer enthusiasts and power users.
add a comment |
Apologies if this question has been answered before. We are going for Exchange hybrid migration to EOL (Exchange Online). On-premise, we have Exchange 2016 mailbox and Exchange 2016 Edge transport servers, DLP appliance (Forcepoint 8.4) and Cisco Email Security as our mail gateway.
We are enabling Centralised Mail Transport (CMT) because we wish to retain the DLP appliance for now until all mailboxes are migrated.
1) When running the HCW, should I choose the Edge Transport server as the Optimal server or the Exchange 2016 mailbox server? The Edge Transport server is used for address-rewrite for outgoing emails. Incoming emails do not traverse the Edge Transport server.
2) Is there any additional configuration needed on the send/receive connectors, so that email delivered to the online mailbox is routed back to the on-premise Exchange (CMT) without issues. I read somewhere that you should not have anything in between the on-premise Exchange and EOL that modifies the email.
3) Is there any address rewriting capabilities in Exchange Online?
Thank you.
email exchange
asked Jan 26 at 4:42
RNathanRNathan
61
Apologies if this question has been answered before. We are going for Exchange hybrid migration to EOL (Exchange Online). On-premise, we have Exchange 2016 mailbox and Exchange 2016 Edge transport servers, DLP appliance (Forcepoint 8.4) and Cisco Email Security as our mail gateway.
We are enabling Centralised Mail Transport (CMT) because we wish to retain the DLP appliance for now until all mailboxes are migrated.
1) When running the HCW, should I choose the Edge Transport server as the Optimal server or the Exchange 2016 mailbox server? The Edge Transport server is used for address-rewrite for outgoing emails. Incoming emails do not traverse the Edge Transport server.
2) Is there any additional configuration needed on the send/receive connectors, so that email delivered to the online mailbox is routed back to the on-premise Exchange (CMT) without issues. I read somewhere that you should not have anything in between the on-premise Exchange and EOL that modifies the email.
3) Is there any address rewriting capabilities in Exchange Online?
Thank you.
email exchange
email exchange
asked Jan 26 at 4:42
RNathanRNathan
61
asked Jan 26 at 4:42
RNathanRNathan
61
asked Jan 26 at 4:42
RNathanRNathan
61
asked Jan 26 at 4:42
RNathanRNathan
61
asked Jan 26 at 4:42
RNathanRNathan
61
61
migrated from superuser.com Jan 26 at 22:49
This question came from our site for computer enthusiasts and power users.
migrated from superuser.com Jan 26 at 22:49
This question came from our site for computer enthusiasts and power users.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
1) Edge server.
2) No. When you add an Edge Transport server to your hybrid deployment, it communicates with EOP on behalf of the internal Exchange servers. The Edge Transport server acts as a relay between the internal Exchange servers and EOP for outbound messaging from the on-premises organization to the Exchange Online organization.
If you need to delete and recreate an Edge subscription that's used to communicate between your on-premises organization and Exchange Online, make sure to run the Hybrid Configuration wizard again.
3)No. We must use Edge server for address rewriting.
answered Jan 28 at 3:25
Jayce YangJayce Yang
744
Thanks. The edge transport only processes outgoing emails for address rewriting. So, is it ok to set this one up as the "hybrid server"?
– RNathan
Feb 3 at 2:06
Thanks Jayce, we have a DLP appliance on prem and most of the users are using IronPort as gateway. That's why I chose Centralised Transport. They are not prepared to decom their legacy stuff at the moment. The Edge server only does outgoing mail. Incoming is straight to the Exchange 2016. We will be turning off the Edge transport server so we will use IronPort for the address rewriting
– RNathan
Feb 7 at 8:07
Thanks for sharing.
– Jayce Yang
Feb 12 at 6:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f950949%2fexchange-hybrid-migration%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1) Edge server.
2) No. When you add an Edge Transport server to your hybrid deployment, it communicates with EOP on behalf of the internal Exchange servers. The Edge Transport server acts as a relay between the internal Exchange servers and EOP for outbound messaging from the on-premises organization to the Exchange Online organization.
If you need to delete and recreate an Edge subscription that's used to communicate between your on-premises organization and Exchange Online, make sure to run the Hybrid Configuration wizard again.
3)No. We must use Edge server for address rewriting.
answered Jan 28 at 3:25
Jayce YangJayce Yang
744
Thanks. The edge transport only processes outgoing emails for address rewriting. So, is it ok to set this one up as the "hybrid server"?
– RNathan
Feb 3 at 2:06
Thanks Jayce, we have a DLP appliance on prem and most of the users are using IronPort as gateway. That's why I chose Centralised Transport. They are not prepared to decom their legacy stuff at the moment. The Edge server only does outgoing mail. Incoming is straight to the Exchange 2016. We will be turning off the Edge transport server so we will use IronPort for the address rewriting
– RNathan
Feb 7 at 8:07
Thanks for sharing.
– Jayce Yang
Feb 12 at 6:21
add a comment |
1) Edge server.
2) No. When you add an Edge Transport server to your hybrid deployment, it communicates with EOP on behalf of the internal Exchange servers. The Edge Transport server acts as a relay between the internal Exchange servers and EOP for outbound messaging from the on-premises organization to the Exchange Online organization.
If you need to delete and recreate an Edge subscription that's used to communicate between your on-premises organization and Exchange Online, make sure to run the Hybrid Configuration wizard again.
3)No. We must use Edge server for address rewriting.
answered Jan 28 at 3:25
Jayce YangJayce Yang
744
Thanks. The edge transport only processes outgoing emails for address rewriting. So, is it ok to set this one up as the "hybrid server"?
– RNathan
Feb 3 at 2:06
Thanks Jayce, we have a DLP appliance on prem and most of the users are using IronPort as gateway. That's why I chose Centralised Transport. They are not prepared to decom their legacy stuff at the moment. The Edge server only does outgoing mail. Incoming is straight to the Exchange 2016. We will be turning off the Edge transport server so we will use IronPort for the address rewriting
– RNathan
Feb 7 at 8:07
Thanks for sharing.
– Jayce Yang
Feb 12 at 6:21
add a comment |
1) Edge server.
2) No. When you add an Edge Transport server to your hybrid deployment, it communicates with EOP on behalf of the internal Exchange servers. The Edge Transport server acts as a relay between the internal Exchange servers and EOP for outbound messaging from the on-premises organization to the Exchange Online organization.
If you need to delete and recreate an Edge subscription that's used to communicate between your on-premises organization and Exchange Online, make sure to run the Hybrid Configuration wizard again.
3)No. We must use Edge server for address rewriting.
answered Jan 28 at 3:25
Jayce YangJayce Yang
744
1) Edge server.
2) No. When you add an Edge Transport server to your hybrid deployment, it communicates with EOP on behalf of the internal Exchange servers. The Edge Transport server acts as a relay between the internal Exchange servers and EOP for outbound messaging from the on-premises organization to the Exchange Online organization.
If you need to delete and recreate an Edge subscription that's used to communicate between your on-premises organization and Exchange Online, make sure to run the Hybrid Configuration wizard again.
3)No. We must use Edge server for address rewriting.
answered Jan 28 at 3:25
Jayce YangJayce Yang
744
answered Jan 28 at 3:25
Jayce YangJayce Yang
744
answered Jan 28 at 3:25
Jayce YangJayce Yang
744
answered Jan 28 at 3:25
Jayce YangJayce Yang
744
744
Thanks. The edge transport only processes outgoing emails for address rewriting. So, is it ok to set this one up as the "hybrid server"?
– RNathan
Feb 3 at 2:06
Thanks Jayce, we have a DLP appliance on prem and most of the users are using IronPort as gateway. That's why I chose Centralised Transport. They are not prepared to decom their legacy stuff at the moment. The Edge server only does outgoing mail. Incoming is straight to the Exchange 2016. We will be turning off the Edge transport server so we will use IronPort for the address rewriting
– RNathan
Feb 7 at 8:07
Thanks for sharing.
– Jayce Yang
Feb 12 at 6:21
add a comment |
Thanks. The edge transport only processes outgoing emails for address rewriting. So, is it ok to set this one up as the "hybrid server"?
– RNathan
Feb 3 at 2:06
Thanks Jayce, we have a DLP appliance on prem and most of the users are using IronPort as gateway. That's why I chose Centralised Transport. They are not prepared to decom their legacy stuff at the moment. The Edge server only does outgoing mail. Incoming is straight to the Exchange 2016. We will be turning off the Edge transport server so we will use IronPort for the address rewriting
– RNathan
Feb 7 at 8:07
Thanks for sharing.
– Jayce Yang
Feb 12 at 6:21
Thanks. The edge transport only processes outgoing emails for address rewriting. So, is it ok to set this one up as the "hybrid server"?
– RNathan
Feb 3 at 2:06
Thanks. The edge transport only processes outgoing emails for address rewriting. So, is it ok to set this one up as the "hybrid server"?
– RNathan
Feb 3 at 2:06
Thanks Jayce, we have a DLP appliance on prem and most of the users are using IronPort as gateway. That's why I chose Centralised Transport. They are not prepared to decom their legacy stuff at the moment. The Edge server only does outgoing mail. Incoming is straight to the Exchange 2016. We will be turning off the Edge transport server so we will use IronPort for the address rewriting
– RNathan
Feb 7 at 8:07
Thanks Jayce, we have a DLP appliance on prem and most of the users are using IronPort as gateway. That's why I chose Centralised Transport. They are not prepared to decom their legacy stuff at the moment. The Edge server only does outgoing mail. Incoming is straight to the Exchange 2016. We will be turning off the Edge transport server so we will use IronPort for the address rewriting
– RNathan
Feb 7 at 8:07
Thanks for sharing.
– Jayce Yang
Feb 12 at 6:21
Thanks for sharing.
– Jayce Yang
Feb 12 at 6:21
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f950949%2fexchange-hybrid-migration%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
