Clarification on Exchange Server SE Edition and Licensing
Hi everyone, We are planning to implement Microsoft Exchange Server on premises. Recently, we noticed that Exchange Server 2019 is approaching its end of life, and we don’t see any pricing information for the new Exchange Server Subscription Edition (SE). In this situation, what is the best approach? Do we need to purchase Exchange Server 2019 first and then upgrade to the SE version? If so, how does the pricing for the Subscription Edition work? Will there be an additional cost (for example, a yearly subscription) after upgrading? We would really appreciate any clarification or guidance on this matter. Thank youResolved: Hybrid Exchange Duplicate (Ghost) Mailbox Created After Assigning Exchange Online License
Summary During a hybrid Exchange migration, a user’s mailbox failed to migrate and mail flow broke due to a duplicate (ghost) mailbox automatically created in Exchange Online. Root Cause An Exchange Online Plan 2 license was mistakenly assigned to the user before migration. Azure AD sync then provisioned a cloud mailbox, even though the user already had an on-prem mailbox. This caused a hybrid mismatch — the user appeared in both environments, and migration failed with mailbox lookup errors. Resolution Steps Removed the Exchange Online Plan 2 license from the user account. Forced a DirSync (AAD Connect) synchronization. Verified that the mailbox existed only on-prem via PowerShell Get-Mailbox -Identity email address removed for privacy reasons | fl Name,RecipientTypeDetails,ExchangeGuid Confirmed the ghost mailbox was removed from Exchange Online. Re-ran migration batch successfully to Exchange Online. Verification Get-MailboxStatistics -Identity email address removed for privacy reasons | fl TotalItemSize,ItemCount,LastLogonTime Ensure only one mailbox object exists and mail flow routes correctly. Prevention Tips Don’t assign Exchange Online licenses to hybrid mailboxes before migration. Always verify mailbox location prior to assigning any license. Use PowerShell or EAC to check where the mailbox resides (on-prem vs. cloud). Environment Hybrid Exchange Deployment Exchange 2016 On-Premises Exchange Online (M365) Azure AD Connect This issue is not caused by connectors or mail flow settings, but by improper licensing before migration. Removing the license and resyncing resolves the ghost mailbox problem.
Arbitration mailbox
Issue: Arbitration Mailbox Issue During Exchange 2016 to 2019 Migration. Environment Overview: Mixed Exchange environment: Exchange 2016: EX1-16, EX2-16, DR1-16, DR2-16 Exchange 2019: EX1-19, EX2-19 Currently migrating mailboxes from Exchange 2016 to Exchange 2019. Issue Description: One system mailbox was found on an orphaned Exchange server and i removed manually. Post-removal, errors were observed related to the Migration and Federation arbitration mailboxes. Both mailboxes appeared under the User container but were not functioning correctly. A user-type mailbox with the display name “Migration” appeared. I thought this may cause issue with arbitration mailboxes. Remediation Steps Taken: Removed the user-type mailbox with the display name “Migration.” Manually removed both FederationMailbox and MigrationMailbox objects. Verified that the Exchange Trusted Subsystem has correct permissions on the Microsoft Exchange Security Objects (MSEO) container. Executed Setup.exe /PrepareAD, Its Re-created the Federation and Migration related users. Executed the following command to enable the arbitration mailbox: Enable-Mailbox -Identity <GUID-of-MigrationMailbox> -Arbitration (command executed successfully). Current Problem: Despite successful execution of the Enable-Mailbox command, the msExchRecipientTypeDetails attribute is not updating to the expected value. Current value: 8388608 and display name also looks wrong because its show “Microsoft Exchange Approval Assistant” seems to be incorrectly tied to the migration mailbox. This issue is preventing proper functionality of the migration mailbox, and as a result, the remaining mailboxes cannot be moved from Exchange 2016 to Exchange 2019.
Emails delayed or not received.
Hello Please i need your help on this issue. Emails delayed or not received. We have noticed that since last Friday (3rd Oct) emails sent to @livener.net addresses have been delayed or not received. This is using the Outlook app, Apple Mail App and Outlook Online.so I do not believe it is a client issue. In particular a mail from massenzana @runeXXXX to Tony @liveXXXXX and Bernie @liveXXXXX on Friday evening has not been received. It was received by other recipients. Test mails from Tony @gmailXXXX to Tony @liveXXXXX and bernie @liveXXXXX sent at approx 09:40 have not been received. A mail from Bernie @soundXXXX sent at 07:02 this morning arrived at Tony @liveXXXX at 09:49
Free/Busy Hybrid Exchange 2019
Hello everyone, I have a hybrid environment with Exchange Server 2019, with a dedicated Exchange application, we renewed the Exchange Auth certificate and then re-ran the HCW, however, free/busy is not working for 365 Pro local users. Has anyone had this problem? Could you help me?
Exchange SE HTTP 500 error
Hi Everyone, Been having this weird thing with 2 new Exchange SE installs. Both of them when trying to sign into ECP get a HTTP500 error once I've entered credentials Not really sure where to go, looked in IIS, checked the bindings, checked event viewer, services I expect to be behind this look to be running. Anyone else come across or have any solves? Thank you
Exchange Migration Cross forest
Hello, I planning to do an exchange Migration from forest A to forest B and the email address will be changed. I don't want to set any trust between the two, i will simply create the active directory users from scratch with new passwords and will install and configure the exchange environment in the target forest and will create the mailboxes. i will use a third-party tool to migrate the mailboxes between the two forests and after cutover i will add the alias of the old email as additional proxy address to the mailboxes. i am assuming everything will work fine however i have seen lot of articles on the internet about we have to migrate the legacyexchangeDN from the source environment and to add it as X500 proxy address as well in the destination or we might face issues in the migrated recurrent meetings when someone wants to edit or when someone reply to a migrated email.... I can afford having some meeting corrupted after migration but i cant afford the headache of NDR when someone reply to the migrated emails it will be a disaster.... anyone had this experience before to share it with me especially regarding the reply to the migrated emails and i did not lot of documentation from Microsoft about such scenario? Thank You.
Exchange 2019 Mailbox Migration Error - Folder conflicts with Exchange Online folder
Hi Exchange Experts, I'm migrating a small Exchange 2019 environment to 365. Been pulling my hair out becuase of just one mailbox giving this error Error description --------------------------- Error: AggregateMailboxFolderConflictPermanentException: The folder 'Files' conflicts with Exchange Online folder 'Files', please move the messages to another folder and restart the job. Data migrated: 0 B (0 bytes) Migration rate: -------------------------------------- Migration user report: 5/14/2025 12:32:05 PM [MEUP300MB0105] Request processing continued, stage CreatingFolderHierarchy. 5/14/2025 12:32:05 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Fatal error AggregateMailboxFolderConflictPermanentException has occurred. ---------------------- It seems to be a system folder and I've tried to remove files from it (although there're no files in it) using MFCMAPI tool with no success. Renamed the folder and tried to re-run the migration with no luck. Has anyone experience this issue? any thoughts or tips are much appreciated ! Thank you.
Missing Teams Contacts after Migration
Hello, We are currently migrating mailboxes from exchange 2019 to exchange online. The migration works absolute flawless. Now we have some employees complaining about missing teams contacts that were previously created in Teams only. The MS support told me that this is a teams limitation and the local contacts are gone. I know about unified contacts, thats contacts are synced now between outlook and teams and newly created contacts are stored in exchange online mailbox. But whatabout the old contacts ?? cant believe that theres no workaround to keep this contacts. Do you know something about this ? Rene
