Introducing AppInsight for Exchange - Server & Application Monitor 6.1 Beta 2 Sneak Peek

Discover

As with AppInsight for SQL, monitoring your Exchange Mailbox Servers with SAM is a fairly simple, straightforward affair. For existing nodes currently managed via WMI simply click List Resources from the Node Details view and select Microsoft Exchange Server directly beneath AppInsight Applications. The same is also true for any new Exchange servers added individually to SAM and managed via WMI using the Add Node Wizard.

Exchange Servers can be added both individually using the methods above, or en masse using the Network Sonar Discovery Wizard. Both one-time and scheduled re-occurring discovery of Exchange servers in the environment using Network Sonar are fully supported. Either method will allow you to begin monitoring your entire Exchange environment in record time.

Please note that AppInsight for Exchange has been designed exclusively for Microsoft Exchange 2010 and Exchange 2013 Mailbox Role servers. This option will not appear for nodes running previous versions of Exchange or servers running other Exchange roles, such as the Client Access role.

Configure

AppInsight for Exchange uses PowerShell to collect virtually all information from the Exchange server. As such, PowerShell 2.0 must be installed on the local Orion server or Additional Poller that the node is assigned to. PowerShell 2.0 must also be installed on the Exchange Server being monitored. Windows 2008 R2 includes PowerShell 2.0 by default. If you're already running Orion on Windows 2008 R2 or greater and plan to monitor Exchange running on a Windows 2008 R2 server, you needn't worry about the PowerShell 2.0 requirement. Microsoft has taken care of that for you.

Beyond simply having PowerShell installed, Windows Remote Management (WinRM) must also be configured. Both locally on the Orion server, and on the remotely monitored Exchange Server. Fear not though; we've made this process incredibly simple and completely painless.

After discovering the Exchange mailbox servers running in your environment and choosing to monitor them, you may find them listed in the All Applications tree resource on the SAM Summary view in an "Unknown" state. This is likely due to WinRM having not been configured on either the local Orion server or the remotely monitored Exchange mailbox server. Clicking on the AppInsight for Exchange application that is in an "Unknown" state from the All Applications resource launches the AppInsight for Exchange configuration wizard.

The AppInsight for Exchange configuration wizard will prompt you for credentials to configure and monitor the remote host. By default, credentials used to manage the node via WMI are selected. However, under some circumstances, such as using the local administrator account to manage the node, these permissions may not be adequate for monitoring Exchange. If that is the case, you can select from the list of credentials available from your Credential Library, or enter new credentials for AppInsight for Exchange to use. The account used for AppInsight for Exchange should have Exchange Admin Role permissions.

Once you've selected existing, or defined new credentials for AppInsight for Exchange to use, simply click "Configure Server". The configuration wizard will do the rest. It should only take a minute or two and you'll be up and monitoring your Exchange mailbox server. Easy peasy, and no agent required.

So what exactly is this magic "Configure Server" button doing anyway? Well nothing that couldn't be done manually with a bit of effort. Quite simply the "Configure Server" button pushes a self signed certificate to the Exchange Server and configures WinRM to function in a secure encrypted fashion between the two hosts. Steps for manually configuring your Exchange Server, as well as creating a least privilege user account for monitoring your Exchange mailbox servers using AppInsight for Exchange will be available in the SAM Administrators Guide once SAM 6.1 is officially released.

Monitor

An Exchange environment is typically comprised of multiple Mailbox Databases. Much like SQL databases, each mailbox database has its own independent status that tells the administrator how that database is currently being used (or not used in the case of databases that are "Dismounted"), as well as the health of that database. In the Mailbox Database Status resource, located on the Application Details view we see all of the databases running on this Exchange server. All but one is in a "mounted" state, but the SAMDB03 database does not appear to be running on its "preferred" server, as designated by its Activation Preference. For smaller environments where two or more Exchange Servers running in a DAG (Database Availability Group) are sitting next to each other, this might not be an issue. For larger distributed environments, losing track of where your mailbox databases are running can lead to end users complaining about email performance problems or worse. For example, If your office was headquartered in Boston, but have a DR facility in your satellite office in Shanghai, the last thing you want is all the traffic from the users in the Boston office traversing the WAN to access their mailboxes from the Shanghai server.

The Replication Status Checks resource, also on the Application Details view, checks all aspects of replication and replay status to provide a complete overview of the mailbox server in the Database Availability Group (DAG). This allows you to proactively monitor continuous replication, the availability of the Active Manager, and the health and status of the underlying cluster service, quorum and network components, to name a few.

In the event of a replication status check failure you will be notified both visually through the UI, as well as through your normal alerting mechanisms. Clicking on the "More" link for any failed Replication Status Check displays the full details of that failure.

Each mailbox database on your Exchange server is a time bomb ticking down until ultimately it runs out of space. Be it from mailbox database limits imposed by the Standard Edition of Exchange, NTFS file size limitations, or simply running out of free space on the volume where the mailbox database is stored, it's only a matter of time before the mailbox database hits the wall. When that time comes, it's certain to negatively impact any and all users whose mailboxes reside on that mailbox server.

To stay ahead of the game it's imperative that you have a good understanding of how your mailbox database size relates to these limitations. This will allow you to be proactive in your approach to managing your mailbox databases, and the individual mailboxes that reside within.

Alerting

This is precisely the kind of information that the Mailbox  Database Size and Space Use resource provides. Not only does this resource list all mailbox databases managed by the mailbox server, their current size on disk, and the amount of white space remaining within the database, but the linear gauge also shows the percentage of the mailbox databases usage as it relates to such things as remaining free space on the volume, and file size limits imposed by Exchange edition/version or the NTFS file system. This information is then available for reporting, trending, and of course, out of the box alerts so you can be notified proactively and avoid such crisis altogether.

This was just a tiny glimpse into a few of the powerful new capabilities included with AppInsight for Exchange. If you'd like to try it out for yourself, don't hesitate! Sign-up here to download SAM 6.1 Beta 2 today. You need only own an existing license of SolarWinds Server & Application Monitor, and be under active maintenance to participate.

Your feedback (both positive or negative) is what we thrive upon. It serves either as confirmation that we're on the right track, or that adjustments and improvements need to be made. Either way, it's what helps us to build great software.