exchange co-exist and SCP

dss ds 526 Reputation points
2022-06-28T21:28:41.563+00:00

when migrating one exchange to another (in the same organisation and same forest/domain) can two SCP connectors on each both co-exist as well and work?

E.g. We have quite a lot of large mailboxes that will take time to transfer across.. Based on how others do in live were mailboxes are queued, I cannot believe that all clients must first "stop" switch all then continue.. There would be too much disruption,

Instead, we were going to migrate in batches... Those on 2013 that haven't be moved can still send/receive email with Outlook, while those on 2016 that have already been moved will continue on new box as if noting happened.

This is correct ? because it looks like based on articles you "change" the SCP connector to new one... But from my understand all this does is suppress the error mismatch you would otherwise get..

Can we also copy over custom send connections ? We have a bunch of custom ones, or do we need to create them from scratch?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
6,095 questions
No comments
{count} votes

Accepted answer
  1. Andy David - MVP 110.4K Reputation points Microsoft MVP
    2022-06-28T21:43:42.577+00:00

    Are the servers in the same AD site? Generally you set the SCP to the same URL so that you can use the same certificate, but there is no requirement to do that.
    As long as the cert is trusted the clients will use it w/o any errors and it will work just fine. They wont stop and switch over. The Outlook client may pick up any of those SCPs in AD

    And yes, you need to recreate any custom receive connectors on the new server if required. You can export the settings for the original using Powershell them create the new ones with the same settings except for any IPs bound to the server itself.

    No comments

1 additional answer

Sort by: Most helpful
  1. dss ds 526 Reputation points
    2022-06-30T22:08:23.407+00:00

    Yes. however the there is also an MX record too... Email would work internally fine, routing to whichever exchange has the user mailbox, but not externally since the MX record can only point to one server at a time.

    Based on articles, its assumed you move mailboxes all over in "one hit" which is impossible on large mailboxes... So there must be a way to route anything that's coming in from outside world and function like it does for internal.. (ii.e route to connect server that has mailbox)

    I think the link here is "MX record", and there can't be two... already been down that path..

    No comments