This command is valid also for Exchange 2016?

Thanks

running below:
[PS] C:\>Get-ClientAccessServer | Test-OutlookWebServices -Identity abc@exch-2013.sv.local -MailboxCredential (Get-Credentialjohn8)

I get below message
Source ServiceEndpoint Scenario Result
Exch-2013.sv.local Exch-2010.sv.local Autodiscover:outlook provider failure

rest are skipped, above I ran on exch-2013

if I test Test-OutlookWebServices result is same as above

Can you please help why ServiceEndpoint still showing 2010 while user mailbox is moved to 2013 and this is even for any new mailbox directly created on 2013, outlook unable to set his account either automatically/manually

Hi Paul,

Have the same issue when running the command.

User’s internally are also disconnected from Exchange (once a day) and forced to reboot to re-establish a connection (work offline/online doesn’t help).
In addition, disabling cached connections makes no difference, as they’ll eventually get dropped too.

Test-Outlookwebservices returns success results on all four scenarios, but with high latency (sometimes in excess of 500ms-1s).

Running the same command including a user account via Get-ClientAccessServer command results in all scenario’s failing, with the Service Endpoint reflected as the internal FQDN rather than the autodiscover URI as configured (as shows up when running ‘Test-OutlookWebservices’.

What the heck am I missing?
Included below are (mildly modified for privacy) logs (Server name & External endpoint renamed but kept consistent with results). We are using a WildCard Cert on the server.

We are running multiple accepted domains, so we have clientdomain1.com, clientdomain2.com as accepted, and our wildcard certificate setup as a 3rd unrelated domain.
I have setup forward lookup zones for the 3rd domain to resolve to the mail server internally.

[PS] D:exchange>Test-OutlookWebServices

Source ServiceEndpoint Scenario Result Latency
(MS)
—— ————— ——– —— ——-
Exch.EL.local mail.elsetup.ca Autodiscover: Outlook Provider Success 488
Exch.EL.local mail.elsetup.ca Exchange Web Services Success 152
Exch.EL.local mail.elsetup.ca Availability Service Success 1016
Exch.EL.local mail.elsetup.ca Offline Address Book Success 120

[PS] D:exchange>Get-ClientAccessServer | Test-OutlookWebServices -Identity administrator@clientdomain.com -MailboxCr
edential (Get-Credential)

Source ServiceEndpoint Scenario Result Latency
(MS)
—— ————— ——– —— ——-
Exch.El.local exch.el.local Autodiscover: Outlook Provider Failure 51
Exch.El.local exch.el.local Exchange Web Services Failure 3
Exch.El.local Availability Service Skipped 0
Exch.El.local exch.el.local Offline Address Book Failure 50

Autodiscover problems have several common causes:

1) The Autodiscover URI has not been configured/changed from the default
Has been set as https://mail.elsetup.ca/autodiscover/autodiscover.xml
2) The Autodiscover URI can’t be resolved in DNS
mail.elsetup.ca resolves internally to the Exchange Server
3) The Exchange server’s SSL certificate does not include the Autodiscover URI
Its a wildcard cert – *.elsetup.ca
4) The Autodiscover SCP does not exist
It does exist, and matches the autodiscover URI

What am I missing?
We are running Exch2013 SP1, so MAPI is enabled, and clients are running Outlook 2013 Sp1.

Any insight would be greatly appreciated!

I have a problem with Exchange and Outlook. I can’t connect Outlook to Exchange.

When I use Microsoft Remote Connectivity Analyzer I have errors(SSL error have becouse I don’t buy certificate yet):

Od zdalnego serwera Unknown otrzymano odpowiedź HTTP 401 Brak autoryzacji. Jest to zazwyczaj wynik użycia nieprawidłowej nazwy użytkownika lub hasła. Jeśli próbujesz zalogować się do usługi Office 365, upewnij się, że używasz pełnej głównej nazwy użytkownika (UPN).
Nagłówki odpowiedzi HTTP:
request-id: 97c5ad44-4e2b-4cc4-94bf-8367602a9d30
X-SOAP-Enabled: True
X-WSSecurity-Enabled: True
X-WSSecurity-For: None
X-OAuth-Enabled: True
Cache-Control: private
Server: Microsoft-IIS/8.5
WWW-Authenticate: Negotiate,NTLM,Basic realm=”autodiscover rivait eu”
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: RIVAITWADOWICE
Date: Mon, 10 Nov 2014 12:07:20 GMT
Content-Length: 0
Upłynęło czasu: 321 ms.

When I use command Test-OutlookWebServices I get this errors:

Autodiscover: Outlook Provider Failure 4854
Exchange Web Services Failure 62
Availability Service Skipped 0
Offline Address Book Skipped 0

How to fix this errors?

Thanks..

Please help….

Exchange 2013

1) The Autodiscover URI has not been configured/changed from the default
– configured as… -AutoDiscoverServiceInternalURI https://mail.mydomain.com/Autodiscover/Autodiscover.xml

2) The Autodiscover URI can’t be resolved in DNS
– it can be resolved…. https://mail.mydomain.com/Autodiscover/Autodiscover.xml

3) The Exchange server’s SSL certificate does not include the Autodiscover URI
– has the ssl cert (SAN) from Comodo.for mail.mydomain.com

4) The Autodiscover SCP does not exist
-serviceBindingInformation = https://mail.mydomain.com/Autodiscover/Autodiscover.xml
-keywords = our site (AD Site), also has a long number

When I run Test-OutlookWebServices,…. I get Autodiscover: Outlook Provider Failure
Can’t download OAB from Outlook 2013. Also, can’t do Out of Off, No calendar free/busy while scheduling.

FYI, Arbitration mailbox is in server mbx01, but when I run Test-OutlookWebServices, the Source server is mbx03. Don’t know if that has to do anything with it.

More buggy crap? Ok.

Well anyway, the OU issue is easily worked around by adding the -OU switch when running the script, as I mentioned here:

https://www.practical365.com/exchange-server-2013-creating-a-test-mailbox-user-for-troubleshooting-with-test-cmdlets/

“If necessary use the –OU parameter to specify which OU the account should be created in.”

I noticed first off that by default these won’t run if you have the word “User” anywhere in your domain. Basically, the script to create the user fails. Running it manually fails as well. This worked for me, http://www.definit.co.uk/tag/new-testcasconnectivityuser-ps1/

In addition, the test on the specific mailbox is telling me that my client access servers are not client access servers? I’m chalking this up to more buggy crap with MS. Just wanted to pass it along.

Thanks

My outlook clients fail to connect to my Exchange2013. It keeps prompting for username and password and i cannot create a new profile. “The connection to Microsoft Exchange is unavailable. Is the error i get.