https://wiki.ihitc.net/mediawiki/index.php?action=history&feed=atom&title=Franske_ITC-2000_Troubleshooting_Lab 2026-04-30T19:51:06Z Revision history for this page on the wiki MediaWiki 1.38.5 https://wiki.ihitc.net/mediawiki/index.php?title=Franske_ITC-2000_Troubleshooting_Lab&diff=7351&oldid=prev 2018-04-19T16:03:09Z

<p><span dir="auto"><span class="autocomment">Troubleshoot Various System Issues</span></span></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 16:03, 19 April 2018</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l7">Line 7:</td> <td colspan="2" class="diff-lineno">Line 7:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>= Troubleshoot Various System Issues =</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>= Troubleshoot Various System Issues =</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>For the remainder of this lab you and your partner will trade off causing and fixing issues on your lab system. You will each get a list of different issues to create (one at a time) and symptoms to report to your partner. Trade off fixing the various issues you have created for each other and observing the troubleshooting process of your partner. If you are doing the troubleshooting try to talk through the troubleshooting steps you are taking out loud so your partner can follow your line of thinking. Your lab report for this lab should include some information from both partners about how you each worked through the troubleshooting process and what you learned about troubleshooting issues.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>For the remainder of this lab you and your partner will trade off causing and fixing issues on your lab system. You will each get a list of different issues to create (one at a time) and symptoms to report to your partner. Trade off fixing the various issues you have created for each other and observing the troubleshooting process of your partner. If you are doing the troubleshooting try to talk through the troubleshooting steps you are taking out loud so your partner can follow your line of thinking<ins style="font-weight: bold; text-decoration: none;">. Once you finish the example issues you have been given you and your partner should each create two more issues for the other to try and troubleshoot</ins>. Your lab report for this lab should include some information from both partners about how you each worked through the troubleshooting process and what you learned about troubleshooting issues.</div></td></tr> </table>

BenFranske https://wiki.ihitc.net/mediawiki/index.php?title=Franske_ITC-2000_Troubleshooting_Lab&diff=7177&oldid=prev 2017-11-28T01:07:46Z

<p><span dir="auto"><span class="autocomment">Check Hardware Boot Issues</span></span></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 01:07, 28 November 2017</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l4">Line 4:</td> <td colspan="2" class="diff-lineno">Line 4:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#* If the system does not boot properly troubleshoot the boot issue. Additional parts which can be swapped in can be obtained from your instructor after explaining your troubleshooting process.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#* If the system does not boot properly troubleshoot the boot issue. Additional parts which can be swapped in can be obtained from your instructor after explaining your troubleshooting process.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div># Once the system does power on verify all lights, ports, drives, etc. are working properly and recognized by the system. Enter the system BIOS and check the boot device order and other BIOS settings for appropriate configuration.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div># Once the system does power on verify all lights, ports, drives, etc. are working properly and recognized by the system. Enter the system BIOS and check the boot device order and other BIOS settings for appropriate configuration.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div># Connect the system to the ITCnet (<del style="font-weight: bold; text-decoration: none;">yellow </del>network jack in <del style="font-weight: bold; text-decoration: none;">B109</del>) and complete the boot process into the Windows OS.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div># Connect the system to the ITCnet (<ins style="font-weight: bold; text-decoration: none;">the GREEN </ins>network jack in <ins style="font-weight: bold; text-decoration: none;">B107</ins>) and complete the boot process into the Windows OS.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>= Troubleshoot Various System Issues =</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>= Troubleshoot Various System Issues =</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>For the remainder of this lab you and your partner will trade off causing and fixing issues on your lab system. You will each get a list of different issues to create (one at a time) and symptoms to report to your partner. Trade off fixing the various issues you have created for each other and observing the troubleshooting process of your partner. If you are doing the troubleshooting try to talk through the troubleshooting steps you are taking out loud so your partner can follow your line of thinking. Your lab report for this lab should include some information from both partners about how you each worked through the troubleshooting process and what you learned about troubleshooting issues.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>For the remainder of this lab you and your partner will trade off causing and fixing issues on your lab system. You will each get a list of different issues to create (one at a time) and symptoms to report to your partner. Trade off fixing the various issues you have created for each other and observing the troubleshooting process of your partner. If you are doing the troubleshooting try to talk through the troubleshooting steps you are taking out loud so your partner can follow your line of thinking. Your lab report for this lab should include some information from both partners about how you each worked through the troubleshooting process and what you learned about troubleshooting issues.</div></td></tr> </table>

BenFranske https://wiki.ihitc.net/mediawiki/index.php?title=Franske_ITC-2000_Troubleshooting_Lab&diff=6642&oldid=prev 2014-11-18T01:32:33Z

<p>Created page with &quot;= Check Hardware Boot Issues = # Setup your PC, display, keyboard and mouse # Try booting your PC and verify that the system boots properly. #* If the system does not boot pro...&quot;</p> <p><b>New page</b></p><div>= Check Hardware Boot Issues =<br /> # Setup your PC, display, keyboard and mouse<br /> # Try booting your PC and verify that the system boots properly.<br /> #* If the system does not boot properly troubleshoot the boot issue. Additional parts which can be swapped in can be obtained from your instructor after explaining your troubleshooting process.<br /> # Once the system does power on verify all lights, ports, drives, etc. are working properly and recognized by the system. Enter the system BIOS and check the boot device order and other BIOS settings for appropriate configuration.<br /> # Connect the system to the ITCnet (yellow network jack in B109) and complete the boot process into the Windows OS.<br /> <br /> = Troubleshoot Various System Issues =<br /> For the remainder of this lab you and your partner will trade off causing and fixing issues on your lab system. You will each get a list of different issues to create (one at a time) and symptoms to report to your partner. Trade off fixing the various issues you have created for each other and observing the troubleshooting process of your partner. If you are doing the troubleshooting try to talk through the troubleshooting steps you are taking out loud so your partner can follow your line of thinking. Your lab report for this lab should include some information from both partners about how you each worked through the troubleshooting process and what you learned about troubleshooting issues.</div>

BenFranske