Blog Post

Exchange Team Blog
3 MIN READ

.NET Framework 4.7 and Exchange Server

The_Exchange_Team's avatar
The_Exchange_Team
Icon for Microsoft rankMicrosoft
Jun 13, 2017
Update 6/15/2017: Added a clarification that .Net Framework 4.7 has shipped and that we are still validating this release with Exchange Server. We wanted to post a quick note to call out that our ...
Updated Jul 01, 2019
Version 2.0
announcements
on premises
Setup
Tips 'n Tricks
Deleted's avatar
Deleted
I installed this just a few mins ago, I only installed on my 2013 edge with cu16 on 2012r2, with .net4.6.2, it rebooted and somehow works, I'm able to send and receive email. Though I have an exising issue with this edge server, it will suddenly eat up all virtual mem, and sometimes the transport service will suddenly stop, figured I'd install the latest .net, I was about to rebuild the vm, but now I'll see if it actually fixes it. Is it supposed to instantly break exchange after installing?
Deleted's avatar
Deleted
Jun 13, 2017
+1 my customer reported Processor reduction after mistakenly installing it and they are not willing to uninstall the update even after sharing this blog.

I can't understand why .net team does not talk to Exchange team before releasing it or why can't they add a prerequisite check to do not install if it is an exchange server.