2016
747 TopicsHotfix update for 2016 CU23 HU18: (KB5066370) breaks OWA and leaves all services disabled
Has anyone else applied the latest hotfix? First of all it tries to validate open files instead of just killing these processes as part of the update, then after rebooting all the services are left in a disabled state. Then I discover it has broken IIS and OWA doesnt work. We have had client issues all day in the office. It looks like another update has been pushed out without sufficient testing. Any help would be grateful at this point, I am looking to take 2 out of 4 servers offline.205Views1like1CommentExchange 2019 Mailbox Migration Error - Folder conflicts with Exchange Online folder
Hi Exchange Experts, I'm migrating a small Exchange 2019 environment to 365. Been pulling my hair out becuase of just one mailbox giving this error Error description --------------------------- Error: AggregateMailboxFolderConflictPermanentException: The folder 'Files' conflicts with Exchange Online folder 'Files', please move the messages to another folder and restart the job. Data migrated: 0 B (0 bytes) Migration rate: -------------------------------------- Migration user report: 5/14/2025 12:32:05 PM [MEUP300MB0105] Request processing continued, stage CreatingFolderHierarchy. 5/14/2025 12:32:05 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Fatal error AggregateMailboxFolderConflictPermanentException has occurred. ---------------------- It seems to be a system folder and I've tried to remove files from it (although there're no files in it) using MFCMAPI tool with no success. Renamed the folder and tried to re-run the migration with no luck. Has anyone experience this issue? any thoughts or tips are much appreciated ! Thank you.949Views0likes5CommentsHow to perform Windows Update for Exchange 2016 DAG Cluster
Hello, I need to install windows server security update on Exchange 2016 DAG which require reboot the server. I will install the updates on the first server Tuesday, and the seconde server on Wednesday. I'm wondering if installing patches on separated days may impact Exchange services, also i need to know the steps to follow before restart each server after installing the patch.71Views0likes2CommentsApplying On-Prem EAP with New-Remote Mailbox
BACKGROUND: my org is in a hybrid AD/Exchange environment, and will remain so for some time. All mailboxes, other than a very small number with on-prem dependencies, were migrated to M365 a few years ago; we will continue to have 1-2 Exchange Servers on-premises for both management and some legacy on-prem processes. All user accounts are created on-premises, and synchronized to M365 through Entra Connect Sync. Our on-prem EAP has the exact address syntaxes that we need [applies to "Users with Exchange mailboxes" + "Resource mailboxes" + "Mail-enabled groups"]. I haven't found a clear answer to the question: with an Exchange 2019 (and soon SE) server on-premises - with users initially created on-premises - is there a way to provision new EXO mailboxes [using the 'new-remotemailbox' cmdlet], such that the on-prem EAP applies during creation? I've been working with these two references, but so far haven't found a way to make the "new-remotemailbox..." cmdlet work to (a) create a new account on-premises and (b) ultimately have an EXO mailbox provisioned with the on-prem EAP addresses in place: On provisioning mailboxes in Exchange Online when in Hybrid | Microsoft Community Hub https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-remotemailbox?view=exchange-ps Any thoughts or suggestions would be welcomed! (OR - perhaps it just can't be done?)41Views0likes0CommentsRequest for Official Cleanup Script to Retire Exchange 2016 After Migrating to Exchange SE
Subject: Request for Official Cleanup Script to Retire Exchange 2016 After Migrating to Exchange SE Hi Exchange Team, I've successfully migrated mail flow and management to Exchange Server Subscription Edition (SE) and am now preparing to retire our legacy Exchange 2016 server (EXCHANGE2016). I’ve followed the documented steps from the Decommissioning Exchange Server 2016 blog post, but I recall that a script—Cleanup-ExchangeLegacyServer.ps1—was referenced or released separately to automate the final cleanup. I’m unable to locate the actual script and would appreciate guidance on where to find it. Here’s a summary of what I’ve completed so far: Steps Completed Mail Flow Migration Reconfigured send connectors: Set-SendConnector "Outbound to Office 365" -SourceTransportServers @("EXCHANGESE") Verified SmartHost routing and TLS settings. Receive Connector Cleanup Disabled all receive connectors on EXCHANGE2016: Get-ReceiveConnector -Server EXCHANGE2016 | Disable-ReceiveConnector Mailbox Migration Moved all user, arbitration, audit log, and monitoring mailboxes: Get-Mailbox -Server EXCHANGE2016 Get-Mailbox -Server EXCHANGE2016 -Arbitration Get-Mailbox -Server EXCHANGE2016 -AuditLog Get-Mailbox -Server EXCHANGE2016 -Monitoring Queue Validation Confirmed no active queues on EXCHANGE2016. Connector Scope Audit Verified EXCHANGE2016 is no longer listed in any send connector: Get-SendConnector | Where-Object {$_.SourceTransportServers -contains "EXCHANGE2016"} Remaining Question Should I now: Run an official cleanup script (e.g., Cleanup-ExchangeLegacyServer.ps1) to safely remove EXCHANGE2016’s configuration objects while keeping Exchange SE intact? Or simply uninstall Exchange 2016 from EXCHANGE2016 and decommission the server manually? I want to ensure I follow Microsoft’s best practices and avoid breaking hybrid management or leaving orphaned AD objects. If the script is available, could you please share the official download link and any updated guidance? Thanks in advance for your help! —MichaelSolved97Views0likes2CommentsExchange 2016 Maximum number of recipients in a message that's sent by the specific sender
Hello, I want to know if the RecipientLimits value on a mailbox can override the MaxRecipientEnvelopeLimit. For example, if I set the MaxRecipientEnvelopeLimit to 50 to limit all organization mailboxes to a maximum of 50 recipients, and then I set the RecipientLimits of a specific mailbox, let’s say user10@mylab.local, to unlimited. Can user10 send an email with 100 recipients or not?Solved108Views2likes6CommentsProblem with Shared Callendar in Outlook
I have hybrid Exchange in company A (exchange 2016). I have created sharing calendar information beetween company A and company B. From company A I can check the availability of calendars of people from company B, but not all of them. From Outlook in Windows, when I try to check availability callendar of some people from company B, I receive no information. For all the people I add after these people (even from company A), I no longer receive information about the availability of the calendar. Once I remove the problematic person, I can check other people's calendars. The problem does not occur from Outlook on the Web or from MS Teams or NewOutlook - everything is OK. The problem only occurs with Outlook on Windows (version 365). How to solve the problem with checking calendar availability from Outlook in Windows?270Views0likes2CommentsShared mailbox: Use send-as, not send on behalf from Outlook 2016
Hello, We have a lot of shared mailboxes. For every shared mailbox, we create a specific security group that contains the members who should have access to that particular shared mailbox. We give full mailbox permissions and send-as permissions for that particular security group onto the shared mailbox. For example, security group A has full mailbox access and send-as permissions onto shared mailbox A. By adding users to security group A, they have full access to the shared mailbox. We create every new shared mailbox/security group combo using Powershell. That has been working flawlessly for the last years. However, for a recent new shared mailbox/security group combination, when a user that's member of the related security group wants to send an e-mail from the shared mailbox (by changing the from field in Outlook and selecting the shared mailbox from the global address list), Outlook tries to send every time 'send-on behalf'. This only happens for that newly created mailbox. I compared the output of Get-Mailbox and Get-RecipientPermission for the new problem shared mailbox and an older shared mailbox (which enable users to send mail send-as from outlook just fine) but I couldn't find any differences. For your information, that's the error we get back immediately after trying to do a send-as for the new shared mailbox: Your message did not reach some or all of the intended recipients. Subject: Test from Outlook Sent: 23/11/2017 9:27 The following recipient(s) cannot be reached: name of sending user on 23/11/2017 9:27 This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524]. Why does Outlook always tries to do a send on behalf (what we don't want) where else for other shared mailboxes, send-as works fine? Using send-as from OWA however works just fine for the newest shared mailbox. It only seems a problem related to Outlook (tested on multiple clients that have access to the shared mailbox) and that particular new shared mailbox. Thanks in advance.Solved314KViews3likes13CommentsProgram for Exchange Gets Contacts with Duplicated "OrganizationalIDNumber"
We have an old VB program that copies contacts from Microsoft Exchange to our SQL database. This worked fine for many years until 2017 when it started getting duplicated OrganizationalIDNumber from new contacts. I have been manually worked around this problem ever since (because I was busy and I am not familiar with this VB program). Now that I get some time, I want to fix this problem for good. We are expecting the OrganizationalIDNumber to be "1", "2", "3", .... But the new contacts all get the same ID "4303". I am under the impression that OrganizationalIDNumber is 32-bit. This should represent a very large number. Moreover, the program is using it as a string, and it is saved in our database as a varchar(255) data field. The ID should not be truncated (or so I thought). This certainly appears like the ID is being truncated though. My questions are: Does this look like something that you have come across? What is the solution? Where is the configuration setting in Microsoft Exchange that defines the data type of OrganizationalIDNumber? Our Exchange is version 2016. Please help if you can. Thanks. jchan113Views0likes2CommentsOutlook with exchange 2016 error 80070005
HI, I have a problem with outlook 2016 and 2019 connecting to an Exchange 2016 cu23 with the latest security patches. I have some outlook clients that have multiple mailboxes configured. There is one main user mailbox plus other service mailboxes. Only the personal mailbox is configured in cached mode. Sometimes when sending the email the error 0x80070005 is returned. I solve the error by deleting the address from the nk2 file and then the email is sent correctly. How come this problem arises? Is there a way to solve the problem permanently as it occurs randomly on multiple computers? Thank you Greetings665Views0likes1Comment