KS-Soft wrote:PowerUser operator should have enough rights to check list of services.
For other tests you need administrator rights (e.g. CPU Usage, Process tests).
Its better to specify admin account for HostMonitor service and use such account for test items (you may specify one default account or several accounts using Connection Manager).
Adding the service account to the remote machines local Power Users group was not successful for the service tests.
This means RCC has access to target system.I am using the RCC GUI for all my changes
HostMonitor does not.
Are you running RCC and HostMonitor on different systems?
I am running RCC on the same system as Host Monitor.
I assume HostMonitor cannot perform some other tests, like Process test, CPU Usage test?
Could you check security event log on target system?
Correct, the other tests will not work. When I refresh a test, the target system generates a security success logon and a success logoff.
To me it seems like if the Host Monitor account isnt in the local admin group, nothing but ping tests will work.
Regards
Alex
Service Tests cannot retireve list of services
HostMonitor service should be started under local admin account. If UAC is enabled then built-in administrator account should be used.
If HostMonitor is running on Windows 2000-2003, its better to specify this admin account using HostMonitor Options dialog and keep "local system" account for settings specified by Windows Services applet.
If HostMonitor is running on Windows 7/8/2008, then its better to specify admin account using Windows Services applet.
At the same time for remote connections (established when HostMonitor starts test probes) you should be able to use different accounts: e.g.
- domain admin accounts for tests like CPU usage, Process
- power user account for service tests
These accounts should be specified using Connection Manager or "Connect as" test property.
Is this how HostMonitor configured on your system?
Regards
Alex
If HostMonitor is running on Windows 2000-2003, its better to specify this admin account using HostMonitor Options dialog and keep "local system" account for settings specified by Windows Services applet.
If HostMonitor is running on Windows 7/8/2008, then its better to specify admin account using Windows Services applet.
At the same time for remote connections (established when HostMonitor starts test probes) you should be able to use different accounts: e.g.
- domain admin accounts for tests like CPU usage, Process
- power user account for service tests
These accounts should be specified using Connection Manager or "Connect as" test property.
Is this how HostMonitor configured on your system?
Regards
Alex