The class org.opennms.protocols.wmi.CheckWmi makes a great tool for troubleshooting WMI issues, but it's a bear to invoke because it depends on several JARs. We should drop a shell script wrapper for it (and probably a batch file one on Windows) in OPENNMS_HOME/bin.
Environment
Operating System: All
Platform: PC
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Jeff Gehlbach September 9, 2010 at 5:35 PM
Script pushed to 1.8 in commit 5f23444776980b63fd29e598f75ea460f9784e90 and cherry-picked to master in commit 7a356840db6e7e01c05a0aefa84c55c5d8f38c8d.
The class org.opennms.protocols.wmi.CheckWmi makes a great tool for troubleshooting WMI issues, but it's a bear to invoke because it depends on several JARs. We should drop a shell script wrapper for it (and probably a batch file one on Windows) in OPENNMS_HOME/bin.