Week 11: Windows Installation, Administration, and Networking

Core 1 taught you to trace hardware, network, and virtual infrastructure as systems.

Core 2 adds another layer without replacing any of those earlier ones.

Windows sits on top of hardware and firmware, owns a boot and storage layout, loads drivers and services, applies identity and policy, configures networking, and finally gives applications somewhere to run.

hardware / firmware
   ↓
boot + disk layout
   ↓
Windows edition + version
   ↓
drivers + services
   ↓
users + groups + policy
   ↓
network + firewall + proxy
   ↓
applications + data

A machine can boot perfectly while the wrong edition blocks a required management feature. A disk can be physically healthy while Windows has no usable mounted volume. A network path can work while a stale mapped drive points to the wrong server. A local setting can keep returning because policy, not the user, owns the final state.

The system question

Which Windows layer owns the requirement or symptom, and what is the smallest tool that can expose that layer?

That is more durable than memorizing where Microsoft moved a button this year.

How the chapter moves

1. Windows Editions, Features, and Requirements connects editions to domain participation, BitLocker, Remote Desktop, policy, RAM support, TPM/UEFI, and upgrade requirements.
2. Install and Upgrade Windows treats deployment as a data, compatibility, boot, partitioning, driver, lifecycle, and recovery decision before setup begins.
3. Windows GUI Tools and Settings maps administrative consoles and Settings surfaces to the system state each one actually exposes.
4. Windows Command Line and Networking Lab separates inspection commands from state-changing commands and applies them to files, disks, identity, policy, and client networking.
5. Windows Technician Practical combines edition, deployment, storage, policy, networking, firewall, recovery, and evidence into realistic service tickets.

One rule for the whole week

Menus move. Tool names sometimes change. Supported Windows versions change too.

The durable knowledge is:

What state am I trying to inspect or change, who owns it, and what evidence will prove the result?

Use current supported Windows behavior and current vendor documentation. Do not preserve an obsolete click path just because an old study guide still shows it.