This guide describes how the Tech Liaison role will function within guidelines established in our service level agreement (SLA). The goal is to help our organization to gain control of their tech support services and costs. This model calls for our management level ‘CIO’ to make strategic decisions and ‘tech liaisons’ to take initial problem reports and make a first brief attempt at troubleshooting the problem.Ground Rules1. Document the problem. Write down any Windows or application error messages on the computer. Describe the situation when the problem occurred. Fill out the problem report as completely as you can.2. Spend no more than 5-10 minutes troubleshooting the problem.3. If you are able to resolve the problem, document the steps taken to resolve it. This information may be able to help the next person with the problem.4. If you are not able to resolve the problem, determine the priority level of the problem using the SLA and report it to the CIO.Level 1: Mission criticala. An urgent problem that seriously affects a substantial number of usersb. A problem that relates to a data or application security issuec. A problem for in which a system is inoperable and there is no workaroundLevel 2: Urgenta. An urgent problem that affects a single userb. A problem that may involve a mid-to low level security issuec. A problem for which there is no workaround and impedes job performanceLevel 3: Importanta. A problem which prevents the user from fully using technology systems and applicationsb. A workaround is available but may be time-consumingc. A problem which inconveniences one or more usersLevel 4: Not time sensitive / annoyancea. A problem which results in minor inconvenience to one or more usersb. A problem which can be solved with a workaroundc. An intermittent problem causing minor disruption to work flowd. Any small technology project that can be scheduled in advance5. Send the completed problem report to the CIO for prioritization. The CIO will call on the necessary resources to resolve the issue.6. Communicate to the affected users. Tell them how the problem will be resolved and when.7. Capture information about the resolution of the problem and keep it on file. As appropriate, use this information to create lists of the most frequently reported problems and the solutions, and communicate this information to tech liaisons and/or staff.Ten Troubleshooting Issues1. Computer doesn’t start up at alla. Check to ensure that the power cords and power strip are firmly connected. Check all cable and power connections. Restart the power strip or check to see that the reset button is in the on position.b. Check to see that there is electricity to the outlet. Check the status of other devices connected to the power strip, like the monitor.c. Check to see if the monitor or computer is running. Look for the ‘on’ light and listen for a fan or hard drive.d. If the hard drive and fan are making noise, check to see if the monitor connection to the computer is snug. If so, try substituting monitors with someone who has a working monitor.2. Computer gets stuck starting up the operating systema. Press “F8” at start up, and try launching in “Safe Mode”. Restart and see if computer reboots normally, or with scan disk.b. Do a ‘hard restart’ of the computer by powering it down. Restart twice, assuming that scan disk will run on the first restart.3. The mouse cursor does not movea. Check the cable connections between mouse and the computer to see if they are connected, and if so to the right ports.b. Clean the mouse.c. Swap the mouse temporarily with one that you know works on another machine.4. The keyboard doesn’t responda. Check the cable connections between the keyboard and the computer to see if they are connected, and if so to the right ports.b. Swap the keyboard temporarily with one that you know works on another machine.5. The computer/terminal will not log onto the networka. Determine whether anyone in the office can log in on any other computerb. Can the staff member log on with their own password to someone else’s computer?c. Attempt to log onto the computer with your log ind. Check to be sure the password being used is correct, and that the CAPS LOCK key is off.e. Check network cables, remove and reinsert.f. Ask if there were network-related error messages at startup.6. The email client is not working properlya. Determine whether the computer is on the network.b. Determine whether other staff members in the same office are able to get into their mail.c. Check to be sure the password being used is correct, and that the CAPS LOCK key is off.d. Determine whether the computer has Internet access7. The computer/terminal will not printa. Determine whether the computer is on the network.b. Check to see if anyone in the office can print from any other computer to that printer, or any other printer.c. Turn printer on and off. Check printer network cables, remove and reinsert.d. Check for a paper jam or other problem at the printer. Press the ‘reset’ button on the printer.e. Restart the printer.f. Delete all files in the printer queue.g. Check the ‘print’ dialog box in the application to be sure that the right printer has been selected, and that the right driver for that printer has been installed.8. The computer/terminal will not access the Weba. Determine whether the computer is on the network.b. Determine whether anyone in the office can get onto the web from any other computerc. Click on the start menu, choose ‘run’, type ‘winipcfg’. Press the ‘release all’ and ‘reset all’ buttons, in that order.9. A software application doesn’t worka. Try opening the application directly, rather than through a file.b. Identify if any files have been deleted from the computer recently. If so, software may need to be reloaded.10. A file will not opena. Determine whether the file has the proper suffix or a valid file name. If not, save a copy, rename the file, and try to open it.b. Open the application that created the file first and load it from within the program.c. Files that have the .zip suffix have been compressed and will need to be decompressed.