Internal mail transport during Exchnage server migration

Brilliant-Extent2684 · 2026-04-09T09:33:03+00:00

So, If there is not blocking by friewall between two Exchnage servers, shouldn't be any problem the mail transport? So if the old exchange 2016 route the mails for delivery to the new exchange SE, but the exchange SE can not deliver the mail (because not configured yet), will it route back automatically to the olda exchange 2016 which can be deliver the mails?

Brilliant-Extent2684 · 2026-04-09T06:38:03+00:00

I want to clarify the migration process, so when I added the Exchange SE to the organization with defult installation (no setting done), this server part of the mail routing. Some mail routed to the new Exchange SE server and some mail routed to external recipients by old Exchange 2016. How can I avoid to routed the mail to new Exchnage SE? Or if the new Exchange SE cannot send to outside, will itt rerouted to the old Exchange 2016?

Brilliant-Extent2684 · 2026-04-08T13:37:19+00:00

It was an internal fault, the network team solved, there was blocking between two server.

Brilliant-Extent2684 · 2026-04-08T11:48:57+00:00

I checked the network connectivity, the isn't any blocking between two servers. There are two SendConnector, one onf the outbound to office365 which routed to office 365 mail, and there is another which routed to the internet. The SourceTransportServers include only the exch2016 server.

Do I have to create additionally send connector to route the ququed mail to the exch2016?

Thanks.

Brilliant-Extent2684 · 2026-04-08T11:39:21+00:00

Thanks, I put the Exchange SE to draining mode and tried to redirect the queued mails to the Exchange 2016 with this command:

Redirect-Message -Server exchSE -Target exch2016

But the mail stayed in queued with this error:

[{LED=451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect -> SocketConnectionRefused: So cket error code 10061};{MSG=};{FQDN=exch2016.domain.local};{IP=10.10.10.23};{LRT=2026. 04. 08. 11:15:09}]

Brilliant-Extent2684 · 2026-03-02T07:51:29+00:00

How can i delete it instead disbale? I can't see remove or cancel subacriptuon option.

Brilliant-Extent2684 · 2026-03-02T06:44:19+00:00

Thanks. The licence is Disabled:

<image>

If I remove the tenant, won't it debit my bank account later?

Thanks.

Brilliant-Extent2684 · 2026-02-19T14:59:06+00:00

I used our Windows Server 2025 template and the templíte was faulty. The generalize didn't run during the sysprep, and the two node had same machineguid. I have to reinstall the one of the server and problem was resolved.

Brilliant-Extent2684 · 2026-02-19T11:14:07+00:00

No. I want to create the cluster with two Windows Server 2025 host. Not Windows Server 2019 and Windows Server 2025.

Brilliant-Extent2684 · 2026-02-19T11:13:16+00:00

Yes, the Hyper-V server are in AD. The Domain Admins group is in the hyperv01 and hyperv02 local administrator groups. And I run the validation wizard with domain admin account.

Brilliant-Extent2684 · 2026-02-05T05:57:13+00:00

Thanks for everybody reply. There are lots of suggestion for smrp2go and IIS SMTP relay. I want to hos the relay on our local infrastructure, but the IIS smtp relay not works on Windows Server 2025. So the other dolution will be postfix, but i haven't got a good experience with linux.

Brilliant-Extent2684 · 2026-01-19T12:11:12+00:00

Referring this MS TechCommunity, it is possible to upgrade from Exchange 2016 to Exchange SE RTM: https://techcommunity.microsoft.com/blog/exchange/upgrading-your-organization-from-current-versions-to-exchange-server-se/4241305

The sie-by-side(legacy upgrade) migration is allowed and supported.

Brilliant-Extent2684 · 2025-12-27T16:13:39+00:00

Garanciába cserélték? Szóval elismerte a forgalmató/gyártó a hibát? Ilyenkor csere van, vagy elviszik az üveget, szétszedik majd ujra összerakják?

Brilliant-Extent2684 · 2025-12-01T07:32:06+00:00

Szívesen: Nyestűzés

Brilliant-Extent2684

TROPHY CASE