ICT career guide
What Does a Systems Administrator Do? Duties, Skills & Career Path
Servers · Access · Recovery
Discover the daily work of systems administrators, solve realistic workplace problems and try a beginner Linux administration lab.
Technology in action
Keep essential systems dependable.Quick answer
What does a systems administrator do?
A systems administrator installs, configures, maintains, monitors and secures an organisation’s servers and computer services. The role includes operating systems, account permissions, updates, backups, troubleshooting and recovery. Administrators help ensure that the technology people rely on remains available and properly protected. [1]
- Real daily duties
- Kenyan career pathway
- Step-by-step Linux lab
1. What does a systems administrator actually manage?
Picture a school with 40 computers. Teachers store lesson plans, students open shared learning materials, and the administration office maintains records. Behind these ordinary activities may be servers that store files, identify authorised users and deliver applications.
A server is a computer or software system that provides a service to other computers. A client is a computer or application that requests the service. A common file-access path looks like this:
1 · Client
The student signs in to a school computer and opens a class folder.
2 · Network and identity
The client contacts the server. Relevant systems help identify the user and determine whether access is permitted.
3 · File server
The server makes the requested files available if the applicable permissions allow it.
Servers can be physical machines, virtual machines or hosted computing services. A virtual machine behaves like a separate computer while running in software on suitable underlying hardware.
| System | Typical administrative task |
|---|---|
| Server operating system | Install, configure, update and troubleshoot Windows Server or Linux |
| File server | Manage shared files, storage and permissions |
| Identity service | Maintain user accounts, groups and authorised access |
| Application services | Check availability and coordinate supported application maintenance |
| Backups | Monitor backup jobs and test the ability to restore information |
| Monitoring | Investigate alerts, performance changes and system logs |
| Virtual infrastructure | Maintain virtual machines and their assigned resources |
On a phone, swipe sideways across wide tables to read all columns.
In a small workplace, one administrator may cover several of these responsibilities. Larger organisations often divide them among infrastructure, network, security and application teams.
2. Seven main duties of a systems administrator
Install and configure servers
Administrators prepare server operating systems, configure approved services, establish access settings and check that the new system works. A business opening another branch might need a file service that staff can use from authorised computers.
Manage user accounts and permissions
Administrators create or disable accounts, manage groups and apply approved permissions. A finance officer may need access to financial documents while a student should not. The least-privilege principle means giving people only the access necessary for their work. [2] [3]
Monitor server health
They observe storage capacity, processor and memory behaviour, service availability, backup results and logs. An alert that a filesystem is almost full is a reason to investigate before applications stop writing data.
Troubleshoot failures
When staff cannot open a shared folder or a service stops responding, the administrator checks evidence, compares affected and unaffected users, narrows the cause and tests a controlled correction.
Maintain security and updates
They apply approved security updates, review configurations and help protect privileged access. Important systems should be updated through a planned process with appropriate recovery options.
Manage backups and recovery
They check backup jobs, protect copies and confirm that information can actually be restored. A backup that has never been tested may fail at the moment it is needed. [4]
Document and automate work
Administrators record important settings, authorised changes and incident findings. They also use scripts to automate suitable repetitive work, such as collecting health information from authorised systems.
3. What does a systems administrator do each day?
Much of the job is preventive maintenance rather than emergency repair. A typical day might involve the following activities:
| Illustrative time | Activity | Reason |
|---|---|---|
| 8:00 a.m. | Review alerts and backup results | Find problems reported overnight |
| 9:00 a.m. | Investigate incidents | Restore affected services |
| 10:30 a.m. | Process authorised account requests | Keep access current and appropriate |
| 11:30 a.m. | Check storage, logs and service health | Identify developing problems |
| 2:00 p.m. | Prepare scheduled updates | Maintain reliability and security |
| 3:30 p.m. | Verify changes and document work | Record what happened and hand over unresolved work |
The timetable is illustrative, not a fixed employment schedule. Some administrators support systems outside normal office hours or take part in on-call rotations. [1]
4. How does an administrator decide what to fix first?
Suppose three requests arrive together. One employee cannot open an optional template; a school examination system is unavailable to all users; and a storage warning reports that a server is nearly full.
Administrators weigh impact (who and what is affected), urgency (how quickly consequences may worsen) and risk (possible loss of data, security or service). Under a typical incident policy, the examination outage requires immediate coordination. The storage warning also needs prompt assessment, particularly if the usage is growing quickly.
Incident
An unplanned service interruption. Example: a shared examination application is unavailable.
Service request
A planned, authorised need. Example: create an account for a new staff member.
Controlled change
An approved modification. Example: patch a server during a maintenance window.
A six-step troubleshooting method
- Confirm the symptoms. Find out exactly what failed, when and for whom.
- Gather evidence. Review messages, logs, monitoring information and recent changes.
- Isolate the likely cause. Compare working and failing accounts, computers or services.
- Make an authorised correction. Choose a suitable change and follow the approval process.
- Verify functionality and security. Check that the original issue is resolved without creating another problem.
- Document and follow up. Record findings, actions, tests and prevention measures.
5. Practical example: Students cannot open their shared folder
A school in Migori has a central file server. Eight students receive an Access denied message when opening their assignment folder, but other students can open it.
The administrator should not assume the server itself has failed. The fact that some students still have access is an important clue.
- Find the common factor. Identify the affected students, their class group and the computers they used.
- Check the exact message. “Access denied” may suggest authentication or permissions; a “network location not found” message suggests a different line of investigation.
- Verify server availability. Confirm that the file service responds and review relevant logs.
- Check approved permissions. Compare the group memberships and folder access of affected and unaffected students.
- Correct the verified cause. If the authorised class group was accidentally omitted, restore the correct permission through the approved procedure.
- Test both sides. Confirm that affected students regain access and unauthorised students remain excluded.
- Record the incident. Write what failed, what evidence was found, which change was approved and the result.
| Field | Illustrative incident record |
|---|---|
| Problem | Eight students receive Access denied for a shared assignment folder |
| Scope | One newly created class group |
| Evidence | File service available; relevant group permission missing |
| Correction | Approved group access restored |
| Verification | Affected users can open files; other access remains restricted |
| Follow-up | Review how new class groups receive folder permissions |
6. Practical example: A company server is 96% full
A manufacturing company’s payroll server generates an alert: the filesystem containing important application data is 96% full. The application still responds normally. What should the administrator do?
- Confirm the measurement. Identify the exact filesystem and check available capacity.
- Investigate the trend. Determine when usage increased and whether it is still growing.
- Identify the files involved. Inspect authorised storage reports, logs and recent application activity.
- Assess consequences. Check retention requirements, available backups and risks before moving or deleting anything.
- Carry out the approved remedy. Correct excessive logging, implement a suitable rotation policy or expand storage where justified.
- Verify and monitor. Confirm that space is available and that the application continues to work.
Suppose the problem arose because an application began producing unusually large diagnostic logs. Deleting those logs immediately could remove evidence needed for support or audit. The administrator first checks retention requirements and involves the relevant application team.
| Observation | What it might mean | Next investigation |
|---|---|---|
| One filesystem nearly full | Files or logs have grown | Inspect that filesystem and recent growth |
| Memory usage looks high | Active programs and caching use RAM | Check available memory and actual system behaviour |
| Service shows failed | A service or dependency may be unavailable | Inspect service state, logs and recent changes |
| Backup failed | A dependency or configuration may need attention | Read the specific backup job error |
7. Practical example: Recovering a deleted SACCO report
An employee at a SACCO accidentally deletes a financial report. The administrator confirms the file name, location and last known good version. After checking the approved recovery options and obtaining any necessary approval, the administrator restores a suitable copy to a safe location and verifies the contents.
The incident is recorded along with the backup source, recovery time and verification result. A restored file must be usable and must not expose information to the wrong people.
Two recovery concepts worth knowing
RPO · Recovery Point Objective
The point in time to which data must be recoverable after a disruption. It influences the maximum tolerable loss of recent data.
RTO · Recovery Time Objective
The intended time window for restoring a system or function before the interruption causes unacceptable operational impact.
For example, if an organisation sets a four-hour RPO, its recovery arrangements should support recovering data to within that specified window. A two-hour RTO is a recovery target, not proof that every outage will be resolved in two hours. [4] [5]
8. Beginner Linux lab: Inspect, copy and verify
This beginner exercise uses Linux in a personal or authorised training environment. The first three commands only display information. They do not install software or change system settings.
Activity A — Inspect system health
Open the Linux terminal. Run each command and read the result before continuing. Use the command-line guide and official manual pages when you need more explanation. [6] [7] [8] [9]
df -h / shows storage information for the filesystem containing the root directory. free -h displays memory and swap information; check the available memory field. uptime reports how long the computer has been running and shows load averages.
| Measurement | Illustrative reading | Interpretation |
|---|---|---|
| Filesystem usage | 96% | Investigate storage use and growth; do not delete unfamiliar files |
| Available memory | 3.1 GiB | A number to interpret alongside application symptoms and workload |
| Uptime | 4 days | A descriptive measurement, not a fault by itself |
| File-sharing service | Responding | Suggests the service is reachable, but does not prove every user can access every folder |
Activity B — Restore a practice file and verify it
The next example creates an isolated temporary practice directory, writes a harmless fictional note, copies it, restores another copy and compares the contents. Run each line in the same shell session.
If the original and restored copies are identical, the final command prints Files match. The temporary folder may be cleared by the operating system; this is not a durable backup or a substitute for an organisation’s protected backup system.
Write your five-line lab report
- Record the filesystem you inspected and how much space remains.
- Write the available-memory figure, without treating high “used” memory as a diagnosis.
- Record the system uptime.
- State whether the copied practice file matched the original.
- Explain your next investigative step if a business filesystem were 96% full.
9. Essential skills for systems administrators
The strongest foundation combines operating systems, networking, security and disciplined troubleshooting.
| Skill | Why it matters | Beginner practice |
|---|---|---|
| Computer fundamentals | Understand files, storage, memory and operating systems | Inspect device settings and learn the basic parts |
| Networking | Understand IP addresses, DNS, DHCP and connectivity | Diagram two computers reaching a shared server |
| Linux | Read services, logs and filesystem information | Use read-only terminal commands |
| Windows administration | Understand accounts, groups and server services | Learn the purpose of Active Directory |
| Security | Limit access, manage patches and protect credentials | Design permissions for fictional users |
| Backup and recovery | Know how protected data can be restored | Restore a fictional test file and compare contents |
| Automation | Reduce repetitive work reliably | Write a small Bash or PowerShell script |
| Communication | Explain incidents and changes to other people | Write a one-page incident report |
Useful terms: DNS helps systems resolve names; DHCP can assign network settings; a system log records events; a patch fixes or improves software; a service provides a function that users or applications may depend on.
10. Which tools does a systems administrator use?
| Technology | Typical purpose |
|---|---|
| Windows Server | Host and manage Windows-based services and infrastructure |
| Linux | Host and administer Linux-based services |
| Active Directory | Manage identities, groups and directory resources |
| PowerShell | Perform administration and automation tasks |
| Bash | Work with Linux shell commands and scripts |
| Windows Event Viewer | Read important Windows event records |
| Linux logs | Investigate operating-system and service activity |
| Hyper-V / VMware | Manage virtualised computing environments |
| Monitoring systems | Track service health, alerts and availability |
| Backup software | Create, protect and restore backed-up information |
Knowing the names of products is less important at the beginning than understanding what each tool solves. Technologies differ from employer to employer, so learn concepts first and products second.
11. Systems administrator vs other ICT roles
| Role | Main emphasis | Practical example |
|---|---|---|
| IT Support Technician | Assists users and resolves device or application problems | Helps a teacher whose computer cannot print |
| Systems Administrator | Maintains servers, operating systems, identity and central services | Fixes an organisation-wide access-permission problem |
| Network Administrator | Operates networking infrastructure and connectivity | Investigates a failed switch or routing issue |
| Cloud Engineer | Builds and operates cloud-hosted infrastructure | Configures hosted application resources |
| DevOps Engineer | Improves software delivery and automation | Automates application builds and deployment |
These are typical emphases, not rigid boundaries. Smaller employers may combine roles; larger organisations often separate them. For a wider career comparison, read NIT’s IT fields in Kenya guide.
12. How to become a systems administrator in Kenya
There is no single universal hiring route. Employers consider the skills, qualifications and experience required for each job. A practical beginner pathway is:
- Start with computer fundamentals. Learn operating systems, files, storage and safe device use.
- Learn networking. Understand IP addresses, DNS, DHCP, switches and shared services.
- Practise Windows and Linux. Use isolated practice machines to explore accounts, logs and services.
- Study security and recovery. Learn least privilege, patching, backup verification and incident handling.
- Build a portfolio. Keep short reports, diagrams and test evidence from your own lab.
- Gain supervised experience. Explore ICT support, junior infrastructure work, internship or industrial attachment.
- Specialise gradually. Develop deeper Windows, Linux, virtualisation, automation or infrastructure-security skills.
A Kenyan qualification that aligns with the field
KASNEB offers the Diploma in Computer Networks and Systems Administration (DCNSA). Its published syllabus has three levels: computing fundamentals; networking and server-related skills; and network troubleshooting, setup and server maintenance. KASNEB lists a KCSE mean grade of C- or another accepted qualification among its entry routes. [10]
Level One
Introduction to Computing Systems, communication and ethics, information-systems support and computer applications.
Level Two
Computer Networking, Network Operating Systems, Windows Server Roles and Features, and Network Security.
Level Three
Network Troubleshooting, Network Setup and Server Maintenance.
This is one recognised route, not a legal requirement for every systems-administrator job. Read individual vacancies to determine whether an employer requires a diploma, degree, certifications or particular experience.
Beginner portfolio projects worth keeping
- A documented Linux system-health report with your own observations.
- A labelled diagram showing a school’s clients, network and file server.
- A fictional account-permissions test using only an isolated practice environment.
- A harmless file-copy-and-verification exercise.
- An incident note describing symptoms, evidence, authorised correction and test results.
For related training opportunities, consult NIT’s current ICT programme list. [13]
13. Systems administrator jobs and pay in Kenya
Schools, healthcare providers, financial institutions, factories, public bodies and ICT companies need people who understand the systems supporting their work.
Actual job advertisements show the range of employer requirements. An NCBA Group systems-administrator vacancy with a closing date of 17 July 2026 emphasised Red Hat Enterprise Linux, Windows infrastructure, virtualisation, patching, backups and business continuity. This is a historical example of an experienced role, not an active vacancy. [11]
What do systems administrators earn?
WageIndicator’s Kenya occupational guide reports an indicative 2026 monthly pay range of KSh 43,691–101,845 for the majority of workers in its systems-administrator category. This is a third-party occupational estimate, not a starting-pay guarantee or a standard salary paid by every employer. [12]
Actual opportunities and earnings depend on the employer, required responsibilities and experience. Read current vacancies for their precise requirements rather than relying on a job title alone.
Is the career changing?
Cloud platforms and automation can reduce some routine administration work, while creating a need for people who can manage integrated infrastructure and recover services. The U.S. Bureau of Labor Statistics projects a decline in its wider network-and-computer-systems-administrator category for 2025–2035; that United States projection is not a forecast for Kenya. [1]
14. Is systems administration a good career for you?
The field may suit you if you enjoy understanding how technology works behind the scenes. You might like investigating faults, working carefully with technical configurations, documenting procedures and helping services stay available.
The job also requires patience and sound judgement. A configuration change on an important server can affect many people. Learning to observe, plan, get authorisation and verify results is just as important as learning commands.
15. Frequently asked questions
Is a system administrator the same as a systems administrator?
Yes. These terms commonly refer to the same broad occupation; “sysadmin” is a common abbreviation.
Does a systems administrator need programming skills?
Not every role requires advanced software development. Basic Bash or PowerShell scripting is useful for automation and repeatable administration.
Should beginners learn Linux or Windows first?
Start with the system you can practise reliably, then learn the other. Your eventual employer or specialisation may place more emphasis on one.
Can you become a systems administrator without a degree?
Some employers accept relevant diplomas, certifications and experience, while others specify a degree. Always check the vacancy requirements.
Can systems administrators work remotely?
Some tasks can be handled through approved secure remote-management tools. Other duties require physical access or on-site work.
Is systems administration the same as cybersecurity?
No. Administrators implement system-level security controls, but specialist security roles may have broader responsibilities for risk, detection, investigation and response.
16. What should you learn first?
If you are a complete beginner, start with computer fundamentals and basic networking. Then practise simple Linux and Windows tasks on your own or an authorised training machine. Once you can gather system information and explain what it means, progress to accounts, services, backups and controlled recovery activities.
Observe the system → collect evidence → identify the cause → make an approved change → verify and document the result.
This sequence is a useful foundation for responsible systems administration.
Your next step
Register for ICT training at Newton Institute of Technology
Build practical ICT foundations at Newton Institute of Technology (NIT) in Migori Town. Explore Basic and Advanced Computer Skills, Cybersecurity, DevOps and other available ICT programmes. Admissions can help you choose a relevant starting point for your goals.
Sources and references
- [1] U.S. Bureau of Labor Statistics (2026). Network and Computer Systems Administrators, Occupational Outlook Handbook. Role, responsibilities and outlook.
- [2] NIST Computer Security Resource Center. Least Privilege, glossary.
- [3] Microsoft Learn. Manage User Accounts in Active Directory Users and Computers in Windows Server.
- [4] NIST SP 800-34 Revision 1. Contingency Planning Guide for Federal Information Systems, including backup and RPO.
- [5] NIST Computer Security Resource Center. Recovery Time Objective, glossary.
- [6] Linux manual pages. free(1), display free and used memory.
- [7] Linux manual pages. df(1), report filesystem space usage.
- [8] Linux manual pages. uptime(1), system uptime and load averages.
- [9] Ubuntu. The Linux command line for beginners, official tutorial.
- [10] KASNEB. Diploma in Computer Networks and Systems Administration (DCNSA): entry requirements and three levels.
- [11] NCBA Group (2026). System Administrator, historical vacancy closing 17 July 2026.
- [12] WageIndicator (2026). Systems administrators: jobs and salaries in Kenya.
- [13] Newton Institute of Technology. Official ICT programmes and admissions information.
Workplace incidents and lab measurements are illustrative. Salary information is an independent estimate, not an assured wage. This guide was updated 10 November 2026.