Topic outline

  • How can I receive help with my technology issues

    Always call Helpdesk if you are unable to resolve your own password issues  

    What makes a good ticket? 

    As a general rule the more help you can provide in your email the faster we can solve the issue.  A helpful ticket includes a concise subject line summarizing the problem and an email body with a description of the problem in terms of what you were expecting and what actually happened.  

    It would help us if you include as many of the following points in the original Helpdesk ticket, or follow up with any as they become available.

    • Clear subject line (do not put the explanation in the subject line) 
    • What you were doing and what technology you were working with. eg Were you on the Windows workstation in the Learning Commons?  A Chromebook on wireless?
    • What is the label name on the device?  ie E002R010SW01
    • What steps did you take to cause the problem?
    • What were you expecting to happen?
    • What actually happened?
    • What was the approximate time the issue first occurred and how often it occurs? Can you recreate the problem or is it apparently random? 
    • Include screenshot(s) if possible (e.g. expected output, actual output, and error messages.)
    • Any troubleshooting steps you've already taken. For example, can you log out and try again, or do you have to reboot the entire workstation?  Were you able to work around the problem and accomplish your task anyway? How?
    • Send the message to only.  There is no need to CC or address it directly to any IT staff, it will get assigned by the Helpdesk to the appropriate individual who will update you on the progress.
    • Include one issue on a ticket. If you have two problems, please file two tickets.
    • Do not ever include passwords in a ticket.

    If you are requesting Apps to be added to School iPads please go to IT Support and our iPads and Apps page to learn what an app request through Helpdesk should include.