Week 11 · Lesson 3

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.

CCNA 200-301 Servers & Virtualisation Verified 2026-10-11
Part 1

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 or Server Core? · select one

Note. Most production Windows servers run Server Core and are managed remotely through RSAT tools or Windows Admin Center. The GUI is convenient, but the minimal install is the more secure default.
Part 2

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.

AD vocabulary · select a term

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.

Part 3

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.

RoleWhat it doesKey port(s)
AD DS (Domain Controller)Directory and authenticationLDAP 389, LDAPS 636, Kerberos 88 (TLS/Kerberos over both UDP and TCP)
DNS ServerName resolution (usually on the DC)53 (UDP/TCP)
DHCP ServerAutomatic IP configuration67 (server), 68 (client), UDP
File ServerShared folders over SMB445 (TCP); legacy 139
Print ServerShared printers (via SMB/RPC)445 (TCP)
Web Server (IIS)Hosts websites and apps80 (HTTP), 443 (HTTPS)
Remote Desktop (management)Graphical remote administration3389 (TCP/UDP)
Role and port explorer · choose a role

Exam tip. Tie AD to its ports: LDAP 389, LDAPS 636, Kerberos 88. A domain controller is first a DNS server, so 53 is always in the picture. These come straight from the Week 9 application-layer table, so revise that table alongside this one.
Part 4

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:

DistributionNotes
Ubuntu ServerDebian-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 StreamFree, community build positioned upstream of RHEL; a rolling preview of what RHEL will ship
DebianLong-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:

L · Linuxthe operating system
A · Apachethe web server (Nginx gives LEMP)
M · MySQLthe database (or MariaDB)
P · PHPthe scripting layer (or Perl/Python)

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.

Part 5

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:

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:

Warning — don’t equate “free” with “zero cost”. Total cost of ownership includes training, support, and administrator time. A “free” Linux distro can cost more in staff hours than a licensed Windows Server, and a subscription Linux can cost less than a Windows licence plus CALs. Choose on requirements, not on the price tag alone.
Part 6

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.

AttributeWindows ServerLinux server
LicensingCommercial: per-core licence plus CALsFree/open source; optional paid support subscriptions
InterfaceGUI (Desktop Experience) or minimal (Server Core)Text console by default; GUI optional
Directory serviceActive Directory (LDAP, Kerberos)LDAP (OpenLDAP), Kerberos, or Samba AD
Role modelRoles and features installed on demandPackages installed on demand
ScriptingPowerShellBash/shell, Python, Perl
PatchingWindows Update / WSUSPackage manager (apt, dnf)
Typical fitWindows-centric corporate estates, AD, IIS, .NETWeb, cloud, containers, high-scale open-source workloads
Side by side · pick an attribute

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.

Windows Server Domain Controller AD DS — LDAP 389 / Kerberos 88 DNS — 53 · DHCP — 67/68 IIS — 80 / 443 File / Print — SMB 445 Managed by GUI or PowerShell Linux Server LAMP host Apache (L) — 80 / 443 MySQL / MariaDB — 3306 PHP scripting layer SSH admin — 22 · SELinux Managed headless from the CLI
Windows Server and Linux differ in licensing, interface, and tooling, but both run services that bind to ports. The Windows host centralises directory and infrastructure roles; the Linux host serves a dynamic website from the LAMP stack.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Microsoft. Windows Server documentation — roles, Server Core, Active Directory. learn.microsoft.com/windows-server.
  2. Microsoft. Active Directory Domain Services overview. learn.microsoft.com.
  3. Red Hat. Red Hat Enterprise Linux documentation (SELinux, subscription model). docs.redhat.com.
  4. Canonical. Ubuntu Server documentation. ubuntu.com/server/docs.
  5. Apache Software Foundation. LAMP stack (Apache HTTP Server). httpd.apache.org.
  6. IANA. Service Name and Transport Protocol Port Number Registry (53, 67/68, 80, 88, 389, 443, 445, 636, 3306, 3389). iana.org.
  7. 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.