Monitoring, Correcting, and Reporting Configuration
In the configuration management processes, after the configuration is enacted, the most important step is to monitor the target systems for configuration drift. Over time, in the life cycle of target systems and the applications running on those systems, there is a high probability of configuration drifting away from the original configuration. In an ideal world, all the changes on the target system would go through the designated configuration management system. This would help to prevent configuration drift. This, however, is certainly not the case in many IT organizations. IT and application administrators prefer quick fixes to the problems that arise in day-to-day operations. Eventually, this leads to a configuration drift. And, when a disaster strikes, with a target system that drifted away from the baseline configuration, it may take more than a few hours to restore services offered to the end users.