Exchange 2010-2013 OWA Form Login (PowerShell)

This template assesses the availability of the Outlook Web Access service for users by performing a user login procedure and returns the length of time it takes to log in.
Note: This template is used for internal OWA. PowerShell is a requirement.

Monitored Components:

Exchange 2010-2013 OWA Form Login Monitor
Performs a user login procedure and returns the length of time it takes to log in.

Last updated 6/27/2014

  • Hi,

    I am trying to use the script to monitor our exchange 2010 OWA login, but I am getting the following error message when running it.

    "Cookies are currently disabled by your browser settings. To access this Web site, cookies must be enabled."

    I have checked and the site address is in the trusted sites for the user running the script.

    Has anyone else seen this issue?

    Thanks

    Rob

  • I'm having an issue using this script to monitor OWA on our Exchange 2013 CU9 servers that I believe is caused by the script failing to log out or close the connection. I can test this script against a single node several times in a row and get different results. I've seen "Login succeeded" as well as "Login Failed" but most of the time I will get "Connection failed to url (https://10.1.1.1/owa/auth.owa). The remote server returned an error: (500) Internal Server Error." When I start getting the 500 errors with the PowerShell script if I attempt to log into OWA manually I get an error that says "There are too many active sessions connected to this mailbox. Please close other open instances and try to sign in again after a few minutes..."  This makes me think the PowerShell script is not logging out and closing the connection to OWA causing this problem.