Exchange health set unhealthy
Hello everyone! Some healthprobes on our Exchange 2016 Server have been reporting an unhealty state since the middle of February. OAB.Proxy, EWS.Proxy, Outlook.proxy and OutlookMapiHttp.Proxy. We have no mailboxes on the server, so its not critical, but I would still like to figure out what is going on. They all fail with "The remote server returned an error: (401) Unauthorized" and if I try to invoke the probe i see this in the response: It looks like the SSL validation is not happening. Is it normal for the probe to use localhost for this? When I run "Get-WebServicesVirtualDirectory" both internal and external virtual directry is set to our external url. Any insight is greatly appreciated!Outlook Search Folder for External Senders
I'm using the Outlook M365 desktop app on the current channel and Exchnage 2019 in Hybrid mode with Exchange Online. We route all mail inbound and outbound via Exchange Server. I'd like to create a search folder in Outlook to show only mails from external senders. The issue is the only criteria I can seem to create would rely on the From field and this seems to map to the SenderName on the MailItem object in Outlook. This is not the actual sender's mail address that would include the @domain etc but rather seems to be the senders name which is arbitrary from I can see e.g SomeSender. How to create a search folder based on the senders actual address?
Exchange Hybrid Wizard Error (413)
Hello, we are running into issues with the Hybrid Wizard. On the last point validation, we always getting the same error and dont know what to do, cuz it says the external server is responding with.... See Log attached. 2025.03.05 08:43:02.035 *ERROR* 10349 [Client=UX, Page=HybridConnectorInstall, Thread=8] The connection to the server '6499703f-91f1-4369-a729-b40098fdd276.resource.mailboxmigration.his.msappproxy.net' could not be completed., The call to 'https://6499703f-91f1-4369-a729-b40098fdd276.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' failed. Error details: The remote server returned an unexpected response: (413) RequestEntityTooLarge.., The remote server returned an unexpected response: (413) RequestEntityTooLarge. OriginalFailureType: ProtocolException, WellKnownException: MRSRemote None MRSRemote Remote stack trace: Remote trace: at System.ServiceModel.Channels.HttpResponseMessageHelper.ValidateResponseStatusCode() at System.ServiceModel.Channels.HttpResponseMessageHelper.ParseIncomingResponse(TimeoutHelper timeoutHelper) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.ReceiveReplyAsync(TimeoutHelper timeoutHelper) at System.ServiceModel.Channels.RequestChannel.RequestAsync(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ClientReliableChannelBinder`1.RequestAsync(Message message, TimeSpan timeout, MaskingMode maskingMode) at System.ServiceModel.Channels.RequestReliableRequestor.OnRequestAsync(Message request, TimeSpan timeout, Boolean last) at System.ServiceModel.Channels.ReliableRequestor.RequestAsync(TimeSpan timeout) at System.ServiceModel.Channels.ClientReliableSession.OpenAsync(TimeSpan timeout) at System.ServiceModel.Channels.ReliableRequestSessionChannel.OnOpenAsync(TimeSpan timeout) at System.ServiceModel.Channels.ReliableRequestSessionChannel.OnOpenAsync(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpenAsync(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod, Object[] args) at generatedProxy_3.ExchangeVersionInformation(VersionInformation, VersionInformation&) at Microsoft.Exchange.Connections.Common.WcfClientWithFaultHandling`2.<>c__DisplayClass4_0.<CallService>b__0() in \_\sources\dev\common\src\Connections\Common\WcfClientWithFaultHandling.cs:line 76 at Microsoft.Exchange.Net.WcfClientBase`1.CallService(Action serviceCall, String context)
After Exc 2019 Cu15 update Outlook problem
After the Exchange 2019 CU15 update, Outlook 2016 or Outlook 2021 keeps asking for a password. When I check the operating systems, I see that they are versions up to Windows 10 Pro 1607 and 22H2. I wonder if there is a feature that affects older operating systems? Do you have any ideas?
How to clear the Discovery Holds folder
To find whether this discovery holds folder is completely full, use the below-mentioned command. Step 1: Connect-ExchangeOnline and then, Step 2: Get-MailboxFolderStatistics -Identity user | select name,foldersize Note: This DiscoveryHolds folder is having a limit of 100 GB. If it is full, we will get issues like "Unable to clear deleted items folder", "deleted items are getting auto-restored" etc., One of the reasons for this folder is full: If Organization Hold is turned on(All Exchange mailboxes are selected in Compliance Retention Policy) or the Individual ID is selected on Compliance Retention Policy. Solution: Please try the below-mentioned steps to overcome this issue. Step 1: Exclude the DiscoveryHolds full ID in the Compliance Retention policy or run the below-mentioned commands in PowerShell. Connect-IPPSSession and then, Set-RetentionCompliancePolicy -Identity "Compliance Retention Policy Name" -AddExchangeLocationException user for multiple users, Set-RetentionCompliancePolicy -Identity "Compliance Retention Policy Name" -AddExchangeLocationException user1, user2, user3 Now on PowerShell, Connect-ExchangeOnline and then, Set-Mailbox -Identity user -RetainDeletedItemsFor 0 and then run the below-mentioned command two times. Start-Managedfolderassistant -Identity user Start-Managedfolderassistant -Identity user After 2-3 minutes, run the below-mentioned commands. Get-Mailbox "user" | FL DelayHoldApplied,DelayReleaseHoldApplied If the output is received as true for any above-mentioned holds, then run the below-mentioned commands. Set-Mailbox user -RemoveDelayHoldApplied Set-Mailbox user -RemoveDelayReleaseHoldApplied and then run the below-mentioned command two times. Start-Managedfolderassistant -Identity user Start-Managedfolderassistant -Identity user After 2-3 minutes, this DiscoveryHolds folder will become zero as per the below-mentioned screenshot. This process helped me a lot. If you have any doubts/concerns/suggestions about this post, please comment below. Best Regards, Venkat Kiran Kona.
Issues after Exchange 2019 CU15 install
Hello, We have some issues with our Exchange server. After CU15 install we have high(er) CPU usage at the server and slow(er) Outlook (online no cache mode enabled) connection at the client. MAPI over HTTP and Exchange Extended Protection is enabled. Have anybody else who have the same issues?
Information about Exchange SE trough SPLA
Does anyone have any information about the possible availability of Microsoft Exchange Subscription Edition (SE) through SPLA ? As you may know, SharePoint Subscription Edition (SE) was already released since a few years, however it never approved by Microsoft to be used in SPLA, it is not mentioned in the SPUR and they don’t provide the installations keys for this version to SPLA hosters. If they follow the same policy with Exchange SE, we will not have any solution to run an Exchange Server on a supported version after 14th of October 2025 when Exchange 2019 reaches end of support. Thanks for your comments Thierry
Unable to open PDF attachments from shared mailbox with OWA
Hi, we are using Exchange 2019 (Build 15.02.1544.011) and are experiencing an issue with Outlook Web Access (OWA) where PDF files cannot be previewed or downloaded. This problem only occurs when opening a shared mailbox in OWA and trying to open a PDF file from an attachment. In the personal mailbox, the files can be previewed and downloaded without any issues. When opening the PDF in a shared mailbox, the following error message appears: {"Body":{"ErrorCode":500,"ExceptionName":"ThreadAbortException","FaultMessage":"Thread was being aborted.","IsTransient":false,"ResponseCode":"ErrorInternalServerError"}} This error occurs in Edge as well as in other browsers. Is this problem already known? Thanks, AlexUnable to Add Exchange 2019 Email Account (Ionos) to Outlook (New) on Windows 11
Hello everyone, unfortunately, I am unable to add my Ionos (Exchange 2019) email account to the Outlook Windows app. On Windows 10, it was still possible to manually configure an Outlook account, which worked fine. However, on Windows 11, this option is no longer available, and I can’t revert to the previous version of Outlook either. When I try to add the account by selecting Microsoft 365 - Office 365, Exchange and entering my email address, I always get the error message: We couldn't find a work or school account with that email address. I have already contacted Ionos, but they couldn’t solve the issue either. They mentioned that Microsoft doesn’t allow setting up an Exchange account this way, even though the option is listed in the selection menu. Does anyone know how to fix that? Thank you very much!
Exchange Room Resource Name Change
We have Room resources on Exchange online which were migrated from on-premise exchange server, last year we completely migrated the on-premise exchange to EXO, now when we had to change the names of these room resources due to some relocations of the meeting rooms, we had to rename it from the on-premise ad since it is syncd. I have just renamed the AD object property(display name, SMTP etc), and once it is syncd via AAD, now could see the new name from the EXO but when we use Get-Mailbox -Identity via Exchange online powershell its still showing up the old name, is there any other on-premise ad attribute which needs to be changed?
