Documentation forIpMonitor
Effective December 31, 2024, IpMonitor will reach its end of life and will no longer be available or supported. If you liked IpMonitor, consider trying another SolarWinds product.

Exchange Server 2007/2010 monitor

The Exchange Server 2007/2010 monitor opens a connection to a database server hosting Microsoft Exchange Server 2007 or Exchange Server 2010 and tests the performance of its subsystems to determine the server's overall health.

Administrators can use this monitor to:

  • Implement pre-configured performance counters provided by the Windows Management Instrumentation service to test multiple Exchange Server subsystems at once
  • Identify any performance degradation in critical Exchange Server components
  • Determine the exact point of failure
  • Take corrective action before email outages occur

WMI requirements

The Exchange Server monitor requires Windows Management Instrumentation (WMI) to be enabled. Also, the remote server must be accessible through an RPC connection to run the WMI queries.

Counters are tested in the order they appear. In the event of multiple counter failures, only the first counter error encountered will be reported.

The built-in internal sampling in Exchange Server monitor helps combat counter spikes. The monitor issues the WMI query five times, once every second, and then calculate an average based on the query results.

Troubleshoot WMI

  1. Verify that the RPC service is enabled and started on the remote system
    1. Log on to the target server as an administrator.
    2. Open Windows Services.
    3. Verify that the Remote Procedure Call (RPC) service is enabled and started.
  2. Verify that DCOM is enabled and configured correctly on the remote system.
    1. Log on to the target server as an administrator.

    2. Navigate to Start > Control Panel > Administrative Tools > Component Services.

      In the Control Panel, switch to Classic View to use this navigation path.

    3. Expand Component Services > Computers.
    4. Right-click My Computer and select Properties.
    5. Select the COM Security tab, and then click Edit Limits in the Access Permissions grouping.
    6. Ensure the user account you want to use to Monitor resources over WMI has Local Access and Remote Access, and then click OK.
    7. Click Edit Default, and then ensure the user account you want to use to Monitor resources over WMI has Local Access and Remote Access.
    8. Click OK.
    9. In the Launch and Activation Permissions grouping, click Edit Limits.
    10. Ensure the user account you want to use to monitor resources over WMI has Local Launch, Remote Launch, Local Activation, and Remote Activation enabled, and then click OK.
    11. Click Edit Default.
    12. Ensure the user account you want to use to monitor resources over WMI has Local Launch, Remote Launch, Local Activation, and Remote Activation enabled.
    13. Click OK.
  3. Verify WMI Security to ensure that the account used by the ipMonitor Credential can access the CIMV2 namespace.
    1. Log on to the targeted server as an administrator.

    2. Navigate to Start > Control Panel > Administrative Tools > Computer Management > Services and Applications.

      Switch to Classic View in the Control Panel to use this navigation path.

    3. Select WMI Control.
    4. Right-click WMI Control and select Properties.
    5. Select the Security tab, expand Root, and click CIMV2.
    6. Click Security and select the user account used to access this computer.
    7. Grant the following permissions:
      • Enable Account
      • Remote Enable
    8. Click Advanced and select the user account used to access this computer.
    9. Click Edit.
    10. In the Apply to field, select This namespace and subnamespaces and click OK.
    11. In Advanced Security Settings for CIMV2 window, click OK.
    12. In the Security for Root\CIMV2 window, click OK.
    13. In the Computer Management navigation pane, click Services.
    14. In the Services result pane, select Windows Management Instrumentation, and then click Restart.

  4. If you are monitoring a target in a workgroup, disable remote User Account Control (UAC).

    This action is not recommended, but it is necessary when monitoring a workgroup computer. Disabling remote user account control does not disable local user account control functionality.

  5. Edit the registry.

    The following procedure requires the modification or creation of a registry key. Changing the registry can have adverse effects on your computer and may result in an unbootable system. Consider backing up your registry before making these changes.

    1. Log on to the computer you want to monitor with an administrator account.
    2. Click Start > Accessories > Command Prompt.
    3. Enter regedit.

    4. Expand the following registry key:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\

    5. Locate or create a DWORD entry named LocalAccountTokenFilterPolicy and provide a DWORD value of 1.

      To re-enable remote UAC, change this value to 0.

  6. If the target computer has Windows Firewall enabled, add a Remote WMI exception to allow remote WMI traffic through. See Connecting to WMI Remotely with VBScript on the Microsoft website located at http://www.microsoft.com for details.
    1. Click Start > Run.
    2. Execute the following command, and press Enter:
      cmdclick

    3. At the command prompt, type the following command, and press Enter: 

      netsh firewall set service RemoteAdmin enable

    4. At the command prompt, type exit and press ENTER.