Is there a way to do a mass removal a particular probe from multiple robots using some sort of distribution task? Right now it seems like the only action I can take is manually clicking on the robot, then clicking on the probe and deleting it.
There is the callback in the controller that you can use (inst_pkg_remove) and if you are able to derive a list of probe addresses you can use Unix utilities like awk to loop through the address list.
./pu -u username -p password /nimsoftdomain/hub/robot inst_pkg_remove packageName(most likely probe name) probeName
Note that this will restart the controller so in some cases if your hub is in your list of robot addresses be aware that any robots hanging of that hub will temporarily lose communications. I suspect this may not be exaclty what you are looking for with regards to an answer but this is the only way I know how to accomlished this task.
Another option is to run some script on nas (very easy one) you can have a list of probes into a csv or txt.
I implemented some one for activating / deactivating probes but you should also be able to have txt / csv like "probe / command" and play with probe_deactivate / probe_activate / inst_pkg_remove.
You can do this without scripting by using the Find option in Infrastructure Manager. If you search for all installs of a probe, you can select them all in the results window and then use the same right-click option to delete them. You can also multi-select in the results window without selecting all rows if you only want to remove some of them.
After doing this, your Infrastructure Manager might be busy and unresponsive for a little while. I would also check after the fact and make sure it managed to update every robot. It would not surprise me if you had to do this a few times to catch all of them; it seems like the Infrastructure Manager is doing all of it in the foreground and probably just moves on when it has any trouble.
I'm going to write a script. The method keithk described is nice, and would be ideal, but it is really flaky as to what it actually deletes. Thank you all for the great advice though!
Is it required to deactivate the probe before calling the callback for deletion of the probe ?
Retrieving data ...