KS-Soft

In my experience, HM does almost everything other tools do, but with an aged interface. Of course, there are much nicer interfaces, but the monitoring concept is the same and HM has much more versatility IMO. And I used HM for more than 20 years by now in multiple companies. All those are still usin...

I don't remember since which version we started to get many OK notifications without an error notification first. Analyzing them, they are all Unknown status we explicitly marked not to be taken as Bad. How can we avoid the OK notifications in these cases? I see that there is an option on Alrt Profi...

Yes, I understand. I think that investing more time on trying to fix it is not wise. Thank you anyway for the help!

Let's see if I got it. You mean, I create a test script with only one line and static values. Then hit Let's Try with the specific agent in script manager (that's what I use to test it all the time). This is the result after 10 seconds (timeout setting): [17:51:54] Agent: XXX is going to execute &qu...

Tried in application mode but it's the same. Tried adding credentials to the Invoke-Command, but it fails inside RMA Agent (not if I run in PowerShell). $statusUnknown = "ScriptRes:Unknown:" $statusOk = "ScriptRes:Ok:" $statusBad = "ScriptRes:Bad:" $computer = $args[0] ...

I tried changing the service account for the agent to the exact same as I was running the script, but the reply is still the same (0). I also tried forcing 32 or 64 bit PowerShell locations, but both returned 0. I do suppose that the invoke command has some issue when the reply returns to the execut...

I understand your last question now. HostMonitor > RMA Agent > Remote System No, we can not try it on HostMonitor as it's not in the same domain as RMA, but RMA is on the same domain as remote system and in there the script works. HostMonitor has no visibility on the remote system (different unreach...

That's what I said it works.

You installed RMA somewhere beside HostMonitor and using it to check some other system over slow link? It does not make sense :roll: Installation is HostMonitor > slow link > RMA > slow link > remote system (two jumps) What exactly means "it ends failing"? Test status? Reply? Reply value ...

The remote RMA agent is running with a domain admin account, that does have access to the remote system. That system is over a slow WAN, and we tried the built-in test, but it ends failing. The PowerShell script that we run on the server with the RMA Agent and pointing to the other remote server giv...

I'm trying to get a folder size through PowerShell instead of internal test because it's across a slow link. But this is not working with HostMonitor. Can someone tell me why the result is 0? When I run the script on the server with the RMA agent, it replies properly (135). If I run through HM that ...

I now moved the option to free space for caller, and it returns the proper disk free space.

The platform should be replaced later this year, so I don't want to change much. If this option works, that is OK for me.

Thank you!

The problem is we're talking about CentOS 6.10 that seems not to support version 1.36 of RMA. It gives the following error when trying to start the process: ./rma: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./rma) ./rma: /lib64/libc.so.6: version `GLIBC_2.14' not found (required b...

I'm having a weird issue. A CentOS Linux partition that is being checked by HostMonitor RMA 1.29 does not return the proper free space. This was identified because we're using another solution now (SCOM) and it alerted us when HostMonitor not. https://i.postimg.cc/wvTgtTPz/disk-space.png https://i.p...

I'm afraid it's not working. OS: Ubutu 18 RMA Agent: 1.36 for Linux Agent mode: passive The ping test to 127.0.0.1 or localhost returns with: "RMA: 500 - not implemented yet" Ping is enabled in the ini file for the agent. And remember that the TCP test was not conclusive as something in th...