Systems Administration
Systems administration is the work of keeping an organization’s computers and services available, secure, consistent, and recoverable. It connects business needs to the day-to-day care of servers, endpoints, accounts, software, networks, data, and operational records across their full lifecycle.
itInfrastructure and operations | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Systems Administration
Systems administration is the operating discipline that keeps computing systems useful over time. A system may be a physical server, virtual machine, cloud instance, employee endpoint, or appliance. Administrators provision it, control access, maintain software and configuration, observe behavior, protect data, respond to failure, and retire it without losing required records.
The work is broader than command execution. A command changes one system at one moment. Administration connects many systems to an organization’s intended state and supplies evidence that the state was reached.
The operating model
A managed environment has several interacting layers:
service requirements and policy
↓
inventory and ownership
↓
identity, access, and management channels
↓
operating systems, software, and configuration
↓
compute, storage, network, and facilities
↓
telemetry, records, backup, and recovery
Requirements state what a service must do and which constraints apply. Inventory identifies the assets that provide it, their owners, and their dependencies. Management channels carry approved changes. The operating system and installed software implement the service. Telemetry and records show what happened. Backup and recovery provide a path back when normal operation fails.
No layer is sufficient alone. A monitored server with no tested recovery path is observable but not recoverable. A patched server with an unknown owner may still be unmanaged. A configuration baseline without an inventory cannot show which assets comply.
Desired state and actual state
Desired state is the approved condition of a system. It includes operating-system settings, installed software, service configuration, accounts, permissions, and security controls. Actual state is what exists now.
Configuration drift is a difference between those states. Drift can come from an emergency repair, an incomplete deployment, a manual edit, a failed update, or a dependency that changed outside the administrator’s control. Some drift is authorized and some is not. The operational task is to detect it, determine its cause and impact, then reconcile it through an approved change.
An inventory, baseline, and change record answer different questions:
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://learn.microsoft.com/en-us/windows-server/administration/overview
Supports
- Windows Server management approaches from local tools through System Center and Azure Arc
- Management approach comparison by scale, interface, connectivity, and operating purpose
- Windows Server overview link rationale and quiz coverage
- https://learn.microsoft.com/en-us/windows-server/administration/manage-windows-server
Supports
- Server inventory, local and remote administration, automation, monitoring, updates, backup, and recovery documentation paths
- Cross-platform course scope and service-path quiz rationale
- https://documentation.ubuntu.com/server/
Supports
- Linux server administration scope and route into current host-level tasks
- Platform lifecycle, access, storage, networking, security, and backup documentation
- Ubuntu Server link rationale and beginner quiz coverage
- https://ubuntu.com/server/docs/how-to/security/user-management/
Supports
- Administrative privilege through sudo and attributable user identities
- Named administrative identity quiz answer
- https://csrc.nist.gov/pubs/sp/800/128/upd1/final
Supports
- Configuration policy, baselines, control, monitoring, and security-focused configuration management
- Desired state, actual state, drift, change records, and configuration-management loop
- Intro, slides, cheatsheet, link rationale, and quiz answers about baselines and drift
- https://csrc.nist.gov/pubs/sp/800/40/r4/final
Supports
- Enterprise patch management as identifying, prioritizing, acquiring, installing, and verifying updates
- Preventive-maintenance framing, planning factors, and staged change controls
- Patch link rationale and staged-rollout quiz answer
- https://csrc.nist.gov/pubs/sp/800/92/final
Supports
- Enterprise log-management infrastructure and operational process
- Log generation, transport, storage, access, analysis, and retention concerns
- Log-management link rationale and actionable-alert context
- https://csrc.nist.gov/pubs/sp/800/34/r1/upd1/final
Supports
- Information-system contingency planning, recovery priorities, strategies, exercises, and plan maintenance
- Alternate processing, alternate equipment, and alternate location as recovery approaches
- Recovery, restore testing, alternate control paths, link rationale, and quiz answers
- https://sre.google/sre-book/practical-alerting/
Supports
- Monitoring as evidence for service behavior, change impact, and incident diagnosis
- Time-series alerting concepts and the distinction between collected data and actionable conditions
- Monitoring link rationale and alert quiz answer
- https://sre.google/sre-book/managing-incidents/
Supports
- Coordinated incident roles and management under service disruption
- Incident flow, ownership, communications, and link rationale
- https://sre.google/sre-book/emergency-response/
Supports
- Tested rollback, alternative access methods, out-of-band communication, and proactive failure exercises
- Evidence preservation, narrow recovery actions, alternate paths, and related quiz answers
- https://sre.google/sre-book/postmortem-culture/
Supports
- Post-incident records covering impact, mitigation, causes, and tracked follow-up actions
- https://www.puppet.com/docs/puppet/5.5/architecture.html
Supports
- Catalogs as desired state and the agent-controller configuration flow
- Agent-based configuration-management model and drift-reconciliation quiz answer
- https://github.com/sindresorhus/awesome
Supports
- Required discovery starting point for the Awesome Sysadmin list
- https://github.com/awesome-foss/awesome-sysadmin
Supports
- Ecosystem discovery for Cockpit, NetBox, restic, Healthchecks.io, Zabbix, and Salt
- Classification of selected projects within system-administration practice
- https://cockpit-project.org/documentation.html
Supports
- Cockpit installation, deployment, usage, and server-interface documentation
- Cockpit Awesome Link rationale
- https://netbox.readthedocs.io/en/stable/introduction/
Supports
- NetBox as an infrastructure source of truth for intended network state
- Inventory and source-of-truth distinctions
- NetBox Awesome Link rationale and inventory quiz answer
- https://restic.readthedocs.io/en/stable/
Supports
- Backup repositories, snapshots, integrity checks, restoration, retention, scripting, and troubleshooting
- Restore-test workflow and restic Awesome Link rationale
- https://healthchecks.io/docs/
Supports
- Heartbeat monitoring for scheduled jobs and alerting on missing signals
- Backup, certificate, and synchronization job examples
- Healthchecks.io Awesome Link rationale
- https://www.zabbix.com/documentation/current/en/manual
Supports
- Host and service data collection, triggers, alerts, discovery, and distributed monitoring
- Zabbix Awesome Link rationale
- https://docs.saltproject.io/en/latest/contents.html
Supports
- Remote execution, desired-state configuration, orchestration, events, and operating-system modules
- Salt Awesome Link rationale and product placement
- https://www.microsoft.com/en-us/system-center
Supports
- Datacenter deployment, configuration, management, monitoring, virtualization, service management, and data protection
- System Center Landscape placement
- https://learn.microsoft.com/en-us/azure/azure-arc/servers/
Supports
- Cloud-based management of servers outside Azure
- Azure Arc Landscape placement
- https://aws.amazon.com/systems-manager/
Supports
- Central node inventory and remote management across AWS, hybrid, and multicloud environments
- AWS Systems Manager Landscape placement
- https://www.redhat.com/en/technologies/management/ansible
Supports
- Enterprise automation orchestration across an IT estate
- Ansible Automation Platform Landscape placement
- https://www.puppet.com/products/puppet-enterprise
Supports
- Enterprise desired-state enforcement, infrastructure control, compliance, and hybrid operations
- Puppet Enterprise Landscape placement
- https://www.chef.io/products/chef-infrastructure-management
Supports
- Policy-based infrastructure configuration, testing, desired-state adherence, and compliance evidence
- Progress Chef Landscape placement
- https://www.redhat.com/en/technologies/management/satellite
Supports
- RHEL provisioning, content, patch, configuration, compliance, and lifecycle management
- Red Hat Satellite Landscape placement
- https://ubuntu.com/landscape
Supports
- Ubuntu fleet enrollment, inventory, patching, auditing, access, compliance, repositories, and API management
- Canonical Landscape product placement
- https://www.suse.com/products/multi-linux-manager/
Supports
- Mixed-Linux patching, content lifecycle, configuration, monitoring, and compliance
- SUSE Multi-Linux Manager product placement
- https://help.hcl-software.com/bigfix/11.0/platform/Platform/Getting_Started/c_bigfix_introduct.html
Supports
- Single-agent endpoint visibility, management, compliance, patching, distribution, and operating-system deployment
- HCL BigFix Landscape placement
- https://www.manageengine.com/products/desktop-central/desktop-administration-overview.html
Supports
- Cross-platform server, desktop, and mobile lifecycle management from one endpoint console
- Patch, software, inventory, configuration, deployment, and remote support scope
- Endpoint Central Landscape placement
- https://www.ninjaone.com/endpoint-management/
Supports
- Cross-platform endpoint visibility, patching, configuration, deployment, automation, and remote diagnosis
- NinjaOne Landscape placement
- https://www.unix.org/unix_history.html
Supports
- UNIX development beginning in 1969
- POSIX.1 publication in 1988
- Timeline events and their operating-system context
- https://kernel.googlesource.com/pub/scm/linux/kernel/git/nico/archive/+/v0.01
Supports
- Linux 0.01 release date and initial source-release scope
- Linux timeline event
- https://docs.cfengine.com/docs/archive.bak/cf2-enterprise.html
Supports
- CFEngine project beginning in 1993 for automated installation and maintenance of networked computers
- CFEngine timeline event
- https://www.ssh.com/academy/ssh
Supports
- SSH creation and public release in 1995 as a secure remote-administration protocol and implementation
- SSH timeline event
- https://www.openssh.org/history.html
Supports
- OpenSSH project origins and OpenSSH 1.2.2 shipping with OpenBSD 2.6 on 1999-12-01
- OpenSSH portability work and timeline event
- https://www.puppet.com/about
Supports
- Puppet founding in 2005 to address manual configuration
- Puppet timeline event
- https://devblogs.microsoft.com/powershell/its-a-wrap-windows-powershell-1-0-released/
Supports
- Windows PowerShell 1.0 release on 2006-11-14
- PowerShell as a shell and scripting environment for system administration
- PowerShell timeline event
- https://0pointer.net/blog/projects/systemd.html
Supports
- systemd public introduction on 2010-04-30
- Dependency-aware service management, supervision, socket activation, and parallel startup proposal
- systemd timeline event
