• |
• |
1 |
Choose Control Panel > Administrative Tools > Active Directory Users and Computers. |
2 |
In the Active Directory Users and Computers window that appears, in the left pane, under the domain node, click Computers. |
4 |
In the Computer Management window that appears, choose System Tools > Local Users and Groups. |
• |
Using the Users node in the right pane, make an existing or a new user an Administrator. |
• |
Using the Groups node, add an existing user to the Administrators group. |
1 |
2 |
a |
b |
In the Component Services window that appears, navigate to Component Services > Computers > My Computer. |
c |
d |
e |
f |
In the Access Permission dialog box that appears, add the Distributed COM Users group to the list and grant it all permissions. |
g |
h |
i |
In the Launch and Activation Permissions dialog box that appears, add the Distributed COM Users group to the list and grant it all permissions |
j |
k |
l |
Close the Component Services window. |
1 |
On the monitored host machine, right-click My Computer, and navigate to Manage > Services and Applications > WMI Control. |
2 |
3 |
4 |
5 |
6 |
7 |
To add subsequent users, they only need to be added to the two groups, Distributed COM Users and Performance Monitor Users, since these groups are already granted the required permissions.
Access to WMI is required for both OS verification while creating an agent, and for collecting OS metrics from the monitored host. In some cases, an access violation on the WMI namespace (error 0x00000005) may occur when the agent connectivity verification fails. The access violation error can occur when the permissions or credentials used to access WMI, and specifically the root\cimv2 namespace and Root\MSCluster (if the machine is included in a cluster), are changed or invalid.
2 |
3 |
4 |
5 |
6 |
7 |
In the Security for ROOT\CIMV2 dialog box that appears, modify or assign permissions as necessary. |
8 |
Click OK on each of the dialog boxes to close them. |
9 |
If the machine is part of a cluster, repeat the procedure for the ROOT\MSCluster namespace. |
In some cases, when the agent queries WMI to collect metrics on the monitored host, the host’s performance may be affected. When this occurs, the agent log includes the message: Quota violation [SWbemServicesEx]. This error stems from WMI rather than the agent, and has been identified by Microsoft® as a known issue in Windows® Server 2003.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center