Stay updated with announcements, get answers from the community and share your feature suggestions with us.
You can also submit a request or send us an email at Help@INSShawnee.com.
Shanley Yates December 28, 2011 • Tips & Tricks
Rebooting is the source of frustration for techs and callers alike in the support world, and it seems as if there are two sides lined up. The users know they are going to be asked to reboot, and line up to defend against that request in an attempt to keep their computer on. The techs, on the other hand, attempt to get the users to reboot their computer before any further troubleshooting can occur.
Sounds like some sort of game, rather than a tech support scenario. And a little silly to boot (ha ha), from both sides. Take this scenario... imagine you've taken your car into your mechanic to have it worked on, yet steadfastly refuse to turn off the engine so that the mechanic can look under the hood. What are the chances that mechanic will be able to solve your problem, in a manner that is efficient for the mechanic and satisfactory for you?
The problem resides in the fact that no one ever mentions why a reboot is necessary. Well, it's mostly because "it just does," but there are other reasons as well.
Of course, the multitude of things that happen and are fixed by rebooting cannot be boiled down to a list of six bullet points, but you get the picture. So when we ask you to reboot, be assured that we are not simply trying to do things by the book, or to give you a pat, standardized answer, but are instead employing the first of many tools to assist us in troubleshooting and ultimately solving your question.