This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Adding a second Exchange Server

Hi,

I have a SG230 and an Exchange 2010 Server running for a couple years now. Lately I installed an Exchange 2016 and plan to decomission the old Exchange Server.

The plan is to have both Exchanges running behind the SG230, and then start to move the users mailboxes (one by one!) to the new Exchange Server. No DAG, not failover/HA or anything. Its basically two exchange servers on the same site.

The new Exchange looks good und running so far. SSL certificates are imported etc. So I just moved myself as a testuser from the old Exchange to the new Exchange Server. Re-opened Outlook, check connection stats, and my Outlook indeed connects successfully to the new Exchange Server. Now the thing is, when I send me an E-Mail, the mail gets delivered to the OLD Exchange instead of the new Exchange Server. The Testmail is then stuck in the message queue on the old Exchange Server, because the recipients mailbox isn't there anymore (obviously). The recipients mailbox is on the new Exchange, but how could the UTM now, right?

https://imgur.com/a/DiH2P

So yeah, I kinda know why the mail gets delivered to the old (wrong) Exchange. The UTM cant know. However, basically everything is set to the NEW Server already (including WAF and Firewall Profiles - not shown in the Screenshots). When I send a testmail, according to "Live Log: SMTP proxy" it will be delivered to the old Server.

I am aware of it's probably not the UTMs fault. I think the "problem" is I have 2 exchange servers, and when the UTM fetches a mail it will be delivered just to the first exchange server in sight. But how to solve this? How to make the UTM (or the old Exchange) aware of forwarding the mail to the new Exchange (in case old server can't find the right Mailbox of the user)? There should be a way to tell the UTM the mail from specific users has to go to the new Server.

(unfortunately, no, I can't just move/migrate the whole Mailbox Databases to the new Exchange and shut off the old Server completely - this would probably work on the fly, but I can't dismount my DBs)

edit: another way that would probably solve my problem (if not feasable to do it through the UTM) is to make the old Exchange aware of the new Exchanges Databases/Mailboxes. But when ever I google for something like that ("share databases" or whatever) I cant find anything useful.

 

edit2: when I send a testmail from my Outlook to my personal (external) Mailaddress, Outlook will carry out that mail (its not in "outgoing" folder anymore), however the mail will not arrive at my personal mailbox. Also theres no trace of that outgoing testmail, not in the UTM, not on the (new) Exchange Server. ?

 

edit3: https://imgur.com/a/JBVe8, removed the old Server from "Host List" and mail is magically coming in now (inbound) for both the Users that are still on the old mail server, and the people I already moved to the new mailbox server. Looks like Exchange 2016 is able to figure out self if another (old) server is around, but not the reverse. (however, still cant have outbound mails for the migrated users/mailboxes - whenever I send a mail from the new Exchange Server, there is not trace of outgoing mail. Not sure what Exchange 2016 does to these mails, theres also no clue at the UTM)



This thread was automatically locked due to age.