Exchange activesync?

Question

Microsoft Exchange

Good afternoon everyone, there is the following problem - after changing the wildcard certificate to exchange (exch 2013 CU10 in DAG), before exchange, all requests from outside are processed by IIS-ARR, an error began to appear during the microsoft connectivity analyzer test. I would solve the problem myself, but the error that the test produces is rarely seen on the Internet and it points (judging by the microsoft forums) to exch 2003:

0 out of 1 rated this helpful - Rate this topic
Topic Last Modified: 2009-08-18
The Microsoft Exchange Analyzer Tool sends an HTTP request using the OPTIONS verb to the Microsoft-Server-ActiveSync virtual directory on the server and analyzes the HTTP headers in the HTTP response. If the MS-ASProtocolVersions header does not contain 2.5 or 12.0, then the Exchange Remote Connectivity Analyzer tool generates the following error:
"Could not negotiate an appropriate Airsync version with server."
For More Information
----------------------------------------------------- ---------------------------------
The Exchange Remote Connectivity Analyzer currently supports Exchange ActiveSync protocol versions 2.5 and 12.0. If you are using Exchange Server 2003 SP1 or earlier, then this error does not necessarily indicate a problem. Rather, it simply indicates that the tool is not able to properly test your server. Upgrade to Exchange Sever 2003 Service Pack 2 to get the ActiveSync v2.5 functionality.
The Exchange Remote Connectivity Analyzer is a new tool with limited documentation at this time. In an additional effort to improve the documentation for each of the errors you might receive, we would like to solicit information from the community. Please use the Community Content section below to post additional reasons why you failed at this point. If you need technical assistance, please create a post in the appropriate Exchange TechNet forum or contact support. "
error in the attachment, I will be glad for any thought, even the most absurd one)
Also - there is an opinion that it is worth digging towards the autodiscover proxy, the following parameter is currently set
Set-OutlookProvider -Identity EXPR -CertPrincipalName *.domain.ru
There may be an error here.

Answer 1

Good afternoon!
Did you install Exchange server 2013 CU10 from scratch, or did you upgrade from a previous version\CU? Did the schema expand normally?
In ADSIedit along the path: CN=Servers,CN=Exchange Administrative Group,CN=Administrative Groups,CN=**OrganizationName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=**domain,DC=**name
Are there only Exchange Server 2013 CU10 servers? What version of the schema?

Answer 2

updated from Exchange 2013 CU9? there was no update, the scheme expanded normally. I ran the logs again, everything went without problems.