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
Bendrinti
Bendrinti
prie
Alara42
Secondary
Computing
Redaguoti turinį
Išsaugoti
Patinka
Spausdinti
Įterpti
Daugiau
Užduotis
Lyderių lentelė
Rodyti daugiau
Rodyti mažiau
Ši lyderių lentelė šiuo metu yra privati. Spustelėkite
Bendrinti
, kad ji būtų vieša.
Ši lyderių lentelė buvo išjungta išteklių savininko.
Ši lyderių lentelė yra išjungta, nes jūsų parinktys skiriasi nuo nustatytų išteklių savininko.
Grąžinti parinktis
Rask tinkamą
yra neterminuotas šablonas. Jis negeneruoja rezultatų lyedrių lentelei.
Reikia prisijungti
Vizualinis stilius
Šriftai
Būtina prenumerata
Parinktys
Labiau taip.
What would you do problem solving
prie
Kferrante
Viktorina
37
Troubleshooting advance computing system steps
prie
Nahidabughname
Rask tinkamą
5
Troubleshooting process steps
prie
Lubnaalmeshaiei
Eilės tvarka
5
CompTIA Troubleshooting Methodology
prie
Freemanc176
Priskyrimas grupėms
22
Problem solving
prie
Annashastak
Laimės ratas
4
Problem solving
prie
Todoaba
Viktorina
6
Problem-solving
prie
Ciaranmckeon
Priskyrimas grupėms
3
network+ troubleshooting methodology
prie
Shreksnose
Diagrama su kortelėmis
7
Pakeisti šabloną
Rodyti viską
Atviri rezultatai
Kopijuoti nuorodą
QR kodas
Naikinti
Atkurti automatiškai įrašytą:
?