MDT Troubleshooting Guide

Useful post/PDF for troubleshooting MDT from Michael Niehaus:
http://blogs.technet.com/b/mniehaus/archive/2012/09/11/troubleshooting-windows-deployments-take-2.aspx
Mirrored the document here (just in case):
Troubleshooting Windows Deployments 2012-09-11

Advertisements

MDT – Deployment Query Date (VBS)

Useful script to determine when you pushed out an image from MDT…

Save the following as a *.VBS file:

Option Explicit
Const strComputer = "."
Const strNamespace = "\root\cimv2"
Const strClassName = "Microsoft_BDD_Info"

Const wbemCimTypeDatetime = 101
'Const wbemCimTypeString = 8
'Const wbemCimtypeBoolean = 11

Dim objSWbemServices: Set objSWbemServices = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & strNamespace)
Dim colInstances: Set colInstances = objSWbemServices.ExecQuery("SELECT * FROM " & strClassName)
Dim iCount, objInstance, objProperty, colProperties
Dim dateTime : Set dateTime = CreateObject("WbemScripting.SWbemDateTime")
On Error Resume Next
Dim o: o = colInstances.count
On Error Goto 0
If Not IsEmpty(o) Then
    iCount = 0
    For Each objInstance in colInstances
        iCount = iCount + 1
        Set colProperties = objInstance.Properties_
        For Each objProperty in colProperties
            If objProperty.cimType = wbemCimTypeDatetime Then
                datetime.Value = objProperty.Value
                If objProperty.Value <> "" Then WScript.Echo objProperty.Name & ": " & datetime.GetVarDate
            Else
                If objProperty.Value <> "" Then WScript.Echo objProperty.Name & ": " & objProperty.Value
            End If
        Next

    Next
Else
    WScript.Echo strClassName & " not found."
End if

Original author – Michael Klinteberg:
http://social.technet.microsoft.com/Forums/en-US/mdt/thread/e783c5ec-da83-4111-80f2-ea4539d603e2

MDT – Deploying a Test Machine to Virtual PC

If you want to run Windows from a Virtual PC image (running on Windows 7) instead of testing on Hyper-V, VMWare or physical hardware, you will need to update the “Validation” settings of your Task Sequence.

Change the processor to “13MHz” in the screenshot below (which is what the processor is emulated at):Virtual PC Validate Settings

Microsoft MDT 2010 – Install SP1 + Support for 512E Hard Drives

Update the WAIK from RTM to include SP1 Features and Enhancements:

1 – Download the WAIK supplement located here

2 – Mount the ISO or burn off to a DVD

3 – Place the ISO or DVD into your MDT Deployment Server

4 – Open an Elevated Command Prompt and enter the following command:

xcopy X:\ "C:\Program Files\Windows AIK\Tools\PETools" /ERUY

It will copy 134 files.

5 – Run the second following command from an Elevated Command Prompt:

xcopy X:\*winpe-dot3svc* "C:\Program Files\Windows AIK\Tools\PETools" /ERY

It will copy 82 files.

(X: refers to your virtual drive or physical drive letter).

At this point, WAIK is now updated to Windows 7 SP1.

Advanced Format Drives have new levels of sector blocks and without a proper driver are not detected by Windows PE RTM. SP1 should fix the issue for you, but adding the latest Intel driver should also help you out.

We will now add the latest Intel Rapid Storage Technology (RST) driver to support advanced formatting of new 512E sector hard drives.

At the time of this writing, the driver was at version 10.6.0.1022 and available here.

Import the drivers into the Deployment Workbench for your Boot WIMs and OS Driver selection profiles.

Now that drivers are updated, we will edit the control files to support the new SP1 version over RTM edition of WAIK.

If you regenerate your boot WIMs at this point, the WIM looks for a RTM code in the registry. Since we are now on SP1, a change has to be made to look for the upgraded components.

NOTE: This breaks the use of Windows RE in Windows PE RTM. If you haven’t used RE in your image deployment solution, don’t worry about it.

If you do, you have to use an unsupported tweak to the Registry to make SP1 think it is RTM.

Reference MS Posting available here. Read and understand the warnings depending on your deployment environment.

Modify the Settings.xml file in the deployment share’s “Control” folder to tell MDT to never use the boot.wim.  The settings look like this:

<Boot.x86.UseBootWim>True</Boot.x86.UseBootWim>
 <Boot.x64.UseBootWim>True</Boot.x64.UseBootWim>

Update them to say:

<Boot.x86.UseBootWim>False</Boot.x86.UseBootWim>
 <Boot.x64.UseBootWim>False</Boot.x64.UseBootWim>

Now, update your Deployment Share’s boot WIMs.

Add the new boot WIMs to your WDS server, and you are ready to rock!

Reference notes from Microsoft regarding 512E and 4k sector hard drives is available here.

Additional write-up by Dell and Advanced Format Disks is available here.