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.
POWERSHELL
PowerShell for Windows Server Administration Playbook
Move from clicking one server at a time to repeatable, reviewable administration with discovery, pipelines, remoting and scripts.
Book 3 | Chapter 20
Chapter opening
Chapter 20 moves from the course overview into powershell for windows server administration. 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 docker containers, images, volumes and networks playbook. This chapter continues the sequence by focusing on powershell for windows server administration playbook, so the reader can connect the architecture to a more specific operational problem.
Learning objectives
- Explain the main purpose of PowerShell for Windows Server Administration in plain language.
- Identify the components that must work together for the service to operate.
- 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
This subject matters because servers infrastructure supports normal business operations. Understanding the design makes purchasing, troubleshooting and recovery decisions easier to explain and verify.
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.
SMB
Server Message Block
The main Windows file-sharing protocol.
In everyday business: It commonly lets staff open shared folders such as Finance or Projects.
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.
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.
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.
Container
What it means: A container packages an application and its dependencies while sharing the host operating-system kernel.
In normal business language: Think of standardised shipping containers: the application is packaged the same way even when moved between compatible systems.
Why the decision matters: Containers improve deployment consistency, but persistent data, networking, security and backup still need deliberate design.
Docker
What it means: Docker is a platform for building and running containers.
In normal business language: It helps IT package an application once and run the same package in test and production with fewer differences.
Why the decision matters: Use Docker where application portability and repeatable deployment matter, not simply because containers are fashionable.
Chapter contents
20.1 PowerShell is an administration language
Microsoft describes Windows PowerShell as a task-based shell and scripting language designed for system administration.
Discover before memorising
Get-Command *SmbShare*
Get-Help New-SmbShare -Full
Get-Member
Objects, not text
Get-Service | Where-Object Status -eq 'Running' | Sort-Object Name
Get-WindowsFeature | Where-Object Installed
Server roles
Get-WindowsFeature
Install-WindowsFeature -Name DHCP -IncludeManagementTools
Remoting
PowerShell remoting can administer remote systems through WinRM when configured and authorised. Restrict administrative endpoints and credentials.
Safe scripting habits
- Use
-WhatIfwhere supported. - Log changes.
- Handle errors deliberately.
- Do not hard-code passwords.
- Test scripts in a lab.
Benefit
Automation reduces configuration drift because the same tested procedure can be applied repeatedly instead of relying on memory and UI clicks.
WORKED BUSINESS SCENARIO
Scenario: turn the technology into an operational service
A company depends on this technology every day. The technical configuration may be correct, but the real requirement is predictable operation, evidence when something fails and documentation another technician can understand.
What the chapter teaches us: Treat the subject as a service with a purpose, dependencies, normal behaviour, failure modes and a recovery method.
Think it through
- What business process depends on this component?
- What would normal operation look like?
- What evidence would prove the cause of a failure?
PRACTICAL WORK
Hands-on lab
Write a read-only PowerShell script that inventories hostname, IP settings, installed roles and available disk space on a lab server, then exports CSV.
Troubleshooting exercise
A script works interactively but fails when scheduled. Check execution context, permissions, working path, credentials and non-interactive assumptions.
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
PowerShell for Windows Server Administration 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.
A good answer should explain the reason, not only repeat a product name or command.
Technical references
Use the current product documentation and project requirements for production work.