Chat now with support
Chat with Support

MessageStats 7.8.1 - Report Pack for Outlook Web Access (OWA) User Guide

OWA Report Descriptions

OWA Reports display successful and unsuccessful OWA logons. However, MessageStats can only report unsuccessful OWA logons that are detected by the Exchange CAS or Mailbox server.

If you use a component in your environment that performs authentication before logons reach the Exchange server, unsuccessful logons will not be reported. Internet Security and Acceleration (ISA) servers and the Forefront Threat Management Gateway are examples of such components.

The following table describes the reports found in MessageStats Report Pack for OWA:

 
Table 1. OWA User Logon reports.
Reports
Description
Filters

Logons by User Account

Lists the user accounts that performed OWA logons and shows the number of successful or unsuccessful logons performed.

Why unsuccessful logons may not be reported
•
Date
•
Detail Level
•
Display Options
•
Trend and Forecast Options
•
Logon Result
•
User Account
•
Organization

Logons by Mailbox

Lists the mailboxes that were accessed using OWA and the number of times they were accessed, successfully or unsuccessfully.

NOTE: The report will be empty unless the Exchange Mailboxes and the Mailbox Account Properties gathering tasks have run successfully. For more information, see the MessageStats Administrator’s Guide.

Why unsuccessful logons may not be reported
•
Date
•
Detail Level
•
Display Options
•
Trend and Forecast Options
•
Logon Result
•
Display Name
•
Organization

Logons by Source IP

Displays the IP addresses of hosts from which users performed OWA logons and the number of successful or unsuccessful logons performed.

Why unsuccessful logons may not be reported
•
Date
•
Detail Level
•
Display Options
•
Trend and Forecast Options
•
Logon Result
•
IP Address
•
Organization

Logons by Server

Lists the number of times users have logged onto their mailboxes using OWA during the time period specified in the report filter,.

Why unsuccessful logons may not be reported
•
Date
•
Detail Level
•
Display Options
•
Trend and Forecast Options
•
Logon Result
•
Server
•
Organization

Logons by Department

Lists the departments of mailboxes that were accessed using OWA and the number of times those mailboxes were accessed.

NOTE: The report will be empty unless the Exchange Mailboxes and the Mailbox Account Properties gathering tasks have run successfully. For more information, see the MessageStats Administrator’s Guide.

Why unsuccessful logons may not be reported
•
Date
•
Detail Level
•
Display Options
•
Trend and Forecast Options
•
Logon Result
•
Department
•
Organization

Logons by Virtual Directory/Web Site

Lists the virtual directories and web sites that handled OWA logons.

Why unsuccessful logons may not be reported
•
Date
•
Detail Level
•
Display Options
•
Trend and Forecast Options
•
Logon Result
•
Server
•
Web Site
•
Virtual Directory
•
Organization

Logons by Internet Browser and Version

Lists the names and versions of internet browsers that were used to perform OWA logons.

Why unsuccessful logons may not be reported
•
Date
•
Detail Level
•
Display Options
•
Trend and Forecast Options
•
Logon Result
•
Internet Browser
•
Internet Browser Version
•
Organization

Server Uptime

Identifies which Exchange servers and associated services were available and running on the network for a full day, and also identifies the ones that were not available. For each date, the report lists the specific server, and whether the server was available for the duration of that day.

By default, this report includes only Exchange servers that have been assigned the OWA server role.
•
Date
•
Server
•
Server Roles
•
Region
•
Organization

Why unsuccessful logons may not be reported

OWA Reports display successful and unsuccessful OWA logons. However, MessageStats can only report unsuccessful OWA logons that are detected by the CAS server.

If you use a component in your environment that performs authentication before logons reach the CAS server, unsuccessful logons will not be reported. Internet Security and Acceleration (ISA) servers and the Forefront Threat Management Gateway are examples of such components.

 

Types of Installations

•
Complete Installations
•
Custom Installations

Complete Installations

In a typical environment, all of the MessageStats components (or features) are installed on the same physical server using a complete installation. This type of installation is recommended for small enterprises.

Before installing the MessageStats Report Pack for OWA components, ensure that the review the minimum requirements and ensure they are met:

•
All MessageStats Report Pack for OWA minimum requirements are met. See System Requirements .
•
All the MessageStats Report Pack for OWA rights and permission requirements are granted to the appropriate accounts. See Rights and Permissions .
•
IIS logging is properly configured. See Configuring IIS Logging on the Exchange Server .
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating