Systems and Network Administration
Introduction
Networks and Embedded Systems – 1st
2025-2026
What is a System?
▪ A system: collection of components organized
to achieve a shared purpose.
▪ Defined procedures, routines, and methods to
accomplish tasks.
▪ Every system includes inputs, outputs, and
feedback mechanisms.
What is a Network?
▪ A network is a set of interconnected devices and
peripherals (wired or wireless).
▪ Enables sharing of hardware and software
resources among multiple users.
What is Network Administration?
▪ Management of network infrastructure (routers,
switches, connectivity).
➢ Focus: design, configuration, monitoring, and
troubleshooting of communication networks.
What is System Administration?
▪ Branch of engineering focused on managing
computer systems.
▪ Collaboration between humans and machines to
provide services or solve problems.
▪ Traditionally applied to mainframes and Unix
systems, but relevant to all platforms.
Is System Administration Just Administrative Work?
▪ Absolutely not – it is a demanding engineering discipline.
▪ Requires broad technical knowledge: hardware, software, user support,
diagnostics, and security.
▪ Also involves management and communication skills.
Why System & Network Administration Matters?
▪ Every organization relies on robust IT infrastructures: Servers, Networks, and Services.
▪ System & Network Administrators ensure:
✓ Availability : services must run 24/7.
✓ Performance : optimize resource usage.
✓ Security : defend against attacks and misconfigurations.
✓ Scalability : support growing business needs.
▪ Examples:
➢ Banking systems uptime.
➢ Cloud service providers (AWS, Azure..etc).
➢ University IT services (email, servers, databases..etc).
Role of the Administrator (Network vs Systems)
Both roles are part of IT. overlap is
common
▪ Overlap especially visible in small
organizations with limited IT staff
▪ Larger organizations draw clear
distinctions between the two roles
▪ As IT infrastructure grows in scale and
complexity:
– Roles become more divided
– Functions get more specialized
Source: [Link]
Role of the Administrator (Network vs Systems)
Network Administrators Focus On:
✓ Monitoring the network → Primary responsibility
✓ Ordering equipment (firewalls, switches, etc.)
✓ Configuring, racking, and testing network
hardware
✓ Performing maintenance (patching & updates)
✓ Troubleshooting network issues
✓ Managing cabling: types, updates..etc
Source: [Link]
Role of the Administrator (Network vs Systems)
Systems Administrators Focus On
✓ Maintaining, configuring & operating
computer systems and servers
✓ Installing & updating software applications
✓ Research & development. staying current
with IT trends and organizational needs
✓ Resolving issues with computer and server
systems
Source: [Link]
Overlap & Collaboration
▪ In many organizations both roles
overlap; same person may handle both
roles if IT staff is small.
▪ Common areas: security (patching,
firewalls), monitoring, troubleshooting
connectivity/performance issues.
➢ Collaboration example: when systems
admin deploys a new web server, the
network admin ensures proper
network path, DNS entries, firewall
rules.
Source: [Link]
Skills & Tools Comparison
Area Network Admin Skills/Tools Systems Admin Skills/Tools
TCP/IP, VLAN, routing, switching, firewalls, OS internals, file systems, system boot
Infrastructure
VPNs, network topologies. process, service management.
Automation of network configurations
Shell scripting (Bash, PowerShell),
Automation / Scripting (e.g. using tools like Ansible for network,
configuration management.
scripts for switch configs).
Tools to monitor network traffic, SNMP, Server monitoring (CPU, RAM, disk), log
Monitoring & Troubleshooting
Wireshark, ping/traceroute. aggregation, system event logs.
Securing network perimeter, intrusion
Securing services, user access, patching,
Security Responsibilities detection, mitigation of network-level
reliable backups, ensuring least privilege.
attacks.
Education & Certifications (Examples)
Example “Day-in-the-Life” Scenarios
Network Admin:
▪ Diagnosing high latency between two data centers
▪ Checking switch logs
▪ Rolling out firmware update to routers during maintenance window.
Systems Admin:
▪ Patch management of servers
▪ Restoring data from backup after inadvertent deletion
▪ Configuring an update to a web service
▪ Adjusting system resources after traffic spike.
Ecosystems: Linux vs Windows
1. Linux Ecosystem (Ubuntu, RedHat, CentOS, Debian, etc.)
➢ Nature: Open-source, community & vendor supported (Canonical, RedHat).
➢ Dominant in: Web servers, supercomputers, cloud infrastructures, IoT, embedded
systems.
➢ Administration Tools:
✓ Remote access: ssh
✓ Service mgmt: systemctl (systemd)
✓ Package mgmt: apt, yum..etc
✓ Scripting & automation: Bash, Python, ..etc
➢ Strengths:
✓ High stability & uptime (common for mission-critical servers)
✓ Security through transparency (open code, frequent patches)
✓ Flexibility: modular kernel, multiple distributions for different needs
✓ Cost-effective (no licensing fees)
➢ Limitations: Steeper learning curve (CLI-oriented), fragmented ecosystem.
Ecosystems: Linux vs Windows
2. Windows Server Ecosystem
➢ Nature: Proprietary, developed by Microsoft, tightly integrated with MS products.
➢ Dominant in: Enterprise environments, corporate IT, institutions with Microsoft
stacks.
➢ Administration Tools:
✓ Directory services: Active Directory
✓ Policy enforcement: Group Policy Objects (GPOs)
✓ Automation: PowerShell, Windows Admin Center
✓ Remote access: RDP (Remote Desktop Protocol)
➢ Strengths:
✓ Enterprise integration (Exchange, SharePoint, Office 365, Azure)
✓ Rich GUI-based management (easy for beginners)
✓ Strong identity & authentication services (Kerberos, AD)
✓ Vendor support and certification paths
➢ Limitations: Licensing costs, less flexible for custom deployments, and resource-
intensive.