Problem on Windows CPU monitoring
edmundlai
Dear All,
We have purchased the version of 8.2.
In the version 8.2, we face a problem would like to get help/advise from yours.
When we setup the "Windows Based Checks" rule for monitoring Windows platforms (we found the same case for monitoring Windows 2003 / 2000 server and Windows XP Pro OS) and run the "Testing Settings", it works fine for MEMORY and DRIVESPACE monitoring but fail for CPU monitoring. I tested for many many times for CPU monitoring and get the same error returned "Access is denied".
I am sure that the User credential setting is correct. I have assigned the user account for monitoring with administration rights and login format is correct. I tested the following login format but all failed the "Testing Settings".
- windomainadmin_account
- [email protected]
- servernameadmin_account (local user account with administration rights)
I clicked the "SUGGEST ERROR SOLUTION" and follow the suggestion to check the tool "DCOMCNFG" and registry key of "Enable DCOM", all settings are correct.
On the Security Event log of Windows server side, I found that the User Name for authentication is "ANONYMOUS LOGON". I think it is the root cause of the problem.
It make me confuse that same User credential setting working for MEMORY and DISKSPACE monitoring but fail for CPU.
I have searched through the forum and tried the solving methods mentioned on it but no luck, please kindly advise how to solve the problem.
Many Thanks!
Regards,
Edmund
We have purchased the version of 8.2.
In the version 8.2, we face a problem would like to get help/advise from yours.
When we setup the "Windows Based Checks" rule for monitoring Windows platforms (we found the same case for monitoring Windows 2003 / 2000 server and Windows XP Pro OS) and run the "Testing Settings", it works fine for MEMORY and DRIVESPACE monitoring but fail for CPU monitoring. I tested for many many times for CPU monitoring and get the same error returned "Access is denied".
I am sure that the User credential setting is correct. I have assigned the user account for monitoring with administration rights and login format is correct. I tested the following login format but all failed the "Testing Settings".
- windomainadmin_account
- [email protected]
- servernameadmin_account (local user account with administration rights)
I clicked the "SUGGEST ERROR SOLUTION" and follow the suggestion to check the tool "DCOMCNFG" and registry key of "Enable DCOM", all settings are correct.
On the Security Event log of Windows server side, I found that the User Name for authentication is "ANONYMOUS LOGON". I think it is the root cause of the problem.
It make me confuse that same User credential setting working for MEMORY and DISKSPACE monitoring but fail for CPU.
I have searched through the forum and tried the solving methods mentioned on it but no luck, please kindly advise how to solve the problem.
Many Thanks!
Regards,
Edmund
This discussion has been closed.
Comments
1) Make sure the Monitoring Service AND Web Server Service are running under a Windows ADMIN account (not user account)
2) Make sure the account has LOCAL admin rights on the remote system
Create a WINDOWSHEALTH check (which combines CPU, Memory and disk space) and try again
Thank You for the hint, after I changed the Monitoring Service AND Web Server Service are running under a Windows Domain account with administrator rights, all works fine now. The remote system are Domain member servers.
Conclusion:
It require Windows Domain account with admin rights to start the ServersCheck services for monitoring CPU rule.
If no need to monitor CPU rule, then local account with admin rights is enough.
Regards,
Edmund