Lesson 3: Install Windows Server (or Windows 11 Pro Lab) and Harden Basics

Section 5 — Lesson 3: Install Windows Server (or Windows 11 Pro Lab) and Harden Basics

Welcome back. This lesson is where your DBA lab becomes real.
You will install the operating system inside your virtual machine and apply the baseline hardening steps
DBAs and sysadmins do before SQL Server ever touches the server.

A poorly configured OS causes endless pain: unstable performance, security gaps, broken patches,
unreliable time settings, and random restarts. Your goal is not “just install Windows.”
Your goal is to build a clean, stable foundation you can repeat.

Lesson description: You will install Windows Server (recommended) or Windows 11 Pro (acceptable for labs),
configure core settings (name, updates, time, power plan, networking),
enable administrative essentials (RDP, local admin practices),
apply basic security and stability hardening,
and prepare the system to install SQL Server and tools confidently.
You will also build a short OS install checklist you can reuse whenever you rebuild your lab.

1) Choose Your Lab OS Path

Option A (Recommended): Windows Server

• Feels like real enterprise environments
• Better practice for server management
• Most aligned with DBA job expectations

Option B (Allowed for Labs): Windows 11 Pro

• Easier for some students to install
• Still valid for learning SQL Server concepts
• Less “server-realistic,” but acceptable

Course guidance: If you can run Windows Server in your VM, do it.
If you cannot, use Windows 11 Pro and follow the same hardening principles.

2) Before You Install: VM Configuration Checklist

Before booting the installer, confirm:

• vCPU: 2 minimum, 4 recommended
• RAM: 8 GB minimum, 16 GB recommended
• Disk: 80–120 GB recommended, stored on SSD if possible
• Network: NAT recommended for simplest setup
• ISO mounted: Windows installation ISO attached to VM CD/DVD

DBA note: If your VM is slow during install, fix resources now.
Do not “push through” a broken foundation.

3) Install Windows (Step-by-Step)

Step 3.1 — Boot to the installer

1. Start the VM.
2. Boot from the mounted Windows ISO.
3. Select language/region/keyboard and continue.

Step 3.2 — Choose edition (Windows Server path)

When prompted for Windows Server edition:

• Choose a standard edition suitable for labs.
• If offered “Server Core” vs “Desktop Experience,” choose Desktop Experience for learning.
  (Core is powerful but not beginner-friendly.)

Step 3.3 — Disk partition and install

1. Select the VM disk.
2. Use default partitioning for lab simplicity.
3. Proceed with installation and let the VM reboot.

Step 3.4 — Create a strong local admin password

Create a password you will not forget. Store it in your secure notes.
DBAs must practice good credential hygiene even in labs.

4) First Boot: Baseline Configuration (Must-Do)

4.1 Set a clear computer name

Rename the VM to something obvious, for example:
SQLLAB01 or SQLDBA-LAB

DBA reason: In real environments, servers must be identifiable in logs, scripts, and monitoring.

4.2 Set time zone correctly

Ensure the VM time zone matches your environment. Incorrect time causes:

• confusing log timestamps
• certificate/authentication problems
• backup job time drift

4.3 Run Windows Update fully

Apply all updates and reboot until there are no pending updates.

DBA rule: Patch the OS before installing SQL Server, not after.

5) Harden Basics (DBA/Sysadmin Essentials)

5.1 Power plan (critical for performance labs)

Set power plan to:
High performance (or best available equivalent).

Why DBAs care: Aggressive power saving can throttle CPU and create misleading performance results.

5.2 Enable Remote Desktop (RDP) for convenience

Enable Remote Desktop so you can connect cleanly to the VM.
Also allow RDP through Windows Firewall when prompted.

DBA note: RDP is common in enterprise environments; you should be comfortable using it.

5.3 Create a “DBA Admin” local user (optional but professional)

Instead of using the built-in Administrator account for everything,
create a dedicated local admin user for your lab, for example:
dba.admin

Reason: Helps you practice least privilege and clearer auditing habits.

5.4 Configure Windows Defender / Security baseline (keep it simple)

In labs, keep built-in security enabled. Do not disable security features unless you have a strong reason.
Your goal is to learn how to run systems safely, not “turn off everything.”

5.5 Confirm Windows Firewall is enabled

Keep firewall enabled. Later, if you practice remote connections to SQL Server,
you will open only the required ports intentionally.

6) Practical Performance & Reliability Settings (Lab-Friendly)

6.1 Confirm disk space and create standard folders

Create consistent folders you will reuse in the course. Example:

• C:\DBA\
• C:\DBA\Installers\
• C:\DBA\Backups\
• C:\DBA\Scripts\
• C:\DBA\Logs\
• C:\DBA\Docs\

DBA reason: Consistent structure prevents confusion and makes rebuilds faster.

6.2 Enable clipboard and shared folders (if your VM tool supports it)

If you are using VMware/VirtualBox/Hyper-V integration features, enable:

• clipboard sharing (copy/paste)
• shared folders (easy transfer of scripts and ISOs)

DBA warning: In real production, you must control these features carefully.
In a lab, they help productivity.

7) Network Basics (Enough for DBA Labs)

For now, keep networking simple:

• NAT: VM can access the internet for downloads and updates
• Confirm you can browse the web from the VM
• Confirm the VM can ping the host (optional)

Later, you will learn how to configure SQL Server connectivity more intentionally.

8) Build Your “OS Install Checklist” (Save This in Your DBA Notebook)

Copy this checklist into your notebook and reuse it whenever you rebuild:

• VM resources set (CPU/RAM/Disk/Network)
• Windows installed successfully
• Computer renamed (SQLLAB01)
• Time zone verified
• Windows fully updated (no pending updates)
• Power plan set to High performance
• RDP enabled and firewall rule confirmed
• DBA folder structure created (C:\DBA\…)
• Security baseline kept enabled (Defender + Firewall)

Practice (You Must Complete Before Moving On)

1. Install Windows in your VM.
2. Rename the VM to SQLLAB01 (or similar) and reboot.
3. Run Windows Update until fully patched.
4. Set power plan to High performance.
5. Create the standard DBA folders under C:\DBA\.
6. Confirm internet access works in the VM.

Lesson Summary

• A stable OS foundation prevents performance and reliability problems later.
• DBAs patch and harden the OS before installing SQL Server.
• Power plan, time settings, and folder standards matter immediately.
• Simple networking (NAT) is best for starting labs.
• A reusable install checklist is part of professional DBA discipline.

Next Lesson: Service Accounts Strategy (What to Do in Lab vs Production)

Next, you will learn how DBAs plan SQL Server service accounts,
what “least privilege” means for services, and the correct approach for labs versus real production environments.