What is the easiest way to tell if the same probes and configurations are present across different hubs/customers? Is probereport.exe the best way? Probereport seems limited to a couple of basic probes. Do we have anything else more detailed?
It probably depends a bit on how strict you would need it to be. At CDW, I more or less accomplished this by using super packages to push out common sets of probes and configs. The packages were version-controlled to help me update the right places when things changed. That sort of solution would get you uniformity at first, but things can diverge over time depending on who is touching the system. I had a probe that could tell me if any robots were running out-of-date versions of probes or the super packages. But it did not check to make sure that no probes were missing or anything like that. Nor did it check anything in the configs. Checking that the right probes are present is probably reasonable, but checking config settings would be quite a bit more work. Doable but trickier.
I am working on a probe for NoD that would be able to check that the right versions of probes are installed, but right now I am not planning on having it check for missing probes or the config settings.
The type of information you're looking for, is it basically the same type of stats you get when you open a robot and choose the "Installed Packages" button? If so, a script could be written to call inst_list_summary to output all these stats and output in some type of report.
Jim and Gyan worked on cleaning up a field developed probe called "inventory". This probe essentially walks through the Nimsoft namespace pulling configurations from hubs/robots/probes. The output is a SQLlite db and is viewed as HTML tables with links that allow you to drill down from component to component.
Take a while to run, but once the configs are loaded into the db, you can run queries to perform comparisons, even down to the probe configuration level.
Would this meet your needs ? If so, reach out to Gyan and Jim for the latest version. Gyan was the last to work on it.
It is not actually a probe, rather it is a LUA script that is run from a nas schedule. The results are displayed from an asp web page added to an iis web server with a style sheet associated to it. It is running on the mspportal hub server. The lua code is in a folder named Inventory in the nas scripts - probe_config2, I believe. The web report can be acecessed from http://192.168.129.7:8089/inventory/scripts/report.asp
get_probe_config2 is that actual lua script name.
There are more pre-requisites that that. The tables used are actually in the SQL Server. You need to create a database for the script to then create the tables that are used. The script also needs to be edited to provide the correct databae connection information as does the report.asp. Attached is a zip file with the entire folder structure with the style sheet and .ASP for placement under ../inetpubs/wwwroot/. Also attached is a notes doc whith installation notes, and the lua script for the nas.
Retrieving data ...