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 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.
Many questions followed my article introducing Office 365 Planner, so clearly I didn’t do such a good job explaining the topic. Here’s an attempt to do so in a question and answer format. If you have other questions, try asking them in the Planner group in Microsoft’s Office 365 Network.
What is Office 365 Planner?
A curious incident occurred in Exchange Online over the last week or so when some European users who connect to their mailboxes using the venerable IMAP4 protocol reported that they couldn’t receive new mail. There’s nothing particularly notable about a glitch occurring with a messaging protocol. After all, Exchange supports quite a few (MAPI, Exchange Web Services, ActiveSync, IMAP4, POP3, and SMTP) in order to be able to provide as wide a client choice as possible.