Top 100 Vocabulary for Adults | IT Support & Systems Administration Professionals
IT support and systems administration vocabulary is the language of keeping everyday technology usable. Professionals connect users, devices, accounts, operating systems, networks, permissions, updates and backups while translating technical failures into clear next actions.
This profession-specific flagship belongs to the eduKate Adult Vocabulary for Professionals system. It complements Cloud & DevOps Professionals, Cybersecurity Professionals and Customer Service & Support.
The Four Banks
Devices & Systems: device, workstation, laptop, server, operating system, application, process, service, driver, firmware, hardware, storage, memory, CPU, peripheral, printer, monitor, endpoint, virtual machine, domain, directory, account, profile, configuration, inventory.
Identity & Access: user, administrator, authentication, authorisation, password, MFA, credential, role, group, permission, access control, least privilege, lockout, reset, provisioning, deprovisioning, joiner, mover, leaver, policy, certificate, encryption, VPN, remote access, privilege.
Troubleshooting & Incidents: symptom, issue, incident, request, ticket, priority, severity, troubleshoot, reproduce, diagnose, root cause, workaround, fix, restart, reinstall, patch, update, rollback, log, event viewer, ping, trace, latency, outage, escalation.
Operations & Support: backup, restore, recovery, image, deployment, endpoint management, monitoring, alert, antivirus, endpoint protection, firewall, patch management, maintenance window, change, asset, lifecycle, licence, compliance, documentation, knowledge base, SLA, response time, resolution time, handover, user education.
Top 100 IT Support & Systems Administration Vocabulary: Working Meanings
| # | Word | Professional meaning |
|---|---|---|
| 1 | Device | A piece of computing equipment used by a person or system. |
| 2 | Workstation | A user computer configured for professional work. |
| 3 | Laptop | A portable personal computer. |
| 4 | Server | A system providing services or resources to other computers. |
| 5 | Operating system | Core software managing hardware and applications. |
| 6 | Application | Software designed to perform user or business tasks. |
| 7 | Process | A running instance of a program. |
| 8 | Service | A background or network-accessible function provided by a system. |
| 9 | Driver | Software enabling an operating system to communicate with hardware. |
| 10 | Firmware | Low-level software embedded in hardware. |
| 11 | Hardware | The physical components of a computing system. |
| 12 | Storage | Hardware or services used to persist data. |
| 13 | Memory | Fast temporary storage used by active programs. |
| 14 | CPU | The central processing unit executing computing instructions. |
| 15 | Peripheral | An external device connected to a computer. |
| 16 | Printer | A device producing physical output from digital documents. |
| 17 | Monitor | A display device used to present visual output. |
| 18 | Endpoint | A user or server device connected to an organisational network. |
| 19 | Virtual machine | A software-defined computer running its own operating system. |
| 20 | Domain | A managed administrative boundary for users, devices or network resources. |
| 21 | Directory | A service storing identities, groups and related information. |
| 22 | Account | A digital identity used to access systems. |
| 23 | Profile | User-specific settings and data. |
| 24 | Configuration | Settings controlling system behaviour. |
| 25 | Inventory | A structured record of devices, software and assets. |
| 26 | User | A person authorised to use a system. |
| 27 | Administrator | A user with elevated system-management rights. |
| 28 | Authentication | Verification of identity. |
| 29 | Authorisation | Determination of what an identity may access or do. |
| 30 | Password | A secret used as an authentication factor. |
| 31 | MFA | Multi-factor authentication using more than one independent factor. |
| 32 | Credential | Information used to prove identity or access rights. |
| 33 | Role | A named collection of permissions associated with a job or function. |
| 34 | Group | A collection of users managed together for access or policy. |
| 35 | Permission | An authorised action on a resource. |
| 36 | Access control | Mechanisms restricting systems and data to authorised users. |
| 37 | Least privilege | Granting only the minimum access required. |
| 38 | Lockout | Temporary or administrative prevention of account access. |
| 39 | Reset | Restoring a password, account state or configuration. |
| 40 | Provisioning | Creating and configuring access or devices for use. |
| 41 | Deprovisioning | Removing access and resources when no longer needed. |
| 42 | Joiner | A new employee or user entering the organisation. |
| 43 | Mover | A user changing role, team or access requirements. |
| 44 | Leaver | A user departing the organisation and requiring access removal. |
| 45 | Policy | A rule or principle governing system use. |
| 46 | Certificate | A digital credential used to establish identity or trust. |
| 47 | Encryption | Transformation of data to protect confidentiality. |
| 48 | VPN | A virtual private network creating a protected remote network connection. |
| 49 | Remote access | Connecting to systems from another location. |
| 50 | Privilege | An elevated right to perform sensitive system actions. |
| 51 | Symptom | The observable behaviour reported by a user or system. |
| 52 | Issue | A matter requiring technical support. |
| 53 | Incident | An unplanned interruption or reduction in service quality. |
| 54 | Request | A user asking for information, access or a standard service. |
| 55 | Ticket | A tracked record of an issue or request. |
| 56 | Priority | The order in which support work should receive attention. |
| 57 | Severity | The seriousness of technical impact. |
| 58 | Troubleshoot | Systematically investigate a technical problem. |
| 59 | Reproduce | Cause the reported problem to occur again under controlled conditions. |
| 60 | Diagnose | Identify the most likely cause of a technical issue. |
| 61 | Root cause | A fundamental causal factor whose correction may prevent recurrence. |
| 62 | Workaround | A temporary alternative enabling progress while the main issue remains. |
| 63 | Fix | A change correcting the technical problem. |
| 64 | Restart | Stop and start a system or service again. |
| 65 | Reinstall | Remove and install software again. |
| 66 | Patch | A software update correcting defects or vulnerabilities. |
| 67 | Update | A newer version or change applied to software. |
| 68 | Rollback | Revert to an earlier known-good version or configuration. |
| 69 | Log | A recorded sequence of system events. |
| 70 | Event viewer | A tool displaying operating-system event logs. |
| 71 | Ping | A basic network test checking reachability and round-trip response. |
| 72 | Trace | A diagnostic view of network path or system events. |
| 73 | Latency | The delay between request and response. |
| 74 | Outage | A period during which a service is unavailable. |
| 75 | Escalation | Raising an issue to higher expertise, authority or urgency. |
| 76 | Backup | A recoverable copy of data or system state. |
| 77 | Restore | Returning data or systems from backup. |
| 78 | Recovery | Restoring usable service after failure. |
| 79 | Image | A packaged operating-system or device configuration used for deployment. |
| 80 | Deployment | Installing and configuring software or devices for users. |
| 81 | Endpoint management | Central administration of user devices. |
| 82 | Monitoring | Ongoing observation of system health. |
| 83 | Alert | A notification indicating a potentially important system condition. |
| 84 | Antivirus | Software intended to detect and block malicious code. |
| 85 | Endpoint protection | Security controls protecting user devices and servers. |
| 86 | Firewall | A control filtering network traffic according to rules. |
| 87 | Patch management | The process of testing, scheduling and applying software patches. |
| 88 | Maintenance window | A scheduled period reserved for system changes. |
| 89 | Change | A planned modification to technology or configuration. |
| 90 | Asset | A device, licence or system of organisational value. |
| 91 | Lifecycle | The stages from acquisition through use to retirement. |
| 92 | Licence | Permission to use software under defined terms. |
| 93 | Compliance | Conformity with applicable technology policies or requirements. |
| 94 | Documentation | A written record of configuration, support and procedures. |
| 95 | Knowledge base | A structured collection of support information and solutions. |
| 96 | SLA | A service level agreement defining formal support commitments. |
| 97 | Response time | The time until support first responds. |
| 98 | Resolution time | The time until an issue is resolved. |
| 99 | Handover | Transfer of issue context and responsibility. |
| 100 | User education | Teaching users how to work safely and effectively with technology. |
The User’s Description Is a Starting Point
“The internet is down” may mean Wi-Fi, DNS, VPN, one application, one device or the entire network. Strong support language narrows the failure domain before applying fixes.
Scenario: User Cannot Sign In
Check identity, account status, password, MFA, lockout, network path and whether the correct system is being used. A password reset is useful only when the password is actually the problem.
Seven-Day IT Support Vocabulary Plan
| Day | Practice |
|---|---|
| 1 | Map devices, operating systems, services and accounts. |
| 2 | Separate authentication, authorisation and permission. |
| 3 | Practise narrowing vague user symptoms. |
| 4 | Trace one incident from ticket to resolution. |
| 5 | Review backup, patching and endpoint-management language. |
| 6 | Recall 75+ IT support terms by function. |
| 7 | Write a one-page support summary with cause, fix, verification and prevention. |
Complete the Digital Experience Wing
- UX/UI Designers
- Cloud & DevOps Professionals
- Database & Platform Professionals
- Cybersecurity Professionals
Conclusion
IT support and systems-administration vocabulary makes everyday technical failure diagnosable. It helps professionals distinguish user symptoms from system causes, access problems from application problems, and quick fixes from durable operational improvement.