Hello,

I have setup an Exchange 2013 CU6 environment which contains the following:

1 machine with client access role

3 machine with mailbox role

1 machine with both client access and mailbox server role.

When I run the Test-EcpConnectivity against the machine which has both roles I get the following:  

WARNING: The test couldn't test the internal URL of this virtual directory, because the InternalURL property isn't set.

But when I run "Get-EcpVirtualDirectory|fl" against the same machine, it shows that internal url property is set.

Why is this happening and how can it be solved?

• Edited by Bogdan Nane Monday, November 03, 2014 2:05 PM

Hi,

The Test-OwaConnectivity cmdlet has been deprecated. It is recommended to use the Get-ServerHealth cmdlet to monitor server state.

Regarding the parameter of Get-ServerHealth

http://technet.microsoft.com/en-SG/library/jj218703(v=exchg.150).aspx

Refer to this similar thread

https://social.technet.microsoft.com/Forums/en-US/e952a854-647e-4f88-b54c-449c82c1c82e/testowaconnectivity-fails-cannot-find-internalurl-property?forum=exchangesvrdeploy

Best Regrads.

no, the internal URL is set on the ECP virtual directory (which is a separate virtual directory than owa)

I admit I initially posted "Get-OwaVirtualDirectory" instead of "Get-EcpVirtualDirectory" by mystake... but I edited it afterwards.

My Problem is related to the Test-EcpConnectivity  which should't be deprecated.

Thank you for the second link thou... the answer marked as solution suggests that there is a problem in Exchange 2013 CU1 and CU2... but I am using CU6. 

... and Test-CalendarConnectivity  is giving me the same problem as Test-EcpConnectivity,