It appears that the Exchange 2013 Test-OutlookWebServices is broken when trying to test 2007 availability services. The test fails on the Availability Service as IIS on the 2007 CAS fails with "(500) Internal Error".
[PS] C:\ >Test-OutlookWebServices -ClientAccessServer Exch2007CAS -MailboxCredential $cred -Identity testuser
Source ServiceEndpoint Scenario Result Latency
(MS)
------ --------------- -------- ------ -------
Exch2013MBX.contoso.local Exch2007CAS.contoso.local Autodiscover: Outlook Provider Success 61
Exch2013MBX.contoso.local Exch2007CAS.contoso.local Exchange Web Services Success 94
Exch2013MBX.contoso.local Exch2007CAS.contoso.local Availability Service Failure 26
Exch2013MBX.contoso.local Exch2007CAS.contoso.local Offline Address Book Success 7
Which generate these lines in the 2007 CAS IIS logs:
POST /ews/Exchange.asmx - 443 contoso\testuser 172.17.49.121 Exch2013MBX/Test-OutlookWebServices/testuser@contoso.local 500 0 0 0
Compared to the 2007 CAS IIS logs created Availability Service request issued by the 2007 version of the commandlet.
POST /ews/exchange.asmx SoapAction=GetUserAvailability;AddressCount=1;local=1;intrasiteproxy=0;x-site=0;x-forest=0;PF=0;LocalLongPoleRPCLatency=31;LocalLongPoleRPCCount=9;LocalLongPoleServer=Exch2007MBX.contoso.local;ADMainThreadRequests=2;ADMainThreadLatency=16;TimeInAS=57; 443 contoso\ExchangeAdmin 172.17.49.9 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.18052) 200 0 0 62
After turning on tracing in IIS, these two parts of the 2013 request's trace stand out.
<t:RequestServerVersion Version="Exchange2010" />
From:
63. -GENERAL_REQUEST_ENTITY <?xml version="1.0" encoding="utf-8" standalone="yes"?><soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <t:RequestServerVersion Version="Exchange2010" />
And:
ErrorInvalidServerVersion</e:ResponseCode>
From:
153. -GENERAL_RESPONSE_ENTITY_BUFFER <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><t:ServerVersionInfo MajorVersion="8" MinorVersion="3" MajorBuildNumber="298" MinorBuildNumber="1" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" /></soap:Header><soap:Body><soap:Fault><soap:Code><soap:Value>soap:Sender</soap:Value><soap:Subcode><soap:Value xmlns:q0="http://schemas.microsoft.com/exchange/services/2006/errors">q0:ErrorInvalidServerVersion</soap:Value></soap:Subcode></soap:Code><soap:Reason><soap:Text xml:lang="en">The specified server version is invalid.</soap:Text></soap:Reason><detail><e:ResponseCode xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">ErrorInvalidServerVersion</e:ResponseCode><e:Message xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">The specified server version is invalid.</e:Message >
And the description of the response code from here:
http://msdn.microsoft.com/en-us/library/microsoft.exchange.webservices.data.serviceerror%28v=exchg.80%29.aspx
“Indicates that an invalid request server version was specified in the request.”
So it looks to me like the 2013 Test-OutlookWebServices puts “Exchange 2010” in the web request, and so the Exchange 2007 CAS fails the request with a response of “ErrorInvalidServerVersion”.