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.

on 2/9/2010 8:41:53 PM
I have added the management pack and following through the document have been able to get the product working for about 90 hosts. That said I think I am coming two limitations in the current management pack:



Number of hosts that can be added via registry seems to be around Ninety Five (95) because of registry characters for hostnames that can be added. Am I the only one experiencing this issue? Are other users able to add more hosts? Is there a way to point to a file containing hostnames instead?



Also as we add more hosts if the ping to each host is sequential then depending on number of pings and RTT, one may hit limitation of never completing ping to all hosts say every two to three minutes and new ping sequence begins. Does that make sense?



Thanks for help/feeback in advance.

on 3/9/2010 1:57:47 AM
Hi Everyone,



First, i'd like to thank you guys for creating this MP :).



My question is, can i configure to have all the monitored IPs into a Group? How? I tried to create a group for these monitors but it seems that it cant be considered (as this is an IP and not device). I want to consolidate all monitored IPs into a single group then assign a specific email subscription for this so that other recipients will not be disturbed incase an IP of such will go down.



Is this possible to do?



Thanks,

Pabs

on 4/7/2010 3:02:52 AM
hi, thanks for this.



When I import MP using Opeations Console there are some monitors and rules missing ?!?!



I can see all monitors, rules and tasks in authoring console but not in Operations Console when importing.



??

on 8/24/2010 10:12:36 AM
TWIMC,



I'd also like to thank the authors for putting this together.



Since I haven't seen any responses to posts for over 4 months I don't know if this thread is being monitored any longer. I have a comment in case it is.



To Shailesh's point it would be nice to be able to point this at a text file. I understand that makes it complex because of varying folder locations. The registry key idea makes admins a little nervous and has its limitations.



Shailesh - If you spread the workload over multiple watcher nodes then both of your issues should be resolved. See the pdf doc in the MP for this.



All little criticism aside, this is an excellent solution allowing me to further push IPMon out the door. I can't touch all servers with agents or even agentless monitoring so this is a great workaround.

on 8/27/2010 10:45:55 AM
Hello everyone!



Also hope folks are still monitoring these posts.



I'm very interested in this MP due to performance Rule overrides available over OpsLogix PING MP!



However, I am curios for an answer to the number of ping targets that can be entered into a single WatcherNode. We have 3000+ network (non Windows) devices we want to monitor for PING response times.



We are thinking of creating custom console tasks (scripts) to perform diagnostic and service stopping actions on Windows PCs when we detect extremely long ms response times over DSL networks when in Dial backup.



While OpsLogix PING MP is nice, it seems more limited and challenging to accomplish monitoring multiple levels of ms response times and thresholds.



We are thinking of either using multiple SCOM monitors or a 3 state monitor for ms response times to trigger console tasks/alerts with custom scripts firing against certain SCOM Agents (Agent IP derived via custom script from ping targets) where the ping target is in Dial backup state. We may simply have to target the actual Windows Computer IP/name with our custom scripts vs. actual SCOM Agents since the tasks will be console based.



None the less or the scripting concerns I may run into, my primary interest is how many Ping Targets can one Ping Watcher support in the registry? I see one post here stating 95 Ping Targets max due to registry limitations. Any update or confirm limit per Ping Watcher?



Any help/comments are truly appreciated.



Thanks,

Terry