Diagnostics results: Have you run system utilities to get even more information? For example: ping can help you remotely check if a server or website in question is reachable.Can the user provide screenshots, video, or other supporting information that can help assist in the troubleshooting process?.Checking the Windows event viewer can be a first step in pointing you towards any relevant logs. Events logs: Do they exist, and if so, what exactly do they say? In addition to error messages, logs often provide a timestamp so you can answer the question of when exactly events happened.For example, Windows blue screens of death provide a relevant error code that’ll give you a good sense of what caused a failure. Error messages: If the user reports one or you’re present to check for one, they can point you in the right direction as to why a failure occurred.Best way to find out? Ask those pertinent questions and then dig up more info from various sources such as: In many instances, what was reported as a general issue (e.g., the Internet is down) is actually something very particular, such as a specific website being offline. How can you answer the most common IT questions? 2) Gather more details, eliminate variables Now that you have a basic understanding of what the issue is all about, you can look into technical details that could point you toward to a solution. Ideally, this will help remove potential confusion related to the issue. It’s a good idea to use some the same language they used and avoid using complex tech terminolgy. Once you’ve got a grasp on the issue, try repeating your understanding of the problem so that you’re both on the same page as to what’s wrong.Does the issue affect just one person or many people? Did it occur right after a significant event on the computer or the network? There are specific questions you can ask to drill down beneath general statements like “I can’t send email.” Are they using a PC or mobile device? Is the PC power on? Are they able to open their e-mail client? Can they send or receive email, or both? What should you ask? The key is to find out the “who, what, and when” of the problem.This approach can move things along and cut down on ambiguous responses. When they’re done, proceed with questions that either have a yes/no answer or can be answered quantifiably (e.g., “How many times did this happen?”). If you’re talking to someone or emailing with them, listen or read carefully and take notes (mental or otherwise). ![]() Getting to the bottom of a computer issue can sometimes feel like playing 20 questions, so it’s crucial to ask the right questions first if you want to discover the root problem quickly. Worry not! We’ve got several problem-solving steps to follow that’ll help ease the stress of solving nearly any IT issue: Step 1: What exactly is the problem? What’s your plan of action for the next vague phone call, email request about tech issues, or help desk ticket from a big wig who needs his computer fixed… RIGHT NOW? End users submit seemingly endless problems ranging from complaints of their Internet being “slow” to forgotten passwords to constant printer pains. ![]() Troubleshooting IT can be… tedious (understatement of the year).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |