Exchange Online Migration: Single Tenant with Multiple Exchange EndpointsExchange 2003 to 2010 Migration...
How much mayhem could I cause as a sentient fish?
Numbers with a minus sign in a matrix not aligned with the numbers wihtout minus sign
Why was Lupin comfortable with saying Voldemort's name?
How to use Mathematica to do a complex integrate with poles in real axis?
Why is it that Bernie Sanders is always called a "socialist"?
What is the difference between rolling more dice versus fewer dice?
Cat is tipping over bed-side lamps during the night
Aligning symbols underneath each other neatly
How does Leonard in "Memento" remember reading and writing?
Graph with overlapping labels
What is a good reason for every spaceship to carry a weapon on board?
Why publish a research paper when a blog post or a lecture slide can have more citation count than a journal paper?
Finding a logistic regression model which can achieve zero error on a training set training data for a binary classification problem with two features
Does every functor from Set to Set preserve products?
Can a Spectator be a bodyguard? So, can its treasure/item to guard be a person/person's item?
Create a Price Tag Icon with Rounded Corners
sObject type 'FlowTestCoverage' is not supported
Consequences of lack of rigour
Gear reduction on large turbofans
Odd 74HCT1G125 behaviour
SET NOCOUNT Error in handling SQL call after upgrade
What incentives do banks have to gather up loans into pools (backed by Ginnie Mae)and selling them?
Difference between i++ and (i)++ in C
Eww, those bytes are gross
Exchange Online Migration: Single Tenant with Multiple Exchange Endpoints
Exchange 2003 to 2010 Migration Backout PlanIntermittent communication issues with Office 365 (Exchange Online)Exchange 2010 to Exchange Online cutover migration errorComplex Exchange 2010 to Office 365 Migration with multiple domainsSimplest way to move a small public folder to Exchange Online?Exchange 2010 to 365 QuestionsCutover migration from exchange 2007 to exchange online errorExchange multi domains hybrid migrationSyncronize Exchange Online account with local exchangeExchange Online Transport Rule
Planning out a migration for 3 separate Exchange Servers/AD forests with no AD trusts configured; there is site-to-site connectivity by way of IPSec tunnels.
These three mail servers share an email domain by way of Internal Relays (configured for MX lookup, which points to a central ISP-owned Linux mail server with forwarding aliases setup for each recipient's respective Exchange Server).
My question is, can you setup multiple Exchange endpoints for a single Exchange Online tenant? Hybrid Full/Minimal or Cutover? Are there 3rd-party solutions that can do this if not?
microsoft-office-365 exchange-migration
add a comment |
Planning out a migration for 3 separate Exchange Servers/AD forests with no AD trusts configured; there is site-to-site connectivity by way of IPSec tunnels.
These three mail servers share an email domain by way of Internal Relays (configured for MX lookup, which points to a central ISP-owned Linux mail server with forwarding aliases setup for each recipient's respective Exchange Server).
My question is, can you setup multiple Exchange endpoints for a single Exchange Online tenant? Hybrid Full/Minimal or Cutover? Are there 3rd-party solutions that can do this if not?
microsoft-office-365 exchange-migration
add a comment |
Planning out a migration for 3 separate Exchange Servers/AD forests with no AD trusts configured; there is site-to-site connectivity by way of IPSec tunnels.
These three mail servers share an email domain by way of Internal Relays (configured for MX lookup, which points to a central ISP-owned Linux mail server with forwarding aliases setup for each recipient's respective Exchange Server).
My question is, can you setup multiple Exchange endpoints for a single Exchange Online tenant? Hybrid Full/Minimal or Cutover? Are there 3rd-party solutions that can do this if not?
microsoft-office-365 exchange-migration
Planning out a migration for 3 separate Exchange Servers/AD forests with no AD trusts configured; there is site-to-site connectivity by way of IPSec tunnels.
These three mail servers share an email domain by way of Internal Relays (configured for MX lookup, which points to a central ISP-owned Linux mail server with forwarding aliases setup for each recipient's respective Exchange Server).
My question is, can you setup multiple Exchange endpoints for a single Exchange Online tenant? Hybrid Full/Minimal or Cutover? Are there 3rd-party solutions that can do this if not?
microsoft-office-365 exchange-migration
microsoft-office-365 exchange-migration
asked 3 hours ago
gravyfacegravyface
12.3k145494
12.3k145494
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is possible in general, although quite tricky to get right; here's the only offical documentation I was able to find: https://docs.microsoft.com/en-us/previous-versions/exchange-server/exchange-150/jj873754(v=exchg.150). It refers to Exchange 2013 and it's marked as "no longer updated content", but it should still be valid.
Here is another unofficial but more recent article:
https://practical365.com/blog/exchange-multi-forest-hybrid-tips-and-tricks/
However, you are using the same SMTP domain in all forests, and this adds a whole lot of issues, not only for mail routing (which probably can still be made to work) but mainly for the Autodiscover service, which can't possibly work for all your users in this scenario, since every Exchange forest doesn't know about users in the other ones; and without a properly working Autodiscover service, lots of things are going to break.
My suggestion would be to perform three cutover migrations in sequence; setting up and running a three-forests hybrid environment where all forests share the same SMTP domain is going to be painful, if it works at all.
Was thinking the same thing: logistically, being in 3 places at once, would be near impossible anyways. There will be a net new AD forest setup centrally, which is what we will be running DirSync on for password synchronization, but getting all those profiles flipped over is going to be a helluva lot of boot prints...
– gravyface
2 hours ago
Yes, migrating everything to a single forest and then going to hybrid is the cleanest solution; I didn't mention it only because I was assuming you didn't want to add another forest to this mess :) But if you have enough time and resources, it's better indeed.
– Massimo
40 mins ago
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%2f956031%2fexchange-online-migration-single-tenant-with-multiple-exchange-endpoints%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
This is possible in general, although quite tricky to get right; here's the only offical documentation I was able to find: https://docs.microsoft.com/en-us/previous-versions/exchange-server/exchange-150/jj873754(v=exchg.150). It refers to Exchange 2013 and it's marked as "no longer updated content", but it should still be valid.
Here is another unofficial but more recent article:
https://practical365.com/blog/exchange-multi-forest-hybrid-tips-and-tricks/
However, you are using the same SMTP domain in all forests, and this adds a whole lot of issues, not only for mail routing (which probably can still be made to work) but mainly for the Autodiscover service, which can't possibly work for all your users in this scenario, since every Exchange forest doesn't know about users in the other ones; and without a properly working Autodiscover service, lots of things are going to break.
My suggestion would be to perform three cutover migrations in sequence; setting up and running a three-forests hybrid environment where all forests share the same SMTP domain is going to be painful, if it works at all.
Was thinking the same thing: logistically, being in 3 places at once, would be near impossible anyways. There will be a net new AD forest setup centrally, which is what we will be running DirSync on for password synchronization, but getting all those profiles flipped over is going to be a helluva lot of boot prints...
– gravyface
2 hours ago
Yes, migrating everything to a single forest and then going to hybrid is the cleanest solution; I didn't mention it only because I was assuming you didn't want to add another forest to this mess :) But if you have enough time and resources, it's better indeed.
– Massimo
40 mins ago
add a comment |
This is possible in general, although quite tricky to get right; here's the only offical documentation I was able to find: https://docs.microsoft.com/en-us/previous-versions/exchange-server/exchange-150/jj873754(v=exchg.150). It refers to Exchange 2013 and it's marked as "no longer updated content", but it should still be valid.
Here is another unofficial but more recent article:
https://practical365.com/blog/exchange-multi-forest-hybrid-tips-and-tricks/
However, you are using the same SMTP domain in all forests, and this adds a whole lot of issues, not only for mail routing (which probably can still be made to work) but mainly for the Autodiscover service, which can't possibly work for all your users in this scenario, since every Exchange forest doesn't know about users in the other ones; and without a properly working Autodiscover service, lots of things are going to break.
My suggestion would be to perform three cutover migrations in sequence; setting up and running a three-forests hybrid environment where all forests share the same SMTP domain is going to be painful, if it works at all.
Was thinking the same thing: logistically, being in 3 places at once, would be near impossible anyways. There will be a net new AD forest setup centrally, which is what we will be running DirSync on for password synchronization, but getting all those profiles flipped over is going to be a helluva lot of boot prints...
– gravyface
2 hours ago
Yes, migrating everything to a single forest and then going to hybrid is the cleanest solution; I didn't mention it only because I was assuming you didn't want to add another forest to this mess :) But if you have enough time and resources, it's better indeed.
– Massimo
40 mins ago
add a comment |
This is possible in general, although quite tricky to get right; here's the only offical documentation I was able to find: https://docs.microsoft.com/en-us/previous-versions/exchange-server/exchange-150/jj873754(v=exchg.150). It refers to Exchange 2013 and it's marked as "no longer updated content", but it should still be valid.
Here is another unofficial but more recent article:
https://practical365.com/blog/exchange-multi-forest-hybrid-tips-and-tricks/
However, you are using the same SMTP domain in all forests, and this adds a whole lot of issues, not only for mail routing (which probably can still be made to work) but mainly for the Autodiscover service, which can't possibly work for all your users in this scenario, since every Exchange forest doesn't know about users in the other ones; and without a properly working Autodiscover service, lots of things are going to break.
My suggestion would be to perform three cutover migrations in sequence; setting up and running a three-forests hybrid environment where all forests share the same SMTP domain is going to be painful, if it works at all.
This is possible in general, although quite tricky to get right; here's the only offical documentation I was able to find: https://docs.microsoft.com/en-us/previous-versions/exchange-server/exchange-150/jj873754(v=exchg.150). It refers to Exchange 2013 and it's marked as "no longer updated content", but it should still be valid.
Here is another unofficial but more recent article:
https://practical365.com/blog/exchange-multi-forest-hybrid-tips-and-tricks/
However, you are using the same SMTP domain in all forests, and this adds a whole lot of issues, not only for mail routing (which probably can still be made to work) but mainly for the Autodiscover service, which can't possibly work for all your users in this scenario, since every Exchange forest doesn't know about users in the other ones; and without a properly working Autodiscover service, lots of things are going to break.
My suggestion would be to perform three cutover migrations in sequence; setting up and running a three-forests hybrid environment where all forests share the same SMTP domain is going to be painful, if it works at all.
edited 42 mins ago
answered 2 hours ago
MassimoMassimo
52.9k44165280
52.9k44165280
Was thinking the same thing: logistically, being in 3 places at once, would be near impossible anyways. There will be a net new AD forest setup centrally, which is what we will be running DirSync on for password synchronization, but getting all those profiles flipped over is going to be a helluva lot of boot prints...
– gravyface
2 hours ago
Yes, migrating everything to a single forest and then going to hybrid is the cleanest solution; I didn't mention it only because I was assuming you didn't want to add another forest to this mess :) But if you have enough time and resources, it's better indeed.
– Massimo
40 mins ago
add a comment |
Was thinking the same thing: logistically, being in 3 places at once, would be near impossible anyways. There will be a net new AD forest setup centrally, which is what we will be running DirSync on for password synchronization, but getting all those profiles flipped over is going to be a helluva lot of boot prints...
– gravyface
2 hours ago
Yes, migrating everything to a single forest and then going to hybrid is the cleanest solution; I didn't mention it only because I was assuming you didn't want to add another forest to this mess :) But if you have enough time and resources, it's better indeed.
– Massimo
40 mins ago
Was thinking the same thing: logistically, being in 3 places at once, would be near impossible anyways. There will be a net new AD forest setup centrally, which is what we will be running DirSync on for password synchronization, but getting all those profiles flipped over is going to be a helluva lot of boot prints...
– gravyface
2 hours ago
Was thinking the same thing: logistically, being in 3 places at once, would be near impossible anyways. There will be a net new AD forest setup centrally, which is what we will be running DirSync on for password synchronization, but getting all those profiles flipped over is going to be a helluva lot of boot prints...
– gravyface
2 hours ago
Yes, migrating everything to a single forest and then going to hybrid is the cleanest solution; I didn't mention it only because I was assuming you didn't want to add another forest to this mess :) But if you have enough time and resources, it's better indeed.
– Massimo
40 mins ago
Yes, migrating everything to a single forest and then going to hybrid is the cleanest solution; I didn't mention it only because I was assuming you didn't want to add another forest to this mess :) But if you have enough time and resources, it's better indeed.
– Massimo
40 mins ago
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%2f956031%2fexchange-online-migration-single-tenant-with-multiple-exchange-endpoints%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