There are a number of known hardware models or configurations that we have seen have some specific issues.

• HP Elitebook 8560w

  • When performing a re-image on this hardware model to Windows 7 x64, even when specifying correct NIC drivers, the drivers are not applied by Windows setup and there is no network access after re-imaging, causing MAG 2 to never run.

• Dell Latitude D620

  • When performing a re-image on this hardware model from Windows XP x86 to Windows XP x86, during the user state capture step, MDT fails.

• PXE Boot Screen hangs at startup

  • When PXE booting a computer, if additional key strokes are in the key buffer when the PXE OS starts up, it may hang at a boot prompt. Pressing enter will allow the startup sequence to continue.

• Gateway NV79C V1.12

  • During PXE boot, the boot menu may flash repeatedly 3 or 4 times until remaining on the screen.

• Blue Screen of Death when re-imaging to Windows XP

  • Depending on hardware configuration, a Blue Screen of Death can be encountered after Windows setup has completed during the initial boot into the new operating system. In some cases this can be resolved by modifying the sysprep.inf and unattend.txt files to ensure that "ExtendOEMPartition=0" is set.

• Import of image missing .driverinfo fails when importing from a mapped drive

  • The mapped drive needs to be mapped in such a way that an Administrator can access it. If the drive was mapped by a standard user then it will not be accessible for import. Ensure that the mapped drive is accessible by an Administrative command prompt or copy the file locally and import from there.

• Error Reached during Re-Image: Dirty Environment Found

  • The cause of this issue is unknown - therefore the following workaround may or may not work for you: Set the flag HideShell=YES in the CustomSettings.ini file (or in the Manual tab in the dashboard).

  • Ref: http://social.technet.microsoft.com/Forums/en-US/mdt/thread/36ed037b-51b1-4053-a248-46bd3ac9ecda/

• Toshiba Satellite L655D PSK2LU-0200C

  • Error reached during bare metal deployment onto this machine make/model: "Unable to determine destination disk". Basically, MDT was unable to determine which disk/partition to use.

    Workaround: Edit the task sequence xml (i.e. D_W7X86_01/ts.xml) in question - removing every variable from
    the <globalVarList> node except those with the names "OSGUID",
    "DestinationDisk" and "DestinationPartition"

• USMT 3 will migrate files, regardless of extension - despite what might have been specified in the configuration file(s).
  • In our testing, we have found that USMT will migrate files regardless of extension. USMT 4 and USMT 5 seem to resolve this issue. However, only USMT 3 can be used with XP to XP deployments, so this issue should be considered.
• MDT Bundle Creation Fails - Error generating PE wim files
  • Certain AV or other security programs can interfere with the use of imagex/dism in mounting WinPE and injecting tools into WinPE. Ensure it is completely off, as sometimes it may appear to be off but still have some process running or can restart itself. Other similar errors may also occur.
• Re-Image with Windows Server 2003
  • Only Service Pack 2 is supported by MDT as the tool BDDRun.exe cannot function correctly otherwise. You can, however, use any 2003 OS Resource as Service Pack does not seem to matter. This holds true for Capture, Bare Metal, and Re-Image.
  • On entry into the new OS, through testing it was discovered that a one-time error might occur wherein you may be required to hit "ok" to bypass the error. Beyond this, the re-image should work as designed. This issue was only found during Re-Image scenarios, and not for Bare Metal.
• USMT StateStore folder persists even after Re-Image
  • this folder persists by design - and should be up
    to the user to remove once they've confirmed that all files and settings have
    been transferred correctly.Consider it a backup - in case things don't go to plan.