6.Preventive Maintenance and Troubleshooting.ppt
- 1. Basics of Preventive Maintenance and Troubleshooting
- 2. The Purpose of Preventive Maintenance • Reduce the likelihood of hardware or software problems by systematically and periodically checking hardware and software to ensure proper operation. • Reduce computer down time and repair costs.
- 3. Hardware Maintenance Make sure that the hardware is operating properly. • Check the condition of parts. • Repair or replace worn parts. • Keep components clean. • Create a hardware maintenance program.
- 4. Software Maintenance • Review updates • Follow policies of your organization • Create a schedule
- 5. Preventive Maintenance Benefits • Reduce computer down time. • Reduce repair costs. • Reduce loss of worker productivity.
- 6. The Troubleshooting Process • Follow an organized and logical procedure. • Eliminate variables one at a time. • Troubleshooting is a skill that is refined over time. • The first and last steps involve effectively communicating with the customer.
- 7. Data Protection Check with customer • Date of the last backup • Contents of the backup • Data integrity of the backup • Availability of media for data restore If no backup can be created, ask customer to sign a release form
- 8. Gather Data from the Customer • Communicate respectfully with the customer • Start with open-ended questions – “What types of problems are you having with your computer or network?” • Then, ask closed-ended (yes/no) questions – “Have you changed your password recently?”
- 9. Verify Obvious Issues • Problem may be simpler than the customer thinks. • Checking for obvious issues can save time. • If this step turns up nothing, continue to the next step of the troubleshooting process.
- 10. Try Quick Solutions • May provide additional information, even if they do not solve the problem. • Document each solution you try. • May need to gather more information from the customer. • If you find the problem at this stage, document it and proceed to the end of the troubleshooting process.
- 11. Gather Data from the Computer • When system, user, or software errors occur on a computer, the Event Viewer is updated with information about the errors: – What problem occurred – The date and time of the problem – The severity of the problem – The source of the problem – Event ID number – Which user was logged in when the problem occurred • Although this utility lists details about the error, you may still need to research the solution. Event View er
- 12. Gather Data from the Computer Device Manager Device Manager • A flag of ! indicates the device is acting incorrectly. • A flag of X indicates the device is disabled.
- 13. • When troubleshooting, power on the computer and listen to the beep code sequence. Document the beep code sequence and research the code to determine the specific hardware failure. • If the computer boots and stops after the POST, investigate the BIOS settings to determine where to find the problem. Refer to the motherboard manual to make sure that the BIOS settings are accurate. • Conduct research to find software to use to diagnose and solve problems. Often, manufacturers of system hardware provide diagnostic tools of their own. • What third-party tools are you aware of to use in computer troubleshooting? Gather Data from the Computer
- 14. Evaluate the Problem, Implement the Solution • Research possible solutions: • Prioritize solutions to try. • Try easiest solutions first. • After an unsuccessful try, undo any changes you have made. – Unnecessary changes could complicate finding the solution.
- 15. Close with the Customer • Discuss the solution with the customer • Have the customer confirm that the problem has been solved • Document the process – Problem description – Solution – Components used – Amount of time spent in solving the problem
- 16. Completed Work Order The gratifying results of a day’s work