Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > ipMonitor service context does not have the necessary privileges to impersonate

ipMonitor service context does not have the necessary privileges to impersonate

Updated October 9, 2018

Overview

The ipMonitor 9 service context does not have the necessary privileges to impersonate.

Environment

ipMonitor 9 

Cause

These errors occur when the Microsoft Windows account assigned to the ipMonitorSrv service is not allowed to impersonate the Windows account used by the credential assigned to one of the monitors.

Details

Check the Windows account

  1. Verify that the Windows Account assigned to the ipMonitorSrv service is not the same Windows Account assigned to the Credential being used by the Monitor. This would be considered double impersonation.
  2. Verify that the Windows Account assigned to the ipMonitorSrv service is listed within the following user assignments under Local Policies:
    • Bypass traverse checking
    • Log on as a service
    • Replace a process level token

Verify that the Windows account is listed within the designated user assignments

  1. Log in to the server hosting ipMonitor.
  2. Navigate to your ipMonitor directory.
  3. Run the iponitor configuration utility by double-clicking:
    ipm9config.exe
  4. Click Service Settings.
  5. Note the selected account.
  6. On the server, navigate to Control Panel > Administrative Tools > Local Security Policy.
  7. Open Local Policies and click User Rights Assignment.
  8. Double-click the above-mentioned policies and add the account noted on step 5.
  9. After the account is added to all policies, right-click Security Settings and select Reload.
  10. Restart the ipMonitorSrv service.
  11. Log back in and see if the Exchange server Monitor is still failing.
     
Last modified

Tags

Classifications

Public