Update: for the most up to date requirements for running Exchange 2016 Edge role on Windows Server 2016, see this article. Please note that there is currently a known issue where Edge setup does no...
Updated Jul 01, 2019
Version 2.0
Blog Post
This is silly.
1) No one installed an edge server and used MS's built in protection. You do an edge server and use a 3rd party spam/antivirus
2) KB4013429 did blow up my edge server and this is the only post I've seen about it and this is over a week after KB4013429 was released. Come on man!
We are still running exchange 2016 edge on windows 2016. KB4013429 was installed before exchange and everything is working fine. EOP requires Enterprise CALs. Very few of my 600 users have Enterprise CALs and the cost would be stunning to add it.
This is clearly a bug and instead of trying to sell Office365 crap fix the problem.
[Rant](WE REALLY DO NOT WANT ANY OF IT! :) It cost more and this stuff isnt' hard to run in house. Also, we've had no major outages in years and MS cloud stuff have massive outages 2 times in the last few weeks!.) [/Rant]
- Yeah, this most obvious a bug. Nasty behaviour from MS. It's pure laziness.
Come on! - when are you going to address this BUG?
- I just lost a complete day on this! New installation and I was aware of this bug, but didn't worry too much as it was installed by our WSUS selection. Later I noticed that this KB was replaced by KB4015438 and that one is replaced by KB4016635. My Transport service is crashing until I uninstall the KB4016635! The bug is still there in that KB. What is even worst is that nothing is mentioned about it in the "Known issues section" of either of the KBs. I do strongly agree that Microsoft WAS a company that was trustworthy, but isn't any longer with too much focus on the cloud and total ignorance of customers and partners.