Hello pls help. I am a administrator in Exchange server 2016.
When i try to access my ecp the login page work but when i log in, HTTP ERROR 500 appear.
How do i access to my ecp pls.
Sorry for my bad english
We're having on-premises Exchange servers and when I want to add mailbox to outlook for iOS (iPhone), it keeps redirecting me to the Authenticator App, Sign In to Microsoft account page. Even if I try to enter my email address there, it says that email address doesn't exist (we don't have m365). Did anyone face this issue?
Just want to add that it is the same if I try to manually add an account (with server, domain, and other details)
daffy.duck@acme.org complained that all of his mails are forwarded to bugs.bunny@acme.org.
There are no forwarding rules active on Exchange, neither ForwardingAddress nor ForwardingSmtpAddress. There are no server-side mailbox rules, also no hidden ones. I even checked with MFC MAPI Tool. There are no client-side mailbox rules on his computer. There are also no other clients except an iPhone, which is the only thing where I can't check myself if some kind of forwarding is configured, as that's a private device.
They use the CodeTwo signature tool which can do forwarding, but no forwarding is configured in there. I also checked the mail flow rules, and there is no relevant rule.
What could still be causing this forwarding, except the iPhone? From the way it is forwarded, I know it's a client-side forwarding, as Bugs receives Daffy as a sender and not the original sender.
Update1:
Update2: Solved! Thank you u/ScottSchnoll!
I am an IT admin for a local supply company and have a problem. Our Exchange server went down hard after a power failure, and I cant mount the information in the database. I can see the EDB file and made a copy, but when running standard utilities im getting missing log errors. What are my options for exchange server recovery tools to recover EDB mailboxes when the database is offline like this?
As you hopefully know, the RTM version of Exchange Server SE continues support for using the product keys from Exchange Server 2019 and that new product keys are expected in CU1.
The new product keys will be distributed via the Microsoft 365 admin center.
To verify your access to CU1 product keys when available, go to https://admin.cloud.microsoft/#/licenses/perpetualsoftwarespage to verify your license position for your billing account(s).
You can also check your current software ownership at https://admin.cloud.microsoft/#/subscriptions/software-products and https://admin.cloud.microsoft/#/subscriptions.
If you currently license Exchange Server and have active Software Assurance or equivalent USLs or entitlements, then you should see Exchange Server SE listed along with the Exchange Server 2019 product keys for the Standard and Enterprise Editions. When CU1 is released along with SE-specific product keys, you'll be ready.
If you don't see that and you believe you have the correct license, subscription, and agreement, contact Microsoft for assistance. This will help ensure a smoother transition to CU1 and the new product keys when they are available.
Sequoia. Apple mail. 1 of 4 exchange accounts from the same company stopped syncing. No noticeable event to correlate.
Webmail and IOS appear without issue.
It’s a MacOS issue, not ostensibly server-side. No result from 1 hr. with GoDaddy mail sppt (level 1 and 2).
Action taken so far after confirming settings are correct, identical to the functioning mailboxes:
Manual sync
Rebuild mailbox
Delete account, quit mail, restart, recreate account. Now I see nothing.
Created new macos login identity and created same mail account.
Attempt to use Outlook for Mac results with the error above:
No filter or rule that affects this.
I’ve seen references to this, but no consistent solution. Is there a keychain entr(ies) to delete? Is there a corrupted file? How would I do anything like that and be sure it affects that one account only.
Hi everyone,
I’m having a small problem with my Exchange Server SE.
I took a snapshot shortly after installation but didn’t delete it, so it’s now almost a year old and storage space on the hypervisor is running low. However, since I want to migrate the Exchange VM to our new Hyper-V failover cluster anyway, this isn’t too much of a problem. The question is, what’s the best way to go about this?
Would it be possible to create a backup with Veeam, shut down the domain controllers, etc., and then restore the Exchange Server? Or how should I go about this as smoothly as possible?
Thanks for your help
Hi all,
I'm in the middle of migrating from Exchange 2010 to Exchange 2016 in an on-prem environment.
I have a problem during the transition:
We still have multiple systems (third-party applications and printers.) that send emails via SMTP directly to the IP address of the old Exchange 2010 server.
These systems cannot easily be changed or updated.
What would be the best practice in this scenario?
thanks
Dear All
Currently I am having a project to migrate mailboxes from on prem to o365 as shared mailboxes . How I know how much storage I have and how much remaining and from where the storage will be consumed ?
Thanks in advance
This is the hot question about Exchange Server SE today: Where is CU1?
It's a reasonable question with a reasonable answer.
It was back in May 2024 when I provided the first Roadmap update for Exchange Server SE that mentioned CU1. At the time, I said that RTM would be released in July 2025, and CU1 would be released in October 2025. I also provided some details on what features and changes were expected in CU1. This was also echoed in the September 2024 post that discussed upgrade paths from previous versions of Exchange Server.
While the RTM version of Exchange Server SE was released in July 2025 as announced, CU1 was not released in October 2025, and in fact, as of this writing, it still has not been released.
On May 22, 2026, Microsoft quietly edited the September 2024 post to include an updated release timeline for CU1 and CU2. Specifically, CU1 is now expected in H2 of 2026 and CU2 is expected in H1 of 2027.
So, what's the reasonable answer? It's the same answer for almost every other delay related to Exchange Server releases over the past several years: security.
CU releases are driven by quality, priority, and payload (e.g., the number of changes being shipped). Security will always take precedence over releasing a CU (unless the release of a CU is needed to fix a security issue, which it sometimes is). In fact, this nuance has evolved the language used to describe the servicing model for Exchange Server.
Prior to April 2022, the servicing model was to release 4 CUs per year (1 per quarter). That turned out to be a troublesome cadence for both customers and the engineering team. In short, it was too much, too fast.
In April 2022, we announced that the servicing model would move from 4 CUs per year to 2 CUs per year. But since then, the engineering team has released only 1 CU per year (for example, the November 2023 release of Exchange Server 2019 CU13). To reflect this reality (which has been true for the past several years now), the servicing model language changed from 2 CUs per year to 1-2 CUs per year.
Since the RTM release of Exchange Server SE, five SUs have been released along with two HUs (one of which contained the first flighted feature in Exchange Server SE). In fact, the June 2026 SU alone addresses multiple CVEs (including CVE-2026-42897), and it's necessary to ensure continued communication between the Exchange Emergency Mitigation and the Exchange Flighting services and the Office Config Service after July 2026.
So, Exchange Server customers are getting updates, just in SUs and HUs and not a CU (yet). If you are feeling anxious or impatient about CU1 not yet being available, that is understandable given the multiple release schedule changes. But the Exchange Server engineering team is hard at work, and their efforts are focused in the right area: security.
If you're still running earlier versions of Exchange Server and you're waiting for CU1 to move to Exchange Server SE, don't wait. Move today and keep your SE servers updated with what has been released. All SUs and HUs released by Microsoft in between CUs are incorporated into the latest CU, and except for IUs, the updates are cumulative, so you always need only install the latest one.
Mostly for emails to collaborate on. I know its not going to be cheap
Hi Team
I deleted the exchange server and I am using exchange recipient management tools from my computer to manager exchange attributes in hybrid environments. All mailboxes are in exchnage online . I created a EMT recipieng management group when I installed recipieng management tools. I was told this group is for non domain admins , I am non domain admin but I am in organizational management . So do I need to be a member of EMT group aswell or if I am able to manage exchange attributes using organizational mamabemeng can I keep using it.
I am trying to set up a rule based on members of a group forwarding calendar invites to a specific domain.
The rule to take action on the message type of calendering is only working for direct calendar invites. The rule is bypassed for forwarded meeting invites.
I see in the received headers this content:
Content-Type: text/calendar; charset="utf-8"; method=REQUEST
Content-Transfer-Encoding: base64
So, I tried making a mail flow rule to trigger on messages with header "Content-Type" and value of "text/calendar," but this still isn't caught.
What's needed to make this work?
I have a legacy application that needs to send and receive email through Microsoft 365 Exchange but does not support OAuth. What are my available options for both cloud-based (online) and on-premises solutions?
Received an email stating the above
Severity: ● High
Time: 6/22/2026 3:00:00 AM (UTC)
Activity: Potentially compromised user account
User: name@domain . com
Details: User name@domain .com has sent 4 internal and 396 external recipients in the last day and was attempting to send to an additional 100 recipients, which would have exceeded their External limit.
I have got the user to change their password and the have 2FA set up which they needed to use to change the password.
I have looked and all of the emails have come from the following IP address 207.189.26.204 which is in Singapore from what I can establish and we are in the UK
They started sending 06/22/26 3:53 AM and the last one at 06/22/26 4:00 AM to random emails that are not associated with our company or the user.
The user only sends email from the works computer in the office which has an ip address 51.*.*.*
What else do I need to do?
Hello,
I have many shared mailboxes that have enabled MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled.
Since a maintenance a few days ago everyone that sends an e-mail as one of those mailboxes to external adresses gets that e-mail attached to an e-mail to the inbox of that shared mailbox with this text:
The attached message was sent by a member of this shared mailbox. Usually, it would appear in Sent Items, but your service is currently being upgraded. Things will be back to normal after the upgrade.
It's still also still stored in Sent Items of the personal and the shared mailbox successfully.
All mailboxes are in Ex Online, but Ex OnPrem is used for incoming/outgoing mail with Central Transport enabled with Hybrid Wizard.
This inbox-e-mail only happens when sent to external addresses, not internal mailboxes.
Background to the maintenance:
Single Exchange SE installed June updates by WSUS
* Exchange KB5904139
* Windows Server 2022 KB5094128
A colleague told me it went like this:
* Updates were installed. Afterwards VM was rebootet.
* Windows CU got rolled back during windows server reboot.
* When Windows finished booting, many services were disabled: Exchange Services, WMI, Remote Registry. He enabled them and started them.
* Then the Windows CU was installed once again (Exchange SU already reported as installed successfully).
* Server was rebooted. This time all seems fine, mail flow worked.
I checked component states, HealthChecker-Script and Logs like C:\ExchangeSetupLogs\ServiceControl.log. So far I can't find anything obvious that looks wrong with Exchange.
Anyone has suggestions, seen this error?
Currently I'm thinking uninstall and reinstall Exchange SU might be an option to try?
Hey,
At my office we have a hybrid environment, on-prem AD which is synced with EntraID.
Now, is it possible that a user can change their phone number on their own via the microsoft portal ?
I believe by default a user cannot change the phone number on their own.
Can we make it so that they can ? Is it a good practice ?
I believe it's possible but I'm not entirely sure.
I wanna know you guy's opinions