Open svajda opened 4 years ago
Installing the EWS Managed API locally on Exchange servers will cause a lot of issues, basically rendering EWS useless. (See symptoms listed e.g. in http://msexchangeguru.com/2018/01/23/exchange-2016-exchange-web-services-managed-api-2-2-issues/). Still, many admins assume that this installation belongs to Exchange. I don't see any warning in the GitHub readme or on the download page https://www.microsoft.com/en-us/download/details.aspx?id=42951 that would warn users against this bad practice. Can we call this out?
Installing the EWS Managed API locally on Exchange servers will cause a lot of issues, basically rendering EWS useless. (See symptoms listed e.g. in http://msexchangeguru.com/2018/01/23/exchange-2016-exchange-web-services-managed-api-2-2-issues/). Still, many admins assume that this installation belongs to Exchange. I don't see any warning in the GitHub readme or on the download page https://www.microsoft.com/en-us/download/details.aspx?id=42951 that would warn users against this bad practice. Can we call this out?