TRAINING LAB

Build a Windows Server and Virtualization Training Lab

Learn Active Directory, DNS, Group Policy, file services and Linux integration without experimenting on production.

Servers textbookChapter 25

Learning objectives

  • Explain the main purpose of Build a Windows Server and Virtualization Training Lab in plain language.
  • Trace CPU, memory, network and storage from a VM through the hypervisor to physical hardware.
  • Use evidence to separate a design problem from a configuration or physical fault.
  • Describe the business impact of a failure and the evidence required for handover.

Why this matters in a real company

Virtualization lets a company run several independent server workloads on fewer physical machines. The benefit is flexibility and easier recovery, but one badly designed host can also become a large single point of failure.

Course: Servers and Virtualization Technical Textbook

PLAIN ENGLISH

Technical terms used in this chapter

You do not need to memorise the jargon first. Understand what each term does and why somebody running a company would care about it.

Active Directory

Active Directory

Microsoft's central directory for users, computers, groups and access control in a Windows domain.

In everyday business: One staff account can be managed centrally instead of separately on every PC.

Hypervisor

Hypervisor

Software that lets one physical server run multiple isolated virtual machines.

In everyday business: One powerful server can safely run several separate business servers.

AD DS

Active Directory Domain Services

The Windows Server role that provides the Active Directory directory and domain authentication.

In everyday business: It gives the company one managed identity system for people and computers.

DHCP

Dynamic Host Configuration Protocol

A service that automatically gives devices IP settings such as address, gateway and DNS.

In everyday business: New laptops and phones can join the network without manual IP configuration.

DNS

Domain Name System

The service that translates names into IP addresses and helps Windows domain clients find services.

In everyday business: People and applications can use names instead of remembering network numbers.

GPO

Group Policy Object

A set of centrally managed Windows settings that can be applied to users or computers.

In everyday business: IT can enforce security and configuration settings across many PCs at once.

KVM

Kernel-based Virtual Machine

Linux kernel virtualization technology that turns Linux into a hypervisor.

In everyday business: A Linux server can run Windows and Linux virtual machines.

VM

Virtual Machine

A software-defined computer running on a hypervisor.

In everyday business: It behaves like a separate server even though it shares physical hardware.

See the complete plain-English glossary

BUSINESS TRANSLATION

What this means outside the server room

This topic affects the systems staff depend on for sign-in, files, applications and business continuity. The technical design determines how easy the environment is to manage and how painful a failure becomes.

VLAN

What it means: A VLAN creates a separate logical network even when devices share the same physical switches.

In normal business language: Think of one office building with separate departments using the same corridors but different access-controlled areas. Staff, cameras, voice and guests can share the same switching hardware without all being in one open network.

Why the decision matters: Use VLANs to separate traffic for security, performance and easier troubleshooting without buying a separate physical switch for every department.

Active Directory

What it means: Active Directory centrally manages users, computers, groups and access in a Windows domain.

In normal business language: Think of it as one employee identity system for the company instead of separate usernames and passwords on every computer and server.

Why the decision matters: Use it when a company needs central sign-in, consistent permissions, controlled administrator access and easier onboarding/offboarding.

DNS

What it means: DNS translates names into IP addresses and also helps many business services locate each other.

In normal business language: It is the company phonebook for systems. Staff type a name such as fileserver or portal instead of remembering a number.

Why the decision matters: Good DNS design reduces configuration mistakes and is especially important for Windows domains, cloud integrations and internal applications.

DHCP

What it means: DHCP automatically gives devices their network settings.

In normal business language: It is like reception assigning each new visitor a desk number and directions automatically instead of somebody configuring every laptop by hand.

Why the decision matters: Use DHCP for normal endpoints and reserve static addressing for infrastructure where predictable addressing is required.

Hypervisor

What it means: A hypervisor lets one physical server run several isolated virtual machines.

In normal business language: Think of one office building divided into secure independent suites. The building is shared, but each tenant operates separately.

Why the decision matters: Virtualization reduces hardware sprawl and improves flexibility, but the physical host becomes important because several business systems can depend on it.

Virtual Machine

What it means: A virtual machine is a software-defined computer with its own operating system, memory, CPU allocation, disks and network interfaces.

In normal business language: It behaves like a separate server even though several VMs may share one physical machine.

Why the decision matters: VMs are useful for separating roles such as domain control, file sharing and applications while keeping management and recovery flexible.

Small infrastructure training lab
Physical Hypervisor HostDC01AD DS + DNSFS01File ServerLINUX01Linux serviceCLIENT01Domain client

Suggested VMs

VMRole
DC01AD DS + DNS
FS01Member/file server
LINUX01Linux service
CLIENT01Windows domain client

Exercises

  1. Build DC01 and a new domain.
  2. Create OUs, users and groups.
  3. Join CLIENT01.
  4. Create and test a harmless GPO.
  5. Join FS01 and create group-based file permissions.
  6. Deploy LINUX01 and test DNS/routing/SSH.
  7. Break DNS deliberately, observe the symptoms, then repair it.
  8. Back up and restore one VM in an isolated network.

Safety

Keep the lab isolated from production DHCP/domain services unless connectivity is deliberately designed. Never allow a lab DHCP server onto the production broadcast domain.

PRACTICAL WORK

Hands-on lab

Create one small lab VM, connect it to the intended virtual network, install an OS, record its vCPU, RAM and disk allocation, and prove network and storage paths.

Troubleshooting exercise

A VM is running but cannot reach the LAN. Check guest IP, guest firewall, vNIC, virtual switch or bridge, VLAN, host uplink and physical switch in that sequence.

Chapter field checklist

  • I can explain the subject without relying only on acronyms.
  • I can draw or describe the main traffic, storage, power or service path.
  • I know what normal operation should look like.
  • I know which logs, counters or test results prove the result.
  • I can explain the business impact if this component fails.
  • I would document the final configuration and evidence at handover.

Chapter summary

Build a Windows Server and Virtualization Training Lab should now be understood as a business service with a technical implementation, not simply a collection of commands or product names. The important habit is to know the purpose, understand the dependencies, measure the result and document what was proven.