Exchange 2013/2016 Installation will be BLOCKED If?

Yes this will happen in Jun ’18 release of Exchange cumulative update and after that If your system does not meet requirements which included .NET Framework 4.7.1 it would not allow to you install either exchange 2013 or Exchange 2016.

So make sure in the next few months you do testing in your lab environment and make sure it goes through you change management process (if any) and get the system ready. This is major update. At this point it not clear how or what will happen if you have existing Exchange 2013/2016 without .NET Framework 4.7.1 and new Servers installed after June ’18 with .NET 4.7.1.

I will update this post as soon as I hear back from Exchange product team, till then stay tuned.

Exchange Team Blog

Released: December 2017 Quarterly Exchange Updates


Recent Release

KB articles that describe the fixes in each release are available as follows:

Reminder for Hybrid

In hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., 2013 CU19, 2016 CU8) or the prior (e.g., 2013 CU18, 2016 CU7) Cumulative Update release.