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
Teilen
Teilen
von
Alara42
Secondary
Computing
Inhalt bearbeiten
Speichern
Gefällt mir
Drucken
Einbetten
Mehr
Zuweisungen
Bestenliste
Mehr anzeigen
Weniger anzeigen
Diese Bestenliste ist derzeit privat. Klicke auf
Teilen
um sie öffentlich zu machen.
Diese Bestenliste wurde vom Eigentümer der Ressource deaktiviert.
Diese Bestenliste ist deaktiviert, da sich Ihre Einstellungen von denen des Eigentümer der Ressource unterscheiden.
Einstellungen zurücksetzen
It's a Match
ist eine Vorlage mit offenem Ende. Es generiert keine Punkte für eine Bestenliste.
Anmelden erforderlich
Visueller Stil
Schriftarten
Abonnement erforderlich
Einstellungen
Eher so
What would you do problem solving
von
Kferrante
Quiz
37
Troubleshooting advance computing system steps
von
Nahidabughname
It's a Match
5
Troubleshooting process steps
von
Lubnaalmeshaiei
Die richtige Reihenfolge
5
CompTIA Troubleshooting Methodology
von
Freemanc176
Die richtige Gruppe
22
Problem solving
von
Annashastak
Glücksrad
4
Problem solving
von
Todoaba
Quiz
6
Problem-solving
von
Ciaranmckeon
Die richtige Gruppe
3
network+ troubleshooting methodology
von
Shreksnose
Beschriftetes Diagramm
7
Vorlage ändern
Alle anzeigen
Offene Ergebnisse
Link kopieren
QR-Code
Löschen
Soll die automatisch gespeicherte Aktivität
wiederhergestellt werden?