We can have a tendency to look at the RM dashboard as providing us with a number of different services. Therefore it is easy to compartmentalize these services and isolate their functions.
However like any good tool box, RM provides us with tools that can be used in an endless number of combinations to get our job done.
Example 1 Patch Management with System Tray Application:
As we know, we can configure our Patch Management policies to include a reboot to complete patch installation. We can also schedule reboots to occur whenever we like.
But what if a user is working late and in the middle of a project? Suddenly the warning window pops up and they are presented with a five minute countdown to reboot without an intuitive way to cancel. This can cause stress and aggravation that will be pointed in your direction, regardless of how much you have communicated the patch schedule.
What’s the answer?
Enter System Tray application. A simple batch file (containing a simple SHUTDOWN/A) can be triggered from the system tray to cancel the reboot. I wouldn’t suggest placing these on standard user machines, but for managers and CEOs this can provide them with a little piece of mind.Example 2 Remote Back Ground with Take Control:
How often do we have the need to remote into a machine that is operating poorly? I don’t know about you but I have lost hours of my life waiting for a slow machine to respond to simple commands like opening service manager or process manger. It can be downright painful to watch multiple instances of Control Panel open because I got impatient as I clicked, and clicked and clicked.
Example 3 Risk intelligence and Patch Management:
How do these two complement each other? Simple, to get customer buy in to your Patch Management offering.
Nothing speaks louder than money.
Often times when you start to talk about a customer’s need to patch, they are yawning looking at their watch. After all, on their computer at home chances are they choose to ignore patch installation all the time, and nothing really bad has happened.
This can lead to you feeling a bit like an insurance salesmen when trying to sell the customer on the need for patching.
The solution?
Run a Max Risk Intelligence Data Breach Security Scan. Even if there is no unprotected data on the machine, a big red X with FAIL over it clearly shows the machine is at risk with a detailed vulnerability summary.
Customers may not understand being told they need to patch, but they can relate to being showed they are Vulnerable in today’s security conscious world. With that clearer understanding, it is easier to roll them into a Patch Management Program.
So there you have it! Just a few ideas to get you started. So what do you think? Do you have mix and matches of your own? We’d love to hear back from you!