# Operating System Installation and Configuration

> Chapter 4 of the Courseiva SERVER-PLUS curriculum — https://courseiva.com//learn/server-plus/operating-system-installation-and-configuration

**Official objective:** 1.2 — Install and configure server operating systems (e.g., Windows Server, Linux).

## Introduction

Operating system installation and configuration – the very first job you’ll do as a server administrator. Without it, a server is just a collection of metal and silicon with no purpose. For the CompTIA Server+ SK0-005 exam, you need to know exactly how to put an OS onto a physical or virtual machine and then tweak it so it can serve files, host websites, or run databases. This isn’t just about clicking “Next” through a wizard; it’s understanding boot media, partitioning, file systems, network settings, and post-install tasks that make the server secure and functional.

## The Smart Home Hub Analogy

7 smart plugs, 4 light bulbs, 2 motion sensors, and 1 hub arrive in the post. Your job is to turn this pile of gadgets into a working smart home. The hub’s firmware is your operating system. Plugging it in and powering it up is like booting the server from a USB drive. Next, you pair each device one at a time – that’s the equivalent of installing device drivers and configuring hardware support. The mobile app you use to name each room and set automations is like the server’s administration console where you set hostnames, IP addresses, and user accounts. If you skip the pairing step, the light bulbs won’t respond to the hub – exactly like missing a network driver on a server. If you assign two plugs the same name, the app gets confused – just as duplicate IP addresses cause networking chaos. Finally, you update the hub’s firmware to patch a security hole, exactly how you run Windows Update or yum update after installing a server OS. Every step maps precisely: the hardware is the sensor, the hub OS is the operating system, and the configuration app is your graphical or command-line administration tool.

This analogy captures the entire lifecycle: hardware preparation, OS installation, driver configuration, network setup, user management, and ongoing patching.

## Core explanation

An operating system (OS) is the master software that manages all hardware resources and provides services for applications. For servers, the two main families are Windows Server and Linux (including distributions like Ubuntu Server, CentOS, and Red Hat Enterprise Linux). The installation process involves several distinct phases that you must understand for the SK0-005 exam.

First, you choose your installation method. The most common are:
- Interactive installation: you sit at the console, insert DVD or USB, and respond to prompts.
- Unattended installation: you provide a configuration file (e.g., answer file for Windows, kickstart file for Linux) so the OS installs without manual input.
- Network boot (PXE): the server boots from a network card, receives an IP address from a DHCP server, and downloads the OS image from a network share.
- Virtual media: for virtual machines, you mount an ISO file instead of physical media.

Before you start, you must decide on the disk layout – partitioning. A partition is a logical section of a hard drive. For example, Windows Server typically uses a single C: partition formatted with NTFS (New Technology File System), while Linux often uses separate partitions for / (root), /home, and swap. The boot loader (e.g., GRUB for Linux, Windows Boot Manager) is installed during this phase to tell the system where the OS lives.

Once partitions are created and formatted, the installation copies files from the installation media to the disk. This includes the kernel (Linux) or the Windows executive, system libraries, default drivers, and core tools. After copying, the installer often asks for an administrator password. On Windows Server, this is the local Administrator account; on Linux, it is the root account (though many distributions encourage creating a regular user with sudo privileges).

After the base OS is in place, you configure networking. A server needs a static IP address (so clients always know where to find it), a subnet mask, default gateway, and DNS server addresses. The exam expects you to know how to set these in both Windows (Network and Sharing Center, netsh, or PowerShell) and Linux (editing /etc/network/interfaces or using nmcli).

Next comes installing roles and features. A role is a major function, like DNS server, web server (IIS on Windows, Apache or Nginx on Linux), or file server. Features are supporting components, like .NET Framework or Telnet client. You add these through Server Manager (Windows) or package managers like apt (Debian/Ubuntu) or yum/dnf (RHEL/CentOS). The SK0-005 will test your knowledge of which role does what – for example, DHCP Server role assigns IP addresses dynamically.

Finally, you apply updates and perform post-install tasks: join the domain (if part of an Active Directory environment), configure firewall rules, set up monitoring, and enable remote management (Remote Desktop for Windows, SSH for Linux). Each step is critical because a misconfigured server is a security risk or a performance bottleneck.

The entire process exists to replace a manual, error-prone approach. Without a standardised OS, every server would need custom software to talk to disks and networks. Installation and configuration tools ensure repeatability and consistency across hundreds or thousands of servers.

## Real-world context

Imagine you are the lone IT administrator for a growing accounting firm. They just bought a new rack-mount server to host their client management software and file shares. The server has no OS installed – it’s bare metal.

Your first step is to choose the operating system. The firm’s existing infrastructure runs Windows Server 2022, so you decide to use the same to avoid compatibility issues. You download a Windows Server 2022 ISO from the Microsoft Volume Licensing Center and write it to a USB 3.0 drive using a tool like Rufus.

In the server room, you connect a monitor and keyboard to the server, then insert the USB drive. You power it on, press F2 to enter the BIOS, and set the boot order to USB first. When the server restarts, it boots from the USB and the Windows Setup screen appears. You select language, click Install Now, and the installer asks for a product key. You enter the volume license key from your company’s agreement.

The next screen asks which edition – Standard or Datacenter. You choose Standard because the firm only needs two virtual machines. The installer then shows the disk configuration. The server has two 1 TB SSDs in a RAID 1 array (mirrored for redundancy). The RAID controller already presents a single 1 TB virtual disk to Windows. You click New, create a 500 GB partition for the OS (C:), and leave the remaining space unallocated for future use. The installer formats C: as NTFS and begins copying files.

After about 20 minutes, the server reboots. At the first logon, you set a strong administrator password – something like ‘AcctFirmR3v3nu3!‘ – and store it in a password manager. Windows Server 2022 Standard comes with the Server Core interface by default (no desktop). You need the full graphical interface, so you download the Desktop Experience feature using PowerShell: Install-WindowsFeature -Name Server-Gui-Shell, Server-Gui-Mgmt-Infra. That takes another five minutes.

Now you configure networking. The server has two network ports; you configure one for the management network with a static IP 192.168.10.10/24, gateway 192.168.10.1, and DNS 192.168.10.5 (the domain controller). The second port will be used for backup traffic later. You use the sconfig command-line tool to set these values quickly.

Next, you install roles. The firm needs a file server, so you add the File and Storage Services role via Server Manager. You also install the DHCP Server role to hand out IP addresses to client workstations. The DHCP scope you configure covers 192.168.10.100 – 192.168.10.200.

Finally, you join the server to the domain ‘acctfirm.local’ – this allows users to log on with their domain credentials and simplifies permissions. You reboot, log in with a domain admin account, and run Windows Update to install the latest patches. The server is now ready for the client management software installation.

In this scenario, every decision – from selecting the edition to setting a static IP – matters. A wrong choice could leave the server unreachable or insecure. The SK0-005 exam expects you to walk through similar steps in multiple-choice questions, often asking for the correct order of operations or the appropriate tool to use.

## Exam focus

The SK0-005 exam tests your understanding of the entire installation and configuration lifecycle for both Windows Server and Linux. Expect roughly 10-15% of the questions to come from this objective. Here is what you need to know cold:

**Installation Methods and Media**
- Know the difference between clean install, upgrade install, and migration. Clean install wipes the disk and starts fresh; upgrade install preserves settings and applications (limited to same-family versions, e.g., Windows Server 2019 to 2022). Migration moves roles to a new server.
- Recognise boot media: DVD, USB, ISO, PXE (network boot). PXE requires a DHCP server and a deployment server (e.g., Windows Deployment Services or FOG for Linux).
- Be aware of unattended installations: answer file (Windows) or kickstart file (Linux). The exam might give you a snippet and ask what it does.

**Disk and Partition Concepts**
- MBR (Master Boot Record) vs GPT (GUID Partition Table). GPT supports disks larger than 2TB and more than 4 primary partitions. UEFI firmware requires GPT; legacy BIOS uses MBR.
- File systems: NTFS for Windows, ext4 or XFS for Linux. Know that REserFS and Btrfs exist but are less common.
- Volume types: simple, spanned, striped (RAID 0), mirrored (RAID 1). The exam may ask which provides fault tolerance (mirror) vs performance (stripe).

**Post-Install Configuration**
- Server roles (e.g., DNS, DHCP, File Server, Web Server) vs features. Windows uses Server Manager, Linux uses package manager. For Windows, know that adding the DHCP role also installs the DHCP Server service.
- Networking: static vs dynamic IP, subnetting basics, default gateway, DNS settings. The exam might ask you to choose the correct command to set a static IP in Linux (e.g., nmcli con mod eth0 ipv4.addresses 192.168.1.10/24).
- Domain join for Windows: requires DNS pointing to the domain controller and appropriate credentials. Linux servers can join using sssd or winbind.

**Trap Patterns**
- They often present two similar installation methods and ask which one to use in a specific scenario. For example: “You need to deploy 50 identical servers with minimal manual intervention.” Answer: unattended installation.
- They might mix up roles and features: “Which role is required to assign IP addresses automatically?” Correct: DHCP Server role, not DNS or IIS.
- Questions about licensing: Windows Server requires a CAL (Client Access License) for each client. The exam may ask about the number of VMs allowed per Standard vs Datacenter license.
- They may test the difference between Server Core and Desktop Experience: Server Core has no GUI, reduces attack surface, and is preferred for high-security environments.

**Key Definitions to Memorise**
- Hyper-V: Microsoft’s hypervisor for virtualisation, installed as a role.
- PXE: Preboot Execution Environment – network boot protocol.
- KVM: Kernel-based Virtual Machine – Linux’s built-in hypervisor.
- LVM: Logical Volume Manager – Linux tool for flexible disk management.

Practise identifying the correct tool for each task: for example, sconfig is the PowerShell-like configuration tool for Windows Server Core; for Linux, you’d use systemctl, nmtui, or editing /etc/hostname.

Finally, the exam loves scenario-based questions. You’ll be given a description of a problem (e.g., server can’t communicate after installation) and must choose the misconfiguration (likely IP vs subnet mismatch or missing default gateway).

## Step by step

1. **1. Prepare Installation Media** — Download the OS ISO from an official source (e.g., Microsoft Evaluation Centre for Windows Server, or the distribution website for Linux). Write it to a USB drive using a tool like Rufus (Windows) or dd (Linux). Alternatively, mount the ISO in a virtual machine's virtual DVD drive. This step ensures the bootable media is ready.
2. **2. Boot from Media** — Insert the USB or DVD into the server and power it on. Access the BIOS/UEFI settings (usually F2, F10, or Del) and change the boot order to prioritise your installation media. For UEFI systems, enable UEFI boot mode and disable Secure Boot if necessary. The server then loads the installer from your media.
3. **3. Partition and Format Disks** — The installer shows the available disk(s). You must decide how to divide the disk into partitions. For Windows, you typically create one primary partition for the OS and format it as NTFS. For Linux, common setup includes a root (/) partition, a swap partition, and optionally a /home partition. Use ext4 for Linux unless you need features of XFS. Partitioning isolates OS files from user data and supports recovery.
4. **4. Install the Operating System** — Select the partition where you want to install and proceed. The installer copies files to the disk, configures the boot loader (e.g., Windows Boot Manager or GRUB), and prompts for initial settings like language, time zone, and administrator password. For Windows Server, you also choose the edition (Standard or Datacenter) and license key. This is the core installation phase.
5. **5. Initial Configuration and Network Setup** — After reboot, log on with the administrator account. Immediately configure networking: assign a static IP address, subnet mask, default gateway, and DNS server. On Windows, use Server Manager or sconfig; on Linux, edit /etc/network/interfaces or use nmtui. Then install any missing drivers (e.g., RAID or NIC drivers). Install operating system updates (Windows Update, apt update/upgrade).
6. **6. Install Roles/Features and Join Domain** — Add the server roles required for its purpose. For a file server, add File and Storage Services. For a web server, install IIS (Windows) or Apache/Nginx (Linux). Use Server Manager or PowerShell for Windows; for Linux, use apt install or yum install. If the server belongs to an Active Directory domain, join it using PowerShell (Add-Computer) or Linux tools like realm join. Finally, reboot to apply all changes.

## Comparisons

### Clean Install vs Upgrade Install

**Clean Install:**
- Erases all existing data and settings on the disk.
- Requires reinstallation of all applications and configuration.
- More reliable because it starts from a known clean state.

**Upgrade Install:**
- Preserves existing applications, settings, and user data.
- Only possible between compatible versions (e.g., Windows Server 2019 to 2022).
- Carries over potential configuration errors and conflicts from the previous OS.

### MBR (Master Boot Record) vs GPT (GUID Partition Table)

**MBR (Master Boot Record):**
- Supports disks up to 2 TB in size.
- Allows a maximum of four primary partitions (or three primary + one extended).
- Compatible with legacy BIOS firmware only.

**GPT (GUID Partition Table):**
- Supports disks larger than 2 TB (up to 9.4 ZB).
- Allows up to 128 primary partitions on Windows (many more on Linux).
- Required for UEFI firmware; also supports legacy BIOS with UEFI-CSM.

### Windows Server Core vs Windows Server with Desktop Experience

**Windows Server Core:**
- No graphical user interface – managed via command line or PowerShell.
- Smaller disk footprint and fewer security vulnerabilities.
- Requires administrator familiarity with command-line tools.

**Windows Server with Desktop Experience:**
- Includes full GUI (Start menu, desktop, windowing system).
- Larger disk footprint and larger attack surface.
- Easier for administrators who prefer graphical management (Server Manager).

## Common misconceptions

- **Misconception:** I must always select the 'Desktop Experience' option when installing Windows Server, or else I won't have a graphical interface. **Reality:** Windows Server can be installed as Server Core (no GUI) by default. You can later add the Desktop Experience feature if needed, but many production servers run Core for security and performance. (Beginners are used to Windows with a desktop; they assume servers also need a GUI. Exam questions deliberately test this difference.)
- **Misconception:** Linux doesn't need any configuration after installation – everything works out of the box. **Reality:** A freshly installed Linux server requires post-install steps: setting a static IP, creating users, configuring firewall (iptables or firewalld), and installing required services. (New users often install Ubuntu Desktop and assume Server is the same. But server distributions have minimal packages and no GUI by default, so manual configuration is essential.)
- **Misconception:** You can only install an operating system using physical media like a DVD. **Reality:** Modern installation methods include USB drives, ISO files mounted over the network, PXE boot, and virtual media for VMs. DVD is slow and rare in data centres. (Older textbooks still emphasise CD/DVD; exam candidates may forget that PXE and network boot are more common in enterprise environments.)
- **Misconception:** Partitioning is optional – you can just let the installer use the whole disk. **Reality:** While you can let the installer auto-partition, proper partitioning separates OS data from user data, enables dual-boot scenarios, and improves recovery. Linux often uses separate /home and / partitions. (Home users are used to clicking 'Next' and accepting defaults; they don't realise servers benefit from custom layouts.)

## Key takeaways

- A clean install wipes the existing disk and installs the OS from scratch; an upgrade install preserves settings but is only possible between compatible versions.
- Windows Server offers two editions: Standard (up to 2 VMs) and Datacenter (unlimited VMs) – the licence determines how many virtual machines you can run.
- The three main installation methods are interactive (manual), unattended (answer file), and network boot (PXE).
- GPT partition table is required for disks over 2 TB and for UEFI firmware; MBR is limited to 2 TB and four primary partitions.
- After installation, you must configure networking (static IP is typical for servers), install roles/features, apply updates, and join a domain if required.
- Server Core (no GUI) is the default for Windows Server 2022; you can add Desktop Experience later via PowerShell if needed.

## FAQ

**What is the difference between a clean install and an upgrade install for Windows Server?**

A clean install erases all data on the disk and installs the OS from scratch. An upgrade install preserves existing applications, settings, and user accounts, but it is only possible from a compatible previous version (e.g., Windows Server 2019 to 2022). Upgrades are riskier and may carry over configuration issues.

**Can I install Windows Server on a regular laptop?**

Technically yes, but it is not recommended. Server OSes expect server-grade hardware (RAID controllers, ECC memory, multiple NICs). Laptop drivers may be missing, and Microsoft licenses limit Server to non-user-facing roles. For learning, use a virtual machine instead.

**How do I set a static IP address in Linux after installation?**

You can use nmcli (NetworkManager command line) or edit the network configuration file. For example, on Ubuntu 20.04+, run 'sudo nmcli con mod eth0 ipv4.addresses 192.168.1.10/24 ipv4.gateway 192.168.1.1 ipv4.dns 8.8.8.8 ipv4.method manual' then 'sudo nmcli con down eth0 && sudo nmcli con up eth0'.

**What is PXE boot and when would I use it?**

PXE (Preboot Execution Environment) allows a server to boot and install an OS over the network without any local media. It is used in large-scale deployments where hundreds of identical servers must be set up quickly and consistently. The server gets an IP from DHCP and downloads the OS image from a deployment server.

**Do I need a product key to install Windows Server Evaluation edition?**

No, the Evaluation edition (available from Microsoft) does not require a key during installation. It runs for 180 days before needing activation. You can later convert it to a fully licensed version with a product key without reinstalling.

**What is the difference between Windows Server Core and Desktop Experience?**

Server Core is a minimal installation without a graphical user interface (GUI). It uses a command prompt or PowerShell. Desktop Experience adds the full GUI, including the Start menu and desktop. Core is more secure and uses fewer resources, while Desktop Experience is easier for administrators not comfortable with command lines.

---

Interactive version with quiz and diagrams: https://courseiva.com//learn/server-plus/operating-system-installation-and-configuration