Microsoft has released its quarterly updates for Exchange:
- Exchange 2016 CU17.
- Exchange 2013 CU18.
It has been quiet around these updates, and they do not bring a whole lot of features.
Important to note is that the minimum Forest Functional Level (FFL) has been raised to Windows Server 2008 R2. Personally I think this is an indication that more exciting stuff is along the way, especially around Exchange 2016 (my personal expectation, don’t shoot the messenger :-))
There are schema changes in Exchange 2016 CU17, so when installing this update you have to execute the following commands:
Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
Setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms
When it comes to the .NET Framework, Microsoft is working on a new .NET Framework release (version 4.7.1). The upcoming quarterly update of December 2018 will support this version of the .NET Framework.
More information (well, not a lot more) can be found here: https://blogs.technet.microsoft.com/exchange/2017/09/19/released-september-2017-quarterly-exchange-updates/
Last week the 2014 edition of IT/Dev Connections took place at the Aria Resort in Las Vegas and as an Exchange Server MVP I was focusing on the Exchange track.
Continue reading IT/DEV Connections 2014
Veeam recently released Patch 4 for Veeam® Backup & Replication™ v7 is now available and contains a host of resolved issues as well as new features and enhancements, including: Continue reading Veeam Backup and Replication V7 – Patch 4
By now you should have heard about the heartbleed bug. This is a serious vulnerablility in the popular OpenSSL cryptographic software library. In case you think “but I don’t use this open stuff” you’re wrong. You might not, but vendors might be.
Continue reading Heartbleed vulnerability, Exchange and load balancers
This issue was brought to my attention by Veeam, VMware recently issues a support KB article about possible data corruption when sending large amounts of data of a virtual NIC. Any data send across the network can get corrupted, including file copies, database actions etc. Naturally this can also impact Exchange server operations.
This occurs only with Windows Server 2012 running inside the VM and when the VM is using the default E1000E virtual network adapter.
Two workarounds are available:
· Disable TCP Offloading in Windows Server 2012, but this may increase CPU utilization.
· Replace the E1000E NIC with an E1000 NIC or a VMXNET3 NIC. This is probably the best solution but it is labor intensive as it means reconfiguration of all your Virtual Machines. PowerCLI may be your friend in this case.
The root cause is currently under investigation. For more information (and updated information over time) please check the VMware support KB article.