Skip to content

Skills Demonstrated

Overview

The osTicket IT Support Service Desk Lab provided practical experience across Service Desk operations, Windows troubleshooting, network diagnostics, user support, knowledge management, and technical documentation.

The skills demonstrated through the project are grouped into six areas: Service Desk Operations, Windows Troubleshooting, Network Troubleshooting, User Support, Knowledge Management, and Technical Documentation.

Service Desk Operations

Ticket Management

Created, investigated, updated, resolved, and closed support tickets using osTicket.

Demonstrated understanding of the ticket lifecycle from initial submission through final closure.

Ticket Triage

Reviewed reported symptoms and categorized incidents according to the affected system or service.

Ticket Assignment

Demonstrated manual ticket assignment to a support technician when individual ownership was required.

Depending on the Service Desk workflow, tickets may also remain routed to a department or team queue until a technician takes ownership.

Priority Management

Applied appropriate ticket priorities based on the nature of the reported issue.

SLA Awareness

Worked with SLA information and ticket due dates to understand expected service timelines.

Help Topics

Used Help Topics to categorize incoming support requests and organize the Service Desk workflow.

Internal Notes

Documented technical investigation, diagnostic findings, actions taken, and resolution details using internal ticket notes.

Customer Communication

Provided customer-facing responses using clear, user-friendly language appropriate for end users.

Ticket Closure

Closed incidents after the reported problem had been resolved and functionality verified.

Windows Troubleshooting

The project included practical troubleshooting on a Windows workstation.

Windows Shell Troubleshooting

Investigated a black screen after login and restored the Windows desktop by manually launching "explorer.exe".

Windows Privacy & Permissions

Investigated a Zoom microphone access problem and corrected the relevant Windows microphone privacy permissions.

Windows Language Configuration

Configured Amharic language support and keyboard input switching on the Windows workstation.

Windows Settings

Used Windows Settings to investigate and modify system configuration, including microphone privacy permissions and language and keyboard settings.

Network Troubleshooting

The project included a practical network troubleshooting scenario involving Wi-Fi and Internet access.

IP Configuration

Used:

ipconfig /all

to examine the workstation's IPv4 address, subnet information, default gateway, DHCP information, and DNS configuration.

DNS Troubleshooting

Used:

nslookup google.com

to test hostname resolution and examine DNS behavior.

Connectivity Testing

Used:

ping google.com

to test external connectivity and packet loss.

Evidence-Based Diagnosis

Interpreted network diagnostic results rather than assuming that a reported Internet problem automatically indicated a DNS or network configuration failure.

The investigation demonstrated the importance of distinguishing between the user's reported symptom and the actual condition observed during technical testing.

User Support

Technical support also requires the ability to communicate effectively with people who may not have a technical background.

The project demonstrated:

  • Clear troubleshooting instructions
  • User-friendly technical explanations
  • Customer-facing ticket responses
  • Appropriate escalation awareness
  • Separation of technical notes from customer communication
  • Verification of the user's reported problem after troubleshooting

Knowledge Management

A Knowledge Base was developed containing eight public FAQs covering common Level 1 support issues.

The FAQs were organized into: - Windows & Software - Network & Connectivity - Accounts & Access - Hardware & Peripherals

This demonstrated the ability to:

  • Identify common and recurring support problems.
  • Create structured troubleshooting documentation.
  • Write instructions for non-technical users.
  • Organize support information into categories.
  • Provide safe, step-by-step self-service guidance.
  • Explain when an issue should be escalated to IT Support.

Technical Documentation

The project documentation demonstrates the ability to record technical work in a structured and reproducible format.

Documentation includes:

  • Lab environment configuration
  • Service Desk configuration
  • Ticket workflow
  • Troubleshooting methodology
  • Incident investigation
  • Diagnostic evidence
  • Identified causes where supported by available evidence
  • Resolution steps
  • Verification results
  • Internal ticket documentation
  • Customer communication
  • Lessons learned

The documentation was designed so that another technician could understand the work performed without needing to repeat the entire investigation.

Tools & Technologies

Technology / Tool| Demonstrated Use osTicket| Service Desk and ticket management Ubuntu Server| Linux server environment Apache| Web server MariaDB| Database backend VirtualBox| Virtualization Windows| End-user troubleshooting Task Manager| Windows diagnostics Windows Settings| System, privacy, and language configuration "ipconfig /all"| Network configuration diagnostics "nslookup"| DNS testing "ping"| Connectivity testing Git| Version control MkDocs| Technical documentation Material for MkDocs| Documentation presentation GitHub Pages| Portfolio documentation hosting

Transferable IT Support Skills

The project also demonstrates several skills that transfer directly to a professional Service Desk environment.

Problem Solving

Breaking unclear or complex technical problems into smaller, testable components.

Troubleshooting Methodology

Following a structured troubleshooting process rather than applying random fixes.

Evidence-Based Diagnosis

Using observable technical evidence to narrow down possible causes and determine appropriate actions.

Attention to Detail

Recording relevant technical information and documenting troubleshooting actions accurately.

Communication

Explaining technical issues and solutions in language appropriate for end users.

Documentation

Creating useful records that support future troubleshooting, knowledge sharing, and service continuity.

Verification

Testing the original user-facing problem after applying a resolution rather than assuming that a configuration change was successful.

Ownership

Following incidents through investigation, resolution, documentation, customer communication, and closure when assigned responsibility for the ticket.

Skills Summary

The project demonstrates practical capability in:

IT Support • Service Desk Operations • Ticket Management • Windows Troubleshooting • Network Troubleshooting • DNS Diagnostics • Application Support • User Support • Windows Configuration • Knowledge Base Management • Technical Documentation • Incident Resolution • Problem Solving • Customer Communication • Evidence-Based Troubleshooting

These skills provide a practical foundation for junior IT Support, Help Desk, Service Desk, Desktop Support, Technical Support, and Network Support roles.