Create internal connector Exchange 2019 before moving mailboxes

Dannny 0 Reputation points
2023-02-21T20:32:05.77+00:00

Hi all, i got this job to migrate my Exchange server 2019 mailboxes in DAG to another Exchange server mailbox in DAG hosted on a cloud platform.
I was able to create my 2 other servers and create a second DAG with recplicated DB.
Since my new infrastructure will have a different ip addres, before moving my mailboxes from sv1/sv2 to sv3 and sv4 i would like to create a connector so that migrated mailboxed will redirected to the first DAG. Once all the mailboxes are migrated i plan to change MX records and DNS records to the new public IP Address.
Would you guide me in the creation of this internal connector?

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,173 questions
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.
7,468 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
446 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Andy David - MVP 144.4K Reputation points MVP
    2023-02-21T20:52:07.77+00:00

    Sounds like you need a shared SMTP space and continue to point the mx record at the existing Exch Servers

    [http://clintboessen.blogspot.com/2020/07/smtp-namespace-sharing-how-it-differs.html]

    To configure SMTP Namespace Sharing, you would change the Accepted Domain to an "Internal Relay Domain" and then create a send connector.  An example config would look like this:

    Set-AcceptedDomain contoso.com -DomainType InternalRelay

    New-SendConnector -Name "SMTP Namespace Sharing for Consoto.com" -Custom -AddressSpaces contoso.com -SmartHosts 10.1.1.54 -SourceTransportServers ExchangeServerFQDN

    User's image

    Once migrated, then you can change the MX record to point to the new infrastructure and set the accepted domain to Authoritative

    1 person found this answer helpful.