How to Troubleshoot - CompTIA A+ 220-1101 - 5.1

[@senjurooo8254]

Thank you professor! Good luck to everyone, we've got this!

[@paulgiovanni1136]

almost to the promise land

[@Cori93]

Right behind you

[@conjurn.]

with you

[@thepluraloftiger]

almooost theere

[@Akerfeldt77]

Still got core 2, bb

[@timestmps]

final stretch, baby

[@AimlessSavant]

1:40 I LOVE this. It is an incredibly scientific way of solving problems. So much so that this pretty much is how Scientific Hypothesis are made.

[@killarha18]

I (Identify) Enjoy (Establish) Taking (Test) Peoples (Plan) Internet (Implement) Very (Verify) Diligently (Document) Makes it easier to remember

[@BeardFaceSuper]

I Eat Tasty People. I'm Very Disgusting.

[@scott6497]

Thanks for this! Something tells me the exam is going make sure we really know this.

[@Fjdndjdm]

What about evaluate the results is it working

[@ukkiekim8109]

I enjoy taking ppl internet very diligently!

[@Randumb96]

Great video! really helped me remember the troubleshooting process.

[@haleylordy941]

I'm confused between the test a theory and implement the action steps. If my theory was the power cord was unplugged and I test it by plugging it back in and now everything is handy dandy, what plan am I establishing and implementing??? Or am I just looking at this wrong?

[@es-7965]

Sometimes the two steps act as one, especially for simple solutions like with what you said The steps are moreso in place for larger scale problems, say for instance malware, identify the problem (say you cant access x software idk) > establish a theory (ermmmm le malware?) > test the theory (confirm le malware) > plan and implement ((plan):determine which antimalware to run, (implement): run it) > etc > etc.. Keep in mind that this is compTIA's troubleshooting process, companies may use their own process that works for them so dont be surprised if you're not deploying this in the field, hope that helps :)

[@ruthsan61]

just skip - that's just if it doesn't resolve it

[@maximusm0104]

2 things i can infer here: The methodology chart is a rough outline of the process depending on the issuek so something like a power cable is ethernet cable wouldnt necessarily warrant approval from your "board" to fix. Furthermore, if you are recreating the entire scenario in a sandbox environment, even something as simple as an unplugged cord, can still be applied to the whole methodology. Feel free to stick ur head into your senior engineers office, every time you need permission to go onsite and plug in a cable :)

[@mserikam21]

What does it mean to receive a "slot from the change control board"?

[@mrbekong]

An implementation window I believe. Like say a company says "You have between Tuesday 5pm and 8pm to implement changes/plans. (Hence messages some products send out saying, "expect a downtime between so and so times")

[@venusrise]

I was expecting this video to explore troubleshooting strategies, like "binary division" etc.

[@johnthefisherman5323]

Nice vid Messer