IT 202 Project One
3 years ago
10
IT202ProjectTwoKnowledgeBaseDocumentTemplate.docx
IT202ProjectTwoTranscriptforChatBox.docx
IT202ProjectTwoTranscriptforPhoneCalls.docx
IT202ProjectTwoFiveTickets1.docx
Instructions.docx
IT202ProjectTwoKnowledgeBaseDocumentTemplate.docx
IT 202 Project Two Knowledge Base Document Template
Complete this template by replacing the bracketed text with the relevant information. Repeat these steps for each user problem that you want to create a knowledge base document for.
Gather Information
[Insert text]
Identify What Has Changed
[Insert text]
Create a Hypothesis
[Insert text]
Determine the Appropriate Fix
[Insert text]
Implement the Fix
[Insert text]
Ensure Satisfaction
[Insert text]
Document the Solution
[Insert text]
1
image1.png
IT202ProjectTwoTranscriptforChatBox.docx
IT 202 Project Two Transcript for Chat Box
This document contains brief chat conversations of users who contacted the IT help desk via the online chat box.
Request Service Chat
User: Good morning. I am trying to edit a PDF, but I can’t.
Help Desk: Good morning! May I ask who I am speaking to? I am happy to assist you.
User: This is Rachelle Lynne Smith. Do you need my employee ID number?
Help Desk: Yes, that would be wonderful. I need to confirm your identity. It also makes it easier if we need to submit any tickets on your behalf, depending on the issue and if I am unable to troubleshoot it.
User: Sure. My ID number is 287937836.
Help Desk: Thank you. So what version of Acrobat Pro do you have on your desktop?
User: I don’t know. I don’t think I have it because when I am trying to open this file from an email I received, a message appears.
Help Desk: What does the message say?
User: Something about an error, and access denied.
Help Desk: Can you confirm that you have Acrobat Pro on your desktop computer?
User: I do not have Acrobat Pro on my desktop computer. That’s why I am messaging you.
Help Desk: Understood. Thank you for this confirmation. Acrobat Pro is a standard, supported product, and we will install the software for you. I can easily create a service ticket to have the software installed. The response time for new software installations is within 2 hours. Is this an acceptable time frame for you?
User: Sure, that’s fine. As long as I have it installed on my desktop by the end of my shift, I should have enough time to complete what I need to do before the deadline. What’s the next step?
Help Desk: Once the ticket has been reviewed, a desktop technician will arrive at your desk to install the software. This is why I want to ensure that this time frame is acceptable for you.
User: Understood. I do have a meeting to attend in five minutes that should last about an hour. Mind making a note of that on the ticket?
Help Desk: Of course. Happy to do so. Now I will need more of your information to create a ticket for you, and so that we can install Acrobat Pro on your desktop in a timely manner.
(Conversation continues. User provides detailed information.)
Incident Service Chat
User: Hello, my name is Larry Adams. I cannot print from my desktop computer. I work in Finance.
Help Desk: In reviewing your call history, I can see that we have sent a technician to look at this problem several times. I am sorry the service call is taking more than one occurrence to resolve your problem. In most cases, we are equipped to handle diagnosis and repair on our first visit to your workstation. However, this situation does require that I dispatch another technician to look at your computer. I am going to send a senior technician on our staff. This is our standard procedure for situations like this.
User: Okay. How long will this take? I need to print something before my next meeting, which is in 30 minutes.
Help Desk: With our workflow, our technicians are expected to resolve an issue within five hours. Since this has been an ongoing issue and you have a meeting soon, I will escalate the issue right away and will see if we can get a technician at your desk within the next 15 minutes. If we do not have a technician available, do you have an alternative plan?
User: Yes, I can share what I need to share electronically, but I want everyone to have a printed copy so they can take notes.
Help Desk: Okay, I am glad to hear that. I am escalating this issue now. Please stand by, and I will update you with further information.
(Conversation continues until technician arrives and troubleshoots the issue.)
1
image1.png
IT202ProjectTwoTranscriptforPhoneCalls.docx
IT 202 Transcript for Phone Calls
This document includes the transcript of the user phone calls. These are phone calls of users who called the help desk for technical support.
Call #1
Help Desk: Good morning. This is William from the IT help desk. How may I help you?
User: Hi. My password is expired. I’m getting really annoyed, because I just reset my password two days ago, and I either already forgot it, or the system is not recognizing my new one.
Help Desk: Okay, I’d be happy to go through the process of resetting your password for you. It should take only a few minutes. May I ask who I am speaking to?
User: Jane. Jane Cole. I am an employee.
Help Desk: Hello, Jane. I am happy to be assisting you. Can you provide me with your employee ID number so I can verify your identity? Then can you also provide me with your mobile phone number?
User: Yes. My employee ID number is ID18902364940. My phone number is (###) ###-####.
Help Desk: Thank you, Jane. I am sending you a text message that contains a link to reset your password. After you click on that link, enter your employee-issued email address in the User ID field. Then type in what you want your new password to be. You will have to type it twice for confirmation.
User: Okay, let me try that… It’s still not working.
Help Desk: Hmmm. What does the screen say?
User: I cannot see the text on my mobile device because the words are too small. There are red words though.
Help Desk: Ah, okay. There is a chance that your new passwords do not match. Please try again, typing your passwords in slowly, and ensuring that they match. It also could be that you’re using the same password that you used in the past, and the system doesn’t allow for passwords to be used again. The red text usually comes up in either of those two cases.
User: Okay. That’s the issue. I must be using a repeat password. I get so confused with all of these passwords.
Help Desk: It is easy to get confused; there are a lot of passwords to remember. Let me know when you receive confirmation that the password has been reset.
User: Okay, it looks like it let me through the system.
Help Desk: Now that you’ve successfully logged onto your mobile, I recommend trying your desktop log-in. If you have any issues with that, please give us a call back, alright?
User: Sounds good. Thank you.
Help Desk: Jane, it was my pleasure to assist you. Have a great day.
Call #2
Help Desk: Good morning. This is Victoria from the IT help desk. How may I help you?
User: Hi. My name is Frederick. I am unable to access Wi-Fi in the café in our building. When I was at my desk, the Wi-Fi was working alright. Can you help me connect to the Wi-Fi using my MacBook Pro?
Help Desk: Hello, Frederick. I would be happy to assist you with your Wi-Fi connection. Could you tell me what department you work in and your email address?
User: Great! I work in Marketing. My email is [email protected]
Help Desk: Frederick, you stated you are using a MacBook Pro. What version of the macOS is installed on your MacBook Pro?
User: Victoria, it’s currently using macOS Catalina, 10.15.4.
Help Desk: Frederick, thank you for that information. Please do the following:
· Click on the Wi-Fi symbol on the upper right corner of your screen, then choose the CafeNet connection
· You will see a pop-up screen. Please enter your employee username and the password for that username.
· You will receive another pop-up that says “Connected to CafeNet.”
· You can now start a web browser. Please confirm.
User: Okay, give me a second… Victoria, I was able to reach our main website via this Wi-Fi. Thanks so much for helping me.
Help Desk: Frederick, it was my pleasure to assist you. Please give the help desk a call if you have any other questions about accessing the SNHU student Wi-Fi.
User: Have a good day.
2
image1.png
IT202ProjectTwoFiveTickets1.docx
IT 202 Project Two Five Tickets
This document contains the five ticket submissions received by the help desk that you work for. The information in these tickets is fictional to provide you with practice as to what an actual IT help desk ticket looks like in the profession. While some of the information on the tickets is necessary for you to troubleshoot, other information is for additional context.
Ticket number INC0352668
Ticket Number INC0354837
Ticket Number INC0352699
Ticket Number INC0352723
Ticket Number INC035946
1
image4.png
image5.png
image1.png
image2.png
image3.png
image6.png
Instructions.docx
IT 202 Project Two Guidelines and Rubric
Competency
In this project, you will demonstrate your mastery of the following competency:
· Use troubleshooting skills and techniques to solve computing problems
Scenario
You are an IT support specialist at a help desk for a large company. Recently, the company created a knowledge base that IT support specialists can refer to when a user calls in with technology issues. The knowledge base has been helpful because the help desk receives many tickets and calls for what turn out to be the same issues. When IT support specialists have documents to refer to during a call or the review of a ticket, the knowledge base increases efficiencies and provides users with more consistent and higher quality support.
As an IT support specialist at the company’s help desk, you are assigned to create documentation that will be added to the company’s knowledge base. This document will speak to the frequent issues that users have experienced within the past 30 days. To complete this project, you will review five tickets, two audio recordings of user calls, and a chat transcript from users who experienced technical issues. Then you will use your troubleshooting skills to assess the underlying causes of the users’ reported symptoms and how they should be resolved.
Directions
Given the scenario and for the purposes of this project, create a user report that describes the IT issues that users have been experiencing and the resolution, where the resolution was found, whether the help desk had to look around for a solution, or the steps that you took to resolve the issues. Then create a knowledge base document to assist other IT support specialists in troubleshooting these user issues in the future.
In order to successfully complete this project, you first must follow the troubleshooting process, which is “a systematic approach to problem solving” (TestOut PC Pro, 2020, Section 2.6.2). Within your user report and knowledge base document, you must make it clear that you have followed each of these steps based on the issues users experience in the tickets, phone calls, and chat transcript.
1. Gather information by identifying the problems that users most commonly experience and that they call the IT help desk for, given the scenario.
2. Identify what has changed in the system that may have caused each problem.
3. Create a hypothesis of what you think the probable cause for each issue is, based on the information gathered in the first step. You may want to come up with several hypotheses.
4. Determine the appropriate fixes by testing your hypotheses. You will also want to account for possible ramifications that you could cause by fixing the issue based on your hypotheses.
· Given the tickets, phone calls, and chat transcript, the IT support specialist assisting those users at the time may or may not have attempted the same fix. If they did, state that they determined the appropriate fix already. If you believe that they did not identify a probable cause, explain what you would have done differently if you were the one assisting the user.
5. Explain how you would implement the fix to verify the cause of the problem if you were the IT support specialist assisting the users at the time.
· In some cases, it could be that the IT support specialist had already implemented the fix, but explain whether you would have handled it similarly or differently.
6. Describe how you would ensure satisfaction of the user after the issue has been resolved.
· In some cases, it could be that the IT support specialist demonstrated ensuring satisfaction, while they did not in other cases. In these circumstances, explain whether you would have done this in the same or a different way.
7. Document the solution within your knowledge base document. Provide how-to’s or steps for common user issues, as well as any lessons learned from troubleshooting these issues that would be beneficial for other IT help desk support specialists to know.
What to Submit
To complete this project, you must submit the following:
User Report and Knowledge Base Document Using the template linked in the Supporting Materials area below, fill in the content and submit your user report and knowledge base document as a Word document. Sources should be cited according to APA style.
Supporting Materials
The following resources may help support your work on the project:
Reading: Five Tickets Before starting your project, review the ticket submissions from the last 30 days to determine the common technical issues that users are experiencing.
Audio Recordings: User Phone Call One and User Phone Call Two Listen to the phone conversations that users and other IT support specialists have been having. During these calls, users express the issues that they are currently facing. For the purposes of this project, the phone calls do not include how the support specialist responds and their resolution.
A text-only version is available: Transcript for Phone Calls .
Reading: Transcript for Chat Box Review an online conversation between a desktop user and an IT support specialist. Reviewing this document can help you determine what another common issue is. As in the phone calls, the chat conversation does not include the resolution.
Template: Knowledge Base Document Template Use this template to create a knowledge base document for your team.