Hello,

When I run TestOutlookConnectivity -ProbeIdentity OutlookSelfTestProbe as suggested on Technet, the following error message is returned:

This is a brand new Exchange 2013 installation on WinServer 2008r2. OWA works. Mails flows.

Thank you for your support

• Edited by Nic75 Tuesday, October 29, 2013 7:17 AM

What is the status if you try the other option mentioned in TechNet?

Test-OutlookConnectivity -ProbeIdentity "OutlookRpcCTPProbe" -MailboxID administrator@contoso.com

Same error occurring when specifying the host name ?

Test-OutlookConnectivity -ProbeIdentity "OutlookSelfTestProbe" -HostName "YourMailboxServer"

• Proposed as answer by Simon_WuMicrosoft contingent staff, Moderator Wednesday, October 30, 2013 2:39 AM

Hi,
I have got the same error as you do in all builds (RTM,CU1,CU2) and my personal thinking about it, is that this cmdlet has been deprecated in favor for Managed Availability even if the documentation doesn't say so.

There are also other cmdlets that we (at least I am not able to) can't use anymore... like Test-OWAConnectivity Get-Logonstatitics and Test-ECPConnectivity to name a few.

No matter the options still fails

"Managed Availability": Martina are you reffering the Microsoft Remote Connectivity Analyzer?

"Managed Availability": Martina are you reffering the Microsoft Remote Connectivity Analyzer?

No, it was not referring to ExRCA.

Exchange 2013 - Managed Availability and Server Health
http://blogs.technet.com/b/exchange/archive/2013/06/26/managed-availability-and-server-health.aspx

Hi,

Is there any update on this thread?

Thanks,

Simon

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com