Exchange synch/profile issue
Dear community, I need help to solve a problem. 1.) I'm using Outlook classic 2016 2.) I need two mail accounts in outlook a.) my gmail account - all good with that one b.) my AWS Workmail account 3.) all used to work fine till I had another problem with teams integration into my calendar which I tried to fix without success. After a while I thought, that when I setup outlook from scratch that this could solve the problem - but it got worse. 4.) when I started the newly installed outlook, I can load my gmail account, and when I add my AWS Workmail account, I get the message that the account was successfully added and need to restart Outlook. 5.) After the restart I get the two messages: - The name cannot be matched to a name in the address list. - Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. An unexpected error has occurred. 6.) so the AWS Workmail is not loaded. I also tried to add the account manually in all different ways but without success. The integration of the AWS mail account on my Android Outlook works perfectly fine. I dont know where the problem is and tried to get answers from AI and Microsoft Support without success. Anyone has an idea? Many thanks, RobResolved: 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.
Sharepoint websites on IIS stopped
Hello, Last Monday, I noticed that SharePoint and SharePoint Central Administration v4 sites were stopped in IIS on our SharePoint application server. (We host each SharePoint component on dedicated servers, the application, search, and database servers are all separate.) SharePoint has continued to work fine since then, no users have reported any issues, and I personally tested it throughout the week without finding any problems. I’m not sure if it’s normal for these two IIS sites to be stopped, and I’d like to know whether it’s safe to start them again or if they should remain stopped. Thank you.Exchange 2016 and 2019 End of Life and Some Interesting Exchange Online Developments
On Oct 14, 2025, Exchange 2019 and 2016 reach end-of-life and Exchange SE becomes the only supported on-premises Exchange server. In other news, we discuss Microsoft guidance for moving to cloud first identity, HVE and ECS and the extension of basic authentication support to September 2028, the introduction of auto-archiving for Exchange Online, and why Microsoft is deprecating the Contact object from Exchange Online. https://office365itpros.com/2025/10/09/exchange-se-news/
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.Exchange 2016 to SE and Exchange Online questions
Hi, We're currently in the process of migrating from Exchange 2016 to Exchange Subscription Edition (SE), along with moving a portion of our mailboxes to Exchange Online. We have approximately 3,000 mailboxes, and around 2,000 of those will eventually end up in Exchange Online—for various reasons (don’t ask why…). I have a few questions I'd like to clarify and hope you can assist: Exchange On-Premises Questions: If a user mailbox is moved to Exchange SE, can they still access shared or user mailboxes that remain on Exchange 2016? Do we need to migrate them in the same batch to preserve access/permissions? (should't be an issue in the same Exchange Org right?) If a shared mailbox is migrated to Exchange SE while the user mailbox remains on Exchange 2016, will access still work? Do we need to point the Hardware Load Balancer (HLB) to the new Exchange SE servers before mailbox moves to allow proper client connectivity and proxying back to Exchange 2016? Or is it okay to keep the HLB pointed to the Exchange 2016 servers until all migrations are complete and then switch it over? Proxy upwards from Exchange 2016 to Exchange SE? What’s the best practice here? Pros/cons? Exchange Online Questions: If we want all outbound mail to go through the on-prem Exchange environment—even for Exchange Online mailboxes—is this configured via the Hybrid Configuration Wizard (HCW)? Is the Litigation Hold status preserved when migrating a mailbox to Exchange Online? Can a mailbox hosted in Exchange Online access a shared mailbox still residing on-prem? (Should't be an issue right?) Can an on-prem mailbox access a shared mailbox that has been migrated to Exchange Online? For mailboxes with Full Access or Send As permissions (e.g. user mailboxes tied to shared mailboxes), do they need to be migrated together in the same batch to retain functionality? We’ll be using native Microsoft migration tools (no 3rd-party solutions). If I recall correctly, separate migrations will still allow Full Access?!?, but Send As may not work properly unless migrated together. Is that still accurate?
Exchange 2016 and deffer delivery
Hi! Is it possible to configure delay of outgoing sending messages for user mailbox, like outlook's deffered delivery? I couldn't find such an option in mailflow-rules, as deepseek says "New-TransportRule -Name "DelaySendForUser" -SenderAddressEquals "email address removed for privacy reasons" -DeferMessageMinutes 2 -Enabled $true" - it doesn't work:))Hotfix update for 2016 CU23 HU18: (KB5066370) breaks OWA and leaves all services disabled
Has anyone else applied the latest hotfix? First of all it tries to validate open files instead of just killing these processes as part of the update, then after rebooting all the services are left in a disabled state. Then I discover it has broken IIS and OWA doesnt work. We have had client issues all day in the office. It looks like another update has been pushed out without sufficient testing. Any help would be grateful at this point, I am looking to take 2 out of 4 servers offline.
