We can absolutely build a small WDS/PXE lab on your personal laptop, and it is actually a good way to understand what is happening at XYZ company.

Since we already have Windows 10 Pro host → VMware → Windows Server 2019 VM, we can build a realistic WDS/PXE lab from scratch and use a second Windows 10/11 VM as the PXE client. 

Your XYZ's Company situation

From what we have described:
 

New laptop
   │
   │ LAN cable
   ▼
F12 → IPv4 NIC
   │
   ▼
DHCP/PXE
   │
   ▼
WDS server IP
   │
   ▼
Boot files downloaded
   │
   ▼
Windows PE / WDS screen
   │
   ▼
Windows 11 installation

Lab architecture 

                 YOUR PHYSICAL LAPTOP
                 Windows 10 Pro
                       │
                     VMware
                       │
        ┌──────────────┴──────────────┐
        │                             │
        ▼                             ▼
 Windows Server 2019 VM        Windows 10/11 VM
 WDS + DHCP                    PXE CLIENT
 192.168.50.10                 DHCP → PXE → WDS
        │                             │
        └──────── Virtual Network ────┘

              www.kumaratuljaiswal.in

Stage 1 — Configure VMware networking

Do this first. 

We need an isolated virtual network so that your experimental DHCP server doesn't interfere with your home/office network.

Open:

VMware → Edit → Virtual Network Editor

Create/use a Host-only network, for example: 

VMnet2
Subnet: 192.168.50.0
Mask:   255.255.255.0

Important:

• Disable VMware DHCP
• If VMware is providing DHCP on VMnet2, disable it.

Why?

• Because eventually Windows Server 2019 will become our DHCP server.

You don't want: 

VMware DHCP
       +
Windows Server DHCP

on the same network. 

You want:

VMware VMnet2
      │
      ├── Windows Server DHCP
      │
      └── Windows PXE Client

Stage 2 — Configure Windows Server 2019 VM

Start your Server 2019 VM.

Go to:

• Control Panel → Network and Internet → Network Connections

Open the Ethernet adapter.

Configure IPv4 manually.

Use:

IP address:       192.168.50.10
Subnet mask:      255.255.255.0
Default gateway:  leave blank
Preferred DNS:    192.168.50.10

For now, don't worry about Internet access.

Your server should basically be:

• SERVER2019
• IP: 192.168.50.10

Now open PowerShell as Administrator:

• ipconfig

You should see: 

IPv4 Address . . . . . . : 192.168.50.10
Subnet Mask . . . . . .  : 255.255.255.0

Then test: 

• ping 192.168.50.10

You should get replies. 

Stage 3 — Install DHCP Server

Now we're going to make your Windows Server behave like an actual corporate deployment server.

Run:

• Install-WindowsFeature DHCP -IncludeManagementTools

Then check:

• Get-WindowsFeature DHCP

You want:

• [X] DHCP Server

Now open:

Server Manager → Tools → DHCP

You'll see: 

DHCP
 └── SERVER2019
      ├── IPv4
      └── IPv6

Stage 4 — Create DHCP Scope

Right-click:

IPv4 → New Scope

Create something like: 

Scope name:
PXE-Lab

IP range: 

Start IP: 192.168.50.20
End IP:   192.168.50.100

Subnet: 

255.255.255.0

 

 

You don't need a gateway for this isolated lab.

Then activate the scope.

You'll have: 

192.168.50.10
       │
       │ Windows Server
       │ DHCP + later WDS
       │
       ├───────────────┐
       │               │
192.168.50.20      192.168.50.21
PXE Client 1       PXE Client 2

Stage 5 — Test DHCP BEFORE WDS

This is important for your troubleshooting skills.

Create your second VM.

For example:

Windows 11 VM

Configure its VMware network adapter to:

VMnet2

Don't use:

NAT
Bridged

Use the same isolated VMnet2 as Server 2019.

Boot the Windows 11 VM.

Inside Windows: 

•  ipconfig

You should eventually get something like: 

IPv4 Address : 192.168.50.20
Subnet Mask  : 255.255.255.0
DHCP Server  : 192.168.50.10

If that happens:

Congratulations — your DHCP portion is working.

Don't move to WDS until this works. 

Stage 6 — Install WDS

Now we're ready for the important part.

On Server 2019:

Install-WindowsFeature WDS -IncludeManagementTools

Verify: 

Get-WindowsFeature WDS*

You should see the WDS role installed.

Open:

Server Manager → Tools → Windows Deployment Services

You should see your server.

Something like:

Windows Deployment Services
        │
        └── Servers
             └── SERVER2019

Stage 7 — Configure WDS

Right-click:

SERVER2019 → Configure Server

You'll go through the wizard.

For your isolated lab, we'll configure WDS as a normal standalone deployment server.

You'll specify a Remote Installation folder.

For example:

D:\RemoteInstall

For example:

• D:\RemoteInstall

If your Server VM only has C:, you can initially use:

• C:\RemoteInstall

But ideally, give the Server VM another virtual disk.

For example:

• C: → Windows Server
• D: → WDS images

Your Windows 10 VM is currently an unknown PXE client. We haven't prestaged/registered it in WDS.

So you want: 

Stage 8 — PXE response settings

The wizard will ask how WDS should respond to PXE clients.

For your lab, select the option that allows WDS to respond to known and unknown clients.

Why?

Because your test Windows 11 VM won't necessarily already exist in WDS.

You want: 

Windows 10 PXE Client
       │
       │ PXE request
       ▼
Windows Server 2019 WDS
       │
       ├── Known client? → Respond
       │
       └── Unknown client? → Respond

Select:

☑ Respond to all client computers (known and unknown)

You do not need to check:

• Require administrator approval for unknown computers.

For this lab, leave that unchecked.

Then click Next.

Your screen should be: 

This is closer to how you'd think about a real deployment server. 

○ Do not respond to any client computers

○ Respond only to known client computers

● Respond to all client computers (known and unknown)

  ☐ Require administrator approval for unknown computers...

Then Next. 

Stage 9 — Add Windows Boot Image

sources
   ├── boot.wim
   └── install.wim / install.esd

 

Boot Images
    ↓
Right-click
    ↓
Add Boot Image

 

 

Stage 10 — Add Windows Install Image

This is an important point because your Windows 11 ISO is currently on the physical Windows 10 host, while WDS is running inside the Windows Server 2019 VM.

You don't need to copy the ISO manually. The easiest method in VMware is to attach the ISO from your physical laptop to the Server 2019 VM's virtual DVD drive.

Your setup will become: 

PHYSICAL LAPTOP
Windows 10 Pro
│
├── Windows 11 ISO
│
└── VMware
      │
      ▼
Windows Server 2019 VM
      │
      │ Virtual DVD Drive
      │
      ▼
Windows 11 ISO
      │
      ├── sources\boot.wim
      └── sources\install.wim
                    │
                    ▼
                  WDS

Step 1 — Shut down Server 2019 VM

You can do this from Windows Server:

Start → Shut down

The VM should be completely powered off. 

Step 2 — Open VMware settings

In VMware Workstation, select:

Windows Server 2019 VM → Edit virtual machine settings

You'll see something like: 

Hardware
  Memory
  Processors
  Hard Disk
  CD/DVD
  Network Adapter

Select:

• CD/DVD (SATA) 

Step 3 — Attach your Windows 11 ISO

Under Connection, select:

Use ISO image file

Then click:

Browse...

Now browse to the location on your physical Windows 10 laptop where your Windows 11 ISO is stored.

For example: 

C:\Users\YourName\Downloads\Win11.iso

Select the ISO.

Make sure:

Connect at power on

is checked.

Then click OK.

Important

You're not copying the ISO into Server 2019.

VMware is simply presenting the ISO on your physical machine as a virtual DVD to Server 2019. 

Step 4 — Start Server 2019

Start your Server 2019 VM.

Log in.

Open:

This PC

You should now see something like: 

Devices and drives

C:  Local Disk

D:  DVD Drive
    Windows 11 

The drive letter might be D:, E:, etc. Don't assume it is D:.

Step 5 — Verify the ISO contents

Open the DVD drive.

You should see folders such as: 

boot
efi
sources
support
setup.exe

Open:

• sources

Look for:

• boot.wim

and:

• install.wim

or possibly:

• install.esd

This distinction matters. 

Step 6 — Add the Boot Image

In Windows Deployment Services: 

Servers
   │
   └── Your Server
         │
         └── Boot Images

Right-click:

• Boot Images → Add Boot Image

Browse to your virtual DVD.

For example:

• D:\sources\boot.wim 

Select boot.wim.

Then continue through the wizard.

Give it a useful name:

• Windows 11 Setup - x64

You should eventually see: 

Step 7 — Add the Install Image

Now:

Install Images
    ↓
Right-click
    ↓
Add Install Image

When it asks for the image group, use:

• Windows 11

Then browse to:

• D:\sources\install.wim

if your ISO contains install.wim.

The wizard should then read the WIM and show the editions contained inside it.

For example: 

Windows 11 Home
Windows 11 Pro
Windows 11 Education

Stage 11 — Now comes the part that matches your Cubic experience

Power off your Windows 11 client VM.

Configure its firmware/network boot so that it can PXE boot.

Start the VM.

Instead of:

Windows Boot Manager

you want:

Network/PXE boot

You should see something conceptually like:

Start PXE over IPv4

 

Then:

DHCP...

Then the client gets:

• 192.168.50.20

Then it communicates with:

• 192.168.50.10

which is your WDS server.

This is essentially the same sequence you see at Cubic when you:

Plug LAN → F12 → IPv4 NIC → connecting to server IP.

Your first milestone

Don't worry about Windows installation yet.

Your first goal is simply:

Windows 11 VM
       │
       │ PXE
       ▼
Windows Server 2019
       │
       │ WDS
       ▼
Windows PE

 If you reach the WDS/Windows PE screen, CONGRATULATIONS 🎉

That means you have successfully reproduced the most important part of your Cubic workflow in your personal lab.

Then we'll move to:

Your next milestone

After installation finishes, we will verify: 

WDS
 ↓
Windows PE
 ↓
Windows 11 Setup
 ↓
Windows 11 Pro
 ↓
Disk partition
 ↓
Installation
 ↓
First boot
 ↓
Windows 11 desktop

Yes. That means your WDS/PXE lab has successfully reached Windows PE. 🎯

Windows 11 PXE Client
        │
        │ F12 → EFI Network
        ▼
DHCP Server 2019
        │
        │ IP: 192.168.50.20
        ▼
WDS Server 2019
        │
        │ PXE boot files
        ▼
Windows PE                         ✅
        │
        ▼
Windows 11 Setup popup            ✅
        │
        ▼
Select Windows 11 Pro
        │
        ▼
Disk partition
        │
        ▼
Install Windows
        │
        ▼
First boot

 NOTE : First thing i want to tell you everything we you are trying to boot or install windows client before this keep Power On, enable WDS service.

Lets again enable WDS  

If you are getting any error like your message: 

Attempting to start up from:
→ EFI Network
>> Start PXE over IPv4
Station IP address is 192.168.50.20
PXE-E16: No valid offer received.

What this tells us

The good part is: 

EFI Network
Start PXE over IPv4
Station IP address: 192.168.50.20 

That confirms your Windows 10 VM is successfully attempting PXE network boot.

The problem is:

• PXE-E16: No valid offer received

This means the PXE client is not receiving a valid DHCP/PXE response that allows it to continue to the WDS server.

So your flow currently is: 

Windows PE
      ↓
Select Windows 11 Pro
      ↓
Disk partition
      ↓
Install Windows
      ↓
First boot

We need to fix DHCP/PXE communication first. Don't touch boot files or boot.wim yet.
 

Then let's consistently use:

IPv4 Address : 192.168.50.20
Subnet Mask  : 255.255.255.0
DHCP Enabled : Yes
DHCP Server  : 192.168.50.10

Windows PXE Client 

Before changing anything, boot the Windows 10 PXE client normally into Windows.

Then open Command Prompt as Administrator and run: 

The most important line is:

• DHCP Server
• If it says:
• DHCP Server . . . : 192.168.50.10

then your Windows Server DHCP is successfully giving the client an address.

If DHCP Server is missing or it shows another address

then we need to fix DHCP before continuing with WDS.

What we have confirmed 

| Check                       | Result            |
| --------------------------- | ----------------- |
| Client connected to network | ✅                 |
| Client received DHCP IP     | ✅                 |
| Correct subnet              | ✅                 |
| DHCP enabled                | ✅                 |
| DHCP Server = Server 2019   | ✅ `192.168.50.10` |

So DHCP is working correctly.

This also explains the PXE message:

• Station IP address is 192.168.50.20
• PXE-E16: No valid offer received

The client is getting a normal DHCP lease, but the PXE/WDS portion isn't responding correctly yet.

Next check — on Server 2019

Don't change anything yet.

On your Windows Server 2019 VM, open PowerShell as Administrator and run:

Get-Service DHCPServer

Then:

• Get-Service WDSServer
• Start-Service -Name "WDDServer" (if WDSServer is disabled) 

I want to see whether both services are running.

Expected:

DHCPServer    Running
WDSServer     Running 

 If the interviewer asks: “Have you worked with WDS/PXE?

“Yes. I have hands-on experience with WDS and PXE in a VMware lab, and I have also been exposed to the same type of network-based Windows deployment workflow in my current IT support environment.

In my lab, I configured Windows Server 2019 with DHCP and WDS on an isolated VMware network. I configured a Windows client VM for PXE boot, verified that it received an IP address from the DHCP server, and configured WDS to respond to PXE clients.

The client then booted through EFI Network using PXE, contacted the WDS server, loaded Windows PE from the boot image, and launched Windows Setup. From there I selected Windows 11 Pro, performed the disk installation, and completed the first boot.

This helped me understand the complete deployment flow from DHCP and PXE to WDS, Windows PE, and the actual Windows installation.”

If they ask about your production experience


Be precise:

“In my current role, I have been exposed to the laptop deployment process where a new laptop is connected through LAN, PXE/network boot is initiated, and the Windows image is deployed through the organization's deployment infrastructure. I don't manage the production WDS server myself, so my deeper configuration experience comes from my personal VMware lab.”

Disclaimer

This WDS/PXE setup is created in an isolated personal VMware lab for educational and troubleshooting practice. The IP addresses, DHCP configuration, WDS settings, and Windows images are lab-specific and may differ from production enterprise environments. Do not apply these configurations to a corporate network or production WDS server without proper authorization and change-management procedures.