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\wdsnbp.com”) 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\wdsnbp.com”) and WDS just running on MDT01:
UEFI Client – Boots perfectly (contacting Server DP1)
BIOS Client – Does not boot (taking hours to recieve dhcp options..)

Solution:

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:

Example:

interface Vlan100
description GEBRUIKERS VLAN
ip address 192.168.101.254 255.255.254.0 show
ip helper-address 192.168.25.6   (DC01)
ip helper-address 192.168.25.7   (DC02)
ip helper-address 192.168.25.30 (MDT01)
end

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

image

MDT Packages & WSUS a very nice feature.

I long time ago I wrote a acticle mdt-automatisch-updates-via-wsus-laten-installeren-tijdens-het-deployen-van-het-os (Dutch) about using wsus with MDT.

After you deploy a Windows 7 SP1 machine updating takes a lot of time.

You can slipstream windows security updates when you deploy a machine… Windows 7 / Windows 8 / Windows 2008 R2 / Windows 2012.

How you do this: It’s quit simpley. Import de WSUS Content in to Packages.

 1

2

3

4

5

The error is normal because not everything is imported.

Important:

Delete every time you do this. Update & Hotfix packages. If you don’t you will end in a error state when you deploy a machine.

Removing Windows 8.1 Built-in Applications

Last year Ben Hunter published a PowerShell script that is designed to remove the built-in Windows 8 applications when creating a Windows 8 image. Well now that Windows 8.1 has been released it must update the PowerShell script to work with Windows 8.1.

The script below takes a simple list of Apps and then removes the provisioned package and the package that is installed for the Administrator. To adjust the script for your requirements simply update the $AppList comma separated list to include the Apps you want to remove. The script is designed to work as part of an MDT or Configuration Manager task sequence. If it detects that you are running the script within a task sequence it will log the to the task sequence folder otherwise it will log to the Windows\temp folder.

I chanced the script a little bit. I don’t want to remove some programs dat Ben Hunter did…

The Script:

<#    
    ************************************************************************************************************
    Purpose:    Remove built in apps specified in list
    Pre-Reqs:    Windows 8.1
    ************************************************************************************************************
#>

#—————————————————————————————————————
# Main Routine
#—————————————————————————————————————

# Get log path. Will log to Task Sequence log folder if the script is running in a Task Sequence
# Otherwise log to \windows\temp

try

{
$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment
$logPath = $tsenv.Value(“LogPath”)
}
catch
{
Write-Host “This script is not running in a task sequence”
$logPath = $env:windir + “\temp”
}
$logFile = “$logPath\$($myInvocation.MyCommand).log”

# Start logging
Start-Transcript $logFile
Write-Host “Logging to $logFile”

# List of Applications that will be removed

$AppsList = “microsoft.windowscommunicationsapps”,”Microsoft.BingFinance”,”Microsoft.BingMaps”,`
“Microsoft.BingWeather”,”Microsoft.ZuneVideo”,”Microsoft.ZuneMusic”,”Microsoft.Media.PlayReadyClient.2″,`
“Microsoft.Media.PlayReadyClient.2″,”Microsoft.XboxLIVEGames”,”Microsoft.HelpAndTips”,”Microsoft.BingSports”,`
“Microsoft.BingNews”,”Microsoft.BingFoodAndDrink”,”Microsoft.BingTravel”,”Microsoft.WindowsReadingList”,`
“Microsoft.BingHealthAndFitness”,”Microsoft.WindowsAlarms”,”Microsoft.Reader”,”Microsoft.WindowsSoundRecorder”,”Microsoft.SkypeApp”

ForEach ($App in $AppsList)

{
$Packages = Get-AppxPackage | Where-Object {$_.Name -eq $App}
if ($Packages -ne $null)
{
  Write-Host “Removing Appx Package: $App”
  foreach ($Package in $Packages)
      {
      Remove-AppxPackage -package $Package.PackageFullName
      }
}
else
{
      Write-Host “Unable to find package: $App”
}
$ProvisionedPackage = Get-AppxProvisionedPackage -online | Where-Object {$_.displayName -eq $App}
if ($ProvisionedPackage -ne $null)
{
      Write-Host “Removing Appx Provisioned Package: $App”
      remove-AppxProvisionedPackage -online -packagename $ProvisionedPackage.PackageName
}
else
{
      Write-Host “Unable to find provisioned package: $App”
}

}

# Stop logging
Stop-Transcript

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.

Solution:

Uninstalling WDS role
Reboot
Installing WDS role

Configuring WDS

Add MDT boot Images.

It works again.

WDS was corrupted Great Sad smile

Remove the Windows 8 Animation during MDT Deployment

In Windows 8 there is a movie that is played for the first time logon and there is a Group Policy setting you can use to disable it. Mikael Nystrom writed a nice MDT Application you can download and install and put it into your task sequence for Windows 8 and you will never ever see it once more. Happy deployment!

Download the zip file, extract it and create a new Application in MDT 2012 Update 1.

Select Application with Source Files

image

Edit Task Sequence

image

MDT & SAMSUNG ATIV Smart PC Tablet Part 1

Last week i was playing with Samsung ATIV Smart PC.

Samsung ATIV Smart PC is a great device. This is one of many Touch laptops from Samsung. This Laptop is also usable as Tablet PC. Because it run Windows 8 x86 you can run al your applications on this device.

De Samsung ATIV Smart PC does not have fast Ethernet nic onboard only a Wifi NIC.

I would like to deploy our company “image” to this device.

1. Download Software Update http://www.samsung.com/us/support/owners/product/XE500T1C-A01US

2. Install Software

3. Search for XE500T1C-A01NL

4. Download al the Drivers and Software

5. Extract all Packages en sort this in Driver and Applications

6. Import the drivers in MDT

7. You need the a NIC I uses the USB 2.0 to Gigabit Ethernet NIC Network Adapter

8. Download the Driver SMSC_LAN7500.zip

9. You find after unpacking in de Windows Folder de driver LAN7500-WDF-v1.2.0.0.exe

10. You can Extract the Driver with “LAN7500-WDF-v1.2.0.0.exe /extract d:\downloads\LAN7500”

11. Import the Drivers in to same Driver Store als descripted in 6.

12. Update Deployment Share Wizard

13. Create A Task Sequence

14. Create a selection Profile descripted here: MDT 2010 Importing automatically the right driver

15. Change import driver on the Task Sequence

16. You need at Least a 4GB USB Stick

17. Format the USB stick with FAT32 How to create a bootable USB drive from an ISO image for UEFI systems

18. Mark the partition als Active
1.Open Command Prompt

2 Type: diskpart

3. At the DISKPART prompt, type: list partition

Make note of the number of the partition that you want to mark as active.

4. At the DISKPART prompt, type:

select partition n

Select the partition, n, you want to mark as active.

5. At the DISKPART prompt, type: active

19. If you’re on Windows 8, double-click your ISO image to mount it. If you’re on earlier versions of Windows, use a 3rd party utility to mount the ISO. Just search the web and you’ll find options. Or, burn the ISO to a DVD and then mount it. Once the ISO is mounted, copy all files and directories over to your newly formatted USB drive by dragging and dropping. You can also do this from the command line using robocopy or xcopy.

20. Delete the install.wim and boot.wim from the sources directory

21. Copy LiteTouchPE_x86.wim from the Boot directory on the MDT server to de Sources Map on the USB Stick

22. Rename LiteTouchPE_x86.wim to boot.wim
WP_20121221_002

23. Disable Secure Boot:
WP_20121221_001

24. Boot From USB

25. You Can deploy now your OS to your Tablet.

Part Two I will write about installing Touch Driver Software/Driver

Deploy Office 2013 with MDT 2012

When you want to deploy Office 2013 with MDT 2012 you must first create a MSP File and saved in Updates Folder:
How to:  Create custom configurations of Office 2013.

1. Copy de Office 2013 install to the Applications folder

2. Create a application:
image

image

image

image

2. Change the Command Line

image
Change Quiet install Command: setup.exe /adminfile \\servername\deploymentshare$\Applications\Microsoft Office 2013 NL x86\Updates\setup.msp

4. Change the Task Sequence:
image

5. Final Deployment