Any professional in any field can tell you the obvious importance of keeping theirs tools in tip-top shape. It doesn’t matter if it is a carpenters saw or as complex as a surgeon’s scalpel, ensuring things are clean and working as expected are crucial to getting the job done right.
We all have network tools that collect data, capture packets or produces reports. Unfortunately these tools typically go unmaintained. The danger lies in leaving potentially sensitive files behind. In some cases these files are left on the unit by those who move on. And to add even more complexity to the mix, many of these files are probably default application or cryptic names with no meaning to them other than the author.
Here’s some questions to keep in the back of your head when using or evaluating these types of tools;
- If there is an automatic feature that saves to disk, is there a corresponding setting that will clean it up?
- Check and clean out the default folder where files are written too.
- If you are using a ring buffer feature, ensure that you know how much space this will occupy or look for disk space settings.
- Create shortcuts to report locations or label the unit as to where report folders are located.
- If you decide to use a script or batch file to manage these files, always ask the user if they are sure and default the response to No.
In this video I use my Fluke Networks Optiview XG as an example of a device that gets loaned out and that I use quite a bit in the field. I chose to delete the files and folders but you can easily modify this approach to move the files to a portable drive first.
Even with the XG, some customer think when they reset the XG settings to default, these report, trace and map files are deleted, and unfortunately they are not.
The batch file is just a few lines, but here you go:
del C:\Users\OptiView\Documents\"Fluke Networks"\OptiViewXG\maps\*.* /Q
del C:\Users\OptiView\Documents\"Fluke Networks"\OptiViewXG\Captures\*.* /Q
rmdir /S /Q C:\Users\OptiView\Documents\"Fluke Networks"\OptiViewXG\Reports\"performance test"\
timeout /T 11