Lesson 2: Install and Upgrade Windows

Core path: 42 minutes

"Install Windows" can mean several different deployment paths.

The technician job is to choose a method that matches the hardware, network, data, scale, and recovery requirement.

Boot and installation methods

Recognize these paths:

• USB installation media;
• network boot/deployment;
• solid-state/flash media;
• internet-based installation/recovery;
• external or hot-swappable drive;
• internal hard-drive partition;
• multiboot configuration.

A method being technically possible does not make it appropriate for every organization.

Installation types

Clean install

Creates a fresh OS environment.

Upgrade

Moves an existing supported installation to a newer supported version while attempting to preserve compatible data/settings/applications.

Image deployment

Uses a prepared system image to deploy a consistent environment.

Remote network installation

Installs over a managed network path rather than local media.

Zero-touch deployment

Automates much of provisioning so the endpoint can configure itself through an organization's managed deployment process.

Recovery partition

Uses recovery content stored on a dedicated partition or recovery environment.

Repair installation

Attempts to repair/rebuild the operating environment while preserving more existing state than a destructive clean install.

Third-party drivers

Some storage, network, or other hardware may require a trusted third-party/vendor driver during or after installation.

Do not download unknown driver packages because installation media does not recognize one device.

GPT vs MBR

GPT

GUID Partition Table is the normal modern partitioning scheme used with UEFI systems and supports modern disk/partition requirements.

MBR

Master Boot Record is the older partitioning scheme associated with legacy BIOS-era workflows and has more limitations.

The boot mode, OS support, disk layout, and deployment requirement need to agree.

Drive format

The target partition must use a filesystem/format appropriate to the operating system and deployment plan. Formatting can destroy existing data, so identify the correct target before making changes.

Upgrade checklist

Before a major installation or upgrade verify:

• backup of required files and user preferences;
• application compatibility;
• driver/backward compatibility;
• hardware compatibility;
• available storage;
• licensing/activation path where applicable;
• recovery/rollback plan;
• product lifecycle/support status.

Feature updates and lifecycle

A system can be technically functional but no longer supported by the vendor. Feature updates, update eligibility, and end-of-support status influence the correct upgrade plan.

Guided cases

Case A: 25 identical lab PCs

A technician wants repeatable configuration across all systems. Image deployment or a managed zero-touch/network workflow may be more appropriate than manually installing from USB 25 times.

Case B: one damaged Windows installation

User data is backed up and the system reaches recovery tools. A repair/recovery-first approach may preserve more state than immediately formatting the disk.

Case C: old hardware

The proposed Windows version does not support the CPU/firmware requirement. Installation media existing does not make the platform supported.

Student action

For six fictional deployment tickets, select:

boot/install method:
installation type:
GPT or MBR consideration:
driver consideration:
backup/recovery requirement:
compatibility check:
lifecycle concern:
verification after install:

Evidence checkpoint

The successful outcome is not "setup completed." It is the correct supported OS was deployed using an appropriate method and required data/functionality were verified afterward.