Why a DHCP server join the Active Directory

Authorizing a DHCP server in Active Directory means:

“This DHCP server is approved by the domain to give IP addresses to clients.”

In a Windows AD domain, a domain-joined DHCP server must be authorized before it can start leasing IP addresses. Microsoft’s Add-DhcpServerInDC cmdlet adds the DHCP server to the list of authorized DHCP servers in Active Directory. (Microsoft Learn)

What do we achieve?

You achieve control and safety.

Without authorization, any domain-joined Windows Server with DHCP installed could accidentally or wrongly start giving IP addresses to computers.

With authorization, Active Directory keeps a list of approved DHCP servers. Only approved DHCP servers should lease IP addresses in the domain.

Why is this helpful in real life?

Imagine a college or company network.

The real DHCP server should give clients correct settings like:

IP address:      192.168.10.50
Subnet mask:     255.255.255.0
Default gateway: 192.168.10.1
DNS server:      192.168.10.10
DNS domain:      college.local

But if someone accidentally enables another DHCP server, clients may receive wrong settings like:

IP address:      192.168.99.50
Default gateway: wrong router
DNS server:      wrong DNS server

Then users may lose access to:

Internet
shared drives
printers
domain login
internal websites
Active Directory services

Microsoft describes DHCP authorization as a Windows Server DHCP feature that helps prevent unauthorized DHCP servers from providing IP addresses to clients. (Microsoft Learn)

Real-life example

A technician installs DHCP on a test server inside a company domain.

Without authorization control:

Test DHCP server starts giving addresses
Some client computers get wrong IP settings
Users cannot access network resources
Help desk receives many tickets

With AD authorization:

Test DHCP server is not authorized
It should not lease addresses in the domain
Production DHCP server remains the trusted source

Simple explanation

DHCP authorization protects an Active Directory network from rogue or accidental DHCP servers. It ensures that only approved DHCP servers can lease IP addresses to clients.

Lab explanation

this step teaches a real enterprise practice:

Add-DhcpServerInDC -DnsName "DC01.powershell.local" -IPAddress "192.168.55.10"
Get-DhcpServerInDC

This proves that the DHCP server is trusted by Active Directory before students test DHCP leases.

Ref: AI Tools, ChatGPT

How to Install DHCP role

Ref: AI Tools, ChatGPT : As is

To install the DHCP Server role on Windows Server 2019, use Windows PowerShell as Administrator on the server VM, not the client VM.

1. Open PowerShell as Administrator

On the Windows Server VM:

Start Menu → Windows PowerShell → Right-click → Run as administrator

2. Check whether DHCP is already installed

Get-WindowsFeature DHCP

If it is not installed, you may see:

Display Name                                            Install State
------------                                            -------------
[ ] DHCP Server                                         Available

3. Install DHCP Server role

Install-WindowsFeature DHCP -IncludeManagementTools

-IncludeManagementTools installs the DHCP management tools also.

4. Verify installation

Get-WindowsFeature DHCP

Expected result:

[X] DHCP Server                                         Installed

Also check the DHCP service:

Get-Service DHCPServer

5. Start or restart the DHCP service

Start-Service DHCPServer

or:

Restart-Service DHCPServer

Verify again:

Get-Service DHCPServer

Expected status:

Status   Name         DisplayName
------   ----         -----------
Running  DHCPServer   DHCP Server

6. If the DHCP server is domain-joined, authorize it in AD

Use the server’s static IP address:

$ServerIP = "192.168.XX.10"
$ServerFQDN = "$env:COMPUTERNAME.powershell.local"

Add-DhcpServerInDC -DnsName $ServerFQDN -IPAddress $ServerIP
Get-DhcpServerInDC

Replace XX with the student’s network number.

Simple version

Install-WindowsFeature DHCP -IncludeManagementTools
Get-WindowsFeature DHCP
Get-Service DHCPServer

This installs and verifies the DHCP Server role.

Power Shell: DHCP Server and Client

Authorize DHCP server in Active Directory if domain joined.

The lab includes this wording:

Authorize the DHCP server so it can lease addresses in an AD domain environment.
If your lab is not domain joined, document that authorization was not applicable and continue only if instructed.

The commands included are:

# Run on the DHCP server. Replace values as needed.
$ServerIP = "192.168.XX.10"
$ServerFQDN = "$env:COMPUTERNAME.powershell.local"

Add-DhcpServerInDC -DnsName $ServerFQDN -IPAddress $ServerIP
Get-DhcpServerInDC

the server listed as an authorized DHCP server.

verify the server is domain joined:

Get-CimInstance Win32_ComputerSystem | Select-Object Name, Domain, PartOfDomain

And after authorization:

Get-DhcpServerInDC

That makes the evidence clearer.

How to? Disable VirtualBox DHCP for host-only network

Ref: AI Tools, ChatGPT, Similar

“Disable VirtualBox DHCP for host-only network” means:

Turn off the built-in DHCP server inside VirtualBox, so your Windows Server DHCP service becomes the only DHCP server giving IP addresses to the client VM.

Why this matters

In your DHCP lab, students are installing and configuring DHCP Server on Windows Server 2019.

But VirtualBox host-only networks can also have their own DHCP server. If VirtualBox DHCP is enabled, then the client VM may get an IP address from VirtualBox, not from the Windows DHCP Server.

That would make the lab confusing because students may think their Windows DHCP scope is working, but actually VirtualBox gave the IP.

Simple example

You want this:

Windows Server DHCP VM
192.168.XX.10
gives IP addresses to client

Not this:

VirtualBox DHCP
gives IP addresses to client

So we disable VirtualBox DHCP.

What to disable

Disable only this:

VirtualBox Host-Only Network DHCP Server

Do not disable the host-only adapter itself.

The host-only adapter/network should still exist so the VMs can communicate with each other.

Steps in VirtualBox

In VirtualBox:

  1. Open VirtualBox Manager
  2. Go to Tools
  3. Open Network
  4. Select the Host-only Network
  5. Go to the DHCP Server section/tab
  6. Uncheck or disable Enable Server
  7. Apply/save

In some versions:

File → Tools → Network Manager → Host-only Networks → DHCP Server → Disable

or:

File → Host Network Manager → select host-only adapter → uncheck DHCP Server

After disabling it

Your DHCP lab should use:

MachineIP setting
DHCP Server VMStatic IP, example 192.168.XX.10
Client VMDHCP / automatic IP
VirtualBox DHCPDisabled

Then the client should get an address from your Windows DHCP scope, for example:

192.168.XX.100 to 192.168.XX.150

Student-friendly wording

Disable VirtualBox DHCP on the host-only network so that the Windows Server DHCP role is the only DHCP server in this lab. Keep the host-only network enabled, but turn off its built-in DHCP server. Otherwise, the client may receive an IP address from VirtualBox instead of from your Windows DHCP scope.

DHCP: Powershell Commands

Commands that work in Windows PowerShell 5.1

These DHCP/networking commands are intended for Windows Server PowerShell:

Install-WindowsFeature DHCP
Install-WindowsFeature DHCP -IncludeManagementTools
Import-Module DHCPServer
Add-DhcpServerv4Scope
Set-DhcpServerv4OptionValue
Get-DhcpServerv4Scope
Get-DhcpServerv4Lease
Get-DhcpServerInDC
Add-DhcpServerInDC
Restart-Service DHCPServer
Get-Service DHCPServer

Related:

Get-NetAdapter
Get-NetIPAddress
New-NetIPAddress
Set-DnsClientServerAddress
Get-DnsClientServerAddress
ipconfig /all

CmdletBinding

Ref: AI Tools/ChatGPT

[CmdletBinding()] turns a normal PowerShell function into an advanced function.

That means the function behaves more like a real PowerShell cmdlet.

Basic example

Normal function:

function Install-Office {
    param(
        [string]$Version
    )

    Write-Host "Installing Office $Version"
}

Advanced function:

function Install-Office {
    [CmdletBinding()]
    param(
        [string]$Version
    )

    Write-Host "Installing Office $Version"
}

What [CmdletBinding()] does

It gives your function cmdlet-style behavior, such as:

FeatureMeaning
Common parametersAllows parameters like -Verbose, -Debug, -ErrorAction
Better parameter handlingWorks better with [Parameter()], mandatory parameters, parameter sets
Pipeline supportWorks well with ValueFromPipeline and process {}
Professional structureMakes custom functions look and behave more like built-in cmdlets

Example with -Verbose

function Test-LabFunction {
    [CmdletBinding()]
    param(
        [string]$Name
    )

    Write-Verbose "The function received the name $Name"
    Write-Host "Hello $Name"
}

Run normally:

Test-LabFunction -Name "Sayed"

Output:

Hello Sayed

Run with -Verbose:

Test-LabFunction -Name "Sayed" -Verbose

Output:

VERBOSE: The function received the name Sayed
Hello Sayed

Without [CmdletBinding()], -Verbose would not work the same way.

Example with mandatory parameter

function Install-Office {
    [CmdletBinding()]
    param(
        [Parameter(Mandatory)]
        [ValidateSet("2013","2016")]
        [string]$Version
    )

    Write-Host "I installed Office $Version."
}

Now if the user runs:

Install-Office

PowerShell asks for the missing mandatory value:

cmdlet Install-Office at command pipeline position 1
Supply values for the following parameters:
Version:

Simple explanation for students

[CmdletBinding()] upgrades a function into an advanced PowerShell function. It allows the function to support cmdlet-like features such as -Verbose, better parameter behavior, validation, parameter sets, and pipeline-friendly design.

Very short version

[CmdletBinding()]

means:

“Treat this function like a professional PowerShell cmdlet.”

The 12 Agile Principles

From AI Tools as is:

The 12 Agile Principles explain how Agile teams should work in practice. Your slides group them as Principles 1–6 and 7–12: early delivery, welcoming change, frequent delivery, daily business/developer cooperation, motivated teams, face-to-face communication, working software as progress, sustainable pace, technical excellence, simplicity, self-organizing teams, and regular reflection/adaptation.

#Agile PrincipleSimple meaning for students
1Customer satisfaction through early and continuous deliveryDeliver useful product pieces early and often so customers see value quickly.
2Welcome changing requirements, even late in developmentAgile accepts that needs may change; the team adjusts instead of resisting change.
3Deliver working software frequentlyRelease usable increments often, usually in weeks rather than months.
4Business people and developers work together dailyProduct/business stakeholders should stay closely involved with the development team.
5Build projects around motivated individualsGive capable people support, trust, and ownership of the work.
6Face-to-face conversation is the most effective communicationDirect conversation is usually faster and clearer than long documents or email chains.
7Working software is the primary measure of progressReal completed product matters more than reports, plans, or documents alone.
8Sustainable development paceTeams should work at a pace they can maintain over time without burnout.
9Continuous attention to technical excellence and good designGood design, clean code, testing, and quality practices make the team more Agile.
10Simplicity — maximize the work not doneDo only the work needed to deliver value; avoid unnecessary features or complexity.
11Self-organizing teams create the best resultsTeams closest to the work should decide how to do the work.
12Regular reflection and adaptationTeams should regularly review how they work and improve their process.

A simple teaching line:

Agile is not just “work faster.” Agile means delivering value early, accepting change, collaborating closely, building quality, and improving continuously.

Kanban Cadences

Kanban cadences are the regular meetings or feedback loops used in Kanban to manage flow, improve delivery, and remove blockers. Kanban does not require fixed sprints like Scrum. Instead, work flows continuously, and cadences help the team inspect and improve that flow.

Your slides describe Kanban using visual workflow, pull system, continuous flow, WIP limits, and continuous improvement.

Kanban cadencePurposeWhat the action looks like
Daily Kanban MeetingCheck flow, blockers, and WIP limits.Team looks at the board, usually from right to left: Done → Review → In Progress → To Do. They ask: What is blocked? What can move forward? Are WIP limits exceeded?
Replenishment MeetingDecide what work should enter the system next.Team/Product Owner reviews the backlog and selects ready, high-priority items to move into “Ready” or “To Do.”
Delivery Planning MeetingDecide when completed work will be released or delivered.Team checks finished items and plans release timing, packaging, handoff, or customer delivery.
Service Delivery ReviewReview how well the team is delivering value.Team checks lead time, cycle time, throughput, quality, and customer satisfaction.
Operations ReviewReview performance across teams/services.Managers or multiple teams look at system-level issues, bottlenecks, capacity, and coordination problems.
Risk ReviewIdentify and manage delivery risks.Team reviews blocked items, aging work, dependencies, recurring defects, or items stuck too long.
Strategy ReviewAlign Kanban work with business goals.Leadership or product stakeholders check whether the work being delivered still supports organizational priorities.
Retrospective / Improvement MeetingImprove the process.Team discusses what to improve: WIP limits, policies, bottlenecks, handoffs, quality checks, or workflow design.

A simple explanation:

In Scrum, the team uses sprint events. In Kanban, the team uses cadences. These cadences are regular checkpoints that help the team manage continuous flow.

For students, you can say:

Kanban cadences are not about starting and ending a sprint. They are about keeping work moving smoothly through the board.

Example:

A team has many items stuck in Review. During the Daily Kanban Meeting, they notice the Review column is full. During the Service Delivery Review, they see cycle time is increasing. During the Retrospective, they decide to reduce new work and assign more people to help with reviews. That is how Kanban cadences support continuous improvement.

Scrum events, XP events, Kanaban Events, Agile Events

From AI Tools/ChatGPT as is:

Key idea

Scrum has formal events.
XP has practices/activities more than formal events.
Kanban has cadences/meetings, not required sprints.
Agile itself is an umbrella approach, so it does not prescribe one fixed set of events.

Your Scrum slides identify the five Scrum events as Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

MethodologyEvent / ActivityWhat it meansWhat the action looks like
ScrumSprintFixed time-box where the team creates a usable product increment. Usually 1–4 weeks.Team works on selected sprint backlog items and aims to meet the sprint goal.
ScrumSprint PlanningMeeting at the start of the sprint to decide what will be done and how.Product Owner explains top backlog items; team selects work; team creates sprint goal and sprint backlog.
ScrumDaily Scrum / Daily StandupShort daily meeting to inspect progress and coordinate work.Team discusses progress toward sprint goal, blockers, and next steps.
ScrumSprint ReviewEnd-of-sprint meeting to inspect the product increment with stakeholders.Team demonstrates completed work and gets feedback.
ScrumSprint RetrospectiveEnd-of-sprint reflection meeting to improve team process.Team discusses what went well, what did not, and what to improve next sprint.

XP events / practices

XP, or Extreme Programming, is Agile but more engineering-focused. It does not usually list “events” the same way Scrum does. It uses short iterations and technical practices.

XP practice / activityWhat it meansWhat the action looks like
Iteration PlanningTeam plans work for a short iteration, often 1–2 weeks.Customer/Product Owner selects stories; team estimates and commits to work.
Small ReleasesDeliver working software frequently.Release a small, useful feature quickly instead of waiting for a large release.
Pair ProgrammingTwo developers work together on the same code.One writes code, the other reviews/thinks; they switch roles.
Test-Driven Development / TDDTests are written before code.Write test → write code → pass test → refactor.
Continuous IntegrationCode is integrated and tested frequently.Developers commit code often; automated tests run regularly.
RefactoringImprove internal code design without changing visible behavior.Clean duplicate code, simplify functions, improve maintainability.
Customer FeedbackCustomer/business representative gives frequent clarification.Team asks questions and adjusts stories based on feedback.

Kanban events / cadences

Kanban does not require fixed sprint events. Kanban as visual workflow, pull system, continuous flow, WIP limits, and continuous improvement.

Kanban cadence / meetingWhat it meansWhat the action looks like
Daily Kanban MeetingShort meeting focused on flow, blockers, and WIP limits.Team looks at the board from right to left: what is blocked, what can move to Done, what needs help?
Replenishment MeetingDecides what new work should be pulled into the system.Product Owner/team reviews backlog and selects ready items for To Do.
Delivery Planning MeetingPlans when completed work can be released or delivered.Team checks finished items and decides delivery timing.
Service Delivery ReviewReviews how well the team is delivering work.Team checks lead time, cycle time, throughput, and customer satisfaction.
Operations ReviewLooks at performance across teams or services.Managers/teams review bottlenecks and system-level improvement needs.
Risk ReviewReviews blocked, delayed, or risky work items.Team identifies recurring blockers and actions to reduce risk.
Retrospective / Improvement MeetingReflects on process improvement.Team discusses how to improve flow, reduce bottlenecks, or adjust WIP limits.

Agile events

Agile itself does not define a fixed event list. Agile is a broad mindset based on values and principles such as customer collaboration, responding to change, frequent delivery, and team reflection. Agile as emphasizing flexibility, customer feedback, and iterative progress.

Agile activityWhat it meansWhat the action looks like
PlanningDecide what value to deliver next.Prioritize backlog, select stories, estimate work.
Iteration / Sprint WorkBuild a small increment of value.Team develops, tests, and integrates features.
Daily CoordinationKeep team aligned and remove blockers.Short daily check-in or board review.
Review / DemoGet feedback on completed work.Show working product to stakeholders.
Retrospective / ReflectionImprove the process.Team identifies lessons learned and improvement actions.
Backlog RefinementPrepare future work.Clarify user stories, split large items, add acceptance criteria.
Release / DeliveryDeliver usable value to users.Deploy or hand over completed product increment.

Simple explanation

You can say:

Scrum has five formal events. XP has short iterations and engineering practices. Kanban has continuous flow and optional cadences. Agile is the umbrella, so events depend on the specific Agile framework being used.

A very simple comparison:

FrameworkFixed sprint?Formal events?Main focus
ScrumYesYesSprint-based delivery and inspection/adaptation
XPUsually short iterationsNot like ScrumEngineering quality and frequent feedback
KanbanNoOptional cadencesContinuous flow and WIP control
AgileDependsDependsFlexibility, feedback, customer value

Reflection:

Reflection:

Reflection in Agile means the team regularly looks back at how the work went and decides how to improve.

In Scrum, the formal event for reflection is the Sprint Retrospective. Sprint Retrospective as one of the five Scrum events, along with Sprint, Sprint Planning, Daily Scrum, and Sprint Review.

Simple definition

TermMeaning
ReflectionThinking back on recent work to learn what went well, what did not go well, and what should be improved.
Sprint RetrospectiveA Scrum meeting held at the end of the sprint where the team reflects on process, teamwork, tools, communication, and improvement actions.
AdaptationChanging the team’s approach based on what was learned from reflection.

Why do we need reflection?

Reflection helps the team improve continuously. It supports one of the Agile principles: teams should regularly reflect and adapt. Your slides mention “regular reflection and team adaptation” as part of the Agile principles.

It helps the team answer:

What worked well?
What problems slowed us down?
What should we change in the next sprint?

What the action looks like

At the end of a sprint, the team may hold a retrospective and discuss:

QuestionExample student/team answer
What went well?We completed most of the high-priority user stories.
What did not go well?Some stories were unclear, so estimation was difficult.
What should we improve?Add better acceptance criteria before sprint planning.
What action will we take next sprint?Product Owner will clarify stories before estimation.