process test on a remote system

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
gdvl
Posts: 103
Joined: Thu Apr 04, 2002 6:00 pm
Location: Belgium
Contact:

process test on a remote system

Post by gdvl »

I 've a problem with a process test on a remote system.
I know about the requirments for security and remote registry service. Let me explain my problem:

- HM box (win XP, HM 5.92) is logged on with user 'A'. (not as a service)
- user 'A' has no access on remote system (server 2003)
- process test is run under user 'B' on HM box
- user 'B' is admin on remote system.
=> test fails (and process list could not be build)

I made user 'A' temporarly admin on remote system and restart "remote registry service".
=> test is successfull

I remove user 'A' from the admin group on remote system
=> test succesfull (also after logoff and logon of HM box)

I restart "remote registry service"
=> test fails

I'm sure there are no other HM tests which use other credentials on the remote system.

I seems the logged on user on the HM box needs access on the remote system, instead of the used credentials for the process test.

I hope this is enough info ?

Regards,
Gert
KS-Soft Europe
Posts: 2832
Joined: Tue May 16, 2006 4:41 am
Contact:

Re: process test on a remote system

Post by KS-Soft Europe »

gdvl wrote:I seems the logged on user on the HM box needs access on the remote system, instead of the used credentials for the process test.
When HostMonitor is trying to perform Process test, at first it tries to use credentials of user specified in "Connect as" box. If attempt fails, it use credentials of logged in user in case HM is running as application and credentials of user specified in Options > Service tab in case of service.
Could you check Security Event Log on 2003 box to resolve, why user you have specified in "Connect as" box, was not able to login?

It is a simple explanation because HostMonitor uses Connection Manager also, if appropriate record is specified.

Regards,
Max
Post Reply