Permissions required for Non-Admin user to monitor Microsoft Monitors
1) To enable WMI permissions for the non admin account follow the steps mentioned in the below link.
As an alternative to Steps 1-6 in the above link, we can perform it from the Active Directory Users and Computers.
- Open Server Manager in the remote server. Go to Tools -> Active Directory Users and Computers.
- In the opened window go to the Users folder and right click -> Properties of the newly created user.
- In the Member Of tab, add the groups give below.
- Distributed COM Users
- Performance Monitor Users
- Apply the settings.
Now continue from Step 7 in https://pitstop.manageengine.com/portal/en/kb/articles/configuring-non-admin-user-account-for-wmi-monitoring
Supported Monitors and WMI namespace used:
Monitor types | Namespace |
Active Directory | root\cimv2, root\MicrosoftActiveDirectory |
Biztalk Server | root\cimv2, root\microsoftbiztalkserver |
| Dynamics AX | root\cimv2 |
Dynamics CRM | root\cimv2 |
Exchange Server | root\cimv2 |
IIS Server | root\cimv2, root\WebAdministration |
| MSMQ | root\cimv2 |
SharePoint Server | root\cimv2 |
Skype for Business Server | root\cimv2 |
Network Policy Server | root\cimv2 |
2) To enable powershell remoting for the non admin user follow the steps given below:
- Open Powershell as administrator in the remote server and run the below command:
Set-PSSessionConfiguration -Name Microsoft.PowerShell -ShowSecurityDescriptorUI -Force - Click Add and select the new user to the list in the opened window.
- Select the required user and enable the Read and Execute permissions.
- Click OK to apply the change.
- Now follow the prerequisites mentioned in the link below:
https://www.manageengine.com/products/applications_manager/help/enabling-powershell.html - Verify by creating a remote session using the steps mentioned in the last section of above link.
Supported Monitors for Powershell mode:
Monitor types |
Active Directory |
Biztalk Server |
Exchange Server |
| MSMQ |
SharePoint Server |
Note: When a non-admin user is used in Powershell, there is a possibility that some of the data may not be available in the respective monitors.
New to ADSelfService Plus?
Related Articles
Setting WMI access through Active Directory and Group Policy Object for non-admin user
In our case, we run Active Directory on Windows 2008 R2 and we want to scan the target machine which is Windows 2012 R2 machine. Our domain is called “APMCLU” and we name our dedicated WMI user-account “wmiuser”. First – Setting done from Active ...Configuring non-admin user account for WMI monitoring
By default, Windows allows only members of the Administrators or Domain Admin groups to read WMI class information. However, you can configure a regular user to access WMI information by performing the following steps on the server that needs to be ...Self monitor Applications Manager using Real User Monitoring
We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Real User Monitoring Agent - Frequently asked questions
How to change Applications Manager details in RUM Agent? Open the AppServer.properties file located under <RUMAgent_Home>/conf/ directory in any text editor. Update Applications Manager hostname in apm.host key. Update Applications Manager SSL Port ...