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
Blog Post
I've read you're issues but we also have an Exchange 2016 CU5 on Windows Server 2016 and it also did accidentally install the .NET 4.7 version. I've rebooted the machine and we have no issues. Nothing in the event viewer and all client connections are running well. I'm waiting for Microsoft to update this post and to finish checking before I revert the update because that will be a hassle for now and everything is working. I'm wondering if we're running into issues when updating to CU6.
Hi Peter,
Thanks for you reply. I think the issue I have was nothing to do with the update as you said your mail server is working fine even with .NET 4.7 installed.
I think the issue may be with my mailbox database, so my plan is to dismount the database and stop the following services "MS Exchange Search Host Controller" and "MS Exchange Search" delete the content index cache from the root of the database folder and run a couple of switches using ESEUTIL to check for errors etc. and then re-mount the database and start both services, then see if the problem persists. If it does I will have to create a new mailbox database and move all my mailbox's over. then attempt to re-build the content index cache.