r/exchangeserver • • Mar 07 '21

NEW! Microsoft Safety Scanner (MSERT) updated for Exchange Vulnerabilities!

200 Upvotes

I just learned that the Microsoft Support Emergency Response Tool (MSERT) has been updated to scan Microsoft Exchange Server!

Microsoft Defender has included security intelligence updates to the latest version of the Microsoft Safety Scanner (MSERT.EXE) to detect and remediate the latest threats known to abuse the Exchange Server vulnerabilities disclosed on March 2, 2021. Administrators can use this tool for servers not protected by Microsoft Defender for Endpoint or where exclusions are configured for the recommended folders below.

...

These remediation steps are effective against known attack patterns but are not guaranteed as complete mitigation for all possible exploitation of these vulnerabilities. Microsoft Defender will continue to monitor and provide the latest security updates.

Information about this can be found in the MSTIC blog post here (all the way at the bottom).

Safety scanner download here.


r/exchangeserver • • Feb 14 '26

Goodbye Exchange Server

163 Upvotes

We finally shut down our remaining exchange servers last week - strange to think that almost 30 years of knowledge has gone with them (I started on Exchange 5.0 SP2) although EXO still retains the bulk of it - there are many things that I won't miss!

Thank you to everyone on here for the guides, links and advice - SMTP2GO being my latest 'find' on here.

So, a world of powershell awaits - any links to decent sites for scripts etc would be great but I'm honest enough to admit that ChatGPT did a lot of the heavy lifting in the last week to enable us to decom completely.


r/exchangeserver • • Feb 20 '24

Article Over 28,500 Microsoft Exchange Servers at Risk from Actively Exploited Security Flaw

Thumbnail
thankyourobot.com
142 Upvotes

r/exchangeserver • • Mar 23 '21

It can't be this hard for MS

Post image
140 Upvotes

r/exchangeserver • • Mar 12 '21

Exchange Breach in a nutshell

Post image
135 Upvotes

r/exchangeserver • • Jan 01 '22

Cheers!

Post image
133 Upvotes

r/exchangeserver • • Sep 11 '26

Time to say goodbye: retired my last Exchange Server today

115 Upvotes

As the title says: this is kind of a strangely emotional moment for me. I have been a regular reader and lurker in the forum and found many supportive and honestly incredibly nice people here. I have been running the Exchange on-premise infra for various organizations, roughly 500 users per domain - a small fish but always a happy admin.

As none of my orgs wanted to move to the cloud, we transitioned to FOSS alternatives, running the Groupware functions via NextCloud and the emails via a FOSS stack. Took a bit to set everything up and document properly, making sure alerts, bells and whistles are installed to make sure it all keeps running. We have been running this infra for about 6 months now and ironed out some of the problems. Users were still using Exchange occasionally and some of the slower ones to migrate were nudged over by my very supportive executive level.

There was hardly anything left when I finally decommissioned the very last Exchange Server today. This ends my 15 years running, caring, fixing and keeping afloat Exchange. I did not believe that this would leave me emotional but it does.

There is really nothing to this post than a bit of waving goodbye. I will most likely stay here for a bit longer as I often turned to this community for help, tips and tricks. New systems have other challenges but the journey continues.

Godspeed to my fellow admins out there - the world would be a less interactive space without y'all!


r/exchangeserver • • Apr 22 '25

The good ole days of Exchange

Post image
115 Upvotes

Life sure was less complex back then.


r/exchangeserver • • Oct 03 '22

Exchange Zero Day Mitigation Bypassed

95 Upvotes

It would appear that that mitigation released by Microsoft on Friday/Saturday (depending on your time zone) can be bypassed easily.

A revised rule structure of .*autodiscover\.json.*Powershell.* has been discovered to work, so update your rules. Hopefully Microsoft will update the EMS to use the new structure.

https://twitter.com/GossiTheDog/status/1576852912877101057


r/exchangeserver • • Oct 29 '25

Stayin alive, stayin alive. Ah ah ah ah stayin aliiiiiiiiiiiiiive.

Post image
93 Upvotes

r/exchangeserver • • Jan 01 '22

I think this is from like Exchange 4.0 launch. Anyways, HAPPY NEW YEAR

Post image
88 Upvotes

r/exchangeserver • • Oct 09 '25

PSA: Do NOT use Windows Server 2025 as the schema master before installing Exchange Server SE RTM

84 Upvotes

PSA: Do NOT use Windows Server 2025 as the schema master before installing Exchange Server SE RTM. The Windows Server team is working on a permanent fix for this issue (to be released in the following months). If you are already affected by this issue, contact Microsoft Support (Active Directory team) and they have a process to allow AD replication to work (but it might require manual schema editing).

#WindowsServer2025 #MSExchangeSE #ADSchema

https://techcommunity.microsoft.com/blog/exchange/active-directory-schema-extension-issue-if-you-use-a-windows-server-2025-schema-/4460459


r/exchangeserver • • Mar 02 '21

IMPORTANT: March 2021 Exchange security updates

82 Upvotes

FYI folks, there is a set of out of band security updates for Exchange Server, now available:

Released: March 2021 Exchange Server Security Updates - Microsoft Tech Community

Update ASAP. There are confirmed live exploits.


r/exchangeserver • • Feb 05 '26

I built a free, open-source tool to extract emails from Exchange EDB files (no Exchange server needed)

79 Upvotes

Hey everyone,

I've been working on a tool that I think could be useful for sysadmins, forensic analysts, and anyone who needs to recover data from offline Exchange databases.

**The problem:** You have an EDB file (Exchange mailbox database) but no running Exchange server. Maybe it's from a decommissioned server, a backup, or a forensic investigation. Microsoft's tools require a working Exchange environment, and commercial recovery tools cost hundreds of dollars.

**The solution:** [MDB Explorer](https://github.com/igrbtn/EDB_Explorer) - a Python GUI application that opens EDB files directly and lets you:

- Browse mailbox folder structure (Inbox, Sent Items, Calendar, etc.)

- View emails with full headers, body (text & HTML), and metadata

- Extract and save attachments (including large ones)

- Export individual emails or entire mailboxes to EML format

- Export calendar items to ICS format

- Search/filter by date, sender, subject, attachment status

- CLI mode for scripting and batch operations

**Technical details:**

- Uses `libesedb` to read the ESE database format

- Handles LZXPRESS compression (Exchange compresses most data)

- Supports multiple encodings (UTF-8, Cyrillic, etc.)

- Cross-platform: Windows, macOS, Linux

- No Exchange server or Outlook required

**Installation:**

```

git clone https://github.com/igrbtn/EDB_Explorer

cd MDB_Explorer

# Windows: install_windows.bat

# macOS: ./install_mac.sh

# Linux: ./install_ubuntu.sh

```

It's completely free and open source. Would love feedback from anyone who tries it out!

**Use cases:**

- Disaster recovery when Exchange is down

- E-discovery and legal holds

- Digital forensics investigations

- Migrating data from old Exchange servers

- Accessing mailboxes from backup EDB files

GitHub: https://github.com/igrbtn/EDB_Explorer


r/exchangeserver • • Apr 13 '21

Released: April 2021 Exchange Server security updates (some with Critical score)

78 Upvotes

The release of April 2021 security updates (SUs) for Exchange Server (2013, 2016, 2019) was just announced. Hopefully the FAQ there is comprehensive enough but TLDR:

  • SUs are released only for supported Cumulative Update (CU) versions (last two for E2016 and E2019 and CU23 for E2013). All update levels of Exchange server 2013, 2016 and 2019 are vulnerable so if your servers are not running a supported CU, you will need to update CUs first.

  • No known active exploits at the time of release (so no scripts to check IOCs etc. like in March).

  • Hybrid customers need to update their on-premises servers; re-running HCW is not needed (if in use).

  • April 2021 SUs contain March 2021 fixes too. You do not need to uninstall March SUs first.

  • Exchange Server 2010 is not impacted.

IMPORTANT: If manually installing security updates, you must install .msp from elevated command prompt (see Known Issues in update KB article).

Update your servers and then – keep them updated!

(I’m not linking to updates here because the blog post might get important updates)


r/exchangeserver • • Mar 09 '21

Hafnium Breach recap + New CompareExchangeHashes Script...

78 Upvotes

In Microsoft Security Script Repo there is a new (at least to me) script called CompareExchangeHashes.ps1 so just a heads up is there is somebody that haven't seen that (like me)

Quote from Microsoft

"This script provides a mechanism for malicious file detection on Exchange servers running E13, E16 or E19 versions. For more information please go to https://aka.ms/exchangevulns

The script currently only validates files in exchange virtual directories only, it does not check any files in the IIS root. This script needs to be run as administrator"

Edit - I can confirm that CompareExchangeHashes.ps1 script from 11 March 2021 (I tested from18:00h CET) makes sense - still I got some false positives. I can also see other people have some doubts about few files from that script, but it is far better than situation at the beginning of this script. I can recommend it at this point.

Edit 3: March 10 12:49h CET: If you are worried about integrity of some files (especially .aspx) and you would like to check hashes of those files inside Exchange installation - check this comment out, it might help you https://www.reddit.com/r/exchangeserver/comments/m16vzq/hafnium_breach_recap_new_compareexchangehashes/gqfq71e?utm_source=share&utm_medium=web2x&context=3

EDIT 4 10th March 2021 17:39h CET- POTENTIALLY IMPORTANT ONE - You can check if you been hacked, but before you click on link, please do your research whether you will trust this link or resource or not. That said - on this link - https://checkmyowa.unit221b.com/ you can check if you have been hacked in this latest breach. According to Allison Nixon from Unit 221 B they somehow got to the list of 86.000 IPs/domains that have been hacked in this breach. If you visit the link above, you can verify yourself by visiting website from the same IP on which you Exchange resides or by sending email to the domain that is potentially breached. I done it and I came up clean. I will update my blog with this info and screenshot, so you can check that out if you like before clicking on the above link.

One credible source that is reporting this also is https://krebsonsecurity.com/2021/03/warning-the-world-of-a-ticking-time-bomb/

Recap of the situation as I can see it until today

Patching:

- You can now apply security patch without the latest Ex CU installed. Also, Ex 2010 support is available.

https://techcommunity.microsoft.com/t5/exchange-team-blog/march-2021-exchange-server-security-updates-for-older-cumulative/ba-p/2192020

In my experience patching via Windows Update is mostly trouble free way. If security update is now available via Windows Update for you - make sure to run it as Administrator after you download.

Here are all the steps needed to patch in short presentation

https://webcastdiag864.blob.core.windows.net/2021presentationdecks/March%202021%20Exchange%20Server%20Security%20Update%20-%20EN.pdf

If you cannot patch immediately - this is the script that can help you mitigate until you are able to apply patches - ExchangeMitigations.ps1, and it can be found here https://github.com/microsoft/CSS-Exchange/tree/main/Security

Here is also a good guide how to protect yourself if you cannot patch yet (although you really should)

https://msrc-blog.microsoft.com/2021/03/05/microsoft-exchange-server-vulnerabilities-mitigations-march-2021/

Scanning systems

After you are done patching (although I think If you are reading this now, it might be too late) next best thing to do is to start investigating if you were breached. This is Zero Day expoit known to be in the wild more than two months. So, maybe you were breached before March 2021.

https://github.com/microsoft/CSS-Exchange/tree/main/Security

Test-ProxyLogon.ps1 script is great start - it will scan your logs and indicate if there is suspicious activity or files on your Exchange box...

If the script Test-ProxyLogon.ps1sweeps returned nothing I would not say congrats - maybe your logs were cleaned by adversary(es) - keep reading and do further research...

http-vuln-cve2021-26855.nse - will help you check if the security patch installed earlier is applied properly.

CompareExchangeHashes.ps1 - is new script addition (to my knowledge) which can help you further establish potential breach.

Indicators of Compromise

Whether you got nothing or something in the script log sweeps, you should investigate further and look for indicators of compromise (IOCs). Adversary probably thrown some web shell scripts on your system if your logs are full - ( .aspx, .js or zip if data exfiltration is underway)

Here is a list of locations you should look for suspicious files on your system

https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Sample%20Data/Feeds/MSTICIoCs-ExchangeServerVulnerabilitiesDisclosedMarch2021.csv

Also here are further instructions for IOCs - https://www.microsoft.com/security/blog/2021/03/02/hafnium-targeting-exchange-servers/

If you found something (inetpub directory is first solid indicator if it has .aspx files) now is time to stop and take a break - if you are obliged to report incident - do it now, also this is good point to inform your management on the situation. One more thing - do not remove anything if you are planing to do forensics, or you have some internal of law restrictions.

Exchange is tightly (im most environments) connected to AD and perhaps local/internal production network, so assume that also is maybe compromised!

Cleaning the mess

Again, do not proceed if you haven't reported incident, and if you need forensics to be done.

At the bottom of this link - https://msrc-blog.microsoft.com/2021/03/05/microsoft-exchange-server-vulnerabilities-mitigations-march-2021/

there is a tool called MSERT (Microsoft Support Emergency Response Tool) it will scan your Exchange server and remove all known attack patterns. Again, not 100% sure because from what I can see, we still learn about this.

What if there is something in the logs but my system is completely clean?

This is one of my lines (I had two) from my initial Test-ProxyLogon.ps1 sweep

2021-03-03T05:00:14.816Z 245cb23a-3c1d-491a-a871-f32b0b345v1 86.105.18.116 MY PUBLIC IP /ecp/y.js X-BEResource-Cookie ExchangeServicesClient/0.0.0.0 ServerInfo~a]@localmail.local:444/autodiscover/autodiscover.xml?# 200

Other than this line, there is absolutely nothing on my systems - everything is at it was. Also, I applied security patch in early morning of March 03 2021.

According to Microsoft Exchange Team member this can maybe be indicator that the system was probed and scanned but not breached.

https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2021-exchange-server-security-updates/bc-p/2188076/highlight/true#M29753

I'm still waiting for some kind of confirmation maybe from other sides.

What if I'm breached?

So far it looks like your data should be intact with this, but your system is compromised. It is all up to you and your situation and maybe company policy. Rebuilding system would be best bet...

Edit 1: Also reset all you AD admin and user passwords.

Other steps/resources

I went in depth with more scripts/tests/sources for my personal reference, and discussed some of mentioned steps/questions in more depth on my blog https://www.informaticar.net/microsoft-exchange-march-2021-breach-hafnium/

I would not like to write books in this post (it is already long) so if you are interested how it went in my case, and what else have I done, you can check the link.

Also if you have any suggestions, especially on topic of items in logs but no evidence of breach - I would be happy to hear.

English is not my native language, so if there are mistakes in text - sorry.

Edit 2: Thank you very much for awards, great comments and helpful suggestions. :)


r/exchangeserver • • Mar 06 '21

End of 2016 patching marathon. We got her folks

Post image
77 Upvotes

r/exchangeserver • • May 07 '22

A nice look back at Exchange 5.5

Thumbnail
youtu.be
75 Upvotes

r/exchangeserver • • Dec 19 '22

For those older geeks in here…how many floppies do you need to get MS Mail up and running?

Post image
74 Upvotes

r/exchangeserver • • Mar 16 '21

New Cumulative Updates out

72 Upvotes

r/exchangeserver • • Feb 10 '25

Exchange Server 2019 CU15 (aka 2025 H1 CU) is out!!

71 Upvotes

Be sure to read the documentation, especially the new Feature Flighting.

Released: 2025 H1 Cumulative Update for Exchange Server -https://techcommunity.microsoft.com/blog/exchange/released-2025-h1-cumulative-update-for-exchange-server/4362055

#MSExchange #CU15 #Announcement #FeatureFlighting


r/exchangeserver • • Jan 12 '22

January Updates ReFS became RAW for Database Volumes

70 Upvotes

Installed these updates tonight, in a two server Exchange 2016 CU22 DAG, running on Server 2012 R2. After a really long reboot, the server came back up with all the ReFS volumes as RAW. NTFS volumes attached were fine. I realize this is not exclusively an exchange question but it is impacting my ability to bring services for Exchange back online.

After further troubleshooting I uninstalled all the updates except the new SU, and now after another long reboot the drives are showing as readable ReFS again! Looking at the status of these database now, it looks like I am going to be doing a re-seed now :(

Anyone have any ideas? dot.net update broke the ability to mount ReFS?


r/exchangeserver • • May 14 '26

URGENT: Microsoft released a mitigation for Exchange Server

68 Upvotes

Microsoft disclosed CVE-2026-42897, a reported vulnerability affecting Exchange Server Outlook on the web (OWA). An attacker could exploit this issue by sending a specially crafted email to a user. If the user opens the email in OWA and certain interaction conditions are met, arbitrary JavaScript can be executed in the browser context.

They released IIS URL Rewrite rule mitigation M2.1.0 for EEMS and EOMT today, as well.

More info at https://techcommunity.microsoft.com/blog/exchange/addressing-exchange-server-may-2026-vulnerability-cve-2026-42897/4518498.


r/exchangeserver • • Jul 12 '18

Exchange Server 2010 mail flow issues after installing July 2018 Windows Updates

67 Upvotes

We look after several small business clients and this morning 3x different clients reported mail flow issues (all are running single-server installs of Exchange 2010 SP3 on Windows Server 2008 R2 Std, or similarly set up SBS 2011). They all have Windows Updates set to Automatic, and all installed the latest updates successfully last night. However this morning at different times between 9-11am they each stopped getting inbound email, and we could see it queuing at their scrubbing provider. After investigation it seems that the Exchange Transport service is not responding. On one of the servers we actually saw errors in the event log saying the server had timed out connecting to itself (exchange transport), but on the other two there were no errors. If we try to stop the service, it just hangs at 'stopping' for over 30min so we reboot the server and after the reboot everything was normal again and mail started flowing again.

I did some quick google searches but have not found anyone else mention similar issues, but having 3 different clients all have the same issue, the day after updates installed, tends to suggest it is not an isolated problem.

The patches installed were:

2018-07 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 7 and Server 2008 R2 for x64 (KB4340556)

2018-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4338818)

Cumulative Security Update for Internet Explorer 11 for Windows Server 2008 R2 for x64-based Systems (KB4339093)

Windows Malicious Software Removal Tool x64 - July 2018 (KB890830)

We're worried that this may reoccur as the servers were working fine for about 5-6 hours after their early morning patching/reboots and then all fell over mid/late morning today...

Has anyone else had any similar issues with the July 2018 Windows Updates?

UPDATE:

It seems removing KB4338818 does fix it, the one that failed again over the weekend had auto-reinstalled as the engineer who removed it forgot to block it from reinstalling. The remaining servers are still working OK as far as I know today.