1. 
   Identify the problem - Interview the user to identify the problem. Ask him or her whether something change prior to the problem.
2. Establish a theory of probable cause - Question the obvious.
3. Test the theory to determine cause - Once the theory is confirmed, determine the next steps to solve the problem. If the theory is not confirmed, establish a new theory and test again.
4. Act - Draw up plan of action to solve the problem and implement the solution.
5. Test and prevent - Check full system functionality and, if applicable, implement preventive measures.
6. Report - Document findings, actions, and outcomes.

Come up with your own hardware problem that needs troubleshooting. Detail what you would put for each of the six (6) troubleshooting steps and what their outcome is, in order to fix the issue.

Then, provide the documentation you would include in Step 6, so that, if the issue happens again, you know what you did to fix it the last time you saw the issue.

SophiaPretty

(5)

Status NEW Posted 20 Nov 2017 08:11 AM My Price 6.00

-----------  ----------- H-----------ell-----------o S-----------ir/-----------Mad-----------am ----------- Th-----------ank----------- yo-----------u f-----------or -----------you-----------r i-----------nte-----------res-----------t a-----------nd -----------buy-----------ing----------- my----------- po-----------ste-----------d s-----------olu-----------tio-----------n. -----------Ple-----------ase----------- pi-----------ng -----------me -----------on -----------cha-----------t I----------- am----------- on-----------lin-----------e o-----------r i-----------nbo-----------x m-----------e a----------- me-----------ssa-----------ge -----------I w-----------ill----------- be----------- qu-----------ick-----------ly

Not Rated(0)

• Buy Answer