Forum Widgets
Latest Discussions
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)
Exchange Online calendar sync tool
We have developed software that synchronizes Exchange calendars. For the past few months, we have been facing a new problem that we did not have before. We synchronize calendar entries based on the LastModifiedDateTime attribute of the Microsoft.Graph.Event class. We are puzzled by the fact that this attribute magically changes without any adjustments on our part. Do you have any advice on this?Exchange 2010 to Exchange 2019 Migration
Old installation getting around to upgrading. Here are my problems\thoughts? Current environment is: Single 2008R2 server, AD, Exch 2010. Moving to Server 2019 vm's. Have a 2019 guest as a DC but forest level still 2008 R2. Exch 2019 requires level to be 2012+. So, after I move the file share and SQL to their own guests (everything on single physical machine currently) plan is to demote current "server2". Exchange likely will complain about no DC but then add as member of the 2019 guest DC. Then bump the forest level to 2012? Then install Exch 2019 to its own guest. Then move the mailboxes from the 2010 store to the 2019 store. Remove and uninstall Exch 2010. Then possibly bump the forest level to current? Thoughts\issues: Will Exch 2010 behave correctly while demoting "server2" and then adding the machine to the domain? Is it possible to go directly to Exch 2019 from Exch 2010 or do I have to create an Exch 2016 as an interim step? I would really hate to export all the mailboxes, remove Exch 2010, bump the forest, install Exch 2019, and import the mailboxes. Thanks in advance,Exchange Online Restricts the Number of Dynamic Distribution Groups
Exchange Online is imposing a new tenant-wide limit of 3,000 Dynamic Distribution Groups. Few tenants might be affected, but the question might be asked why Microsoft is limiting DDGs at this point. Is it a cunning plan to prompt people to use dynamic Microsoft 365 groups instead? Or are some tenants abusing DDGs in weird and wonderful ways? Who knows, but the limit applies from early April 2025. https://office365itpros.com/2025/03/10/dynamic-distribution-groups-limit/Transport Rule and Mail-enabled Security Group: Delayed Evaluation of Group Members
I have the following transport rule: If the message: Is sent to a member of group 'group-name@domain' Take the following actions: Redirect the message to 'shared-mailbox@domain' and Stop processing more rules When I add or remove members of the mail-enabled security group it takes a very long time until the transport rule seems to notice. Meaning, after adding members the messages are still NOT redirected and after removing member the messages ARE still redirected. It takes about 4 hours until the change of the group becomes effective. After that the rule works perfectly fine. Did anyone come across this too and is there any way to circumvent this?Public Folder Calendar Creation
We use basic public folder calendars for a number of things. These were originally hosted on on-prem Exchange, and are now on Exchange Online. I normally create them in Outlook, and select 'calendar items' from the list of types. However, I'm currently testing New Outlook, and that doesn't appear to have any ability to create public folders (you can only add existing ones to the favourites list). So I've looked in Exchange Online, and although that can create public folders, it seems to only create basic empty public folders, with no ability to select calendar items to make a calender. Am I missing something obvious, or is it actually impossible to create public folder calendars if using a New Outlook / Exchange Online setup? ThanksUsing iOS Build Numbers in Exchange ActiveSync Device Access Rules
A change made in late 2024 allows Microsoft 365 tenants to use IOS build numbers in Exchange ActiveSync device access rules. Apparently, the idea is that tenants can insist that people use iOS devices with very specific build numbers (like iOS 18.3.1 22D72) before the devices can synchronize with Exchange Online mailboxes. You never know when you might need the feature (or so they say). https://office365itpros.com/2025/03/06/device-access-rule-ios-build/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!
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.
