Now the model im going to present here is by no means

Info icon This preview shows pages 18–19. Sign up to view the full content.

View Full Document Right Arrow Icon
resolve a very broad range of problems. Now, the model I'm going to present here is by no means all-inclusive. You may need to add, remove, or reorganize the steps we're going to talk about to match a particular situation. However, this model should give you a good base to start from. Now, before we begin, I want you to understand that many new system administrators make a very catastrophic mistake when they start troubleshooting system problems. Instead of using a methodical troubleshooting approach, they go off half-cocked and start trying to implement fixes before they really even know what the problem is. I call it shotgun troubleshooting. The administrator tries one fix after another, hoping that one of them will just magically repair the problem. Now, this is a very dangerous and very bad practice. I've watched system administrators do this and cause more problems than they actually solve. Sometimes, they even cause catastrophic problems. Case in point, several years ago, I was setting up several servers in a network and one of the servers was misconfigured and having trouble synchronizing information with the other servers. So, while I was trying to figure out what the source of the problem was, my co-worker, let's just call him Sid,starting implementing one fix after another in shotgun fashion, trying to get the server to sync with the other servers. And in the process, he managed to catastrophically mess up all of them. The actual issue the server was experiencing was relatively minor and would've required about 20 minutes of time to fix. Instead, because of Sid's actions, we had to spend the rest of the day and most of the night reinstalling each server from scratch and restoring data. So, instead of using a shotgun troubleshooting approach, you should instead use a standardized troubleshooting model. The goal of a troubleshooting model is to concretely identify the source of a problem before you start trying to fix things. Now, I know that sounds really simple, but many system administrators really struggle with this basic concept. So, here is a suggested troubleshooting modelthat you can use to develop your own personal troubleshooting methodology. 1. Gather Information 3:22-3:39 First step, gather information. This is critical. You need to determine exactly what has happened.What were the symptoms? Were there any error messages displayed? What did those error messages say? How extensive is the problem? Is it isolated to a single system or are their many systems that are experiencing the exact same problem? 2. Identify What has Changed 3:40-3:53 Step two, then identify what has changed. In this step, you should identify what's changed in the system. Has any new software been installed? Has a new piece of hardware been installed? Did the user change something? Did you change something?
Image of page 18

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 19
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern