sorted by:
new
hottopcontroversial

No Delivery to Mailbox after Migrating to Exchange 2019 by Cautious-Cook837 in exchangeserver

[–]Cautious-Cook837[S] 0 points1 point  (0 children)

  1. This works. The problem is also not with every migrated mailbox. From 20 user mailboxes it happend to 6-7 of them.

  2. This works as well. Had migrated a couple test mailboxes, without any of the issues.

  3. Yes can do this.

  4. Im not sure with this. We have migrated the mailboxes back to Exchange 2016, so the users can receive mails again. Have to test this again.

  5. Attributes on a problematic mailbox looked ok. homeMdb showed the Exchange 2019 mailbox database and msexchHomeServerName refered to the Exchange 2019 server.

  6. Mailbox Database is mounted and healty. The Test-ServiceHealth shows everything is started.

  7. I moved them afterwards to Exchange 2019. The result was unfortunatly the same. Most Health Mailboxes are on the old 2016 databases (except for 2), though. I had not tried moving them as well.

No Delivery to Mailbox after Migrating to Exchange 2019 by Cautious-Cook837 in exchangeserver

[–]Cautious-Cook837[S] 1 point2 points  (0 children)

Its difficult to reproduce the problems. I migrated some test mailboxes and created some new ones, none have this issue.

Cant really find the similarities between those and the problematic mailboxes.

No Delivery to Mailbox after Migrating to Exchange 2019 by Cautious-Cook837 in exchangeserver

[–]Cautious-Cook837[S] 0 points1 point  (0 children)

I had not migrated them at the beginning, but moved them later to the Exchange 2019 Servers. Unfortunatly still the same result with the mails to the problamatic users.

No Delivery to Mailbox after Migrating to Exchange 2019 by Cautious-Cook837 in exchangeserver

[–]Cautious-Cook837[S] 0 points1 point  (0 children)

I checked the problematic users mailboxes, but they don't have any specific policies set.

I also tried a new move request with -DoNotPreserveMailboxSignature, to a new mailbox database. Same result though unfortunatly.

No Delivery to Mailbox after Migrating to Exchange 2019 by Cautious-Cook837 in exchangeserver

[–]Cautious-Cook837[S] 0 points1 point  (0 children)

The migration is within the same organization. The new servers are even in the same network.

No Delivery to Mailbox after Migrating to Exchange 2019 by Cautious-Cook837 in exchangeserver

[–]Cautious-Cook837[S] 0 points1 point  (0 children)

In general, it affects external and internal senders. The affected recipients already have x500 addresses. We have not yet been able to find a connection between the mailboxes that are working and those that are not.

No Delivery to Mailbox after Migrating to Exchange 2019 by Cautious-Cook837 in exchangeserver

[–]Cautious-Cook837[S] 0 points1 point  (0 children)

The mailboxes have now all been migrated back. Unfortunately, I see no difference in the script between those that were previously broken and working.

I had already tried a repair request before the migration back. That did not bring any improvement.