Water Mark
Feb 18, 2020 | view(s) | people thought this was helpful

Test Microsoft Exchange Autodiscovery and Impersonation

Test Microsoft Exchange Autodiscovery and Impersonation

Cisco Webex Teams Calendar service subscription for users failing due to Autodiscovery issues

Cisco Webex Teams Calendar service is pending Activation due to Autodiscovery issues

Note: For Directory Connector deployment and troubleshooting help, see:


As a Hybrid Calendar Service troubleshooting step, use this procedure to test autodiscovery with your Microsoft Exchange Server (or Exchange Online) and to check that the service has the required access permissions.

Before You Begin

  • For accurate results, run these tests from a machine that has similar network conditions to the connector Expressway-C node (DNS, external connectivity, and so on).
  • Download EWS editor (EwsEditor 1.20 - bin.zip) from https://github.com/dseph/EwsEditor/files/1989889/EwsEditor.1.20.-.bin.zip, then double-click on EWSEditor and extract all the files to a desired location.
  • The EWSEditor runs on Microsoft Windows. See the documentation for other requirements.
Testing steps:

Setup EWSEditor.
  • To verify autodiscovery, do the following substeps:
    1. Open EWSEditor.exe from the location where the EWSEditor files were extracted, choose Tools > Discovery > Autodiscover Viewer.
    2. In the Autodiscover Viewer window, click Use Autodiscover to get Auto Discover service URL.
    3. Uncheck the Default Windows Credentials check box. For User and Password, enter the impersonation service account's userPrincipalName (UPN) and password, and leave the Domain field empty.
    4. In the Mailbox SMTP field, enter the email address of a user to test.
    5. In order to simulate Calendar Connector behavior, choose Exchange2010_SP2 from the EWS Schema drop-down list.The Calendar Connector uses this EWS schema version regardless of the version of Exchange that it communicates with.
    6. Optionally, check the Enable SCP record lookup check box if your environment supports autodiscovery via LDAP. If it does not support LDAP lookup, have the Enable SCP record lookup check box deselected.  If you are not sure, test with the option checked and then with it unchecked.
    7. If your Expressway-C that runs the Calendar Connector uses a proxy to connect to the Cisco Collaboration Cloud, select Specify Proxy Settings and enter the server and port of your proxy.
    8. Click Run to run the test and check the results.
If there are errors in the run, check the EWSEditor log for more information. The default location is C:\Users\<username>\Documents\ewseditor.log.
  • In EWSEditor, test application impersonation and autodiscovery of a particular user email address:
    1. Open EWSEditor.exe from the location where the EWSEditor files were extracted.
    2. Choose File > NewExchangeService.
    3. In the Exchange Service Configuration window, click Autodiscover Email and enter the email address of a user to impersonate.
    4. In order to simulate Calendar Connector behavior, choose Exchange 2010_SP2 from the EWS Schema Version drop-down list. The Calendar Connector uses this EWS schema version regardless of the version of Exchange that it communicates with.
    5. Click Use the following credentials instead of the default Windows credentials. For User Name and Password, enter the impersonation service account's userPrincipalName (UPN) and password, and leave the Domain field empty.
    6. Check the Check if using EWS Impersonation check box. From the Id Type drop-down list, choose SmtpAddress.
    7. For Id, enter the same email address that you entered in the Autodiscover Email field (the user to impersonate).
    8. Click OK to run the test and check the results.

If the test finishes without errors, application impersonation and autodiscovery are working, and you are ready to configure the Calendar Connector on the Expressway-C node.

  • If you find configuration errors that you can't resolve, from the customer view in https://admin.webex.com, go to your username and click Feedback to open a ticket. Attach the EWSEditor log or generated HTML report along with a description of the issue in the ticket notes.


Using Microsoft Remote Connectivity Analyzer

As a Hybrid Calendar Service troubleshooting step, use the Microsoft Remote Connectivity Analyzer to test the connection to your Exchange Server deployment. The HTML report provides information about any potential connection issues.

Before You Begin

The EWSEditor tool provides tests which can more closely mimic the operation of the Calendar Connector, and does not require your Exchange Server to be publicly addressable from the internet.

  1. In your browser, go to https://testconnectivity.microsoft.com, and then select the Office 365 tab.
  2. Under Microsoft Exchange Web Services Connectivity Tests, choose Service Account Access (Developers), and then select Next.
  3. Follow these steps before you run the test:
    1. Enter an email address of a mailbox that you want to test.
    2. Enter your Microsoft service account credentials.
    3. Select Use Autodiscover to detect server settings.
    4. Select Test predefined folder, and choose Calendar from the drop-down.
    5. Check Use Exchange Impersonation and enter the email address of a user to impersonate. Choose SMTP Address from the Impersonated user identifier drop-down.
    6. Leave the Ignore Trust for SSL check box unchecked.
  4. Check the acknowledgment checkbox, enter the verification characters, and then select Verify.
  5. After you run the test, download the report in HTML format.
  6. If you encounter issues with configuration, from the customer view in https://admin.webex.com, go to your username, click Feedback to open a ticket, and then attach the generated HTML report along with a description of the issue in the ticket notes

Was this article helpful?

Related Articles

Recently Viewed