User permissions for Windows Performance Counters over RPC in SAM

12/20/2018 1:07 AM

12/20/2018 1:07 AM

This article discusses user permission requirements for Windows Performance Counters over RPC. RPC is one of the available fetching methods available to Window Performance Counter component monitors within Server & Application Monitor (SAM). Description of available fetching methods are available here: Configure Performance Counter monitor fetching method order for SAM.

Note: Starting in SAM 2020.2, WinRM is the default transport method used to collect data for WMI-based component monitors (for example, Performance Counter Monitors) to gather data from target nodes for SAM templates and application monitors. A fallback mechanism automatically switches to legacy RPC/DCOM polling, if necessary. 

For the latest information about SAM application monitor polling, see:

• Use WinRM for application monitor polling in SAM
• SAM component monitors
• Choose a fetching method for Performance Counter Monitors in SAM

Server Application Monitor

To monitor Windows Performance Counters over RPC, the user account must either be a member of the Administrators group or a member of the Performance Monitor Users group in Windows.



Monitoring processes via RPC uses the same permissions as listed in the screenshot above. However, Windows services via RPC require Administrative permissions. You will need to define permissions on a per-service level using the sc sdset command (© 2018 Stack Exchange Inc, available at https://stackoverflow.com, obtained on December 19, 2018).

Screenshots property of © 2018 Microsoft

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.