Server Operating Systems
The server operating system is the platform every service runs on. The exam expects you to know the two dominant families — Windows Server and Linux — how they are administered, what each is good at, and how licensing differs. This lesson also introduces Active Directory, the directory service that powers Windows domains.
What a server OS adds
A desktop operating system is tuned for one person sitting in front of it. A server OS is tuned for many concurrent users and for running without a human present. Compared with a desktop OS, a server OS adds four things:
Server services
Roles and features that do not exist on a desktop: directory services, name resolution, address assignment, web hosting.
Remote management
Tools to administer the machine across the network, since there is no local screen.
Headless operation
The ability to run with no graphical interface at all, saving resources and attack surface.
Hardening
Security defaults aimed at a multi-user, Internet-facing machine rather than a single-user workstation.
Windows Server: the GUI and Server Core
Windows Server is Microsoft’s server operating system. Its defining feature is that functionality is delivered as roles and features you install on demand — a fresh install is a platform, and you add the role you need.
Windows Server can be installed in two forms, and this is exam-relevant:
- Desktop Experience (GUI). A familiar graphical interface with Start menu, Server Manager, and wizards. Easier for newcomers and for occasional administration.
- Server Core. A minimal install with no graphical shell — a command line and remote tools only. It uses fewer resources, needs fewer patches, and presents a smaller attack surface than the full GUI.
Active Directory essentials
Active Directory (AD) is Microsoft’s directory service: a central database of users, computers, and other objects, plus the services that authenticate them. Four concepts cover what the exam asks.
- Domain controller (DC). A server that runs the AD DS role and holds a writable copy of the directory. It authenticates logons and authorises access. Organisations run at least two DCs for redundancy.
- Domain. A logical security boundary that shares one directory database and one set of policies. Objects within a domain are administered together; the domain name often mirrors the DNS namespace (for example,
corp.example.com). - Organisational unit (OU). A container inside a domain used to organise objects (by department, site, or function) and, crucially, to target policies and delegate administration.
- Group Policy. Rules pushed from the domain (as Group Policy Objects, GPOs) that configure settings on users and computers automatically — password rules, drive mappings, firewall settings, software deployment.
AD is a directory accessed with LDAP, and it authenticates users with Kerberos. That is why domain controllers must be reachable on the ports listed next.
Windows Server roles and their ports
Each role turns the server into a specific kind of server. Learn the ports, because they connect this lesson back to Week 9.
| Role | What it does | Key port(s) |
|---|---|---|
| AD DS (Domain Controller) | Directory and authentication | LDAP 389, LDAPS 636, Kerberos 88 (TLS/Kerberos over both UDP and TCP) |
| DNS Server | Name resolution (usually on the DC) | 53 (UDP/TCP) |
| DHCP Server | Automatic IP configuration | 67 (server), 68 (client), UDP |
| File Server | Shared folders over SMB | 445 (TCP); legacy 139 |
| Print Server | Shared printers (via SMB/RPC) | 445 (TCP) |
| Web Server (IIS) | Hosts websites and apps | 80 (HTTP), 443 (HTTPS) |
| Remote Desktop (management) | Graphical remote administration | 3389 (TCP/UDP) |
Linux servers, distributions and the LAMP stack
Linux is the open-source kernel that underpins most of the Internet’s servers. A distribution (distro) bundles the kernel with utilities and a package manager. The server distros to know:
| Distribution | Notes |
|---|---|
| Ubuntu Server | Debian-based, very popular, gentle learning curve, apt package manager |
| Red Hat Enterprise Linux (RHEL) | Enterprise, commercial subscription and support, dnf/yum; common in corporate data centres |
| CentOS Stream | Free, community build positioned upstream of RHEL; a rolling preview of what RHEL will ship |
| Debian | Long-lived, stable, the foundation of Ubuntu; apt |
LAMP is the classic open-source recipe for hosting a dynamic website. The acronym names four layers that stack together:
The point of knowing LAMP is that it shows the server-software layers working together: a request arrives at the web server, which asks the scripting layer to build a page, which queries the database, all running on Linux.
Headless administration, SELinux, and licensing
Linux servers are almost always managed over the network from a text console. The standard tool is SSH (port 22), which gives an encrypted shell; there is no requirement for a graphical interface. Administration is done by editing configuration files and running commands, and the same commands can be automated in scripts — a major reason Linux dominates server farms.
SELinux (Security-Enhanced Linux) is a mandatory access control system built into many enterprise distributions, notably RHEL and its relatives. Ordinary file permissions decide who can touch a file; SELinux adds labels that restrict what a process may do even if it runs as root. It confines a compromised service so it cannot roam the system. In enforcing mode it blocks violations and logs them; that is a security benefit, but it is also a common source of “permission denied” surprises when a new service is deployed.
CLI versus GUI administration
Windows and Linux both offer graphical and command-line administration, but they lean differently:
- The GUI (Server Manager, Active Directory Users and Computers) is discoverable and good for one-off tasks and for administrators who are new to a platform.
- The CLI (PowerShell on Windows; Bash and the shell on Linux) is faster for repeated tasks, scriptable, and remote-friendly. On Linux it is effectively the default.
Microsoft has moved toward this model too: PowerShell and PowerShell Desired State Configuration let administrators automate Windows the same way Linux administrators automate with shell scripts. The skill that transfers between both worlds is automation.
Licensing reality
“Open source” does not mean “no cost”, and “commercial” does not mean “closed”. The honest picture:
- Linux is generally free to download and use, and its source code is available (free as in freedom). You can still pay for an enterprise subscription — RHEL charges for support, updates, and certification — but the software itself is not sold per seat.
- Windows Server is commercial: you buy a licence, typically per core, and you also pay for Client Access Licences (CALs) for the users or devices that connect. Active Directory, IIS, and Hyper-V are included features of the licensed product.
Windows Server versus Linux server
The two families overlap more than the marketing suggests. Both run the same services, bind the same ports, and can be scripted. The differences are in licensing, tooling, and the ecosystem each one assumes.
| Attribute | Windows Server | Linux server |
|---|---|---|
| Licensing | Commercial: per-core licence plus CALs | Free/open source; optional paid support subscriptions |
| Interface | GUI (Desktop Experience) or minimal (Server Core) | Text console by default; GUI optional |
| Directory service | Active Directory (LDAP, Kerberos) | LDAP (OpenLDAP), Kerberos, or Samba AD |
| Role model | Roles and features installed on demand | Packages installed on demand |
| Scripting | PowerShell | Bash/shell, Python, Perl |
| Patching | Windows Update / WSUS | Package manager (apt, dnf) |
| Typical fit | Windows-centric corporate estates, AD, IIS, .NET | Web, cloud, containers, high-scale open-source workloads |
The final figure compares the two families in practice. On the left, a Windows Server domain controller hosting directory, DNS, DHCP, IIS and file/print roles; on the right, a Linux host running the LAMP stack for a website.
Review
Check what you have learned with these review questions.
Sources & references
- Microsoft. Windows Server documentation — roles, Server Core, Active Directory. learn.microsoft.com/windows-server.
- Microsoft. Active Directory Domain Services overview. learn.microsoft.com.
- Red Hat. Red Hat Enterprise Linux documentation (SELinux, subscription model). docs.redhat.com.
- Canonical. Ubuntu Server documentation. ubuntu.com/server/docs.
- Apache Software Foundation. LAMP stack (Apache HTTP Server). httpd.apache.org.
- IANA. Service Name and Transport Protocol Port Number Registry (53, 67/68, 80, 88, 389, 443, 445, 636, 3306, 3389). iana.org.
- Simpson, W. RFC 1552: The PPP Internetworking Packet Exchange Control Protocol (IPXCP) — cited only to note the historical, non-SMB scope of this RFC; it does not define SMB. rfc-editor.org/rfc/rfc1552.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.