Before You Begin
For accurate results, run these tests from a machine that is on the same subnet as the connector Expressway-C node.
The EWSEditor runs on Microsoft Windows and requires .NET Framework 4.5.1
The Microsoft Remote Connectivity Analyzer runs in a web browser and requires your Microsoft Exchange server to be publicly accessible from the internet. Its HTML report provides information about any potential connection issues, but its testing does not simulate the connector operation as the EWSEditor does.
|1 || Download EWSEditor.|
|2 || In EWSEditor, test application impersonation and autodiscovery of a particular user email address:|
- Open EWSEditor.exe.
- Choose .
- In the Exchange Service Configuration window, click Autodiscover Email and enter the email address of a user to impersonate.
- From the EWS Schema Version drop-down list, choose Exchange2010_SP2.
- 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.
- Check the Check if using EWS Impersonation check box. From the Id Type drop-down list, choose SmtpAddress. For Id, enter the same email address that you entered in the Autodiscover Email field (the user to impersonate).
- 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.
|3 || To verify that the Calendar Connector will have access to the attributes it needs to serve users, do the following substeps: |
- In EWSEditor, choose .
- In the Autodiscover Viewer window, click Use Autodiscover to get AutoDiscover service URL.
- 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.
- In the Mailbox SMTP field, enter the email address of a user to test.
- From the EWS Schema drop-down list, choose Exchange2010_SP2.
- Check the Enable SCP record lookup check box if it is not already checked.
- Click Run to run the test and check the results.
If the test finishes without errors, the Calendar Connector should have the access that it needs. If there are errors, check the EWSEditor log for more information. (The default location is C:\Users\<username>\Documents\ewseditor.log.)
|4 || If you are unable to test with EWSEditor, use the Microsoft Remote Connectivity Analyzer:|
- In your browser, go to https://testconnectivity.microsoft.com, and then select the Office 365 tab.
- Under Microsoft Exchange Web Services Connectivity Tests, choose Service Account Access (Developers), and then select Next.
- Enter an email address of a mailbox that you want to test.
- Enter your Microsoft service account credentials.
- Select Use Autodiscover to detect server settings.
- Select Test predefined folder, and choose Calendar from the drop-down list.
Do not change the Exchange impersonation and SSL settings.
- Run the test.
- Check the acknowledgment check box, enter the verification characters, and then select Verify.
|5 || If you find configuration errors that you can't resolve, from the customer view in https://admin.ciscospark.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.|
Copyright © 2017, Cisco Systems, Inc. All rights reserved.