Check Process fails after adding remote machine to doamin

[bkeadle]

related to this thread

http://www.ks-soft.net/cgi-bin/phpBB/vi ... fe636a1c90

I added a machine to the domain, and now the Process test is failing. I'm unable to connect with any credentials in the test properties (HOSTNAME\Username or DOMAIN\Username - both are local administrators), even though I can connect to the machine with those credentials with a net use command. I've specified registry permissions to the perflib key as noted in the above close thread.

I suspect adding my HostMon machine to the domain might fix it, but what if that's not an option? It would indeed appear that the Connect As facility of the test is not working as intended.

[KS-Soft]

related to this thread
http://www.ks-soft.net/cgi-bin/phpBB/vi ... fe636a1c90

I don't think 10 years old topic can be related
Windows 2012 does not work exactly like Windows 2000 and HostMonitor version 9 works very different from version 3.
Unless... what Windows do you use on HostMonitor and target system?
UAC enabled?
HostMonitor version?
HostMonitor started as application? service? what account do you use to run HostMonitor?

What exactly is your configuration? HostMonitor installed on HostA in domainB checks target host systemC located in domainB? domainD? not located in any domain?
or may be HostMonitor checks target systemC using Remote Monitoring Agent installed on systemE?

I added a machine to the domain, and now the Process test is failing.

What exactly machine? HostMonitor system? Target system (system specified for this Process test)? Some other machine?
"Failing" means "test status Unknown, test Reply empty"?
Could you try to setup CPU Usage test for the same target system? Status? Reply?

I suspect adding my HostMon machine to the domain might fix it, but what if that's not an option? It would indeed appear that the Connect As facility of the test is not working as intended.

Please check security event log on target system.

Regards
Alex

[bkeadle]

Hostmonitor is running on WinXP, as an application, with local account "Hostmon", member of Administrator's group. Target is a Windows 7 Machine. Also created a local account on that machine to match (Hostmon, member of adminnistrator's group, and set password to be the same).

I can not get a process list with either:
(workstation name)\Hostmon
(workstation name)\Administrator
(Domain)\Administrator

UAC is disabled
Hostmonitor version 8.86

Status=Unknown. in the test properties, unable to retreive a list of processes.

[KS-Soft]

Could you please answer all questions?
- what exactly is your network configuration? target system located in different domain? what exactly system was added to domain (you said "I added a machine to the domain, and now the Process test is failing")? do you mean this test worked fine when target system did not belong to any domain?
- test performed by HostMonitor or RMA?
- any errors in security event log on target system?
- could you try to setup CPU Usage test for the same target system? test Status? Reply?

Also created a local account on that machine to match (Hostmon, member of adminnistrator's group, and set password to be the same).
I can not get a process list with either:
(workstation name)\Hostmon
(workstation name)\Administrator
(Domain)\Administrator

in such case "Hostmon" should work (without using (workstation name)\Hostmon)

Regards
Alex

[bkeadle]

Target system (Windows 7) was added to the domain. Hostmon machine still in a workgroup. The test work fine when both machines were *NOT* in the domain.

Test performed by HostMonitor

I'm away from the system till next week, so I can't review the event log or setup the CPU usage test. Perhaps Dan will be able to chime in.

[bkeadle]

Hmmm...after rebooting the target system (again) the problem seems to have resolved itself. Go figure.

[KS-Soft]

Next time try to setup CPU Usage test for the same system, it may provide additional information (if test fails, check error description in Reply field of the test)

Regards
Alex

[bkeadle]

Will do. Thank you.