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
Podijeli
Podijeli
Autor
Alara42
Secondary
Computing
Uredi sadržaj
Spasi
Sviđa mi se
Ispis
Postavi
Više
Zadatke
Top-lista
Pokaži više
Pokaži manje
Ova top-lista je trenutno privatna. Odaberite opciju
Podijeli
da biste je javno objavili.
Ovu top-listu onemogućio je vlasnik sadržaja.
Ova top-lista je onemogućena jer se vaš odabir opcija razlikuje od postavki vlasnika sadržaja.
Vrati opcije na početne postavke
Spoji parove
je otvoreni predložak. Ne generira rezultate za top-listu.
Prijava je obvezna
Vizualni stil
Fontovi
Potrebna je pretplata
Postavke
Više ovako
What would you do problem solving
Autor
Kferrante
Kviz
37
Troubleshooting advance computing system steps
Autor
Nahidabughname
Spoji parove
5
Troubleshooting process steps
Autor
Lubnaalmeshaiei
Poredak
5
CompTIA Troubleshooting Methodology
Autor
Freemanc176
Razvrstaj u grupe
22
Problem solving
Autor
Annashastak
Čudnovati kotač
4
Problem solving
Autor
Todoaba
Kviz
6
Problem-solving
Autor
Ciaranmckeon
Razvrstaj u grupe
3
network+ troubleshooting methodology
Autor
Shreksnose
Slika s oznakama
7
Promijeni predložak
Prikaži sve
Otvoreni rezultati
Kopiraj vezu
QR kôd
Izbriši
Vrati automatski spremljeno:
?