AppInsight for Exchange requirements and permissions
AppInsight for Exchange works only with the Mailbox Role, which is used for data storage. All other Exchange servers running different roles should use the Exchange application monitor templates included with SAM if you intend to monitor them. Data is collected at the same default five-minute polling interval as traditional application monitor templates.
Supported Microsoft Exchange Server versions
- Microsoft Exchange Server 2010
- Microsoft Exchange Server 2013
- Microsoft Exchange Server 2016
- Microsoft Exchange Server 2019
Exchange hybrid versions are not supported.
To gain insight into metrics, services and Database Availability Group (DAG) status for Microsoft Exchange Server 2013 and 2016, see Monitor your Microsoft Exchange Server with a free tool, Exchange Monitor in the SolarWinds online IT community, THWACK.
AppInsight for Exchange permissions
The following permissions are required to modify Exchange and WinRM settings on the server, as well as poll performance counters:
- Local administrator permissions are needed for automatic configuration, but are not needed for monitoring after configuration is complete.
- To provide organization-wide capability, the service account (Domain User) must be a member of the View-Only Organization Management group. Membership to this group gives the user object read-only access to the entire Exchange environment, without providing any domain or local access on the Exchange server. It also prevents unauthorized access to the account.
- To gather information, the user object must be assigned the Mailbox Search management role within Exchange. The account must be a member of the Local Administrators group.
Note: Users without this role can access Exchange, but the additional level of permission is required modify Exchange and WinRM settings on the server, or poll performance counters.
- For Mailbox statistics, Hub Transport Servers need to be accessed via RPC.
- PowerShell 2.0 or later must be installed. See Use PowerShell in SAM.
- Permissions must be granted for PowerShell to be accessed. See Set PowerShell permissions for Exchange.
Common configuration issues