IT Help Desk Prep
Diagnose carefully. Explain clearly. Protect the user.
Learn a repeatable support process, computer and network foundations, secure account support, ticket writing, and practical troubleshooting through complete lessons and fictional workstations.
Learn the foundations, one lesson at a time
Read each lesson, try its task, and pass the knowledge check to complete it automatically. You can practice or take an exam at any time.
1The help desk role and the support conversation
Understand the job, boundaries, and a respectful first response.
The help desk role and the support conversation
Understand the job, boundaries, and a respectful first response.
Learning goals
- Distinguish incidents from service requests
- Ask useful opening questions
- Work within your authority
Support is a service job
A help desk connects people who need technology with the teams and processes that keep it working. An incident is an unplanned interruption or reduction in service. A service request asks for something standard, such as approved software or access. Classifying these accurately routes work and avoids treating every request as an emergency.
Begin by introducing yourself, verifying the requester through the approved method, and asking what they were trying to do. Ask what happened instead, when it last worked, and whether anyone else is affected. Listen without blaming the person or assuming that a vague description identifies the cause.
Translate technical language
Say “the laptop is connected to Wi-Fi but cannot reach the website” instead of using unexplained acronyms. Repeat the problem back so the person can correct it. Ask permission before taking actions that interrupt work, such as closing an application, restarting a device, or starting an approved remote session.
Never imply the user is foolish. Frustration often comes from being unable to do a job. Explain your next step and what you expect to learn. If you need time, give an honest update or follow-up plan rather than promising a fix you cannot guarantee.
Authority and escalation
Entry-level support does not mean unrestricted administrator access. Use only approved tools and permissions. A security incident, possible data loss, shared service outage, or task outside your access needs the designated team. Protect evidence and document what you have done.
A strong escalation includes the user, device, impact, exact symptom, tests, results, and next owner. Do not send credentials or unnecessary personal details. Stay responsible for the handoff according to policy; sending a ticket somewhere is not the same as verifying it reached the right team.
Try the task
Write four opening questions for that call.
Incomplete
2A troubleshooting method you can repeat
Gather evidence, isolate a cause, test safely, and confirm the result.Locked — complete previous lessons
A troubleshooting method you can repeat
Gather evidence, isolate a cause, test safely, and confirm the result.
Learning goals
- Separate symptoms from causes
- Change one thing at a time
- Verify and document a fix
Define the problem before fixing
Record the exact error, affected task, device, timing, scope, and recent changes. “Slow” can mean startup, an application, a network transfer, or an entire shared service. Ask for a concrete example you can reproduce without exposing private information.
Compare working and failing conditions: another user, device, application, cable, or approved network. This narrows the location of the problem. A successful comparison is evidence, not permission to bypass security controls or copy another person’s account.
Use the least disruptive test
Form a plausible hypothesis and choose a safe test. If only one external display fails, inspect power, input selection, and cables before changing operating-system settings. Change one variable at a time so you know which action affected the result.
Before a restart or reset, save work and explain possible interruption. Factory resets, deleting profiles, mass updates, and disabling protection are not routine first steps. Get authorization and a recovery plan for destructive or broad changes.
Verify the original task
After a possible fix, repeat the task that originally failed. Confirm the result with the user, not just the absence of an error. A printer showing “online” does not prove the user can print the intended document.
Document tests, outcomes, final action, and confirmation. If the issue persists, avoid repeating the same unsuccessful step indefinitely. Escalate with evidence, possible next tests, and the impact on work. Close only according to the employer’s criteria.
Try the task
Explain why doing five changes at once makes diagnosis weaker.
Incomplete
3Computer hardware and safe handling
Learn what major components do and how to check simple physical faults.Locked — complete previous lessons
Computer hardware and safe handling
Learn what major components do and how to check simple physical faults.
Learning goals
- Explain RAM, storage, CPU, and peripherals
- Check connections methodically
- Recognize hardware safety limits
Recognize the major parts
The CPU executes instructions. RAM is working memory used by running applications. Storage retains files when power is off. A device can have ample free storage but too little available RAM for its workload. More capacity in one component does not automatically solve every performance problem.
Peripherals include keyboards, mice, displays, printers, docks, and headsets. Note model, connection type, and asset tag. A dock can carry power, video, and network connections, so one dock issue may affect several apparently separate functions.
Check power and signal paths
For a dark display, distinguish computer power from monitor power. Confirm the correct display input, secure connections, and compatible cables. Try a known-good approved cable or port if permitted. A USB-C connector shape alone does not guarantee every device supports video or the same charging capability.
For a laptop that will not charge, inspect the approved adapter, outlet, connector, and visible damage. Do not force connectors or substitute an unsuitable charger. Record whether charging lights appear and whether the machine can run on battery.
Stop when handling is unsafe
A swollen battery, burning smell, liquid damage, exposed wiring, or excessive heat requires the employer’s safety procedure. Stop using the equipment and notify the appropriate team. Do not open a power supply or puncture a battery.
Internal repairs require authorization, manufacturer procedures, power isolation, and appropriate handling. Do not remove parts while power is connected. Protect against static discharge when trained to do so. Ordinary help desk work often ends with a safe hardware escalation rather than a repair.
Try the task
List two symptoms that mean you should stop using a device.
Incomplete
4Operating systems, applications, and updates
Work with settings, approved software, processes, and versions.Locked — complete previous lessons
Operating systems, applications, and updates
Work with settings, approved software, processes, and versions.
Learning goals
- Separate an OS issue from an application issue
- Use approved installation sources
- Plan updates and restarts
Know the layers
An operating system manages hardware, accounts, files, and running software. An application performs a user task. A browser problem may involve the browser, extension, site, account, or network. Avoid calling every failure “Windows broken” before isolating it.
Record the OS and application versions when relevant. Menu names vary by version and platform. Follow the current manufacturer guidance and employer procedure rather than relying on a screenshot from an old guide.
Processes and workload
When a machine is slow, use an approved system monitor to observe CPU, memory, disk, and application usage. High usage identifies a clue, not proof that a process is malicious. Background updates, indexing, and heavy applications can use resources legitimately.
Do not terminate an unfamiliar process just because it is busy. Save work, identify the process, and use a safe application close or restart when appropriate. Escalate recurring faults or suspicious activity without destroying useful logs.
Install and update responsibly
Obtain software through the employer’s approved catalog or verified vendor source. Random driver sites, pirated applications, and unsolicited “repair” tools can create security and licensing problems. Verify authorization before granting elevated privileges.
Updates may require a restart or temporarily interrupt service. Coordinate timing, save work, and follow backup or rollback instructions when required. Do not indefinitely ignore updates, but do not push a disruptive change to shared systems without the responsible team’s plan.
Try the task
Draft a short restart request that respects the user’s work.
Incomplete
5Files, backups, permissions, and cloud sync
Prevent accidental loss while resolving file-access problems.Locked — complete previous lessons
Files, backups, permissions, and cloud sync
Prevent accidental loss while resolving file-access problems.
Learning goals
- Distinguish sync from backup
- Recognize permission problems
- Protect data before changes
Files have locations and ownership
Know whether a file is on local storage, a shared drive, or an approved cloud service. A shortcut points to something; it is not necessarily the document itself. Record the path without placing confidential contents in the ticket.
Access can depend on the user, group, device, and service permissions. If one user cannot access a shared folder while others can, verify the intended entitlement. Do not make the folder public or borrow another person’s login as a shortcut.
Sync is not automatically backup
Sync keeps locations aligned. A deletion or bad edit may also sync. Backup and version history provide recovery options according to their configuration. Check which mechanism actually exists before promising that a lost file can be recovered.
Before removing a profile, resetting an app, or reinstalling software, determine where unsynced files live and follow the approved preservation process. A visible cloud icon does not prove every file is uploaded. Verify status and avoid moving data to personal storage.
Handle changes conservatively
When storage is full, review approved cleanup options and retention rules. Ask the owner before deleting work files. Emptying a recycle bin can remove an easy recovery path. Do not treat size alone as evidence that a file is disposable.
When recovery is needed, stop actions that could overwrite data and contact the responsible team. Document the last known working version, file location, and suspected change. Recovery attempts and access changes should be authorized and traceable.
Try the task
Explain the danger of granting “everyone” access to fix one user’s issue.
Incomplete
6Network foundations: Wi-Fi, IP, DNS, and reachability
Separate local connection, addressing, and name-resolution issues.Locked — complete previous lessons
Network foundations: Wi-Fi, IP, DNS, and reachability
Separate local connection, addressing, and name-resolution issues.
Learning goals
- Explain Wi-Fi versus internet access
- Describe IP, gateway, DHCP, and DNS
- Use comparisons to isolate scope
Connectivity has several stages
A Wi-Fi connection joins a wireless network; it does not guarantee access to every internet or internal service. A wired connection can help compare symptoms when it is approved. Ask whether one device, one site, or many users are affected.
An IP address identifies an interface on a network. A default gateway provides a route beyond the local network. DHCP commonly supplies addressing settings. DNS translates a host name to addressing information. These are different jobs, so a failure in one does not prove all have failed.
Read clues without overclaiming
If a known internal service works by an approved IP test but not by its name, name resolution is a useful hypothesis. If neither works, broaden the investigation. A failed ping alone is not definitive because a device or firewall may block that type of request.
On some Windows IPv4 networks, a 169.254 address may indicate the device did not receive normal DHCP settings. Check the intended network and approved diagnostic procedure. Do not invent a static address or alter organization DNS settings without permission.
Choose safe connection checks
Check airplane mode, Wi-Fi enablement, approved network name, signal, and whether other users have the same issue. Record errors and whether a restart or reconnect is authorized. Use current vendor guidance and preserve settings before disruptive changes.
Avoid restarting shared routers during business hours as an individual experiment. Do not connect a company device to an unapproved hotspot to evade security restrictions. An outage affecting many users belongs with the network team and incident process.
Try the task
Describe DNS in one plain-language sentence.
Incomplete
7Printing, docks, displays, and everyday peripherals
Resolve common device complaints without disrupting shared resources.Locked — complete previous lessons
Printing, docks, displays, and everyday peripherals
Resolve common device complaints without disrupting shared resources.
Learning goals
- Identify the correct printer and queue
- Check basic peripheral connections
- Verify with a real task
Follow the print path
Check the selected printer, connection, device status, paper, and visible error. A user may send a job to a similarly named printer or a PDF destination. Determine whether the issue affects one document, one computer, or all users of the device.
A stuck queue may prevent later jobs from printing. Follow the approved queue procedure and understand which jobs you are canceling. Do not clear every colleague’s job without authorization. Use current printer and operating-system instructions for driver changes.
Docks and headsets need compatible settings
For a dock problem, check power, compatible cables, connected ports, and whether a directly attached peripheral works. Record what changes when the dock is removed. Avoid guessing that every USB-C connection provides the same features.
For a headset, verify the selected input and output in the application and operating system, mute state, volume, and connection. A microphone that works in one app suggests an app setting or permission issue rather than proving the headset is broken.
Protect documents and shared equipment
A printer may contain confidential documents, queued data, or saved destinations. Do not use sensitive material as a test page. Confirm an approved test prints and that the user can repeat the required task.
Escalate physical jams, damage, or shared-network faults beyond your training. Follow manufacturer instructions rather than forcing parts. Offer an approved alternative printer when appropriate and communicate the incident’s scope.
Try the task
Name three checks before reinstalling a printer driver.
Incomplete
8Accounts, MFA, and safe remote support
Help users regain access without bypassing identity protections.Locked — complete previous lessons
Accounts, MFA, and safe remote support
Help users regain access without bypassing identity protections.
Learning goals
- Follow account recovery rules
- Protect MFA and passwords
- Obtain consent for remote sessions
Identity verification is required
A familiar name, urgent tone, caller ID, or knowledge of a supervisor is not enough to authorize an account change. Use the employer’s approved verification method. If verification fails, follow escalation rather than inventing a workaround.
Resetting a password and granting access are different actions. A password reset does not authorize new privileges. Requests for elevated access need the designated approval, scope, and expiration where applicable.
Never collect secret credentials
The user should enter their password privately. Do not ask for passwords, one-time codes, recovery codes, or approval of an unexpected MFA prompt. Repeated unsolicited prompts can indicate an attempted account compromise and need security escalation.
Use approved enrollment and recovery procedures when a phone is lost or replaced. Do not disable MFA just because it is inconvenient. Record nonsecret evidence, such as time and affected account, in the authorized ticket.
Remote access should be transparent
Use only the organization’s approved remote-support tool and process. Explain the session, obtain required consent, and ask the user to close private material where appropriate. The user should know when you have control and when the session ends.
Do not install remote tools from unsolicited calls, leave unattended access without authorization, or share a technician account. If suspicious activity appears, stop routine troubleshooting and use the security incident workflow.
Try the task
Write a response when a user offers their MFA code.
Incomplete
9Phishing and security incident recognition
Spot suspicious requests and report without destroying evidence.Locked — complete previous lessons
Phishing and security incident recognition
Spot suspicious requests and report without destroying evidence.
Learning goals
- Inspect sender and destination
- Recognize credential and payment traps
- Report using an independent channel
Look beyond the display name
A message may display a real executive’s name while using a different sender address. Inspect the actual sender, destination, attachment, and request. A professional logo or correct grammar does not prove a message is trustworthy.
Unexpected urgency, credential requests, unusual payment instructions, and pressure to bypass normal approval deserve independent verification. Check through a known contact or approved portal, not the phone number or link supplied by the suspicious message.
Avoid interacting with suspicious content
Do not click a questionable link or open an attachment merely to investigate as a beginner. Use the approved reporting tool or send the required evidence to the security team. Be careful about forwarding live links to coworkers.
If the user already interacted, gather what happened and when without blame. Follow security instructions for isolation, credentials, and evidence. Do not erase logs or run random cleanup programs that may interfere with response.
Security and service work together
A possible compromise changes priority and ownership. Explain that specialized support is needed and preserve useful timestamps, message details, and affected device information. Avoid placing confidential message contents into an unnecessary public channel.
A report is valuable even when the message turns out to be legitimate. Encourage prompt, honest reporting. Do not promise that an attack is impossible because antivirus is present or a site uses HTTPS.
Try the task
List three signs you would inspect in a suspicious email.
Incomplete
10Tickets, priority, service targets, and handoffs
Create records another technician can act on.Locked — complete previous lessons
Tickets, priority, service targets, and handoffs
Create records another technician can act on.
Learning goals
- Write factual notes
- Prioritize impact and urgency
- Distinguish workaround from resolution
A ticket is an operational record
Include the requester, asset or service, exact symptom, onset, scope, and relevant error. Separate what the user reported from what you observed. Use clear timestamps and steps so another technician does not have to start over.
Record tests and results, not just “tried everything.” Never include passwords or MFA codes. Write neutrally and professionally because the record may be reviewed by coworkers, managers, or the requester.
Priority comes from policy
Impact describes how much work is affected; urgency describes how quickly action is needed. A shared outage can outrank one person’s inconvenience. A suspected security issue may need urgent routing even if the device still works. Apply the employer’s defined matrix.
A service target or SLA is a commitment defined by the organization, not a reason to promise an unsupported resolution time. State the current status, next owner, and update plan. Notify the right team if a target or major incident process is at risk.
Resolution and handoff are different
A workaround lets work continue temporarily. Resolution addresses the incident sufficiently under policy. Document both without pretending they are the same. “Escalated” means another authorized team must act, not that the original fault disappeared.
A useful handoff explains the problem, affected scope, action already taken, results, and requested next step. Confirm assignment and communication. Closing a ticket merely to improve a statistic weakens service and the record.
Try the task
Write a better note than “printer broken, sent to IT.”
Incomplete
11Practice shift: prioritization, service, and change control
Combine technical judgment with reliable workplace habits.Locked — complete previous lessons
Practice shift: prioritization, service, and change control
Combine technical judgment with reliable workplace habits.
Learning goals
- Triage a queue
- Communicate during delays
- Respect approved change procedures
Work the queue deliberately
Read impact, urgency, age, and assigned ownership. Follow the priority matrix and any major incident process. Do not simply pick the easiest ticket or the loudest requester. Keep waiting tickets visible and document why they are waiting.
Several reports of the same symptom may indicate one shared incident. Link or route them under policy rather than treating each as unrelated. Communicate the known issue and approved workaround without exposing other users’ information.
Do not hide mistakes
If an action creates a new problem, stop, document it, notify the responsible person, and follow recovery instructions. Avoid making additional unapproved changes to conceal the error. Accountability and timely communication reduce further damage.
Change control applies when a modification can affect shared service, security, or business operations. Approved timing, testing, rollback, and authorization protect users. A technically possible change is not automatically an authorized change.
Finish the shift cleanly
Update ownership, current status, pending approvals, user communication, and outstanding tasks. A handoff should let the next shift continue without guessing. Sign out of privileged and remote sessions and secure company equipment.
Use a simple personal learning record without confidential data: the kind of problem, what you learned, and which approved reference helped. Repeated issues can lead to better knowledge articles, but publishing internal details requires approval.
Try the task
Draft a handoff for an unresolved incident awaiting vendor advice.
Incomplete
12Getting ready for interviews and your first support job
Translate independent practice into honest evidence.Locked — complete previous lessons
Getting ready for interviews and your first support job
Translate independent practice into honest evidence.
Learning goals
- Build a small practice portfolio
- Answer scenario questions clearly
- Plan continuing study
Show your method, not just an answer
Employers may ask how you would handle a problem you have not seen. Explain how you gather facts, check scope, choose safe tests, verify results, document, and escalate. Saying “I would search online” is incomplete unless you also explain source verification and authority.
Describe a customer-service example using situation, action, and result. School, volunteering, retail, and family tech support can show patience and communication. Do not exaggerate independent practice into paid enterprise experience.
Prepare a safe portfolio
Create fictional tickets, network vocabulary explanations, and before-and-after troubleshooting notes. Explain the reasoning behind each step. Use only systems you own or are allowed to use, and never expose another person’s files, usernames, or credentials.
Match further study to actual job postings. Some employers value certifications, while others prioritize experience, college coursework, or customer support skills. Check current provider objectives and costs before paying for an exam.
Learn well after hiring
Expect onboarding on internal tools, privacy, security, assets, permissions, and service procedures. Ask where the knowledge base lives, how incidents are prioritized, who approves changes, and when to escalate.
Success as a beginner means dependable safe progress, not pretending to know everything. Review feedback, take accurate notes, ask focused questions, and identify one gap at a time. This course develops foundations but does not make you a systems administrator.
Try the task
Practice answering: “What would you do if you do not know the fix?”
Incomplete
Reference resources and next steps
Course content reviewed October 2026. Training requirements, products, and procedures vary; check the current official instructions.
Microsoft Support: Windows Wi-Fi troubleshootingMicrosoft Support: Printer troubleshootingNIST: Recognizing phishingCISA: Small and medium business security resourcesCompTIA: A+ certification and current exam objectivesBLS: Computer support specialist career overviewIndependent job preparation—not CompTIA, Microsoft, or other vendor certification. This course does not authorize changes to an employer’s devices or networks. Use approved procedures and supervision in real work. Never submit real passwords, recovery codes, or company information here.