Anavem
Languagefr
How to Deploy Windows 11 with WAPT WADS as an Alternative to MDT

How to Deploy Windows 11 with WAPT WADS as an Alternative to MDT

Deploy Windows 11 workstations over the network using WAPT WADS functionality with PXE boot, WinPE environments, and automated domain integration.

Evan MaelEvan Mael
March 26, 2026 15 min
mediumwapt 9 steps 15 min

Why Choose WAPT WADS Over Traditional MDT for Windows 11 Deployment?

WAPT WADS (Windows Automated Deployment Services) represents a modern alternative to Microsoft's MDT (Microsoft Deployment Toolkit) for deploying Windows 11 across enterprise networks. While MDT has been the traditional choice for Windows deployment, WADS offers significant advantages in terms of simplicity, network efficiency, and maintenance overhead.

What Makes WADS Different from Standard Deployment Methods?

The key differentiator lies in WADS' simplified architecture. Unlike MDT, which requires complex file server setups, manual answer file configuration, and CIFS-based network protocols, WADS uses iPXE and HTTPS for OS image downloads. This eliminates the need for dedicated file servers and reduces network complexity significantly. All necessary files, deployment configurations, and OS updates are bundled into a single WAPT software package, streamlining the entire deployment process.

What Will You Accomplish with This WAPT WADS Tutorial?

By following this tutorial, you'll establish a complete Windows 11 deployment infrastructure using WAPT WADS. You'll learn to create WinPE boot environments, import Windows 11 ISO images, configure automated answer files, and deploy systems both via USB and network PXE boot. The process includes driver integration, domain joining automation, and post-deployment WAPT agent configuration. This approach is particularly valuable for organizations seeking to modernize their deployment processes while maintaining enterprise-grade control and automation capabilities.

Implementation Guide

Full Procedure

01

Install WAPT WADS Package on Management Station

Before using WADS functionality, install the required package on your WAPT management station. Two packages are available: minimal (basic WinPE creation) and full (additional functionality).

wapt-get install tis-wads-console

Open the WAPT Console and navigate to the WADS section. If this is your first time accessing WADS, you'll see a prompt to upload WinPE files.

Pro tip: Install the full WADS package if you plan to deploy multiple Windows versions or need advanced driver integration capabilities.

Verification: Check that the WADS tab appears in your WAPT Console interface and shows no error messages.

02

Upload and Configure WinPE Environment

WinPE (Windows Preinstallation Environment) is the minimal OS that bootstraps your Windows 11 deployment. This step is critical for network-based deployments.

In the WADS Console, click Upload WinPE when prompted. You'll see a configuration dialog with several important options:

  1. Keyboard Layout: Select your physical keyboard layout (US, French, German, etc.)
  2. Certificate Selection: Choose the certificate for signing USB stick files
  3. Network Drivers: Add drivers if your target machines need specific network drivers for PXE boot
Warning: The keyboard layout selection is critical. You'll need to type hostnames in WinPE using this layout, so choose the layout that matches your physical keyboard.

Wait for the upload process to complete. This involves two phases:

  • Upload to WAPT administration computer
  • Upload to WADS Server

Verification: Confirm the WinPE file appears in the WADS Console with a green status indicator showing successful upload to the WADS Server.

03

Import Windows 11 ISO Image

Import your Windows 11 ISO file into WADS. Use the latest official Windows 11 release for best compatibility and security updates.

In the Install ISO section of the main WADS Console:

  1. Click the + button to add a new ISO
  2. Browse and select your Windows 11 ISO file
  3. Choose the appropriate Windows 11 edition (Pro, Enterprise, etc.)
  4. Wait for the upload and processing to complete
# Verify ISO integrity before upload (optional)
Get-FileHash -Path "C:\path\to\windows11.iso" -Algorithm SHA256

The system will extract and process the ISO contents, making them available for deployment. This process can take 15-30 minutes depending on your network speed and server performance.

Pro tip: Keep your Windows 11 ISO files organized by version (22H2, 23H2) and edition to avoid confusion during deployment selection.

Verification: Check that the ISO appears in the Install ISO list with a complete status and shows the correct Windows version information.

04

Configure Driver Bundles for Hardware Compatibility

Add hardware-specific drivers to ensure your Windows 11 deployment works on target machines. This step prevents post-deployment hardware issues.

In the Drivers section of WADS Console:

  1. Click the + button to add a driver pack
  2. Upload your driver bundle (typically a ZIP file containing INF files and drivers)
  3. Associate the driver bundle with your Windows 11 deployment profile

Common driver categories to include:

  • Network adapters (Ethernet, Wi-Fi)
  • Storage controllers (SATA, NVMe)
  • Graphics adapters
  • Audio devices
# Example: Extract and organize drivers
Expand-Archive -Path "drivers.zip" -DestinationPath "C:\temp\drivers"
Get-ChildItem -Path "C:\temp\drivers" -Recurse -Filter "*.inf"

Verification: Confirm driver bundles appear in the Drivers list and show successful upload status. Test with a known hardware configuration if possible.

05

Create Bootable USB Deployment Key

Create a bootable USB stick for initiating Windows 11 deployment on target machines. This method works even without network PXE infrastructure.

Warning: The USB stick MUST be FAT32 formatted and completely empty before starting this process. All data will be erased.

Insert your prepared USB stick into the WAPT administration workstation, then:

  1. Click Create WinPE USB Key in the WADS Console
  2. Select your USB drive from the dropdown list
  3. Choose the keyboard layout (must match your WinPE configuration)
  4. Wait for the USB creation process to complete
# Format USB stick to FAT32 (if needed)
format E: /FS:FAT32 /Q /V:WAPT_DEPLOY

The process creates a bootable USB with:

  • WinPE boot environment
  • WAPT deployment tools
  • Network configuration scripts
  • iPXE boot loader

Verification: Check that the USB stick contains boot files and shows as bootable in your system's boot menu. Test boot on a non-production machine if available.

06

Configure Answer File for Automated Installation

WADS automatically generates answer files, but you can customize them for your environment. This includes domain joining, user accounts, and regional settings.

In the WADS Console, access the answer file configuration:

  1. Select your Windows 11 deployment profile
  2. Click Edit Answer File or Customize Deployment
  3. Configure key settings:
<!-- Example answer file customization -->
<component name="Microsoft-Windows-UnattendedJoin">
    <Identification>
        <JoinDomain>yourdomain.local</JoinDomain>
        <DomainAdmin>administrator</DomainAdmin>
        <DomainAdminPassword>YourPassword</DomainAdminPassword>
    </Identification>
</component>

Key configuration areas:

  • Regional Settings: Time zone, language, keyboard
  • Network Configuration: Domain joining credentials
  • User Accounts: Local administrator settings
  • Windows Updates: Update behavior during deployment
Pro tip: Use WAPT's built-in variables like %COMPUTERNAME% and %DOMAIN% to create dynamic answer files that work across multiple deployments.

Verification: Review the generated answer file XML to ensure all settings match your requirements. Test with a single machine before mass deployment.

07

Initiate Network Deployment on Target Machine

Start the actual Windows 11 deployment process on your target machine using either USB boot or PXE network boot.

For USB Boot Method:

  1. Insert the WAPT deployment USB stick into the target machine
  2. Boot from USB (modify BIOS/UEFI boot order if needed)
  3. WinPE will load and display the WAPT deployment interface
  4. Enter a hostname when prompted (use the correct keyboard layout)

For PXE Network Boot Method:

  1. Ensure target machine is connected to the network
  2. Configure BIOS/UEFI for network boot priority
  3. Boot the machine - it will automatically connect to WAPT WADS
# Check network connectivity in WinPE (if needed)
ipconfig /all
ping wapt-server.yourdomain.local
Warning: The iPXE file provided by WAPT does not support secure boot. Use USB deployment method if secure boot is required on your target machines.

Verification: Confirm the target machine appears in the WADS Console with "Waiting to Deploy" status and shows correct hardware information.

08

Execute Automated Windows 11 Installation

Trigger the automated installation process from the WADS Console and monitor progress through completion.

In the WADS Console:

  1. Select the target host from the machine list
  2. Click Start Deploy button
  3. Confirm the "Waiting to Deploy" status changes to True
  4. Reboot the target machine to the same boot option (USB or network)

The automated installation process includes:

  • Disk partitioning and formatting
  • Windows 11 file copying and installation
  • Driver installation from your uploaded bundles
  • Answer file application (domain joining, user setup)
  • WAPT agent installation and registration
# Monitor deployment progress (on WAPT server)
Get-WAPTDeploymentStatus -ComputerName "TARGET-PC-01"
Get-EventLog -LogName "WAPT" -Newest 50

Installation typically takes 20-45 minutes depending on hardware speed and network bandwidth.

Pro tip: Monitor multiple deployments simultaneously using the WADS Console dashboard. You can queue multiple machines for deployment and track their progress in real-time.

Verification: Watch for the "OS Deploy" tab status to switch to Done in the WADS Console. The target machine should automatically reboot into Windows 11 and appear in your domain.

09

Verify Deployment and Post-Installation Configuration

Confirm successful Windows 11 deployment and complete any remaining configuration tasks.

Immediate Verification Steps:

  1. Check that Windows 11 boots successfully on the target machine
  2. Verify domain joining (if configured)
  3. Confirm WAPT agent is installed and communicating
  4. Test network connectivity and driver functionality
# Verify Windows version and build
Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, WindowsBuildLabEx

# Check domain membership
(Get-WmiObject -Class Win32_ComputerSystem).Domain

# Verify WAPT agent status
wapt-get status
wapt-get update

Post-Deployment Tasks:

  • Install additional software packages via WAPT
  • Apply group policies and security configurations
  • Configure Windows Updates and maintenance schedules
  • Set up user profiles and data migration (if needed)
Pro tip: Create a post-deployment checklist WAPT package that automatically configures common settings, installs essential software, and runs system health checks.

Verification: Run a comprehensive system check including hardware detection, network connectivity, domain authentication, and WAPT package management functionality.

Frequently Asked Questions

What are the main advantages of WAPT WADS over Microsoft MDT for Windows 11 deployment?+
WAPT WADS offers several key advantages over MDT: it uses iPXE and HTTPS instead of CIFS file servers, eliminating complex file server setup requirements. WADS automatically generates answer files rather than requiring manual configuration, and it bundles all deployment files into a single WAPT package. The system supports both USB and network deployment methods, making it more flexible for environments without full PXE infrastructure. Additionally, WADS integrates directly with WAPT's software management system, providing seamless post-deployment package management.
Can WAPT WADS deploy Windows 11 on machines with secure boot enabled?+
WAPT WADS has limited secure boot support depending on the deployment method. When using official WinPE files for USB stick deployment, secure boot is supported and will work normally. However, the iPXE file provided by WAPT does not support secure boot, so network PXE deployments require secure boot to be disabled. For organizations requiring secure boot compliance, the recommended approach is to use the USB deployment method with official Microsoft WinPE files, then re-enable secure boot after deployment completion.
What are the minimum system requirements for running WAPT WADS deployments?+
For the WAPT management station, you need sufficient storage for ISO files and WinPE images (typically 10-20GB per Windows version). Target machines require standard Windows 11 hardware requirements: TPM 2.0, UEFI firmware, 4GB RAM minimum, and 64GB storage. The WAPT agent itself requires only 512MB RAM, 1 CPU, and 300MB drive space. Network infrastructure should support PXE boot if using network deployment, and USB ports must be available for USB-based deployments. All machines should have reliable network connectivity to the WAPT server during deployment.
How does WAPT WADS handle driver integration during Windows 11 deployment?+
WAPT WADS provides a dedicated driver management system within the console. You can upload driver bundles as ZIP files containing INF files and associated drivers, then associate these bundles with specific deployment profiles. The system automatically injects drivers during the Windows installation process, ensuring hardware compatibility from the first boot. Critical drivers like network adapters, storage controllers, and graphics drivers should be included in your driver bundles. WADS also supports adding network drivers directly to the WinPE environment for machines that need specific drivers for PXE boot functionality.
What happens if a WAPT WADS deployment fails or gets interrupted during installation?+
WAPT WADS includes several recovery mechanisms for failed deployments. The system maintains deployment status tracking in the WADS Console, allowing you to monitor progress and identify failure points. If a deployment fails, you can restart the process by selecting the target machine and clicking 'Start Deploy' again. The system will typically restart from the beginning rather than attempting to resume from the failure point. For interrupted deployments, ensure the target machine can boot back to the deployment environment (USB or PXE) and reinitiate the process. Common failure causes include network connectivity issues, hardware compatibility problems, or corrupted ISO files, all of which can be addressed by checking prerequisites and re-uploading necessary files.
Evan Mael
Written by

Evan Mael

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

Sign in to join the discussion