Using ews_response probe - helpful notes

Document ID : KB000034282
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction: 

Using ews_response probe - helpful notes

Background:  

Notes on configuring the ews_response probe instead of using exchange_response.

Environment:  

ews_response probe GA in CA UIM version 7.6 or later 

Instructions: 

The ews_response probe can run remotely and does not have to be installed on the exchange server itself. But you have to provide the IP address of the system where Exchange server resides when configuring.

Outlook is not required on the server running the probe.

Other Requirements:

Platform: Windows NT/2K/XP/2K3, Windows 64 bit, Linux, Solaris
Software: Nimsoft java_jre package deployed where the probe is installed.

The probe tests Exchange Server mail response by sending mail messages and reading a mailbox. This version is based on exchange webservice APIs available with only Microsoft Exchange 2007 SP1, 2010 and 2010 SP1 versions.

Please first refer to the Help at:

http://docs.nimsoft.com/prodhelp/en_US/Probes/Catalog/ews_response/1.0/index.htm

For any 'unauthorized' error messages, please check that no local or remote firewalls are in the way.

e.g., Jul 30 13:57:38:348 [XY-NimExchXXXX-ABC-XXXX-test, ews_response] Trying to login to exchange at https://xxxxx-exch2k7-1.computer.com/ews/Exchange.asmx, username=NimXXXXXXXX-XXX, server=xxxxx-exch2k7-1.computerBlah.com, client=20071

And make sure domain name of Exchange server is valid - e.g., try with the full AD Domain name in place of domain name. For example on one case, the AD Domain was exchange2k7.com but we configured the probe as exchange2k7\username and got the same error, but when we configured as exchange2k7.com\username the probe worked fine.)

For round-trip QoS:

This can be monitored/collected using options below:

- Send to a non-existing user on a mail server that will issue an 'Unknown user' return mail.
- Send to another test user whose mailbox is being monitored by another instance of this probe, and “Bounce Nimsoft Test mail from other sources back to sender” is Checked for that Instance as shown below snapshot.
- Send to a user where auto reply or auto forward rule is applied.

If the user to whom the mails are sent is not configured to be a monitored user in the probe the bounced mails will not be received automatically. The Exchange server should be configured for Auto Reply/Auto Forward.

Eg. If mails are sent from ABC to DEF then mails should also be sent from DEF to ABC and both should be separate users in the probe and the bounce back functionality should also be checked.

- Send to a non-existing user on a mail server that will issue an 'Unknown user' return mail.

***In this case the round-trip time will be calculated between the time the user sends the mail and the exchange server sends the Undeliverable mail back.

- Send to another test user whose mailbox is being monitored by another instance of this probe, and “Bounce Nimsoft Test mail from other sources back to sender” is checked.

***In this case if mails are send from A to B then A and B should both be configured as separate Users in the probe (one user will be A having B as profile and another user will be B having A as profile). The bounce back functionality should be checked.

- Send to a user where auto reply or auto forward rule is applied.

***In this case if A is sending mail to B and B is not a monitored user in the probe then the Outlook of B should be manually configured to send Auto Reply/Auto Forward to calculate roundtrip time.

Other Notes:

a) As per current functionality the email round-trip QOS is calculated in seconds. If round trip time is less than 1000 millisecond then the probe displays it as 0 seconds.

b) The user would be able to get the QOS data for roundtrip response if he sends a mail to a non-existent user, and the bounce back functionality option is selected in the 'Setup' Tab.

Once you set the probe up to send test mail to a non-existent user on the clients exchange server you should see the round trip QoS response.