Exchange 2016 iApp RC2 issue

There is no plan for NTLMv2 support, AFAIK that's up to the developers of curl to implement and I haven't been able to find any evidence of plans to do that.

Unfortunately, with the architectural changes in Exchange 2013 and 2016, our advanced monitors aren't as useful. Marking the Exchange server down because one mailbox is unavailable doesn't give us a correct picture of the server health; in other words, if any mailbox is available though client access services, the server should be marked up, but adding a separate monitor for each mailbox database doesn't scale.

The plan for now with our Exchange solution is to recommend using only the "simple" monitors (which are what Microsoft officially recommends), and F5 will explore addtional advanced monitoring options in the future.