KS-Soft

We use Hostmon 8.32 The system is running on Windows 2k3, which I don't believe has Virtual Store/UAC (which is almost unfortunate, as the behavior I'm seeing would be answered nicely by that) I'm checking the HD for errors now, and we'll see what that might turn up. I think my verbiage is wrong; it...

Within the last 6 months, we've had one of our Hostmon servers do the following twice: 1) System crashes/becomes unresponsive 2) Upon restart, resumes service 3) Shortly afterwards, we discover that the HML test profile it's using is old (anywhere from a few weeks to a few months) 4) We revert to a ...

Perfect ! That'll do the trick nicely.

Thanks !

My active RMA agent was unable to connect to Hostmon, and all the tests using the agent spammed alerts saying: RMA not connected is Unknown Now, in this case, it was user error (Hostmon was running as a service, and someone started another instance as an application). So essentially, one instance wa...

I recently had an issue where an active agent wasn't able to connect to the master Hostmon instance, and all the alerts using the agent alerted en masse. I want to create a dependency so that if the agent is unavailable, there is ONE test that ONLY looks at the agent connectivity, and then make all ...

Figured it out.

HKLM\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters

Set 'Size' from 1 to 2

I'm guessing this becomes an issue once a certain threshold in the amount of monitors in reached. In Win7, default set to 2. XP/Win2k3 : 1.

Well, I've been banging my head against this the last 2 days, and I'm stumped. For whatever reason, we have 2 racks (50 systems) (one of HP systems, one of Supermicro) that were just racked/imaged with Win7, and they give totally erratic results. Nt log: security/security monitors intermittently rep...

To the previous question, it's the XP 'Clients' that don't seem to have the problem. Per my previous update, those systems also are running dual Xeons as opposed to the Nehalems in the newer systems.

So I did some brainstorming with the team, and think we have a lead: the REAL common element on all these new machines is the processor. They're all running dual Nehalems (E5520 @ 2.27Ghz). I am going to pray to the google gods (and our tech rep for these systems) that there is some issue with PerfO...

It took some doing, but I duplicated our existing x64 XP hostmon system onto a Win2k3 box with duplicate FW rules, and I also upgraded to 8.32. I successfully imported our old tests, installed as a service, and have it running under the same conditions as the old installation. Unfortunately, the int...

Here's the test methods we're getting alerts from: Performance counter (Available Mbytes, Bytes total/sec) UNC availability Process CPU Usage NT Event Log They universally either have no additional info, or report 'RPC call failed' or 'RPC server is unavailable'; however they intermittently report '...

We recently migrated our Hostmon monitored x64 XP systems to x64 Win7, and are using the same kinds of monitors for the system. However, we're noticing a large incidence of 'unknown' status coming up, which typically recover, but typically enough to more than occasionally trigger alerts. We're using...

Hostmon is hosted on a Windows2003 SP2 x64 box; it's monitoring over 100 other systems with similar configurations (Vista/XP) with largely no issues like this.

Sorry, old habit, it is SP3. That RPC timeout seems like a good lead, I'm praying to the Google gods for a registry key to hunt down, no luck so far. Let me know if you track it down.

Thanks !

We recently swapped out a box previously running Vista, with a box running the same apps but on XP SP2 (with more memory). I've instituted the same monitors, however now there are a few tests that randomly seem to not be able to connect. Specifically, I've got two 'process' monitors that randomly re...