Released: December 2016 Quarterly Exchange Updates

"It generally is not our practice to change these entries as it gives people the impression the product has changed when it hasn’t"

The last version of Jetstress was posted for download about four months prior to the general release of Windows 2016 RTM so it’s reasonable for people in the field such as myself to assume that it has not been tested with Windows 2016 and that’s a legitimate concern for those of us who are working to deploy your product on Windows 2016 for our mutual customers. New Operating System, new storage drivers, etc...

When your group can't be bothered to make minor doc updates and continues to generate botched quarterly updates, e.g. CU3 and the failed Windows 2016 support in September, then it becomes evident to everyone (except perhaps your dedicated fanboys) that your group doesn't care that much about the success of the product and cares even less about those in the field that are working hard to deploy it.

Twenty years after the release of Exchange 4.0, your documentation continues to exhibit holes and rather than address the holes you prefer to waste everyone’s time by forcing them to post basic questions here for clarification. For some reason those questions are generally ignored and the few responses that are provided are mostly excuses.