This is part 2 of a multi-part blog series looking at Lync Server 2010 reporting using Quest MessageStats
Disclaimer: I do not work for Quest Software, nor do I recommend using Quest MessageStats to report against Microsoft Lync Server 2010
Before we having a look at installing and configuring Quest MessageStats for reporting Lync Server let have a quick overview of Quest MessageStats and how it gathers from different systems to report against them.
Out of the box Quest MessageStats will report against a Microsoft Exchange environments and there are lots and lots of great reporting to be able to capacity plan and have a good idea of how your Exchange environment is being used right down to a per user level, but I’m not going to cover this here.
It is important to note that Quest MessageStats is a reporting solution and isn’t a monitoring solution like System Center Operations Manager (SCOM).
Outside of Exchange Server Reporting, there are a number of report pack to report against other systems:
- Outlook Web Access/App (OWA)
- Windows Mobile
- Lotus Notes (does anyone still use that?)
- Archive Manager
- Microsoft Online
At a basic level Quest MessageStats: Gathers -> Stores -> Reports
However there are couple components:
- MessageStats Console: MMC console for Administration and Configuration
- MessageStats Scheduler service: In a distributed gathering model, the MessageStats Scheduler Service coordinates all the gathering servers (Task Execution Servers)
- Task Execution Server: A server on which you install the task processors is called a Task Execution Server.
- MessageStats Database: A SQL Server repository in which the gathered data is stored, available for report queries. (there is only one database per MessageStats environment)
- Report Console: A web-based interface that allows you to view and analyse reports using the gathered data that exists in the MessageStats database. (Hosted on IIS)
In a small environment everything run can run on one server but in a larger environments, the component would be separated for performance reasons.
Here is generally what the architecture looks like this, specific to OCS/Lync:
See you soon for Part 3 of the multi-part blog series looking at Lync Server 2010 reporting using Quest MessageStats.