Forum Widgets
Latest Discussions
Microsoft Changes Strategy for High Volume Email
A surprise announcement brings the news that the Exchange Online High Volume Email (HVE) solution will only deliver messages to internal recipients from June 2025. Azure ECS is now the sole offering for sending large volumes of email to external recipients. On the upside, HVE will support basic authentication until September 2028 to give tenants the chance to upgrade devices and apps. https://practical365.com/hve-new-strategy/
Missing Sent Items after IMAP Migration
Hello, I current did a migration from IBM Domino onpremise mail server to exchange online. The migration is still underway but there are some earlier migration batches (used IMAP as migration method) that show the sync is perfect and even shows number of items migrated. On the users end they are only able to see all their inbox mails from the previous mail server (IBM Domino). What could be the issue in this case? I have done multiple migrations but haven't seen such an issue before. Any ideas are highly appreciatedExchange Hybrid Wizard won't run
Hi all, 2 x Exchange 2019 (CU 14 and April SU) in a dag Windows Server 2022 I'm trying to run the Hybrid Configuration Wizard but nothing happens. From one of the servers I go to https://aka.ms/HybridWizard. Using Edge it offers to Open Microsoft.Online.CSE.Hybrid.Client.application but nothing happens when I click Open. I downloaded the application and tried to run it manually but absolutely nothing happens. Nothing in the event logs to say why nothing happened. I had a look and ClickOnce Application Deployment Support Library is the default to open .application files. Tried using the old IE to run it (as some posts online suggest) but again nothing happens. If I run the application from another PC (Windows 10), it attempts to run but fails and I get the error: Deployment and application do not have matching security zones Has anyone else had this issue and was able to resolve? thanks justin EDIT: I am looking at doing the Classic Full hybrid.
exchange 2019 send to person not save in sent item
Hi, I have problem in organization with exchange 2019. I have user then send mail to outside one domain, mail not save in sent items. Tracking logs show is this mail send to customer. Customer recive this mail but not in mailbox user sent items. #TYPE Selected.Microsoft.Exchange.Management.TransportLogSearchTasks.MessageTrackingEvent "Timestamp","Sender","Recipients","MessageSubject","EventId","ServerHostname" "06.05.2025 09:10:45","email address removed for privacy reasons","user@customer.domain","FW: new order_season 2025","RECEIVE","exchange" "06.05.2025 09:10:46","email address removed for privacy reasons","user@customer.domain","FW: new order_season 2025","HAREDIRECT","exchange" "06.05.2025 09:10:46","email address removed for privacy reasons","user@customer.domain","FW: new order_season 2025","RECEIVE","exchange" "06.05.2025 09:10:46","email address removed for privacy reasons","user@customer.domain","FW: new order_season 2025","SUBMIT","exchange" "06.05.2025 09:10:46","email address removed for privacy reasons","user@customer.domain","FW: new order_season 2025","AGENTINFO","" "06.05.2025 09:10:46","email address removed for privacy reasons","user@customer.domain","FW: new order_season 2025","TRANSFER","exchange" "06.05.2025 09:10:53","email address removed for privacy reasons","user@customer.domain","FW: new order_season 2025","SENDEXTERNAL","m.net" "08.05.2025 09:33:17","email address removed for privacy reasons","user@customer.domain","RE: new order_season 2025","RECEIVE","exchange" "08.05.2025 09:33:17","email address removed for privacy reasons","user@customer.domain","RE: new order_season 2025","HAREDIRECT","exchange" "08.05.2025 09:33:17","email address removed for privacy reasons","user@customer.domain","RE: new order_season 2025","RECEIVE","exchange" "08.05.2025 09:33:17","email address removed for privacy reasons","user@customer.domain","RE: new order_season 2025","SUBMIT","exchange" "08.05.2025 09:33:17","email address removed for privacy reasons","user@customer.domain","RE: new order_season 2025","AGENTINFO","" "08.05.2025 09:33:17","email address removed for privacy reasons","user@customer.domain","RE: new order_season 2025","TRANSFER","exchange" "08.05.2025 09:33:27","email address removed for privacy reasons","user@customer.domain","RE: new order_season 2025","SENDEXTERNAL","mxw.net" "08.05.2025 10:19:55","email address removed for privacy reasons","user@customer.domain;user@customer.domain","RE: shipping documents xxx #20","RECEIVE","exchange" "08.05.2025 10:19:55","email address removed for privacy reasons","user@customer.domain;user@customer.domain","RE: shipping documents xxx #20","HARECEIVE","exchange" "08.05.2025 10:19:55","email address removed for privacy reasons","user@customer.domain;user@customer.domain","RE: shipping documents xxx #20","SUBMIT","exchange" "08.05.2025 10:21:04","email address removed for privacy reasons","user@customer.domain;user@customer.domain","RE: shipping documents xxx #20","HADISCARD","exchange" "08.05.2025 10:27:36","email address removed for privacy reasons","user@customer.domain;user@customer.domain","RE: combined shipment: xxx ","RECEIVE","exchange" "08.05.2025 10:27:36","email address removed for privacy reasons","user@customer.domain;user@customer.domain","RE: combined shipment: xxx ","HARECEIVE","exchange" "08.05.2025 10:27:36","email address removed for privacy reasons","user@customer.domain;user@customer.domain","RE: combined shipment: xxx ","SUBMIT","exchange" "08.05.2025 10:29:09","email address removed for privacy reasons","user@customer.domain;user@customer.domain","RE: combined shipment: xxx ","HADISCARD","exchange" "09.05.2025 15:22:38","email address removed for privacy reasons","user@customer.domain","RE: xxx","RECEIVE","exchange" "09.05.2025 15:22:38","email address removed for privacy reasons","user@customer.domain","RE: xxx","HAREDIRECT","exchange" "09.05.2025 15:22:38","email address removed for privacy reasons","user@customer.domain","RE: xxx","RECEIVE","exchange" "09.05.2025 15:22:38","email address removed for privacy reasons","user@customer.domain","RE: xxx","SUBMIT","exchange" "09.05.2025 15:22:39","email address removed for privacy reasons","user@customer.domain","RE: xxx","AGENTINFO","" "09.05.2025 15:22:39","email address removed for privacy reasons","user@customer.domain","RE: xxx","TRANSFER","exchange" "09.05.2025 15:22:56","email address removed for privacy reasons","user@customer.domain","RE: xxx","SENDEXTERNAL","mx.ner" I cant target this problem. Thansk for answers DSHow to Find Active EWS-Based Apps in a Microsoft 365 Tenant
Microsoft will retire Exchange Web Services (EWS) from Exchange Online on October 1, 2026. A new usage report helps tenants understand what apps use EWS. Many of the apps are likely to be first-party (Microsoft) apps, but some might be third-party apps developed externally or internally. Those apps need to be retired or upgraded to use Graph APIs. Time is slipping away to do the work. https://office365itpros.com/2025/04/29/exchange-web-services-apps/
The Downside of Losing the Exchange Mailbox Audit Search Cmdlets
Microsoft recently announced the deprecation of the Exchange cmdlets to search for mailbox audit data. The audit data is ingested into the Microsoft 365 unified audit log, but it’s more difficult to find and retrieve Exchange mailbox audit events. Methods are available to find mailbox audit data, but interpreting what comes back is different. Any script that depends on the old cmdlets must be updated to interact with the unified audit log. https://office365itpros.com/2025/05/08/exchange-mailbox-audit-data/Decommissioning Last Hybrid Exchange Server – All Mailboxes in Cloud, Still Using AAD Connect
Hi all, We're currently running a hybrid Exchange environment with AAD Connect in place. All user mailboxes have already been fully migrated to Exchange Online, and Exchange Online is handling all mailbox mail flow. The only thing left on-prem is the last Exchange 2019 hybrid server, which we want to decommission. Our current setup includes: AAD Connect for syncing identities from Active directory to Entra Exchange 2019 hybrid server (used only for recipient management and SMTP relay) An SMTP relay connector used by on-premises applications and printers No mailboxes hosted on-prem Our plan: Decommission the on-prem Exchange server Install the Exchange 2019 CU12+ Management Tools on a domain-joined server or admin workstation to manage recipient attributes Replace our on-prem SMTP relay with an Azure-hosted relay Questions: Has anyone here successfully removed their last Exchange hybrid server while keeping AAD Connect in place? Do we have to just turn off the last physical server and not uninstall exchange server 2019 ? Any gotchas or issues managing recipients via the new Exchange Management Tools post-decommission? Does Microsoft still recommend keeping an Exchange server in this case, or is the Management Tools path fully supported now? Would appreciate any insights or lessons learned from folks who’ve gone down this path. Thanks in advance!
Upgrade Exchange 2019 from CU12 to CU15 Failed
Dear All, I am have a major issue with hybrid Exchange server 2019, since it failed, the Exchange server has now been offline. Here it is the error message from the Wizard for upgrade Error: The following error was generated when "$error.Clear(); if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true)) { if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue) { # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4. get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName; $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 ); if ( $mbxs.length -eq 0) { $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if($dbs.Length -ne 0) { $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1); if ($mbxUser.Length -ne 0) { enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity; } } } } else { write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission." } } " was run: "Microsoft.Exchange.Management.Tasks.RecipientTaskException: The user's Active Directory account must be logon-disabled for linked, shared, or resource mailbox. at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.PrepareRecipientObject(ADUser& user) at Microsoft.Exchange.Management.RecipientTasks.EnableRecipientObjectTask`2.PrepareDataObject() at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.RecipientObjectActionTask`2.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)". And this from the Exchange Log [05/02/2025 21:38:26.0710] [1] [ERROR] The user's Active Directory account must be logon-disabled for linked, shared, or resource mailbox. [05/02/2025 21:38:26.0716] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___590e51a8a98846d3a7fa8ddcc5472c74 Component=EXCHANGE14:\Current\Release\PIM Storage\Discovery What I have been trying is that according to this post below https://community.spiceworks.com/t/exchange-2016-failed-applying-cu-19/793248/18 SUCCESS. The error log was whinging about discovery but it turned out to be the Search Results mailbox. I went through every account which looked like it might have something to do with exchange and checked its attribs. Search Results had a corrupt entry. I fixed it and that was that. Back up again! BOOM For everyone reading this. If you get this error you need to check each account: System Federation Migration Discovery and Search Results. I tried every single user account that I'd think Exchange related, updating the HomeMDB with the attribs that found in the DiscoverySearchMailbox, still could not pass the error above. Any help/ advice would be really greatly appreciated. Kind Regards
