Identify the problem, Ask the user to describe the problem or symptoms, check for error messages, or recreate the problem., Identify what has changed, Establish what has changed. Most often, problems are caused by new hardware, software, or configuration changes. If necessary, ask users to recall what might have changed from the time the software worked and the time it didn't. Remember to inquire about environmental and infrastructure changes that could be relevant, Create hypothesis, With the information gathered in the preceding steps, conduct research and then develop several hypotheses that could potentially explain the problem. From your research and the information you have already gathered, narrow your hypotheses down to the one or two mostly likely causes., Determine the appropriate fix, Review knowledge bases, other websites, and your own experience to identify steps to remedy the problem. Before implementing any steps, think through all possible ramifications that might occur from the planned fixes. Often, the fix itself creates side effects that are just as bad or worse than the original issue, Implement the fix, It's finally time to implement the steps of the fix you have planned. Resist the urge to jump into troubleshooting by starting with this step., Verify functionality, After implementing the fix, verify that the fix repaired the problem. If the problem still exists or a new problem appears, start back at step one again., Document the solution, It might be tempting to move on to other problems, but be sure to document the previous six steps. This will save a lot of time and effort if the problem happens again in say a year or two.
0%
Troubleshooting Process
Share
Share
by
Alara42
Secondary
Computing
Edit Content
Save
Like
Print
Embed
More
Assignments
Leaderboard
Show more
Show less
This leaderboard is currently private. Click
Share
to make it public.
This leaderboard has been disabled by the resource owner.
This leaderboard is disabled as your options are different to the resource owner.
Revert Options
Match up
is an open-ended template. It does not generate scores for a leaderboard.
Log in required
Visual style
Fonts
Subscription required
Options
More like this
What would you do problem solving
by
Kferrante
Quiz
37
Troubleshooting advance computing system steps
by
Nahidabughname
Match up
5
Troubleshooting process steps
by
Lubnaalmeshaiei
Rank order
5
CompTIA Troubleshooting Methodology
by
Freemanc176
Group sort
22
Problem solving
by
Annashastak
Spin the wheel
4
Problem solving
by
Todoaba
Quiz
6
Problem-solving
by
Ciaranmckeon
Group sort
3
network+ troubleshooting methodology
by
Shreksnose
Labelled diagram
7
Switch template
Show all
Open results
Copy link
QR code
Delete
Continue editing:
?
