eG Help

This test emulates a user logging into an Exchange server and accessing a mailbox. In the process, the test reports the total duration of the simulation, time taken for the login, and the time taken for accessing the mailbox. Additionally, the test also captures failures (if any) at each step of the simulation. Using the real-time and detailed insights provided by this test, Exchange administrators can proactively detect logon slowness/failures and precisely pinpoint when the slowness/failure occurred - is it when accessing the web interface? during login authentication? or during mailbox access? This way, Exchange administrators are enabled to isolate the probable pain-points of the Exchange infrastructure, even before users complain.

Measurement	Description	Measurement Unit	Interpretation
Logon_availability	Indicates whether/not the simulator logged into the Exchange server successfully, when attempting to access this mailbox.	Percent	The value 100 for this measure indicates that logon was successful, and the value 0 indicates that logon failed. If this measure reports the value 0, then no other measures will be reported for that mailbox. You can also use the detailed diagnosis of this measure to view the output of the simulation script, scrutinize it, and isolate the failure and problem points of the Exchange infrastructure at first glance.
Logon_duration	Indicates the time taken by the simulator to login to the Exchange server (via the OWA interface or Office365 portal), when attempting to access this mailbox.	Secs	If the Total_duration for a mailbox exceeds its threshold, compare the value of this measure with that of the other duration values reported by the test to know where the bottleneck lies - in login? or mailbox access? or log out? If the comparison reveals a bottleneck at login, then use the detailed diagnosis of this measure to view the output of the simulation script. This will point you to the exact login step where the delay/failure occurred - was it when launching the chrome browser? was it because the login form took too long to open? or was it due to a delay in authentication?
App_launch_availability	Indicates whether/not this mailbox was successfully opened.	Percent	The value 100 for this measure indicates that the mailbox was successfully opened, and the value 0 indicates that access failed.
App_launch_duration	Indicates the time taken for this mailbox to open.	Secs	If the Total_duration for a mailbox exceeds its threshold, compare the value of this measure with that of the other duration values reported by the test to know where the bottleneck lies - in login? or mailbox access? or log out? If the comparison reveals a bottleneck at login, then use the detailed diagnosis of this measure to view the output of the simulation script. This will point you to the exact login step where the delay/failure occurred - was it when launching the chrome browser? was it because the login form took too long to open? or was it due to a delay in authentication?
Logoff_duration	Indicates the time taken by the simulator to log out of the OWA interface or Office 365 portal, while simulating a user access to this mailbox.	Secs	If the Total_duration for a mailbox exceeds its threshold, compare the value of this measure with that of the other duration values reported by the test to know where the bottleneck lies - in login? or mailbox access? or log out?
Total_duration	Indicates the total time taken by the simulator to simulate a user access to this mailbox.	Secs	An abnormally high value for this measure could indicate a logon slowness. In such a case, compare the value of all the duration values reported by the test to know where the bottleneck lies - in login authentication? application enumera in login? or mailbox access? or log out? If the comparison reveals a bottleneck at login, then use the detailed diagnosis of this measure to view the output of the simulation script. This will point you to the exact login step where the delay/failure occurred - was it when launching the chrome browser? was it because the login form took too long to open? or was it due to a delay in authentication?