Don’t use DHCP Option 60/66/67 when you want to use UEFI & Legacy PXE Boot with MDT

If you want to use EUFI Boot with MDT 2013 Update X.
Don’t use DHCP Option 60/66/67!!!

DC01 = Windows Server 2008 R2 SP1
DC02 = Windows Server 2012
MDT01 = Windows Server 2012 R2

UEFI Client: Dell Laptop E5450
BIOS Client: HyperV Virtual machine with Legacy network adapert

DC1; MDT01 and DHCPServer all in Subnet1.
(IP Helper is set for DHCPServer for DHCP and for DC01 & MDT01 for DHCP and BootP – I checked serveral times if everything is right here)
UEFI Client and BIOS Client in Subnet2.

Situation1 — Using no DHCP Options and WDS running (IP HELPER-ADDRESS):
UEFI Client – Boots perfectly (contacting Server MDT01)
BIOS Client – Boots perfectly (contacting Server MDT01)

Situaion2 — Using no DHCP Options and WDS just running on MDT01:
UEFI Client – Does not boot (no error information is provided)
BIOS Client – Does not boot (no Bootfilename recieved)

Situation3 — Using DHCP Options(Option 66=”IP of MDT01″ Option 67=”\x86\”) and WDS just running on MDT01:
UEFI Client – Does not boot (no error information is provided)
BIOS Client – Boots perfectly (contacting Server DP1)

Situation4 — Using DHCP Options(Option 60=”PXEClient” Option 66=”IP of MDT01″ Option 67=”\x86\”) and WDS just running on MDT01:
UEFI Client – Boots perfectly (contacting Server DP1)
BIOS Client – Does not boot (taking hours to recieve dhcp options..)


On most switches you can configure ip helper-addresses. This is most time al ready configured for the use of DHCP.

Add the IP of the MDT server als ip helper-address:


interface Vlan100
ip address show
ip helper-address   (DC01)
ip helper-address   (DC02)
ip helper-address (MDT01)

How to speed up PXE boot in WDS (MDT)


During a PXE boot, when the boot image file is being loaded in the client, it should not take any longer than a few minutes time depending on the size of the boot.wim and your network. If it seems that your PXE boot times are extremely slow, you may be able to speed up the process by increasing the TFTP block size. This article will show you how to speed up PXE boot in WDS and SCCM.

Trivial File Transfer Protocol (TFTP) is the network protocol used for downloading all files during network boots. TFTP is an inherently slow protocol because it requires one ACK (acknowledgment) packet for each block of data that is sent. The server will not send the next block in the sequence until the ACK packet for the previous block is received. As a result, on a slow network, the round-trip time can be very long.

Change the Maximum Block Size to 16784 on your WDS server Winking smile


PXE booting fails with "PXE-T04: Access Violation" and "PXE-E36: Error Received from TFTP Server

I had a very strange issue. After updating to MDT 2013 and ADK 8.1 wen a client response getting error PXE-T04: Access Violation” and “PXE-E36: Error Received.


Uninstalling WDS role
Installing WDS role

Configuring WDS

Add MDT boot Images.

It works again.

WDS was corrupted Great Sad smile

System Center Virtual Machine Manager 2012 Beta Evaluation

System Center Virtual Machine Manager 2012 delivers industry leading fabric managment, virtual machine management and services deployment in private cloud environments. Virtual Machine Manager 2012 offers key new features that include hypervisor creation and management, network management, storage management, private cloud creation, self-service usage and service creation. It features deep investments in server application virtualization, service design and service modeling all of which can be used to efficiently offer an on-premises private cloud.

Feature Summary

  • Fabric Management
    • Hyper-V and Cluster Lifecycle Management – Deploy Hyper-V to bare metal server, create Hyper-V clusters, orchestrate patching of a Hyper-V Cluster
    • Third Party Virtualization Platforms – Add and Manage Citrix XenServer and VMware ESX Hosts and Clusters
    • Network Management – Manage IP Address Pools, MAC Address Pools and Load Balancers
    • Storage Management – Classify storage, Manage Storage Pools and LUNs
  • Resource Optimization
    • Dynamic Optimization – proactively balance the load of VMs across a cluster
    • Power Optimization – schedule power savings to use the right number of hosts to run your workloads – power the rest off until they are needed
    • PRO – integrate with System Center Operations Manager to respond to application-level performance monitors
  • Cloud Management
    • Abstract server, network and storage resources into private clouds
    • Delegate access to private clouds with control of capacity, capabilities and user quotas
    • Enable self-service usage for application administrator to author, deploy, manage and decommission applications in the private cloud
  • Service Lifecycle Management
    • Define service templates to create sets of connected virtual machines, os images and applica tion packages
    • Compose operating system images and applications during service deployment
    • Scale out the number of virtual machines in a service
    • Service performance and health monitoring integrated with System Center Operations Manager
    • Decouple OS image and application updates through image-based servicing
    • Leverage powerful application virtualization technologies such as Server App-V

System Requirements

  • Supported Operating Systems:Windows 7 Enterprise;Windows 7 Professional;Windows 7 Ultimate;Windows Server 2008 R2;Windows Server 2008 R2 Datacenter;Windows Server 2008 R2 Enterprise
    • Windows Server 2008 R2 (full installation) Standard, Enterprise, Datacenter x64
    • Windows 7 Professional, Enterprise, Ultimate x32, x64
    • Windows Remote Management (WinRM) 2.0
    • Windows PowerShell 2.0
    • Microsoft .NET Framework 3.5 Service Pack 1 (SP1)
    • Windows Automated Installation Kit (AIK) for Windows 7
    • SQL Server 2008 or SQL Server 2008 R2 Standard, Enterprise, and Datacenter
    • Windows Deployment Services (WDS) – (Version on Windows Server 2008 R2)
    • Windows Software Update Services (WSUS) 3.0 SP2 64bit

Download System Center Virtual Machine Manager 2012 Beta Evaluation HERE

MDT Achtergrond Wijzigen

Open de MDT Deployment Share Properties

In de twee tabs Windows PE x86 Settings & Windows PE x64 Settings vind de instellingen.

Bijvoorbeeld: Windows PE x86 Settings


Onder Windows PE Customizations vind je Custom Background Bitmap file:
Deze verwijst standaard naar: %installdir%\Samples\Background.bmp
Eigenlijke map is: C:\Program Files\Microsoft Deployment Toolkit\Samples

Her noem het de huidige Background.bmp naar Background Oud.bmp
Plaats in de zelfde map nu de nieuwe achtergrond met de naam Background.bmp

Je moet nu nog Update Deployment Share doen en zorg er voor dat regenerate boot image aanvinken.

Voeg als laatste de twee wim files opnieuw toe aan WDS en als je alles goed hebt gedaan heb je nu een custom achtergrond tijdens deployen in je achtergrond n.


Essentiele Handleiding voor het uitrollen van Windows 7

Microsoft heeft een gratis E-book ter beschikking gesteld waar door middel van een aantal onderwerpen is uitgelegd wat er allemaal komt bij komen bij een Windows 7 uit rol. Hier komen ook MDT en WDS in voor.  Ik heb het even snel doorgelezen en er zitten zeker een aantal interessante onderwerpen tussen. Lees het pdf goed door.

– Implementatieplatform
– Planning Deployment
– Testen Application Compatibility
– Ontwikkeling Disk Images
– Migrating User State Data
– Deploying Applications
– Voorbereiding Windows PE
– Configuring Windows Deployment Services (WDS)
– Met behulp van Volume Activation
– Implementeren met Microsoft Deployment Toolkit (MDT)


MDT 2010 Officieel Vrijgegeven & MDT 2010 Nieuwe Functies

Microsoft heeft MDT 2010 vrijgegeven. Dit is de tool van Microsoft waarmee OS mee uitgerold kunnen worden. De nieuwe versie heeft heel veel nieuwe functies. Deze versie ondersteund Windows XP, Windows Vista, Windows 7, Windows Server 2003, Windows 2008 en Windows 2008 R2.
Downloaden doe je MDT 2010 HIER

 Michael Niehaus heeft een overzicht gemaakt van alle nieuwe functies en stuk voor stuk uitlegt wat het doet. Ik heb even een mooi overzicht van gemaakt:

Automatically update MDT 2010 boot images in WDS
Automating Long-Running MDT 2010 Tasks

MDT 2010 New Feature #1: Logging directly to the network
MDT 2010 New Feature #2: Gathering virtualization details
MDT 2010 New Feature #3: Suspend and resume a Lite Touch task sequence
MDT 2010 New Feature #4: Folders everywhere
MDT 2010 New Feature #5: Support for multiple deployment shares
MDT 2010 New Feature #6: Drag and drop
MDT 2010 New Feature #7: Boot image creation optimized
MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE
MDT 2010 New Feature #9: Copy and paste support in the Deployment Workbench task sequence editor
MDT 2010 New Feature #10: Detection of signed drivers
MDT 2010 New Feature #11: Windows 7 and Windows Server 2008 R2 support
MDT 2010 New Feature #12: USMT 4.0 hardlink support
MDT 2010 New Feature #13: New task sequence templates
MDT 2010 New Feature #14: Database improvements
MDT 2010 New Feature #15: Finish actions
MDT 2010 New Feature #16: PowerShell support
MDT 2010 New Feature #17: Customizable boot image process
MDT 2010 New Feature #18: Selection Profiles
MDT 2010 New Feature #19: Improved Driver Management
MDT 2010 New Feature #20: General Purpose ConfigMgr wizard
MDT 2010 New Feature #21: Copying extra folders

VMWare vSphere NIC (VMX 2 & VMX 3) Drivers aan MDT 2010 toevoegen

1. Download HIER de drivers die standaard mee gegeven worden met vSphere. Hier zitten ook de de drivers voor VMX2 Enhanced Driver en de VMX 3 Driver.

2. Maak onder Out-of-Box Drivers twee mapjes aan. Zie de afbeelding hieronder.
image image 

3. Importeer de drivers uit de 7zip bestand.

4. Klik de MDT Deployment Share weer aan en klik op Update Deployment Point


6. Wil je dit met Powershell doen klik op view script dan krijg het volgende powerscript te zien:

Add-PSSnapIn Microsoft.BDD.PSSnapIn
New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\Distribution"
update-MDTDeploymentShare -path "DS001:" -Verbose

7. Vergeet niet om de oude LiteTouchPE_x64 & LiteTouchPE_x86 in WDS te verwijderen en opnieuw toe te voegen.


Skipping MDT Wizard Pages (CustomSettings.ini & Bootstrap.ini)

1. Open MDT

2. Ga naar Deployments Points
3. Rechter muis op je deployment point en kies properties
4. Ga naar Rules Tab.


5. Neem de onderstaande instellingen over.


TimeZoneName=W. Europe Standard Time

6. Klik vervolgens op Edit Bootstrap.ini & neem onderstaande settings over.



7. Klik vervolgens op X en kies voor Save.
8. Klik op Apply & OK.
9. Rechtermuis op je deployment en kies voor update. Hij gaat nu het wim & iso bestand updaten.

Opmerking: Vergeet de bijgewerkte WIM image niet opnieuw te koppelen aan WDS anders moet je nog steeds door veel schermen heen klikken.


De gemaakte Deployment Point Image “LiteTouchPE_x86.wim” Toevoegen aan Windows Deployment Services (WDS)

Onder E:DistributionBoot vind je 2 bestanden LiteTouchPE_x86.wim en LiteTouchPE_x86.iso

De WIM kun je aan WDS aan hangen onder Boot Images en de ISO kun je branden als je toevallig een netwerkkaart kaart hebt die geen PXE ondersteund.