Exchange Server 2013: Using Test-OutlookWebServices to Verify Web Services Functionality

The Test-OutlookWebServices PowerShell cmdlet allows you to test the functionality of the following services:

  • Autodiscover
  • Exchange Web Services
  • Availability Service
  • Offline Address Book

Running the cmdlet on a Client Access server will test the local server using the test mailbox user created earlier.

[PS] C:\>Test-OutlookWebServices

Source                                         Scenario  Result
------                                         --------  ------
E15MB1.exchange2013demo.com AutoDiscoverOutlookProvider Success
E15MB1.exchange2013demo.com         ExchangeWebServices Success
E15MB1.exchange2013demo.com         AvailabilityService Success
E15MB1.exchange2013demo.com          OfflineAddressBook Success

You can also perform the test for a specific mailbox by using the –Identity and –MailboxCredential parameters.

[PS] C:\>Get-ClientAccessServer | Test-OutlookWebServices -Identity paul.cunningham@exchange2013demo.com -MailboxCredential (Get-Credential)

Tip: Testing a specific mailbox is useful if you are troubleshooting problems with one or more of the Outlook Web Services in a particular site within your organization. You can compare results between test mailboxes in different sites to help you narrow down the source of any problems you’re seeing.

About Paul Cunningham

Paul is a Microsoft Exchange Server MVP and publisher of Exchange Server Pro. He also holds several Microsoft certifications including for Exchange Server 2007, 2010 and 2013. Connect with Paul on Twitter and Google+.

Comments

  1. Hello Paul,
    and congratulation for your work on this website!
    Have you test this cmdlet on an environement with separed roles?
    If I test with one of my CAS Servers, I’ve an error message “The specified server, CAS-Server, isn’t a Client Access server”.

    If I test with one of my Mailbox servers, this command is executed. (The autodiscover scenario result is failure, normal..)
    Thanks

  2. Hello Paul,
    are you sure this command runs still in Exchange 2013, in my case it is Ex2013 SP1. I get always the error missing user or user mailbox.
    I´ve heard that several test commands are used by the managed availability and so you can not use them anymore directly.
    Do you know which test commands are still working in Exchange 2013 and which not?

  3. Milinko says:

    Hi Paul,

    I’m having issue with autodiscovery on new exchange 2013. I’ve ran

    Get-ClientAccessServer | Test-OutlookWebServices -Identity username@domainname.com -MailboxCredential (Get-Credential)

    and result is that all three services failed. None of the domain connected workstations and outlook 2013 installed on them can connect to the exchange failing with error The attampt to log on to Microsft Exchange failed.

    Please advise!

    • Autodiscover problems have several common causes:

      1) The Autodiscover URI has not been configured/changed from the default
      2) The Autodiscover URI can’t be resolved in DNS
      3) The Exchange server’s SSL certificate does not include the Autodiscover URI
      4) The Autodiscover SCP does not exist

      Which of those can you say you’ve already checked out?

  4. Milinko says:

    Weird thing is that from exchange server itself outlook connects without problem using autodiscovery to any user mailbox but if I try to do it from any of the domain connected workstations running outlook fails with error that outlook needs to be connected.

    1: Autodiscover URI is https:// FQDN/Autodiscover/Autodiscovery.xml

    when connected to that url I get prompted, fill in the user name/pass and will get 600 ErrorCode which means that the thing is working. I guess.

    2. All of the workstation running outlook are on internal network and are part of the domain. They should get their autodiscover through AD. or not? I dont have autodiscover DNS pointing to internal mail server.

    3. Exchange server SSL is the default one that was installed while setting up the Exchange. in Subject Alternative Name I have just server name and FQDN of the server.

    4. When I run Get-AccessClientServer I do get hostname of the server and when I run Get-ClientAccesServer | fl I do get FQDN of the server, OutlookAnywhereEnabled true, AutoDiscoverCN = hostname, ms-Exchange-AutoDiscover-Service, that url from answer 1 and IsOutOfService is set to False.

    OWA is working properly, ActiveSync is working good as well and I can login into admin without problem. Really weird.

    Thank you for taking time to help me!

  5. Milinko says:

    Last Update. After installing certificate from trusted CA Authority everything is back to normal.

    Thank you for very much your help!

    btw! I’m buying your book as well :)

Leave a Comment

*

We are an Authorized DigiCert™ SSL Partner.