Virtual Machine
Virtual Machine
A software-defined computer with virtual CPU, memory, disks and network adapters.
In everyday business: A company can run a domain controller, file server and Linux application as separate servers on one host.
HYPER-V
Hyper-V Host Deployment and Virtual Machine Playbook
Install Hyper-V, design networking and storage, create VMs and avoid the common host-design traps.
Book 3 | Chapter 11
Chapter opening
Chapter 11 moves from the course overview into hyper-v host deployment and virtual machine. The aim is not to memorise product menus or commands. The reader should understand what problem the technology solves, how it fits into the wider servers and virtualization technical textbook, what normal operation looks like, and how to prove the result in the field.
The previous chapter introduced active directory trusts playbook. This chapter continues the sequence by focusing on hyper-v host deployment and virtual machine playbook, so the reader can connect the architecture to a more specific operational problem.
Learning objectives
- Explain the main purpose of Hyper-V Host Deployment and Virtual Machine 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.
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.
vSwitch
Virtual Switch
A software switch inside a hypervisor that connects VM network adapters to each other and to physical networks.
In everyday business: It is the virtual equivalent of plugging server cables into a network switch.
Backup
Backup
An independent recoverable copy of data or system state.
In everyday business: It is the safety net for deletion, corruption, ransomware, hardware loss or major mistakes.
VLAN
Virtual LAN
A logical Layer 2 network that separates devices even when they use the same physical switches.
In everyday business: Staff, cameras and guest WiFi can be kept apart without buying a separate switch for each.
PAT
Port Address Translation
A form of NAT that lets many internal connections share one public address by tracking transport ports.
In everyday business: Hundreds of users can browse the Internet through one public IPv4 address.
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.
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.
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.
Backup
What it means: A backup is an independent recoverable copy of data or system state.
In normal business language: Think of it as having a duplicate of important company records stored safely away from the live filing cabinet.
Why the decision matters: A backup only counts if it can be restored. Test recovery, not just backup completion.
Firewall
What it means: A firewall controls which network connections are allowed between users, systems and external networks.
In normal business language: It is a security checkpoint between parts of the company network. It should allow legitimate work while blocking unwanted access.
Why the decision matters: Firewall rules should describe real business flows such as 'staff may reach accounting on HTTPS', not unexplained broad permits.
Chapter contents
11.1 Install the role
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -RestartPlan before building
- CPU and hardware virtualization support.
- RAM for host plus guests.
- VM storage, checkpoint growth and backup space.
- Management network and VM networks.
- UPS-backed power and hardware monitoring.
Create an external virtual switch
Get-NetAdapter
New-VMSwitch -Name "Production-vSwitch" -NetAdapterName "Ethernet 1" -AllowManagementOS $trueAn External switch connects VMs to the physical network through a host NIC. Internal and Private switches are useful for isolated scenarios.
Create a VM
New-VM -Name "DC01" -Generation 2 -MemoryStartupBytes 4GB `
-NewVHDPath "D:\VMs\DC01\DC01.vhdx" `
-NewVHDSizeBytes 80GB -SwitchName "Production-vSwitch"The resource values are examples, not recommendations.
Checkpoints
Use checkpoints for controlled short-term change/testing. Do not treat long-lived checkpoints as backup, and monitor the storage they consume.
Host rule
FIELD PRACTICE: keep business applications in VMs instead of installing them into the Hyper-V management OS where possible. This keeps the host easier to patch, recover and support.
WORKED BUSINESS SCENARIO
Scenario: five business servers now run on one host
The company consolidates a domain controller, file server, application server, monitoring server and Linux service onto one virtualization host.
What the chapter teaches us: Hardware use is improved, but one host, one storage pool or one network uplink can now affect several services at once. Virtualization changes the failure domain rather than removing it.
Think it through
- Which physical components can now stop all five services?
- What must be backed up independently?
- How would you prove that network and storage paths are resilient?
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
Hyper-V Host Deployment and Virtual Machine Playbook 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.
END OF CHAPTER
Review questions
- Explain the subject in plain language to a business owner.
- List the main dependencies that must be healthy before this service can work.
- Describe one realistic failure and the first three pieces of evidence you would collect.
- Explain what should be documented at handover.
- Which physical failures can affect multiple VMs at once?
- Why is a VM checkpoint not automatically a backup?
A good answer should explain the reason, not only repeat a product name or command.