2016
766 TopicsExchange 2016 Hybrid, move mailbox failed
We have configured the exchange hybrid config a while ago and tested the migration and succesfully moved a mailbox from on prem to Exchange Online. Yesterday was planned to start the migration for all the users, but as we know there were problems. Today they should be fixed, but when the migration status shows below 11/14/2026 11:11:29 [AMZPR05MB943814] The Microsoft Exchange Mailbox Replication service 'AMZPR05MB943814.eurprd05.prod.outlook.com' (15.21.592.10 ServerCaps:1FFFFFFFFF, ProxyCaps:37FFFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:1FFFFFFFFF) is examining the request. 11/14/2026 11:11:29 [AMZPR05MB943814] Resource information was found with reservation. 11/14/2026 11:11:29 [AMZPR05MB943814] Content from the Shard mailbox (Mailbox Guid: ef34477b-0084-487b-a27f-e89da129956e, Database: eurprd05.prod.outlook.com/f670e037-4a2a-4fbe-aa9a-2132c89edaf6) will be merged into the target mailbox. 11/14/2026 11:11:29 [AMZPR05MB943814] Connected to target mailbox 'customer.onmicrosoft.com\0a4112f9-5389-4200-85c9-765bf37cb330 (Primary)', database 'EURPR05DG745-db166', Mailbox server 'AMZPR05MB943814.eurprd05.prod.outlook.com' Version 15.21 (Build 592.0). 11/14/2026 11:11:30 [AMZPR05MB943814] Transient error CommunicationErrorTransientException has occurred. The system will retry (5/60, 5/605). I created a new migration point successfully , but the errors above are the same. inbound/outbound firewall settings were not changed between the first successfull migration and today. Is this still something left over from the mayor outage Yesterday , or can someone point me in the right direction ? Kind regards Jacco Dominicus116Views0likes6CommentsBackdoor.MSIL.Webshell.gen
Hello ; My antivirus detected Trojan -------------------- Probably infected object detected: Trojan HEUR:Backdoor.MSIL.Webshell.gen. Object name: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\owa\8e05b027\e164d61b\App_Web_z1qruv0b.dll MD5 file hash: fd34b27c2ea1a4702e265f6d1f05fe16 File SHA256 hash: a4f7b4261a9f70bd5247f497ff384012a71d75010765cc7174724ed04ed9b047 ---------------------- and w3wp.exe I alreday upgraded that to CU22 before this atttack and also installed the last Security patch for CU22. I ran the MSERT tool and other Security Script for Exchange . But has been removed but the mystery of the re-infections continues . Could you help me3.2KViews0likes1CommentWhy do Apple macOS and Ubuntu clients display Exchange meeting times one hour earlier than scheduled
If a meeting is generated from Apple macOS and Ubuntu clients showing the meeting time as one hour earlier than the actual scheduled time email solution is exchange server 2019, what will be the issue.314Views0likes1CommentFIX - Outlook 2013,2016,2019 fails open mailbox Exchange 2019 on-prem in offline LAN
Exchange 2019 on-prem + Outlook 2013/2016/2019 in offline LAN Symptoms: - OWA works - ECP works - Autodiscover works - Test-MAPIConnectivity is successful - Outlook profile can be created - Outlook fails to open the mailbox / “Cannot start Microsoft Outlook” / “The set of folders cannot be opened” / “The attempt to log on to Microsoft Exchange has failed” - Environment has no internet connection Root cause: The Windows client had a default gateway configured, but the gateway IP did not respond to ping. In our case the client received 192.168.1.1 as default gateway, but this IP was unreachable in the offline network. Fix: Set the client default gateway to an existing reachable IP address, for example the Exchange/DC server IP 192.168.1.5. Internet access is not required, but the default gateway must be reachable/responding. After changing: Default gateway: 192.168.1.5 DNS: 192.168.1.5 mail/autodiscover DNS or hosts pointing to Exchange 2019 Result: Outlook 2013, Outlook 2016 and Outlook 2019 connected to Exchange 2019 successfully.411Views0likes1CommentExchange 2016 Decommission
Hi all, I am trying to decom my 2016 environment and cannot disable (Disable-Mailbox) the final 16 mailboxes (out of thousands). Am getting the error Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0. I have been troubleshooting this for HOURS now. It's not enabling inheritance on the user perms (every article suggests that). The perm exchange trusted subsystem isn't there. The users do not have any admin groups. It's nothing that I can find in the first 6 pages of googling. Sadly, of course, there is no support anymore so can't even raise a ticket. Can't uninstall Exchange with mailboxes left :( Any idea's are more than welcome, please. Thank you.405Views0likes2CommentsPreserving permissions during EXO migration
Hi, Can you help me understand the outcome of preserving the permissions in our scenario. Exchange Server 2016 (soon Exchange SE) in a hybrid with Exchange Online. We are moving 75% of the mailboxes to Exchange Online. What ways will preserve or break the full-access or sendas permissions? I guess best way would be to migrate both the user and the shared mailbox at the same time in the same batch to keep the permission? If we migrate the user in batch 1 and shared mailbox in batch 2 will that preserve/break the full access/send as? If we migrate the shared mailbox in batch 1 and usermailbox in batch 2 will that preserve/break the full access/send as? If the permission is linked directly on the shared mailbox or via a security group is there a difference? Thanks!418Views0likes2CommentsExchange database dismounted due to NTFS file extent limit reached – unexpected outage
Hi everyone, We experienced a serious outage on our Exchange 2016 server recently, and I wanted to share what we found during the root cause analysis – in case it helps someone else avoid the same scenario. Summary: After digging deep, we discovered that the issue was caused by the NTFS file system hitting its internal file extent limit on the .edb file. Once this threshold was reached, the database could no longer grow, and the system dismounted the database unexpectedly. No prior warning, just service interruption. Details: The .edb was around 1.2 TB in size. This isn’t a limit on database size itself — it’s about how fragmented the file is on disk. Once NTFS couldn’t track any more extents, the database stopped working. Microsoft doesn’t publish a clear fix for this; only scattered references to similar behavior in past cases. What we did: Created a fresh, clean database. Manually moved user mailboxes into the new DB. The old database couldn't be mounted anymore, so we brought the system live without historical mail – just to maintain continuity. We're now working on extracting data from the unmounted .edb using third-party tools. Looking for thoughts: Has anyone else hit the NTFS extent wall with Exchange? How do you monitor extent growth proactively? Did switching to ReFS solve this for you long-term? Open to any input or similar experiences – appreciate it in advance. Thanks!726Views1like4CommentsLinking cloud only shared mailbox with onpremise object
Hi all, We currently have a cloud only shared mailbox in exchange online that we need to exist in onprem exchange for a smtp relay that is setup in a hybrid config. Is it possible to create onprem and match these objects onprem/cloud - or will the mailbox need to be recreated onprem and then it will sync to cloud552Views0likes1CommentHybrid Configuration Wizard fails to run – manifest download error on all machines
Hello, I am unable to run the Exchange Hybrid Configuration Wizard (HCW) for our Exchange 2016 environment. The issue occurs on multiple machines and networks, so it does not appear to be a local configuration problem. Environment: Exchange Server: 2016 CU23 Windows versions tested: Windows Server 2016, Windows 10 (all fully updated) .NET Framework: 4.8 (Release 528040 / 4.8.03761) TLS: TLS 1.2 enabled, SSL 3.0/TLS 1.0/1.1 disabled Network: No proxy, firewall, or other network restrictions; internet access available Problem: When attempting to run HCW via https://aka.ms/HybridWizard, the wizard fails to start. I have also tried to run HCW offline by downloading Microsoft.Online.CSE.Hybrid.Client.application, but it immediately fails. The error log shows the following repeated messages: Downloading file:///C:/Users/.../Application Files/Microsoft.Online.CSE.Hybrid.Client_17_1_3902_0/Microsoft.Online.CSE.Hybrid.Client.exe.manifest did not succeed. Could not find a part of the path 'C:\Users\...\Application Files\Microsoft.Online.CSE.Hybrid.Client_17_1_3902_0\Microsoft.Online.CSE.Hybrid.Client.exe.manifest' This occurs on all tested machines (three PCs across three different networks). ClickOnce cache has been cleared, root certificates are up-to-date, .NET is 4.8, and TLS 1.2 is active. Attempts to resolve: Ensured TLS 1.2 is enabled and default in .NET and OS Verified .NET 4.8 installation Cleared ClickOnce cache (rundll32 dfshim CleanOnlineAppCache) Updated root certificates Tried multiple machines and networks Tried to run offline using .application file and local copy of Application Files Result: HCW fails immediately with DeploymentDownloadException / DirectoryNotFoundException for the manifest. The issue is reproducible on all tested machines. Request: Please advise if there is an official offline installation method for HCW or a way to obtain a working manifest. If this is a temporary issue with the hosted distribution, please confirm expected resolution or workaround. Thank you for your assistance.1.5KViews0likes2CommentsExchange 2016 Mail Flow is Not Working
We had issues with updating to a latest Cumulative Update and messed up our EMS and some Web Config. It seems our Exchange Server is totally bricked. So, we decided to boot our Exchange Server from backup. The backup was dated September 2025. Unfortunately, after booting up the September 2025 backup, we noticed that the internal and external mail flow is not working (our Exchange 2016 is Exchange hybrid configured). The outgoing emails are stuck in Draft folder. The following troubleshooting steps have been done to no avail: -Checked if the port 25 is open -> This port is opened -Check the network settings if the Preferred DNS Address points to the correct DNS Server --> It points to the correct DNS Server -Modified the DNS lookup under Exchange Admin Center > Servers > DNS Lookups > Internal DNS Lookups --> Added the IP Address of the DNS Server -Modified the hosts file under System32 > drivers > etc --> Pointed the IP Address of the Exchange Server to the FQDN of the Exchange Server Currently, are not sure of the next steps to do in order to fix the issue. Any advice?422Views0likes3Comments