on 7/21/2009 12:14:35 PM

on 10/15/2009 12:13:14 PM I have installed this MP i have created the registy.. all worked ok. I wanted to add new servers to be monitored... nothing happens.. no new servers.. appear...?? what do I do wrong?

on 10/16/2009 3:45:28 AM Am I assuming correctly that you have changed the registry keys on already discovered watcher nodes? If so the updates should start appearing in OpsMgr within some hours. The discovery process is deliberatly set to use resources very moderatly. So most of the time it helps being patient. Should you have added the key on new watcher nodes, just remember to enable proxying for them. Otherwise no objects will be discovered.

on 10/22/2009 5:52:49 PM Hi- I've installed the MP, modified the registry and installed it on some different nodes. I verified that the agents are set to act as a proxy, but nothing is coming through the console (in the Multi-Host Ping 3.0 group, everything is blank) Is there a step I may be missing? Its been active for approx 2 hours. We are running R2 on Windows 2003/32bit. Thanks for this!!

on 10/31/2009 4:44:24 PM Hello, We are currently using the Ping management pack from Opslogix shown here http://www.opslogix.com/#ping. Does anyone know how the Opslogix management pack compares to the Mulit-Host Ping MP 3.0? Thanks

on 11/2/2009 12:46:30 AM Different modules underneath. Multi-host Ping MP uses a native WMI module that does not use scripts, so Multi-host Ping MP scales really well. They are using something different, but have a GUI setup wizard where we use a registry key on the watcher nodes. Multi-host Ping has quite a lot of performance views and reports as well.