What should you document when defining an operating-system failure?
Describe what fails, when it began, how often it occurs, and what the user was doing before changing anything.
Study Operating-System Troubleshooting Basics with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.
What should you document when defining an operating-system failure?
Describe what fails, when it began, how often it occurs, and what the user was doing before changing anything.
How should you reproduce a failure before attempting a repair?
When practical, repeat the same steps that caused the failure so you can compare results before and after a repair.
Why reproduce a failure using the same steps?
A repeatable failure is easier to compare before and after a repair.
What does scoping an operating-system failure involve?
Determine whether it affects one application, the whole system, multiple users, or startup.
What should you protect before a repair could overwrite evidence?
Preserve important data and capture relevant logs before repairs that might overwrite evidence.
Which recent changes should you note when defining a failure?
Record recent updates, driver installations, configuration edits, or new hardware.
What does a failure limited to one application suggest about its scope?
A failure limited to one application suggests a different troubleshooting path from one affecting the whole system.
How does a system-wide failure differ in scope from an application-only failure?
A system-wide failure affects the whole system, rather than being limited to one application.
What is the basic sequence for operating-system troubleshooting?
Collect evidence, test a likely explanation, make a controlled change, then check whether the failure is resolved.
Which circumstances help define an observable failure?
Record what fails, when it began, how often it happens, and what the user was doing.
What should you check about the number of affected users?
Check whether the failure affects multiple users; this is one way to assess its scope.
When should you preserve important data and capture relevant logs?
Preserve important data and capture relevant logs before a repair that could overwrite evidence.
Focused study of installation failures, crashes and application compatibility.
Focused study of recognition, isolation and remediation workflow concepts.
Focused study of mobile OS, application, connectivity and synchronization problems.