I've added a third CAS to our existing environment, which has operated with 2 CAS for years. All pre-requisite steps were followed, the CAS certificate is correct, and this CAS has matching settings on all applications to one of the other CAS (except of course where a setting refers specifically to this CAS' hostname, etc.). I am QA'ing before deploying this one to production behind our HLB. When I run Test-ActiveSyncConnectivity, it always fails on the Ping scenario. On both of my other CAS servers, this test runs all the way through quickly. There is no firewall on this server, and no firewall between it and other servers. Can any one help? I've searched all over and found no one else reporting this specific failure point for this cmdlet. Thanks!
[PS] C:\Windows\system32>Test-ActiveSyncConnectivity | FLRunspaceId : 8afc75aa-515f-4a91-8f33-8a6eabf26479
LocalSite : US-Seattle
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : STL-CAS3-v
LocalSiteShortName : US-Seattle
ClientAccessServer : STL-CAS3-v.company.corp
Scenario : Options
ScenarioDescription : Issue an HTTP OPTIONS command to retrieve the Exchange ActiveSync protocol version.
PerformanceCounterName :
Result : Success
Error :
UserName : extest_b14f12a6b3f24
StartTime : 12/4/2014 9:28:52 AM
Latency : 00:00:00.2500000
EventType : Success
LatencyInMillisecondsString : 250.00
Identity :
IsValid : True
RunspaceId : 8afc75aa-515f-4a91-8f33-8a6eabf26479
LocalSite : US-Seattle
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : STL-CAS3-v
LocalSiteShortName : US-Seattle
ClientAccessServer : STL-CAS3-v.company.corp
Scenario : FolderSync
ScenarioDescription : Issue a FolderSync command to retrieve the folder hierarchy.
PerformanceCounterName :
Result : Success
Error :
UserName : extest_b14f12a6b3f24
StartTime : 12/4/2014 9:28:52 AM
Latency : 00:00:00.2031250
EventType : Success
LatencyInMillisecondsString : 203.12
Identity :
IsValid : True
RunspaceId : 8afc75aa-515f-4a91-8f33-8a6eabf26479
LocalSite : US-Seattle
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : STL-CAS3-v
LocalSiteShortName : US-Seattle
ClientAccessServer : STL-CAS3-v.company.corp
Scenario : First Sync
ScenarioDescription : Initialize the Sync partnership for the test folder and create a sync state on the server
.
PerformanceCounterName :
Result : Success
Error :
UserName : extest_b14f12a6b3f24
StartTime : 12/4/2014 9:28:52 AM
Latency : 00:00:00.1093750
EventType : Success
LatencyInMillisecondsString : 109.38
Identity :
IsValid : True
RunspaceId : 8afc75aa-515f-4a91-8f33-8a6eabf26479
LocalSite : US-Seattle
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : STL-CAS3-v
LocalSiteShortName : US-Seattle
ClientAccessServer : STL-CAS3-v.company.corp
Scenario : GetItemEstimate
ScenarioDescription : Issue a GetItemEstimate command to retrieve count of items waiting to sync.
PerformanceCounterName :
Result : Success
Error :
UserName : extest_b14f12a6b3f24
StartTime : 12/4/2014 9:28:52 AM
Latency : 00:00:00.0625000
EventType : Success
LatencyInMillisecondsString : 62.50
Identity :
IsValid : True
RunspaceId : 8afc75aa-515f-4a91-8f33-8a6eabf26479
LocalSite : US-Seattle
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : STL-CAS3-v
LocalSiteShortName : US-Seattle
ClientAccessServer : STL-CAS3-v.company.corp
Scenario : Sync Data
ScenarioDescription : Sync all existing data in the test folder.
PerformanceCounterName :
Result : Success
Error :
UserName : extest_b14f12a6b3f24
StartTime : 12/4/2014 9:28:52 AM
Latency : 00:00:00.0625000
EventType : Success
LatencyInMillisecondsString : 62.50
Identity :
IsValid : True
RunspaceId : 8afc75aa-515f-4a91-8f33-8a6eabf26479
LocalSite : US-Seattle
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : STL-CAS3-v
LocalSiteShortName : US-Seattle
ClientAccessServer : STL-CAS3-v.company.corp
Scenario : Ping
ScenarioDescription : Execute Ping command for testing DirectPush against a test folder. An item is created in
the folder to trigger the Ping response.
PerformanceCounterName : DirectPush Latency
Result : Failure
Error : Exchange ActiveSync command Ping failed with error code 1.
Protocol log:
UserName : extest_b14f12a6b3f24
StartTime : 12/4/2014 9:28:52 AM
Latency : -00:00:01
EventType : Error
LatencyInMillisecondsString :
Identity :
IsValid : True
[PS] C:\Windows\system32>