Troubleshooting performance counter access

Owned by Kiss, Mate
May 24, 2022
2 min read

Performance counter access troubleshooting tips

Sometimes SCOM cannot access the custom performance counters generated by 3rd party applications. In order to sort this issue please check the following.

Collector service privileges and conectivity

Make sure that the collector service has Local Administrator privilege on the host where it wants to access to the performance counters. The TCP port 135 and 445 is has to be open.

Local services

Start the following services, and set the startup type to Automatic for the

  • Remote Procedure Call (RPC)
  • Remote Registry
services, and set at least Manual for the

  • WMI Performance Adapter

  • Performance Counter DLL Host

  • Performance Logs and Alerts

  • Remote Procedure Call (RPC) Locator

services.

Local Service privileges

If the issue still present, please do the following:

Step 1 - Open a regedit and navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Window NT\CurrentVersion\Perflib

Step 2 - Right click on Perflib key and select permissions

Step 3 - Click Add and add Local Service with full control

Step 4 - Save and exit

Step 5 - Restart the Remote Registry Service

Rebuilding Perfmon Performance Counters

If the steps above didn't help and you still can't see the performance counters in SCOM, you have to rebuild the performance counters and restart the server. Open an administrator command prompt and enter the following commands:

cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R
WINMGMT.EXE /RESYNCPERF

After this, restart the server. Don't forget to start the services specified above.

Accessing performance counters on Windows Server 2008 R2

Windows Server 2012 can only manage Windows Server 2012 and Hyper-V Server 2012 servers by default. For the other servers, the Windows Managemement Framework have to be installed. In order to access the performance counters on these servers please follow these steps:

Step 1 - Download and Install the Windows Management Framework 3.0 for Windows Server 2008 SP2 and Windows Server 2008 R2 SP1. The .Net Framework 4 is a prerequisite for this.

Step 2 - Install this hotfix: http://support.microsoft.com/kb/2682011

Step 3 - Execute the following PowerShell commands as administrator:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
Configure-SMRemoting.ps1 -force -enable