With all kinds of real-life problems on your mind, monitoring security just isn't a day-to-day concern. Then suddenly something happens � a crash, a slowdown, a server that sounds like R2-D2 with gas. The physical checks turn up nothing, so suddenly the dreaded "What if�?" comes to mind. And then you're wandering the midnight forest with a penlight, trying to scratch up enough security expertise and data to make any kind of guess at what the problem might have been. Meanwhile, your useless supervisor turns into Jiminy Cricket, perched on your shoulder chirping his little mantra in your ear, "If only you'd paid more attention to security. If only�"

Well, swat the little insect. With a little forethought, a little planning, and a little automation, you can turn that midnight terror trudge into a calm garden stroll � or at least give yourself a bigger flashlight. On the Microsoft side, do yourself a favor and actually read the documentation on reporting. Microsoft has done loads of work on its reporting engine, yet most administrators dump this stuff right away because it's too much work, the learning curve is in the way, and it usually involves asking your boss for a SQL Server box and license. Well, bite the bullet, dent the budget, and RTFM (read the effing manual) because combined with platforms such as System Center, a regular schedule of reports can save your life when you're hunting the network for a bad-guy bug.