GGSGD Field SolutionsEngineering Services
// GSGD Field Solutions · SCCM Deployment Hub

Deploy Windows 11 to HP G8+ Models with SCCM

A practical SCCM deployment guide for imaging HP EliteBook, ProBook, and ZBook G8 through G11 devices with Windows 11 23H2 or 24H2.

Use this guide to prepare Configuration Manager, import Windows source files, add HP driver packages, build a clean task sequence, configure WinPE, and validate each finished laptop before handoff.

Start the SCCM HP G8+ Deployment Guide Download the Deployment Checklist
  • SCCM Current Branch
  • Windows 11 23H2 / 24H2
  • HP G8+
  • Task Sequence
  • WinPE
  • Driver Packages

Overview

This deployment hub shows technicians, SCCM admins, and desktop engineering teams how to use Microsoft Configuration Manager to deploy Windows 11 to supported HP business laptops.

The primary focus is HP G8 and newer models. The workflow is built around repeatable SCCM imaging, clean driver management, task sequence control, and post-deployment validation.

By the end, you should have a working SCCM process for deploying Windows 11 23H2 or 24H2 to HP EliteBook, ProBook, and ZBook G8 through G11 devices.

SCCM Requirements

Before starting, make sure your environment has the following components ready:

  • 01Microsoft Configuration Manager Current Branch 2503 or newer
  • 02Windows ADK for Windows 11
  • 03Windows PE add-on for the Windows ADK
  • 04SCCM Distribution Point
  • 05PXE boot support or SCCM bootable USB media
  • 06Windows 11 23H2 or 24H2 installation source files
  • 07HP driver packs for each supported model generation
  • 08Network access to the SCCM content library and deployment share
  • 09A test collection for pilot deployments

Deployment Workflow

Follow this five-step SCCM workflow to build a clean Windows 11 deployment process for HP G8+ laptops.

  1. Prepare SCCM and Windows ADK

    Install or confirm the required SCCM version, Windows ADK, and WinPE add-on. Update boot images, distribute them to the correct Distribution Points, and confirm that PXE or USB boot media is working.

  2. Import Windows 11 Source Files

    Add Windows 11 23H2 or 24H2 source files to SCCM. Create or update the operating system image package, distribute the content, and confirm that clients can access it during deployment.

  3. Import HP G8+ Driver Packages

    Download the correct HP driver packs for each supported EliteBook, ProBook, or ZBook generation. Import the drivers into SCCM, organize them by model and generation, and distribute the packages to the right Distribution Points.

  4. Build the SCCM Task Sequence

    Create a task sequence that partitions the disk, applies Windows, injects the correct HP drivers, joins the domain if required, installs applications, applies updates, and runs cleanup or validation steps.

  5. Deploy, Test, and Validate the Image

    Deploy the task sequence to a pilot collection first. Image one device from each supported HP model line, confirm driver detection, verify application installs, test network and BitLocker behavior, and complete the validation checklist before expanding deployment.

Recommended Task Sequence Flow

Use this structure as the starting point for the SCCM task sequence:

  1. 01Restart in Windows PE
  2. 02Gather device information
  3. 03Set computer name
  4. 04Format and partition disk
  5. 05Apply Windows 11 operating system image
  6. 06Apply Windows settings
  7. 07Apply network settings
  8. 08Inject HP model-specific drivers
  9. 09Install Configuration Manager client
  10. 10Install required applications
  11. 11Apply Windows updates
  12. 12Enable BitLocker if required
  13. 13Run post-deployment validation script
  14. 14Restart into Windows
  15. 15Confirm deployment success

Network configuration for PXE

Most stuck deployments are not SCCM problems — they are network problems. PXE works between three machines in three different VLANs: the laptop being imaged, the DHCP server, and the SCCM Distribution Point with PXE enabled. If any one of those links is wrong, the laptop sees nothing on screen and the technician assumes the task sequence is broken.

Use this section before you blame SCCM. Verify the network path first.

Download the PXE Troubleshooting Cheatsheet (PDF)Free, no account required · 2 pages · everything below in printable form.

When PXE does nothing — the top 7 reasons

  1. No DHCP relay (IP helper) on the client VLAN

    The laptop and the DHCP/SCCM server are on different subnets. Without `ip helper-address` on the client VLAN interface, the DHCP DISCOVER never reaches the server.

  2. DHCP options 66/67 still set from a legacy WDS server

    Options 66/67 hard-pin clients to one PXE server. Remove them when you move to SCCM PXE (use IP helpers instead).

  3. UEFI vs BIOS boot file mismatch

    BIOS clients need `wdsmgfw.com` / `pxeboot.com`, UEFI clients need `wdsmgfw.efi`. SCCM serves both — confirm the client's firmware is set correctly.

  4. Secure Boot blocking the WinPE boot image

    Your boot image must be signed. Update the boot image in SCCM and redistribute. Disable Secure Boot temporarily only if signing is broken.

  5. Switch port has spanning-tree convergence delay

    STP holds the port for ~30 seconds before forwarding. The laptop times out on PXE before STP settles. Enable PortFast (Cisco) or Edge Port (Aruba/HP) on access ports.

  6. PXE responder service not started on the DP

    On the SCCM Distribution Point, confirm the `Windows Deployment Services` and `ConfigMgr PXE Responder` services are running. Restart after enabling PXE.

  7. Firewall blocks UDP 67/68/69/4011 between subnets

    DHCP (67/68), TFTP (69), and Proxy DHCP (4011) must traverse from the client VLAN to the DP. If you have an internal firewall between VLANs, open these UDP ports.

DHCP relay (IP helper) — the right approach for SCCM PXE

When the laptop, DHCP server, and SCCM DP live on different VLANs, configure DHCP relay on every client VLAN that needs to image. Two helpers: one to your DHCP server, one to the SCCM DP. Do not use DHCP options 66/67 with SCCM.

! Cisco IOS — client VLAN interface
interface Vlan20
 description Workstation_VLAN
 ip address 10.20.0.1 255.255.255.0
 ip helper-address 10.10.5.10    ! DHCP server
 ip helper-address 10.10.5.20    ! SCCM Distribution Point (PXE)
!
! Aruba / HPE ArubaOS-CX equivalent
interface vlan 20
 ip helper-address 10.10.5.10
 ip helper-address 10.10.5.20

Firewall ports PXE actually needs

If clients and the SCCM DP are separated by an internal firewall, open these from the client VLAN to the DP. Without these the laptop sees DHCP but never finishes the boot image transfer.

PortProtoPurpose
67 / 68UDPDHCP DISCOVER / OFFER
69UDPTFTP — boot image download
4011UDPProxyDHCP (PXE binding)
80 / 443TCPHTTP(S) — content + WinPE peer cache
445TCPSMB — fallback content source
8530 / 8531TCPWSUS / SCCM software update point
10123TCPClient notification (CMG / push)

Switch port settings for imaging

  • Enable PortFast (Cisco) or Edge Port (Aruba/HP) on every access port a tech will image from — STP convergence kills PXE.
  • Disable 802.1X on imaging ports, or pre-stage the laptop's MAC in NAC for guest VLAN bypass during deployment.
  • Confirm the port is in the same VLAN that has the DHCP IP-helpers you configured.
  • Auto-negotiate speed/duplex — most HP G8+ NICs are 1 Gbps; older docks may renegotiate to 100 Mbps and break PXE timing.
  • If imaging through a dock: confirm the dock passes through PXE (some Type-C docks block UEFI PXE on first boot).

HP G8+ firmware checklist

  • F10 BIOS → Advanced → Boot Options: UEFI Boot enabled, Legacy disabled.
  • Network Boot: enabled. IPv4 PXE: enabled (IPv6 PXE off unless your environment supports it).
  • Secure Boot: keep ON. Your SCCM boot image must be signed. If you have to disable Secure Boot to PXE, your boot image is the real problem.
  • Intel VMD (G10/G11): if enabled, inject the Intel RST VMD driver into the boot image, or NVMe is invisible to WinPE.
  • Wake-on-LAN: enable if you want SCCM to wake devices for overnight imaging.
  • BIOS password: pre-set so the technician does not need to clear it after deployment.

5-minute diagnostic when PXE does nothing

  1. 01On the laptopPress F12 (or F9 on HP) at boot. If you see no "Start PXE over IPv4" line, the firmware is set to Legacy / Network Boot is disabled. Fix in F10 BIOS.
  2. 02On the switchConfirm the access port is up and assigned to the correct imaging VLAN. Run `show interfaces status` and `show vlan brief`. Verify PortFast/Edge is on.
  3. 03On the DHCP serverWatch the lease pool while the laptop boots. If no DISCOVER arrives, the IP helper is missing or wrong. If a lease is issued but no boot file is offered, the DP-side helper is missing.
  4. 04On the SCCM DP`Get-Service WDSServer, SccmExec` should both be Running. Check `C:\SMS_DP$\sms\logs\smspxe.log` — every PXE request shows up here. No entries = traffic never arrived.
  5. 05End-to-endFrom a server inside the client VLAN run `Test-NetConnection -ComputerName <DP> -Port 4011` (UDP probe via tnc is limited — also try `nslookup` and `Test-NetConnection 445`). If TCP/UDP probes fail, the firewall rule is missing.

Downloads and Resources

Every file is free. The complete toolkit requires a quick free account.

Start Here: SCCM HP G8+ Deployment Guide

A plain-English starting point for building an SCCM imaging process for HP G8 through G11 business laptops.

Download Guide

Simplest Deployment Process

A one-page checklist that walks from "I have an SCCM server" to "I have a freshly imaged HP laptop."

Download Process

Windows 11 23H2 / 24H2 Task Sequence Guide

Step-by-step guidance for creating a Windows 11 task sequence in SCCM, including source files, boot images, driver packages, and deployment collections.

Download Task Sequence Guide

HP G8+ Driver Import Guide

Instructions for organizing, importing, and applying HP driver packs for EliteBook, ProBook, and ZBook G8 through G11 models.

Download Driver Guide

WinPE Prompt UI

A technician-friendly WinPE prompt for capturing computer name, department, asset tag, and deployment options before imaging begins.

Download WinPE Prompt

Post-Deployment Validation Checklist

A field checklist for verifying drivers, activation, domain join, BitLocker, applications, Windows updates, network connectivity, and user readiness.

Download Checklist
Free account required

Complete SCCM Deployment Toolkit

A complete collection of SCCM deployment resources for Windows 11 imaging on HP G8+ models, including scripts, task sequence examples, documentation, and validation tools.

Download Toolkit

Who This Is For

This guide is built for:

  • Desktop engineering teams standardizing Windows 11 deployment
  • SCCM administrators building or cleaning up task sequences
  • Field technicians imaging HP laptops
  • IT teams supporting HP EliteBook, ProBook, and ZBook fleets
  • Organizations moving from manual imaging to repeatable SCCM deployment

What You Will Build

After following the guide, you should have:

  • A working SCCM Windows 11 deployment workflow
  • Organized HP G8+ driver packages
  • A repeatable task sequence for HP business laptops
  • WinPE boot support through PXE or USB media
  • A simple validation process for every completed laptop
  • A cleaner handoff process for technicians and end users

Ready to build a cleaner SCCM imaging process for HP G8 and newer laptops?

Start with the deployment guide, then use the checklist to validate your first test device.

Start the SCCM HP G8+ Deployment Guide Download the Deployment Checklist

Legacy HP G7 material may be available separately, but this guide focuses on HP G8 and newer devices.