Best practise running HostMonitor as a service

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
JuergenF
Posts: 331
Joined: Sun Jan 26, 2003 6:00 pm
Location: Germany, North Rhine-Westphalia

Best practise running HostMonitor as a service

Post by JuergenF »

I'm nearly desperate :cry:
Whatever I tried, something doesn't work at all.

What is the best practise running HostMonitor as a service and testing services on remote machines.
HostMonitor running in Domain A on W2K Server, machines in the same, in other domains and in workgroups must be tested (W2K and NT4).

What I've found in the help and newsgroup is (from my pov):
- Start the HostMonitor service with the "Local system account". OK !
- In "option" "service tab" log on as "loacl system account", "local admin" or "domain admin", what is better ?
- I think use "connect as" in the test itself only when needed. Tests are much quicker without a special login for a test. Is that OK ?
- When using "connect as" in the test itself. What's better using local admin on the to-test machine or the domain admin ?
- How to specify the local admin. Only "administrator" or "server\administrator" ?

Thanks a lot

Juergen
Top
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:
Contact KS-Soft

Post by KS-Soft »

HostMonitor running in Domain A on W2K Server, machines in the same, in other domains and in workgroups must be tested (W2K and NT4).
If you need to check systems in another domain, I would recommend to use RMA installed on that domain.
- In "option" "service tab" log on as "loacl system account", "local admin" or "domain admin", what is better ?
If you need to perform tests such as CPU Usage, Service, Process, Performance Counter and NT Event Log, "local system account is not acceptable.
What's better using local admin on the to-test machine or the domain admin ?
"local admin" or "domain admin"? It depends. I will say domain admin THAT HAS necessary rights. I mean domain account that included into "local admin" groups on each monitored system.
- I think use "connect as" in the test itself only when needed. Tests are much quicker without a special login for a test. Is that OK ?
I think its Ok but truth to say I don't understand why some systems needs a lot of time to establish connection that already established...
How to specify the local admin. Only "administrator" or "server\administrator" ?
According to Microsoft documentation, it doesn't matter. In both cases local account database will be used.

Regards
Alex
Top
Post Reply

Return to “Configuration, Maintenance, Troubleshooting”