The final MTTR process step impact is Remediation. Once we know the problem, we must connect to the asset and perform the Remediation. While that may seem trivial, it often is not. With ConsoleWorks we are either already connected to the asset or simply click on the device’s name and are automatically connected to the […]

Looking back at the first and second blog in this series, we see that by using ConsoleWorks IEMs the DETECT and ISOLATE steps are completed automatically in milliseconds (effective value = 0) taking a significant amount of time off of our MTTR. That leaves us with Detect = 0, Isolate = 0, Analyze = ?, […]

In the first blog we identified that ConsoleWorks IEMs automatically capture log-file changes and scan them for vendor-defined error codes. This automation moved the MTTR detect process step from reactive failure with log trolling to real-time event detection. Now that real-time events are detected, the next step is the isolate those events that are real […]

If you could reduce Mean Time To Repair (MTTR) down to a fraction of what it is now would you do so? Of course, anyone would slash MTTR down if they could and there are a lot of companies who promise just that. Before we look at MTTR reduction, let’s first get a stake in […]

Closed Loop Remediation – The ability to monitor, log, remediate, and secure physical and virtual infrastructure in all machine states; power on, single user, maintenance, production, and failure. ConsoleWorks allows privileged users to perform their daily work while it works behind the scenes to monitor and respond to Events and changes to devices and applications. […]

Virtually all computers, networks, and similar devices have a communication port through which they send boot and status messages. Usually, this console information is lost because it is impractical to monitor and respond to the geographically scattered computing infrastructures common in modern-day businesses. ConsoleWorks puts an end to this data loss and handles device monitoring information […]