WMI Permissions and Security
When monitoring CPU information on a Windows based machine with DBTuna, either the OS Agent part of the Database Agent, or the DBTuna/Server agent, Windows Management Instrumentation WMI is used to remotely gather the metrics. WMI is often frustrating to troubleshoot, therefore this article explains some potential problems and pitfalls.
The minimum requirements for DBTuna when using WMI
WMI makes use of RPC. RPC listens on a well-known port (135) but then allocates a dynamic port for subsequent communication. Therefore you need to configure your Firewall to allow 135 (always) and follow the dynamic RPC ports. It can be done - you don’t need to restrict the port range, and there are several articles already on the internet that explain this, just ask Google!
To delegate permissions for WMI Control, run wmimgmt.msc . If you don't have a shortcut to the program, then simple click the Start Menu, and then search for the executable.
Now step through the following instructions to confirm you will have the correct permissions:
1. Right click on the WMI Control icon on the left and select properties.
2. Select the Security Tab
3. Select the Root node of the tree, and click Properties
4. For the named user account you would like to run DBTuna as you will need to ensure that it has the relevant permissions. The minimum permissions that your remote Windows account needs for DBTuna are:
- Execute Methods
- Enable Account
- Remote Enable
If you miss any one of the three then you end up with one of:
Error=800706BA The RPC server is unavailable. SWbemLocator
or
Error=80070005 Access is denied. SWbemLocator
REQUEST A DEMO
START A FREE TRIAL