Buyers can often go to great lengths to evaluate their options before investing in a product. Consider your last software investment. You might have done some Googling, watched some videos and read some reviews before downloading a trail version or two. You might have run a proof of concept with the vendor before justifying the investment to the board and signing the cheque.
So why potentially waste all that work by not taking the time to set the software up following best practice?
In order to work as it should, software needs to be installed and configured properly. The first step might be to go on (or send someone else on) a training course. At the very least, someone will need to read the manual.
Help the product to do its job
One of the common functions of IT monitoring solutions is the auto discovery element and it’s one that we see falling short of expectations time and again because…. It hasn’t been configured properly! The purpose of auto discovery is to periodically go off and detect what’s on your network without you needing to do very much at all. It has the potential to find, and document graphically or otherwise, everything within a network.
You might want it to:
- Visualise or map the network to show hierarchies and dependencies
- Provide an inventory of assets – vendor, model, serial number, version
- Identify changes as devices, applications and more are added or removed
- Identify security gaps: find missing patches, open ports and so on