"NeedsApproval"
Hi All, So I have been migrating mailboxes from onprem to O365 in the hybrid config with no issues. Today I have two migration batch jobs that state "NeedsApproval", but everything migrated. Kind of confused as i don't see a way to "approve" the jobs and I don't see any issues. Any ideas?Exchange Hybrid Configuration Wizard - Error 1603 - Connector registration failed
Did any of you encounter this error while installing hcw on an exchange server? Here is the event viewer error details: Connector registration failed: Make sure you are a Global Administrator of your Active Directory to register the Connector. Error: '"The registration request was denied. "'Microsoft’s Grand Plan to Force Upgrades of Unsupported Exchange Servers
Microsoft announced that Exchange Online will block old Exchange Servers by throttling and then rejecting their inbound email into Exchange Online. The hope is that this tactic will convince those who operate unsupported versions of Exchange Server to upgrade and use supported software that isn't vulnerable to known attack vectors. https://practical365.com/microsoft-block-old-exchange-servers/
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.
Birthday Calendar reappears
Hey everybody, I am currently trying to set up the calendar and contact environment for my company and keep running in the most ridiculous issues. Today on the menu: Birthday Calendar. We want to use a central contact book so that not everybody has to manage their own contact book. I tried around with public folders which works in theory but I couldn't find a way to set up an automated birthday calendar for public folders. So I decided to use a shared mailbox for that which seems to be working fine. Now I don't require the personal birthday calendar anymore and a quick google search showed where to deactivate it. "Outlook Online - Settings - Calendar - Deactivate Birthday Calendar". Now, the problem is that the birthday calendar reactivates it self every single time. I doesn't matter if I have the outlook app open or closed at the time. This calendar won't go away. After multiple tries I now have 5 personal Birthday Calendars in my outlook app. Anyone has an idea on how to solve this? Thanks in advance and best regards.
Unable to Mount Database in Exchange
Hello Everyone, I am unable to mount my mailbox database Kindly assist, below is the error i am receiving. Failed to mount database "Mailbox Database 0366631746". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionDatabaseError: Unable to mount database. (hr=0x80004005, ec=1108) Diagnostic context: Lid: 65256 Lid: 10722 StoreEc: 0x454 Lid: 1494 ---- Remote Context Beg ---- Lid: 45120 dwParam: 0x7E9CC7 Lid: 57728 dwParam: 0x7E9D25 Lid: 46144 dwParam: 0x7EB149 Lid: 34880 dwParam: 0x7EB149 Lid: 34760 StoreEc: 0xFFFFFDE3 Lid: 41344 Guid: acd58de2-81d0-444b-ac76-3278e906c7b4 Lid: 35200 dwParam: 0x5C9C Lid: 46144 dwParam: 0x7EB541 Lid: 34880 dwParam: 0x7EB541 Lid: 54472 StoreEc: 0x1388 Lid: 42184 StoreEc: 0x454 Lid: 1750 ---- Remote Context End ---- Lid: 1047 StoreEc: 0x454 [Database: Mailbox Database 0366631746, Server: sciexch01.sciafrica.net]TLS 1.2 is coming to Exchange on-premises using hybrid and free/busy might fail
This article is intended to help customers and motivate them to check their on-premises TLS settings. This spring, your on-premises users might not be able to do free/busy requests in calendaring from on-premises mailboxes towards Exchange online mailboxes. In addition, your on-premises Exchange servers might start logging events like this: Log Name: Application Source: MSExchange Availability Date: 17.03.2022 09:45:01 Event ID: 4001 Task Category: Availability Service Level: Error Keywords: Classic User: N/A Computer: server01.contoso.com Description: Process Microsoft.Exchange.InfoWorker.Common.Delayed`1[System.String]: <User1@contoso.mail.onmicrosoft.com>SMTP:User1@contoso.mail.onmicrosoft.com failed in application Mailtips. Exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.AutoDiscoverFailedException: Autodiscover failed for email address User1@contoso.mail.onmicrosoft.com with error System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host The interesting parts of the event above are the following pieces of information: AutoDiscoverFailedException: Autodiscover failed and The underlying connection was closed: An unexpected error occurred on a send Since Autodiscover fails, let’s test it from the on-prem server and see if it can reach the server in Exchange online via Powershell: Invoke-WebRequest -Uri "https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc" On a non-working on-prem server, I get the result: The underlying connection was closed: An unexpected error occurred on a send. This error is unexpected, whereas this 401 would have been expected: This raises some suspicion, if the TLS settings on-premises are ok when the on-prem servers try to reach the servers in Exchange online. You can verify that your on-prem TLS settings are outdated, by forcing TLS 1.2 for the above test connection trying this Powershell call: [Net.ServicePointManager]::SecurityProtocol += [Net.SecurityProtocolType]::Tls12 Invoke-WebRequest -Uri "https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc" The result now as expect is: Invoke-WebRequest : The remote server returned an error: (401) Unauthorized. You now have proof that the TLS settings on-premises are outdated and your on-prem server not using TLS 1.2 prevents your server from connecting to the Exchange online servers. Microsoft hast announced in Messager Center Post MC240160 and here: Disabling TLS 1.0 and 1.1 for Microsoft 365 https://docs.microsoft.com/en-us/microsoft-365/compliance/tls-1.0-and-1.1-deprecation-for-office-365?view=o365-worldwide that we are enabling TLS 1.2 more and more in Exchange online starting October 2020 and now it affects more and more Exchange customers who so far have not enabled support for TLS 1.2 on-premises. Microsoft has announced the deprecation of TLS 1.0 and TLS 1.1 already in 2018. Those articles also contain detailed information on how you can enable TLS 1.2, which in short is only adding some registry keys and doing a reboot: Exchange Server TLS guidance, part 1: Getting Ready for TLS 1.2 Exchange Server TLS guidance Part 2: Enabling TLS 1.2 and Identifying Clients Not Using It Exchange Server TLS guidance Part 3: Turning Off TLS 1.0/1.1 As these articles above explain, you can enable TLS 1.2 in addition to your current usage of older TLS versions and solve your Free/Busy issue. Later, you can disable TLS 1.0 and 1.1 since they are not secure anymore. To prevent configuration errors like this, Microsoft recommends running the Exchange health checker on your on-premises Exchange servers on a regular basis, e.g. each month: https://aka.ms/ExchangeHealthChecker
EWS with oAuth "An internal server error occurred. The operation failed."
Hi... Since yesterday, my synchronization application starts throwing exceptions with the following error "An internal server error occurred. The operation failed." It only happen for mailboxes when I authenticatate with oAuth (CreateWithApplicationOptions). Has anyone experienced the same and found a solution? Tracing the call: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> <Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">*</Action> </s:Header> <s:Body> <s:Fault> <faultcode xmlns:a="http://schemas.microsoft.com/exchange/services/2006/types">a:ErrorInternalServerError</faultcode> <faultstring xml:lang="en-US">An internal server error occurred. The operation failed.</faultstring> <detail> <e:ResponseCode xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">ErrorInternalServerError</e:ResponseCode> <e:Message xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">An internal server error occurred. The operation failed.</e:Message> </detail> </s:Fault> </s:Body> </s:Envelope>
How to determine what SSL Certificate used between On-Prem and Exchange Online
Hi, After renewing our SSL Certificate for SMTP this week on our On-Prem Exchange 2019 server, I was reviewing our Send Connector configuration to Exchange Online and no SSL Certificate was defined under the TLSCertificateName attribute. However, the Receive Connector in Exchange Online is configured to only allow mail items signed with TLS with Subject containing our domain. Mail flow is working fine but I am intrigued to find out what certificate is being used if not our CA Certificate. I should say that the server is not configured for Hybrid. Any pointers much appreciated. Thanks in advance.
