A recent Microsoft blog lauded the wonders of online archives, specifically of the type made available in on-premises Exchange and Exchange Online (just in case you thought otherwise). Interestingly, the post says that “studies suggest that three-fourths of an organization’s intellectual property is contained within email and messaging systems.”
Following my post on “The story of Exchange IOPS” outlining the journey of Exchange from being an I/O hog to something far less demanding on storage systems, a recent request from Josh Odgers from Nutanix to consider his post “Peak performance vs Real World – Exchange on Nutanix Acropolis Hypervisor (AHV)” seemed to be opportune.
The history of software is littered with examples of grand strategic changes that never amounted to much when implemented. The crusade to reduce the number of disk I/O operations generated per user per second (IOPS) is an example of how a big bet paid off.
The disclosure on the EHLO blog that Exchange on-premises servers will run into some known issues if .NET Framework 4.6.1 is installed might surprise some, especially because it has become a recommended update distributed by Windows Update, but it’s not really much of a shock.
A recent message from a reader piqued my interest because it describes a problem that I think many people face today. Here’s what it said: