Microsoft Deployment Toolkit 2010: Troubleshooting Reference

Microsoft Deployment ®
Toolkit 2010
Troubleshooting Reference
Published: September 2009
For the latest information, please see

microsoft.com/technet/SolutionAccelerators.
The information in this document and any document referenced herein is provided for informational purposes
only, is provided AS IS AND WITH ALL FAULTS and cannot be understood as substituting for customized
service and information that might be developed by Microsoft Corporation for a particular user based upon that
user’s particular environment. RELIANCE UPON THIS DOCUMENT AND ANY DOCUMENT REFERENCED
HEREIN IS AT THE USER’S OWN RISK.
© 2009 Microsoft Corporation. All rights reserved.
If the user of this work is using the work SOLELY FOR NON-COMMERCIAL PURPOSES INTERNALLY
WITHIN A COMPANY OR ORGANIZATION, then this work is licensed under the Creative Commons
Attribution-NonCommercial License. To view a copy of this license, visit http://creativecommons.org/licenses/by-
nc/2.5 or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105,
USA.
MICROSOFT CORPORATION PROVIDES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO

THE INFORMATION CONTAINED IN THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN.
Microsoft Corporation provides no warranty and makes no representation that the information provided in this
document or any document referenced herein is suitable or appropriate for any situation, and Microsoft
Corporation cannot be held liable for any claim or damage of any kind that users of this document or any
document referenced herein may suffer. Your retention of and/or use of this document and/or any document
referenced herein constitutes your acceptance of these terms and conditions. If you do not accept these terms
and conditions, Microsoft Corporation does not provide you with any right to use any part of this document or
any document referenced herein.
Complying with the applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise), or for
any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights or other intellectual property rights
covering subject matter within this document. Except as provided in any separate written license agreement
from Microsoft, the furnishing of this document does not give you, the user, any license to these patents,
trademarks, copyrights or other intellectual property.
Information in this document, including URL and other Internet Web site references, is subject to change
without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail
addresses, logos, people, places and events depicted herein are fictitious, and no association with any real
company, organization, product, domain name, e-mail address, logo, person, place or event is intended or
should be inferred.
Microsoft, Active Directory, ActiveX, BitLocker, SQL Server, Visual Basic, Windows, Windows Server, and
Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective
owners.
Solution Accelerators microsoft.com/technet/SolutionAccelerators

Troubleshooting Reference: Contents iii
Contents
Introduction to Troubleshooting Reference...................................................................................1
Feedback..................................................................................................................................... 1
Known Issues and Workarounds....................................................................................................2
Deployment Workbench..............................................................................................................2
Adding Custom Windows Vista WIM Files...........................................................................2
Error Message “Access to the path \\...\scripts\Autorun.inf is denied” Is Displayed.............3
Understanding Logs.........................................................................................................................4
MDT 2010 Logs...........................................................................................................................4
Operating System Logs...............................................................................................................5
Windows Vista......................................................................................................................5
Windows XP......................................................................................................................... 5
System Center Configuration Manager Operating System Deployment Logs............................6
Identifying Error Codes....................................................................................................................7
Converting Error Codes.............................................................................................................13
Review of Sample Logs.............................................................................................................14
Failure to Access the Database..........................................................................................14
Troubleshooting.............................................................................................................................. 15
Application Installation...............................................................................................................15
Blocked Executables..........................................................................................................15
Lost Network Connections.................................................................................................16
The 2007 Microsoft Office System.....................................................................................16
AutoLogon................................................................................................................................. 17
Logon Security Banners.....................................................................................................17
Prompted for User Credentials...........................................................................................17
BIOS.......................................................................................................................................... 18
Configuration Files.....................................................................................................................18
Database Problems...................................................................................................................19
Blocked SQL Browser Requests........................................................................................19
Named Pipe Connections...................................................................................................19
Deployment Scripts...................................................................................................................21
Credentials_script...............................................................................................................21
ZTIWindowsUpdate............................................................................................................21
Deployment Shares...................................................................................................................22
Failure to Update WIM Files...............................................................................................22
Deployment Wizard...................................................................................................................23
Wizard Pages Are Not Skipped..........................................................................................23
Disks and Partitioning................................................................................................................23
BitLocker Drive Encryption.................................................................................................23
Disk Partitioning Errors.......................................................................................................25
Support for Logical and Dynamic Disks.............................................................................25

iv Microsoft Deployment Toolkit 2010
Domain Join...............................................................................................................................25
Driver Installation.......................................................................................................................26
Combining $OEM$ Mass Storage Drivers with MDT 2010 Mass Storage Logic...............26
Troubleshooting Device Installation with SetupAPI.log......................................................26
New Computer Deployments.....................................................................................................27
Failure to Copy Log Files to Shared Folders......................................................................27
PXE Boot............................................................................................................................ 27
Printers...................................................................................................................................... 29
Product Keys.............................................................................................................................29
Restarting the Deployment Process..........................................................................................29
Sysprep..................................................................................................................................... 30
Joining a Domain................................................................................................................30
The Computer Account Is in the Wrong OU.......................................................................30
Execution Limit...................................................................................................................30
System Center Configuration Manager.....................................................................................31
Task Sequences........................................................................................................................31
Bad Task Sequence Item (Invalid OS GUID) Message in Windows Deployment
Wizard................................................................................................................................ 32
Apply Network Settings......................................................................................................32
Upgrading from BDD 2007—Missing Task Sequence Steps..............................................32
Using Continue on Error.....................................................................................................33
User State Migration Tool..........................................................................................................33
Missing Desktop Shortcuts.................................................................................................33
USMT-related Errors During Deployment—Error 1618......................................................34
Windows Deployment Services.................................................................................................35
WDS Service Fails When PXE Filter Is Installed................................................................35
Windows Imaging Format Files.................................................................................................36
Corrupt WIM File................................................................................................................36
Windows PE.............................................................................................................................. 36
Deployment Process Not Initiated—Limited RAM or Wireless Network Adapter...............36
Deployment Process Not Initiated—Missing Components.................................................37
Deployment Process Not Initiated—Missing or Incorrect Drivers.......................................37
Deployment Process Flow Charts.................................................................................................38
LTI Deployment Process Flowcharts.........................................................................................38
ZTI Deployment Process Flowcharts.........................................................................................50
Finding Additional Help.................................................................................................................. 60
Microsoft Services Premier Support..........................................................................................60
Internet Support.........................................................................................................................60

Troubleshooting Reference: Introduction 1
Introduction to Troubleshooting
Reference
The deployment of operating systems and applications as well as the migration
of user state can be a challenging endeavor, even when you are equipped with
appropriate tools and guidance. This reference, which is part of Microsoft®
Deployment Toolkit (MDT) 2010, provides information on current known issues,
possible workarounds for those issues, and troubleshooting guidance.
Note In this document, Windows applies to the Windows® 7, Windows Vista®, Windows XP
Professional, Windows XP Tablet PC Edition, Windows Server® 2008 R2, Windows Server 2008,
and Windows Server 2003 operating systems unless otherwise noted.
Note The Microsoft Diagnostics and Recovery Toolset (DaRT) contains powerful tools for
recovering and troubleshooting client computers that do not start or have become unstable. You
can use DaRT to determine the cause of a crash, restore lost files, and so on. You can also use
DaRT as a troubleshooting tool when developing and deploying a Windows operating system. For
example, if a built image fails to start correctly, you can start the client computer containing the
image by using ERD Commander—a diagnostic environment. Then, you can explore the client
computer’s hard disk, view the event log, remove updates, change operating system settings, and
so on. DaRT is part of the Microsoft Desktop Optimization Pack (MDOP) for Software Assurance.
To learn more about DaRT, see Microsoft Diagnostics and Recovery Toolset at
http://www.microsoft.com/windows/products/windowsvista/enterprise/dart.mspx.
Feedback
Please direct questions and comments about this guide to
[email protected].
Please provide feedback on the usefulness of this guide by filling out the survey
at http://go.microsoft.com/fwlink/?LinkID=132579.

2 Microsoft Deployment Toolkit 2010
Known Issues and Workarounds

This chapter describes known issues you may encounter while using MDT 2010.
Deployment Workbench
The following are possible solutions for issues that may arise with the
Deployment Workbench.
Adding Custom Windows Vista WIM Files

Problem: The following error might appear when you try to add a custom
Windows Vista Windows Imaging Format (WIM) file to the Deployment
Workbench:
Error during wizard processing

An unexpected error occurred while processing the wizard
results.
Collection was modified; enumeration operation may not
execute.
Possible Solution: You can resolve this issue by applying the update mentioned
in the Microsoft Knowledge Base article, “You cannot create a Windows Vista-
based WIM build in Solution Accelerator for Business Desktop Deployment,” at
http://support.microsoft.com/kb/941595.

Troubleshooting Reference: Known Issues and Workarounds 3
Error Message “Access to the path \\...\scripts\Autorun.inf is

denied” Is Displayed
Problem: The error message “Access to the path \\...\scripts\Autorun.inf is
denied” is displayed when running the Deployment Workbench.
Possible Solution: This can be caused by antivirus software preventing access

to the Autorun.inf file. You can resolve this issue using one of the following
methods:
 Configure the antivirus software to allow access to the file.

 Remove the Autorun.inf file from the:
 installation_folder\Templates\Distribution folder (where installation_folder
is the folder where you installed MDT 2010).
 deployment_share\Scripts folder (where deployment_share is the
deployment share affected).
Note When you remove the Autorun.inf file from these folders, you will need to manually copy
the Autorun.inf file to media folders created in Media in the Deployment Workbench.

Understanding Logs
Before effective troubleshooting of MDT 2010 can begin, you must have a clear
understanding of the many .log files used during an operating system
deployment. When you know which log files to research for what failure condition
and at what time, issues that were once mysterious and difficult to understand
may become clear and understandable.
The MDT 2010 log file format is designed to be read by Trace32, which is part of
the Microsoft Systems Management Server (SMS) 2003 Toolkit 2, available for
download from http://www.microsoft.com/downloads/details.aspx?
FamilyID=61e4e21f-2652-42dd-a04d-b67f0573751d. Use this tool whenever
possible to read the log files, because it makes finding errors much easier.
The rest of this section details the log files created during deployment as well as
during Windows Setup. This section also provides examples of when to use the
files for troubleshooting.
MDT 2010 Logs
Each MDT 2010 script automatically creates log files during its execution. The
names of these log files match the name of the script—for example,
ZTIGather.wsf creates a log file named ZTIGather.log. Each script also updates a
common master log file (BDD.log) that aggregates the contents of the log files
that MDT 2010 scripts create. MDT 2010 log files reside in
C:\MININT\SMSOSD\OSDLOGS during the deployment process. Depending on
the type of deployment being conducted, the log files are moved at the
completion of the deployment to either %WINDIR%\SMSOSD or %WINDIR
%\TEMP\SMSOSD. MDT 2010 creates the following log files:
 BDD.log. This is the aggregated MDT 2010 log file that is copied to a

network location at the end of the deployment if you specify the SLShare
property in the Customsettings.ini file.
 DeployUpdates_Platform.log. This file is created when deployment shares
are updated or when updating Windows Preinstallation Environment
(Windows PE). Platform represents the platform being updated—either 32 bit
(x86) or 64 bit (x64). This log file is useful when troubleshooting Windows PE
driver-integration issues. It resides in the %TEMP% folder.
 LiteTouch.log. This file is created during Lite Touch Installation (LTI)
deployments. It resides in %WINDIR%\Temp\BDDLogs unless you specify
the /debug:true option.

Troubleshooting Reference: Understanding Logs 5
 Scriptname.log. This file is created by each MDT 2010 script. Scriptname

represents the name of the script in question.
 SMSTS.log. This file is created by the Task Sequencer and describes all
Task Sequencer transactions. Depending on the deployment scenario, it may
reside in %TEMP%, %WINDIR%\System32\ccm\logs, or
C:\_SMSTaskSequence, or C:\SMSTSLog.
 Wizard.log. The deployment wizards create and update this file.
 WPEinit.log. This file is created during the Windows PE initialization process
and is useful for troubleshooting errors encountered while starting
Windows PE.
Operating System Logs

Review Windows Setup log files during troubleshooting activities.
Windows Vista
The following list is a subset of the Windows Setup log files that are most useful
for troubleshooting deployment issues. For more detailed information about
Windows Vista Setup log files, see the Microsoft Help and Support article,
“Windows Vista setup log file locations,” at
 Netsetup.log. Resides in %WINDIR%\Debug; useful when troubleshooting

domain join issues
 Setupact.log. Resides in %WINDIR%\panther; lists installation actions and is
useful when investigating failed installations
 Setupapi.dev.log. Resides in %WINDIR%\inf; useful when investigating
failed driver installations
 Setuperr.log. Resides in %WINDIR%\panther; details errors that occurred
during installation
Windows XP
The following log files, located in %WINDIR%, are the most useful when
troubleshooting Windows XP with Service Pack 2 (SP2):
 Netsetup.log. Resides in %WINDIR%\Debug; useful when troubleshooting

domain join issues
 Setupact.log. Lists installation actions; useful when investigating failed
installations

 Setupapi.log. Contains information about hardware detection during

installation; useful for investigating failed driver installations
 Setuperr.txt. Contains information about Setup errors during the installation
 Setuperr.log. Details errors that occurred during installation
 Setuplog.txt. Contains information about Setup actions during the installation
System Center Configuration Manager Operating

System Deployment Logs
For information about which operating system deployment log files Microsoft
System Center Configuration Manager 2007 creates, see Log Files for Operating
System Deployment at http://technet.microsoft.com/en-us/library/bb932135.aspx.
When executing Windows User State Migration Tool (USMT) operations,

MDT 2010 automatically adds the logging options to save the USMT log files to
the MDT 2010 log file locations. The log files and when they are created are as
follows:
 USMTEstimate.log. Created when estimating the USMT requirements

 USMTCapture.log. Created by the USMT when capturing data
 USMTRestore.log. Created by the USMT when restoring data
The ZeroTouchInstallation.vbs script automatically scans the USMT progress log
files for errors and warnings. During this process, the script writes each error and
warning to the ZeroTouchInstallation.log file. (The script writes at least the first
100 errors and warnings while ignoring “Failed to locate the file object” warnings,
because these are too common.) In addition, the script generates event ID 41010
to System Center Operations Manager with the following summary (where
usmt_type is ESTIMATE, SCANSTATE, or LOADSTATE; error_count is the total
number of errors found; and warning_count is the total number of warnings
found):
ZTI USMT <usmt_type> reported <error_count> errors and

<warning_count> warnings
If the error count is greater than 0, this event is an Error type. If the warning
count is greater than 0 with no errors, then the event is a Warning type.
Otherwise, the event is an Informational type.

Troubleshooting Reference: Identifying Error Codes 7
Identifying Error Codes

Table 1 lists the error codes that the MDT 2010 scripts create and provides a
description of each error code. These error codes are recorded in the BDD.log
file.
Table 1. Error Codes and Their Description
Error code Description

5201 A connection to the deployment share could not be made. The
deployment will not proceed.
5206 The Deployment Wizard was canceled or did not complete
successfully. The deployment will not proceed.
5208 DeploymentType is not set. Must set some value for
SkipWizard.
5208 Unable to find the SMS Task Sequencer. The deployment will
not proceed.
5400 Create object: Set class_instance = New class_name
5490 Create MSXML2.DOMDocument.
5495 Create MSXML2.DOMDocument.ParseErr.ErrCode.
5496 LoadControlFile.FindFile: ConfigFile
5601 Verify OS guid: %OSGUID% exists.
5602 Open XML with OSGUID: %OSGUID%.
5610 Verify file.
5630 Verify file: ImagePath.
5640 Verify file: ImagePath.
5641 FindFile: ImageX.exe.
5643 Find BootSect.exe.
5650 Verify directory: SourcePath.
5651 Verify directory: SourcePath\Platform.


5652 FindFile: bootsect.exe.
6001 Verify drive.
6002 Verify drive.
6010 Test for TSGUID.
6020 Robocopy returned value: Value.
6021 Robocopy returned value: Value.
6101 Check for file: DeployCab.
6102 Expand Sysprep files from DEPLOY.CAB.
6111 Run Sysprep.exe.
6121 Run Sysprep.
6191 Test for CloneTag in registry to verify Sysprep completed.
6192 Test for SystemSetupInProgress in registry to verify Sysprep
completed.
6401 Authorized DHCP server.
6501 Computer backup not possible, no network path
(BackupShare, BackupDir) specified.
6502 ERROR - Unable to locate IMAGEX, unable to perform
backup.
6601 GetObject(... root/wmi:BCDStore).
6602 BCD.OpenStore (BCDStore).
6701 Configured protectors.
6702 Moved boot files.
6703 Create BDE partition.
6704 Defragment drive.
6705 Shrink drive.
6706 Testing for more than 1 partition.
6707 Create boot files.
6708 Encrypt the disk.
6709 Connect to MicrosoftVolumeEncryption WMI provider.
6710 Encrypting the disk.
6711 ProtectKeyWithTPM.
6712 ProtectKeyWithTPMAndPIN.


6713 ProtectKeyWithTPMAndStartupKey.
6714 Save external key to file.
6715 Protect with external key.
6716 Save external key to file.
6717 Protect key with numerical password.
6718 GetKeyProtectorNumberialP@ssword.
6718 Save password to file.
6719 Open PasswordFile.
6720 Encrypt the drive.
6721 Open DiskPartFile.
6722 Create partition.
6723 Get existing BDE drive.
6724 Open DiskPartFile.
6727 Attempt to open DiskPartFile.
6729 Create text file DiskPartFile.
6730 Execute cmd /c DISKPART.EXE /s DiskPartFile >>
LogPath\ZTIMarkActive_diskpart.log 2>&1
6731 Find bcdboot.exe.
6732 Connect to Microsoft TPM provider.
6733 Get a TPM instance in the provider class.
6734 Get TPM instance.
6735 Check to see if TPM is enabled.
6736 Check to see if TPM is activated.
6737 Check to see if TPM is owned.
6738 Check to see if TPM ownership is allowed.
6741 Check to see if TPM is owned and ownership is allowed.
6741 TPM Owner Password set
6742 TPM Owner P@ssword set to AdminP@ssword.
6743 Set TPM Owner P@ssword to value.
6745 Check TPM owner.

6746 Check for endorsement key pair.
6748 Check to see if TPM ownership is allowed.
6749 Convert owner p@ssword to owner authorization.
6750 Create endorsement key pair.
6751 Change owner authorization.
6752 Run Cmd.
6753 Validate TPM.
6754 Get BDE instance.
6755 Protect key with TPM.
6756 Check for removable media to configure.
ProtectKeyWithTpmAndStartupKey.
6757 Protect key with TPM and startup key.
6758 Look for BDE pin.
6759 Protect key with TPM and Pin.
6760 Find removable media for BDEKeyLocation.
6761 Protect with external key.
6762 Recovery P@ssword being saved to PasswordFile.
6764 Configure BitLocker policy.
7000 Unable to locate ZTIConfigure.xml; aborting.
7001 Looking for unattend AnswerFile.
7100 ERROR - This script should only run in the full OS.
7101 ERROR - Not enough values supplied for generating
DCPromo answer file.
7102 ERROR - Mandatory properties for creating a new replica DC
were not specified.
7103 ERROR - Mandatory properties for creating a new child
domain were not specified.
7104 ERROR - Mandatory properties for creating a new forest were
not specified.
7105 ERROR - Mandatory properties for creating a new forest were

not specified.
7200 Unable to configure DHCP server because the service is not
installed.
7201 Unable to read the scope details; GetScopeDetails() failed.
7202 Not enough values specified for scope creation.
7203 Not enough values provided to set the IP range for this scope.
7204 No value specified for scope exclusion range.
7300 Unable to issue DNS commands.
7700 Not a New Computer scenario; exiting disk partition.
7701 Disk is not large enough for System and BDE partitions,
Required = 1.5 GB.
7702 Disk is not large enough for System and WinRE partitions,
Required = 10 GB.
7703 DeployRoot is on disk # DiskIndex. Running an OEM
Scenario: Skip.
7704 Running an OEM Scenario: Skip.
7704 Extended and logical partitions are not allowed with BitLocker.
7712 Verify Drive/Volume Drive is present. Format.
7900 Findfile: Microsoft.BDD.PnpEnum.exe.
7901 AllDrivers.Exists("GUID").
7904 AllDrivers.Exists("GUID").
9200 Findfile(PkgMgr.exe).
9601 ERROR - ZTITatoo state restore task should be running in the
full OS; aborting.
9701 Nonzero return code from USMT estimate, rc = Error.
9702 User state capture not possible; insufficient local space and
no network path (UDShare, UDDir) specified.
9703 Nonzero return code from USMT capture, rc = Error.
9704 No valid command line option was specified.
9801 ERROR - Attempting to deploy a client operating system to a
machine running a server operating system.
9802 ERROR - Attempting to deploy a server operating system to a
machine running a client operating system.


9803 ERROR - Machine is not authorized for upgrading
(OSInstall=OSInstall); aborting.
9804 ERROR - Memory MB of memory is insufficient. At least
Memory MB of memory is required.
9805 ERROR - Processor speed of ProcessorSpeed MHz is
insufficient. At least a ProcessorSpeed MHz processor is
required.
9806 ERROR - insufficient space is available on Drive. An
additional Size MB is required.
9807 ERROR - insufficient space is available on Drive. An
additional Size MB is required.
9901 The ZTIWindowsUpdate script should not run in Windows PE.
9902 ZTIWindowsUpdate has run and failed too many times. Count
= Count.
9903 Unexpected issue installing the updated Windows Update
Agent, rc = Error.
9904 Failed to create object: Microsoft.Update.Session.
9905 Failed to create object: Microsoft.Update.UpdateColl.
9906 Critical file File was not found; aborting.
10000 Create object: Set oLTICleanup = New LTICleanup.
10201 Unable to Join Domain Domain. Stop installation.
10203 FindFile(LTISuspend.wsf).
10204 Run Program LTISuspend.
41024 Run ImageX.
52012 All the wizard parameters are not set.
Listing 1 provides an excerpt from a log file that illustrates how to find the error
code. In this excerpt, the error code reported is 5001.
Listing 1. Excerpt from an SMSTS.log File That Contains Error Code 5001
.
.
.
The operating system installation failed. Please contact
your system administrator for assistance.

The action "Zero Touch Installation - Validation" failed

with exit code 5001
.
.
.
Converting Error Codes

Many error codes presented in the log files seem cryptic and difficult to correlate
to an actual error condition. However, the following process demonstrates how to
convert an error code and obtain meaningful information that may assist in
problem resolution.
Problem: An image capture fails with error code 0x80070040.
Possible Solution 1: The error code presented is in hexadecimal format that

you need to convert to decimal format. To do this, you need a scientific
calculator, and the calculator included with Windows operating systems is well
suited to this task.
To convert an error code
1. Click Start, and then point to All Programs. Point to Accessories, and then
click Calculator.
2. From the View menu, click Scientific.
3. Select Hex, and then enter the last four digits of the code—in this case, 0040,
as shown in Figure 1.

Figure 1. Error conversion
Notice that leading zeros are not displayed while the calculator is in
Hexadecimal mode.
4. Select Dec.
The hexadecimal value 40 is converted to a decimal value of 64.
5. Open a Command Prompt window, type NET HELPMSG 64, and then press
ENTER.
The NET HELPMSG command translates the numerical error code into
meaningful text. In the case of the error code provided here, it translates to
“The specified network name is no longer available.”
This information indicates that a networking problem may exist on the target
computer or between the target computer and the server on which the
deployment share resides. These problems might include network drivers not
being installed properly or a mismatch in speed and duplex settings.
Possible Solution 2: Use the Microsoft Exchange Server Error Code Look-up
utility. This command-line utility is valuable in assisting with error code
translation. It is available for download from Microsoft Download Center at
http://www.microsoft.com/downloads/details.aspx?familyid=be596899-7bb8-
4208-b7fc-09e02a13696c.
Review of Sample Logs

Failure to Access the Database
Problem: An error occurs while executing a deployment that used a
CustomSettings.ini file containing numerous sections and specifying, with the
Priority property, the priority of each section to be processed. BDD.log contains
the following error messages:
 ERROR - Opening Record Set (Error Number = -2147217911) (Error

Description: The SELECT permission was denied on the object
'ComputerAdministrators', database 'AdminDB', schema 'dbo'.)
 ADO error: The SELECT permission was denied on the object

'ComputerAdministrators', database 'AdminDB', schema 'dbo'.
(Error #-2147217911; Source: Microsoft OLE DB Provider for SQL
Server; SQL State: 42000; NativeError: 229
 ERROR - Unhandled error returned by ZTIGather: Object required

(424)

Note For clarity, the log file contents above have been represented as they appear while being
viewed using the Trace32 program.
Possible Solution: The issue, as pointed out on the first line of the log file
sample, is that permission to access the database was denied. Therefore, the
script cannot establish a secure connection to the database, possibly because a
user ID and password were not available. As a result, database access was
attempted using the computer account. The easiest way to work around this
issue is to grant everyone Read access to the database.

Troubleshooting Reference: Troubleshooting 16
Troubleshooting
Prior to embarking on in-depth troubleshooting processes, review the following
items and ensure that any associated requirements have been met:
 Installation issues can result if all software and hardware prerequisites have
not been met.
 MDT 2010 uses the tools from the Windows XP Deploy.cab file as part of the
LTI process. This process uses the System Preparation Tool (Sysprep) to
properly prepare the Windows XP master image before capturing the
operating system in a WIM file. Copy the Deploy.cab file into the
deployment_share\Tools\platform folder, where deployment_share is the
name of the share and platform is the name of the platform folder. MDT 2010
will find the Deploy.cab file and extract the necessary files.
Application Installation
Review the problems and solutions for application installation issues:
 Installation source files that are blocked for security reasons as described in
Blocked Executables.
 Loss of network connectivity as described in Lost Network Connections.
 Installation error 30029 while installing the 2007 Microsoft Office system or
related files as described in The 2007 Microsoft Office System.
Blocked Executables
Problem: If installation source files are downloaded from the Internet, it is likely
that they will be marked with one or more NTFS file system data streams. For
more information about NTFS data streams, see File Streams at
http://msdn2.microsoft.com/en-us/library/aa364404(VS.85).aspx. The existence
of NTFS file system data streams might cause an Open File – Security
Warning prompt to be displayed. The installation will not proceed until you click
Run at the prompt.
As Figure 2 shows, you can view NTFS file system data streams using the More
command and the Streams utility, which is available for download from
http://technet.microsoft.com/en-us/sysinternals/bb897440.aspx.

Figure 2. NTFS data streams
Possible Solution 1: Right-click the installation source file, and then click
Properties. Click Unblock, and then click OK to remove the NTFS file system
data streams from the file. Repeat this process for each installation source file
that is blocked by the existence of one or more NTFS file system data streams.
Possible Solution 2: Use the Streams utility, as Figure 2 shows, to remove the
NTFS file system data streams from the installation source file. The Streams
utility can remove NTFS file system data streams from one or more files or
folders at once.
Lost Network Connections

Problem: An installation may fail if it installs device drivers or alters device and
network configurations. These changes may result in a lapse in network
connectivity that causes the installation to fail.
Possible Solution: Implement the ZTICacheUtil.vbs script to enable download

and execution for the installation. This script is designed to tweak the
advertisement to enable download and execute. The download uses Background
Intelligent Transfer Service (BITS) if the System Center Configuration Manager
distribution point is Web-based Distributed Authoring and Versioning (WebDAV)
and BITS enabled. At the same time, it modifies System Center Configuration
Manager to run the ZTICache.vbs script first, which makes sure the program
doesn’t delete itself during the deployment process.
The 2007 Microsoft Office System

Problem: While deploying the 2007 Office system and including a Windows
Installer patch (MSP) file, the installation may fail with error code 30029.
Further investigation in the ZTIApplications.log shows the following messages:

 About to run command: \\Server\Deployment$\Tools\X86\bddrun.exe

\\Server\Share\Microsoft\Office\2007\Professional\setup.exe
/adminfile
\\Server\Share\Microsoft\Office\2007\Professional\file.msp
 ZTI Heartbeat: command has been running for 12 minutes (process

ID 1600) Return code from command = 30029
 Application Microsoft Office 2007 Professional returned an

unexpected return code: 30029
Possible Solution 1: Relocate the MSP file to the Updates directory, and then
run setup.exe without specifying the /adminfile option. For more information
about deploying updates during the installation, see “Deploying the 2007 Office
system” at http://technet2.microsoft.com/Office/en-us/library/78ad4dd8-f15e-
41a9-8bf1-92cfeaac47801033.mspx.
Possible Solution 2: Verify that the MSP file does not have the Suppress
modal box selected. For more information about configuring this setting, see
Overview of 2007 Office System Deployment at http://technet.microsoft.com/en-
us/library/bb490141.aspx.
AutoLogon
Review the problems and solutions for automatic logon issues:
 Interruption of the LTI and ZTI deployment processes because of logon

security banners as described in Logon Security Banners.
 Interruption of the LTI and ZTI deployment processes because of prompts for
user credentials as described in Prompted for User Credentials.
Logon Security Banners

Problem: MDT 2010 task sequences are processed during an interactive user
session, which requires that the target computer be allowed to log on
automatically using a specified administrative account. If a Group Policy object
(GPO) is in place that enforces a logon security banner, this automatic logon will
not be allowed to proceed, because the security banner halts the logon process
while it waits for a user to accept the stated policy.
Possible Solution: Be sure that the GPO is applied to specific organizational

units (OUs) and not included in the default domain GPO. When you add
computers to the domain, specify that they be added to an OU that is not affected
by a GPO that enforces a logon security banner. In the Task Sequence Editor,
include as one of the last task sequence steps a script that relocates the
computer account to the desired OU.

Note If you are reusing existing Active Directory® Domain Services (AD DS) accounts, ensure
that, prior to deploying to the target computer, you have relocated the target computer’s account to
an OU that is not affected by the GPO that enforces the security logon banner.
Prompted for User Credentials

Problem: You created an image of a computer that was joined to the domain.
While deploying the new image to a target computer, the deployment process
halts, because auto-logon does not occur and the user is prompted to enter
appropriate credentials. The deployment process resumes when the credentials
are provided and the user is logged on.
Possible Solution: When capturing images, the source computer should not be
joined to a domain. If the computer was joined to a domain, join the computer to
a workgroup, re-capture the image, and attempt the deployment to a target
computer to determine whether the issue is resolved.
BIOS
Problem: While deploying to a target computer that is equipped with Intel vPro
technology, the deployment may end with a stop error. Even though all updated
drivers have been included as out-of-box drivers in the Deployment Workbench,
the target computer does not start.
Possible Solution: Review the settings in the target computer’s basic

input/output system (BIOS) to determine whether the default Serial Advanced
Technology Attachment (SATA) mode is configured as Advanced Host Controller
Interface (AHCI). Unfortunately, certain Windows operating systems do not
support AHCI by default.
Configuration Files
Problem: While deploying Windows XP using a customized Sysprep.inf file
within MDT 2010 as shown below, MDT 2010 appends a section with just the
information provided by MDT 2010 instead of adding the information to the INF
file. This can cause issues when deploying the image, because Sysprep sees
only the first occurrence of the commented section, not the new section that
MDT 2010 added.
Sysprep.inf prior to MDT 2010 customizations:
[UserData] ;For Windows XP a Volume License Key is required

to avoid activation
FullName=My Test Name
OrgName=My Test Organization
Sysprep.inf after MDT 2010 customizations:
[UserData] ;For Windows XP a Volume License Key is required

to avoid activation
FullName=My Test Name
OrgName=My Test Organization[SysprepCleanup][UserData]
ProductKey=<some valid product key>
ComputerName=TestComputer
During the MiniSetup phase of deployment, only the first [UserData] section
sets the FullName and OrgName properties but does not set the
ComputerName or ProductKey properties. The user is prompted during
MiniSetup for this information.
Possible Solution: Do not use inline comments in INF files for MDT 2010 to
customize.
Database Problems
Review database-related problems and solutions:
 Errors generated as a result of improperly configured firewalls on database

server as described in Blocked SQL Browser Requests.
 Errors generated as a result of broken connections with the database server
as described in Named Pipe Connections.
Blocked SQL Browser Requests

Problem: During the MDT 2010 deployment process, information can be
retrieved from Microsoft SQL Server® databases. However, errors might be
generated that relate to an improperly configured firewall on the database server.
Possible Solution: The Windows Firewall in Windows Server 2008 helps

prevent unauthorized access to computer resources. However, if the firewall is
configured incorrectly, attempts to connect to a SQL Server instance may be
blocked. To access an instance of SQL Server that is behind the firewall,
configure the firewall on the computer that is running SQL Server. For more
information on configuring firewall ports for SQL Server, see the Microsoft Help
and Support article, “How do I open the firewall port for SQL Server on Windows
Server 2008?,” at http://support.microsoft.com/kb/968872.
Named Pipe Connections

Problem: During the MDT 2010 deployment process, information can be
retrieved from SQL Server databases. However, errors might be generated that
relate to broken SQL Server connections. These can be caused by not enabling
named pipe connections in Microsoft SQL Server 2005 or SQL Server 2000.

Possible Solution: To resolve these problems, enable named pipes in

SQL Server. Also, specify the SQLShare property, which it is required when
making a connection to an external database using named pipes. When
connecting using named pipes, use integrated security to make the connection to
the database. In the case of LTI deployments, the user account that you specify
makes the connection to the database. For Zero Touch Installation (ZTI)
deployments that use System Center Configuration Manager, the network access
account connects to the database. Because Windows PE has no security context
by default, you must make a network connection to the database server to
establish a security context for the user who will be making the connection.
The network share that the SQLShare property specifies provides a means to
connect to the server to gain a proper security context. You must have Read
access to the share. When the connection is made, you can then establish the
named pipe connection to the database. The SQLShare property is not needed
and should not be used when making a TCP/IP connection to the database.
Enable named pipe connections by performing the following tasks based on the
version of SQL Server you are using:
 Enable named pipe connections for SQL Server 2005 as described in Enable

Named Pipe Connections in SQL Server 2005.
 Enable named pipe connections for SQL Server 2000 as described in Enable
Named Pipe Connections in SQL Server 2000.
Enable Named Pipe Connections in SQL Server 2005

To enable named pipe connections in SQL Server 2005, perform the following
steps:
1. On the computer running SQL Server 2005 that hosts the database to be

queried, click Start, and then point to All Programs. Point to Microsoft
SQL Server 2005, point to Configuration Tools, and then click SQL Server
Surface Area Configuration.
2. In the SQL Server 2005 Surface Area Configuration dialog box, click
Surface Area Configuration for Services and Connections.
3. In the Surface Area Configuration for Services and Connections –
server_name dialog box (where server_name is the name of the computer
running SQL Server 2005), in Select a component and then configure its
services and connections, go to MSSQLSERVER\Database Engine, and
then click Remote Connections.
4. Click Local and remote connections, click Using both TCP/IP and named
pipes, and then click Apply.

5. In the Surface Area Configuration for Services and Connections –

server_name dialog box (where server_name is the name of the computer
running SQL Server 2005), in Select a component and then configure its
services and connections, go to MSSQLSERVER\Database Engine, and
then click Service.
6. Click Stop.
The MSSQLSERVER service stops.
7. Click Start.
The MSSQLSERVER service starts.
8. Click OK.
9. Close SQL Server 2005 Surface Area Configuration.
For additional information, see the Microsoft Help and Support article, “How to
configure SQL Server 2005 to allow remote connections,” at

Enable Named Pipe Connections in SQL Server 2000

To enable named pipe connections in SQL Server 2000, perform the following
steps:
1. On the computer running SQL Server 2000 that hosts the database being

queried, click Start, and then point to All Programs. Point to Microsoft
SQL Server, and then click Server Network Utility.
2. In the SQL Server Network Utility dialog box, on the General tab, ensure
that Named Pipes is in the Enabled protocols list.
If Named Pipes is in the Disabled protocols list, click Named Pipes, click
Enable, and then click OK.
3. Click Start, and then point to All Programs. Point to Microsoft SQL Server,
and then click SQL Server Service Manager.
4. In the SQL Server Service Manager dialog box, in Services, select
SQL Server, and then click Stop.
5. In the SQL Server Service Manager dialog box, click Start.
6. Close SQL Server Service Manager.
Deployment Scripts
Review MDT 2010–related problems and solutions:
 Prompted for user credentials and may receive error 0x80070035 as

described in Credentials_script.
 Error message “Wuredist.cab not found” appears as described in
ZTIWindowsUpdate.
Credentials_script
Problem: During the last start-up of a newly deployed computer, the user is
prompted to provide user credentials and may receive error 0x80070035, which
indicates that the network path was not found.
Possible Solution: Be sure that the WIM file does not include a MININT or
_SMSTaskSequence folder. To delete these folders, first use the ImageX utility
to mount the WIM file, and then delete the folders.
Note If an Access Denied error occurs when you attempt to delete the folders from the WIM file,
open a Command Prompt window, switch to the root of the image contained in the WIM file, and
then run RD MININT and RD _SMSTaskSequence.

ZTIWindowsUpdate
Problem: If you use the ZTIWindowsUpdate.wsf script to apply software updates
during deployment, note that this script may communicate directly with the
Microsoft Update Web site to download and install the required Windows Update
Agent binaries, scan for applicable software updates, download the binaries for
the applicable software updates, and then install the downloaded binaries. This
process requires that your networking infrastructure be configured to allow the
target computer to gain access to the Microsoft Update Web site.
If the deployment share does not contain the Windows Update Agent installation
files and the target computer does not have appropriate Internet access, error
“wuredist.cab not found” is reported in the ZTIWindowsUpdate.log and BDD.log
files.
Possible Solution: Follow the steps outlined in “ZTIWindowsUpdate.wsf,”

located in the “Scripts” section of the MDT 2010 document, Toolkit Reference.
Deployment Shares
Review deployment share–related problems and solutions:
 Updating WIM files fails when updating a deployment share as described in

Failure to Update WIM Files.
Failure to Update WIM Files

In a “simple” environment:
 For Windows XP, Windows Server 2003, Windows Vista, and Windows

Server 2008, MDT 2010 locates WIMGAPI.DLL in C:\Program Files\Windows
Imaging, which should be in the system PATH. The WIMGAPI.DLL should
not reside in C:\Windows\system32: It will be present in the C:\Program
Files\Windows AIK directory tree, but MDT 2010 rarely uses it from that
location.
 For Windows 7 and Windows Server 2008, MDT 2010 typically picks up
WIMGAPI.DLL from C:\Windows\system32 (always in the path). The version
of this WIMGAPI.DLL must match the version (build) of the operating system.
 On a 64-bit operating system, MDT 2010 always uses the x64 WIMGAPI.DLL
file; only that file should be in the system PATH. On a 32-bit operating
system, MDT 2010 always uses the x86 WIMGAPI.DLL file; only that file
should be in the system PATH. (Other products, such as System Center
Configuration Manager, use the 32-bit version of WIMGAPI.DLL, even on a
64-bit operating system, but they manage and install that version.)

Problem: When attempting to update a deployment share, the user will be

informed that the mounting of one or more .wim files did not succeed.
Possible Solution: Open a Command Prompt window and run where

WIMGAPI.DLL. For the first entry in the list (the first location found by searching
the path), ensure that the Version property matches the build of the Windows
Automated Installation Kit (Windows AIK) that is installed. On Windows 7 or
Windows Server 2008 R2 machines, ensure that the property also matches the
operating system build number.
Deployment Wizard
Review Windows Deployment Wizard–related problems and solutions:
 Windows Deployment Wizard pages are displayed even when LTI is

configured to skip the wizard pages as described in Wizard Pages Are Not
Skipped.
Wizard Pages Are Not Skipped

Problem: A wizard page is displayed even though the MDT database (MDT DB)
or CustomSettings.ini file specify that the wizard should be skipped.
Possible Solution: To properly skip a wizard page, include all properties that
would be specified on that wizard page where appropriate in the MDT DB or
CustomSettings.ini file along with appropriate values. If a property is configured
improperly for a skipped wizard page, that page will be shown. For more
information about which properties are required to ensure that a wizard page is
skipped, see the section, “Providing Properties for Skipped Windows Deployment
Wizard Pages,” in the MDT 2010 document, Toolkit Reference.
Disks and Partitioning

Review disk partitioning problems and solutions:
 BitLocker™ Drive Encryption issues as described in BitLocker Drive

Encryption.
 Disk partitioning errors as described in Disk Partitioning Errors.
 Failures during Refresh Computer deployment scenarios caused by logical or
dynamic disks as described in Support for Logical and Dynamic Disks.

BitLocker Drive Encryption

Using LTI to deploy BitLocker Drive Encryption requires a specific configuration
for proper deployment. The following potential problems may be related to the
configuration of the target computer:
 USB devices, CD drives, DVD drives, or other removable media devices on

the target computer that appear as multiple drive letters, as described in
Devices Appear as Multiple Drive Letters.
 Shrinking drive C on the target computer to provide sufficient unallocated disk
space as described in Problems with Shrinking Disks.
Devices Appear as Multiple Drive Letters

Problem: Some devices can appear as multiple logical drive letters, depending
on how they are partitioned. In some cases, they can emulate a 1.44-megabyte
(MB) floppy disk drive and a memory storage drive. Therefore, Windows may
assign the same device drive letters A and B for floppy disk emulation and F for
the memory storage drive. By default, MDT 2010 scripts use the lowest drive
letter (in this example, A).
Possible Solution: Override the default setting on the Specify the BitLocker
recovery details page in the Windows Deployment Wizard. The Windows
Deployment Wizard summary page displays a warning to inform the user which
drive letter was selected to store BitLocker Drive Encryption recovery
information. In addition, the BDD.log and ZTIBDE.log files record the removable
media devices detected and which device was selected to store the BitLocker
Drive Encryption recovery information.
Problems with Shrinking Disks

Problem: Not enough unallocated disk space exists on the target computer to
enable BitLocker Drive Encryption. To deploy BitLocker Drive Encryption on a
target computer, at least 2 gigabytes (GB) of unallocated disk space is required
to create the system volume. The system volume is the volume that contains the
hardware-specific files needed to load Windows after the BIOS has booted the
computer.
Possible Solution 1: On existing computers, use the Diskpart tool to shrink

drive C so that the system volume can be created. In some instances, though,
the Diskpart tool may not be able to shrink drive C sufficiently to provide 2 GB of
unallocated disk space, possibly because of fragmented disk space within
drive C.
One possible solution to this problem is to defragment drive C. To do so, perform

the following steps:

1. Run the Diskpart shrink querymax command to identify the maximum

amount of disk space that can be unallocated.
2. If the value returned in step 1 is less than 2 GB, clean drive C of any
unnecessary files, and then defragment it.
3. Run the Diskpart shrink querymax command again to verify that more than
2 GB of disk space can be unallocated.
4. If the value returned in step 3 is still less than 2 GB, perform one of the
following tasks:
 Defragment drive C multiple times to ensure that it is fully optimized.
 Back up the data on drive C, delete the existing partition, create a new
partition, and then restore the data to the new partition.
Possible Solution 2: The ZTIBDE.wsf script runs the Disk Preparation Tool
(bdehdcfg.exe) and configures the system volume partition size to 2 GB by
default. You can customize the ZTIBDE.wsf script to change the default, if
necessary. However, modifying the MDT 2010 scripts is not recommended.
Disk Partitioning Errors

Problem: When using LTI to deploy Windows XP on some hardware, the
computer halts with a stop error or stops responding while loading Mup.sys after
the computer attempts to start in mini-setup. This problem occurs because
Windows Vista and Windows PE version 2.0 create disk partitions differently than
Windows XP does. This problem occurs only on computers that use certain BIOS
firmware.
Possible Solution 1: See the Microsoft Help and Support article, “You cannot
install Windows XP successfully after you use Windows Vista or Windows PE 2.0
to create partitions on a hard disk,” at http://support.microsoft.com/kb/931760/en-
us, which describes the problem and provides an update for Windows XP that
can serve as a workaround for the issue. This problem can also occur because of
a hardware abstraction layer (HAL) mismatch between the source computer and
the destination computer or may be the result of a missing mass storage driver.
Possible Solution 2: Add data and values to the registry of Windows PE

version 2.0. These settings change how Windows PE partitions and formats the
hard disk before the Windows XP image is applied. Add the following settings to
the Windows PE registry to work around the issue:
[HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\AL
IGNMENT]
"LessThan4GB"=dword:00000000
"Between4_8GB"=dword:00000000

"Between8_32GB"=dword:00000000
"GreaterThan32GB"=dword:00000000
Support for Logical and Dynamic Disks

Problem: When performing a Refresh Computer deployment scenario, the
deployment process may fail when deploying to a target computer that is using
logical drives or dynamic disks.
Possible Solution: MDT 2010 does not support deploying operating systems to

logical drives or dynamic disks.
Domain Join
Problem: During deployment, you use the Windows Deployment Wizard to
provide all the necessary information for the target computer, including
credentials, domain join information, and static IP configuration. When Setup
finishes, you can see that the system has not joined the domain and is still in a
workgroup.
Possible Solution: An LTI deployment of MDT 2010 configures the static IP

information after the operating system is up and running. If the target computer is
located on a network segment that does not have Dynamic Host Configuration
Protocol (DHCP), an automated domain join specified in Unattend.xml will fail
when no DHCP is present.
Configure Unattend.xml to join a workgroup. Then, use the built-in Recover from
Domain task sequence step to add a step in the task sequence to join the
domain after the static IP has been applied.
Driver Installation
To ensure the best possible user experience, installation of hardware devices
and software drivers should run as seamlessly as possible, with little or no user
intervention. Microsoft provides tools and guidelines to help create installation
packages that meet this goal. For general information about driver installation,
see Driver Lifecycle at http://www.microsoft.com/whdc/driver/install/default.mspx.
Review device driver installation–related problems and solutions:
 Problems that occur when using $OEM$ mass storage drivers with
MDT 2010 as described in Combining $OEM$ Mass Storage Drivers with
MDT 2010 Mass Storage Logic.
 Troubleshooting device driver installation issues using the SetupAPI.log as
described in Troubleshooting Device Installation with SetupAPI.log.

Combining $OEM$ Mass Storage Drivers with MDT 2010 Mass

Storage Logic
Problem: A storage driver or set of drivers defined within the Windows XP or
Windows Server 2003 operating system source directory of the deployment
share can conflict with normal operation of the ZTIStorageDrivers.wsf script,
because ZTIStorageDrivers.wsf will not copy over any existing Txtsetup.oem file
on the local machine. For example, if the driver package \Distribution\Operating
Systems\Windows XP\$OEM$\txtsetup.oem (or similar) is present, it causes
installation of the new driver to fail.
Possible Solution: Do not combine $OEM$ mass storage drivers with the mass-
storage logic that MDT 2010 uses. Ensure that there are no mass storage drivers
in the $OEM$ directory of any Windows XP or Windows Server 2003 source
directory.
Troubleshooting Device Installation with SetupAPI.log

The white paper, “Troubleshooting Device Installation with the SetupAPI Log
File,” at http://www.microsoft.com/whdc/driver/install/setupapilog.mspx provides
information about debugging device installation for Windows XP and later
versions of Windows. Specifically, the paper provides guidelines for driver
developers and testers to interpret the SetupAPI log file.
Windows XP and later Windows versions log system operations more extensively
than previous versions of Windows. One of the most useful log files for
debugging purposes is the SetupAPI.log file. This plain-text file maintains the
information that SetupAPI records about device installation, service pack
installation, and update installation. Specifically, the file maintains a record of
device and driver changes as well as major system changes beginning from the
most recent Windows installation. This paper focuses on using the SetupAPI log
file to troubleshoot device installation; it does not describe the log file sections
that are associated with service pack and update installations.
New Computer Deployments

Review the problems and solutions for New Computer deployment scenarios:
 Error messages that indicate a shared folder does not exist as described in
Failure to Copy Log Files to Shared Folders.
 Problems starting the deployment process using Pre-Boot Execution
Environment (PXE) boot as described in PXE Boot.

Failure to Copy Log Files to Shared Folders

Problem: When using the New Computer or Replace Computer deployment
scenario, a warning message may appear similar to the following, even though
the specified share does exist:
Warning - Unable to copy local logfile

(C:\MININT\SMSOSD\OSDLOGS\ZeroTouchInstallation.log) because
\\servername\Logs does not exist.
Possible Solution: This message can occur when the deployment scripts do not
have the appropriate credentials to access the \\servername\Logs folder when
the \\servername\Logs folder resides on a server other than the deployment
share. For more information on providing the appropriate credentials for the
different deployment phases, see the MDT 2010 document, Using the Microsoft
Deployment Toolkit.
PXE Boot
In brief, the PXE protocol operates as follows: The client computer initiates the
protocol by broadcasting a DHCP Discover packet containing an extension that
identifies the request as coming from a client computer that implements the PXE
protocol. Assuming that a boot server implementing this extended protocol is
available, the boot server sends an offer containing the IP address of the server
that will service the client. The client uses Trivial File Transfer Protocol (TFTP) to
download the executable file from the boot server. Finally, the client computer
initiates execution of the downloaded image.
The initial phase of this protocol piggybacks on a subset of the DHCP messages
to enable the client to discover a boot server (that is, a server that delivers
executable files for new computer setup). The client computer may use the
opportunity to obtain an IP address (which is the expected behavior) but is not
required to do so.
The second phase of this protocol takes place between the client computer and a
boot server and uses the DHCP message format as a convenient format for
communication. This second phase is otherwise unrelated to the standard DHCP
services. The next few pages outline the step-by-step process during PXE client
computer initialization.
For more information on troubleshooting PXE boot-related issues in Windows

Deployment Services running in Legacy or Mixed mode, see the Microsoft Help
and Support article, “Description of PXE Interaction Among PXE Client, DHCP,
and RIS Server,” at http://support.microsoft.com/kb/244036.
Review the following solutions for PXE boot issues:

 Disable Windows PE logging to SetupAPI.log as described in Disable

Windows PE Logging in Windows Deployment Services.
 Ensure that DHCP is configured properly as described in Ensure the Proper
DHCP Configuration.
 Improve the response times for assigning IP addresses to PXE client
computers as described in Improve PXE IP Address Assignment Response
Time.
Disable Windows PE Logging in Windows Deployment Services

The first procedure recommended is to make sure that logging to setupapi.log
has been disabled.
Ensure the Proper DHCP Configuration

Depending on the router models in use, the specific router configuration of DHCP
broadcast forwarding may be supported to either a subnet (or router interface) or
a specific host. If the DHCP servers and the computer running Windows
Deployment Services are separate computers, ensure that the routers that
forward DHCP broadcasts are designed so that both the DHCP and Windows
Deployment Services servers receive the client broadcasts; otherwise, the client
computer does not receive a reply to its remote boot request.
Is there a router between the client computer and the remote installation server
that is not allowing the DHCP-based requests or responses through? When the
Windows Deployment Services client computer and the Windows Deployment
Services server are on separate subnets, configure the router between the two
systems to forward DHCP packets to the Windows Deployment Services server.
This arrangement is necessary, because Windows Deployment Services client
computers discover a Windows Deployment Services server by using a DHCP
broadcast message. Without DHCP forwarding set up on a router, the client
computers’ DHCP broadcasts do not reach the Windows Deployment Services
server. This DHCP forwarding process is sometimes referred to as DHCP Proxy
or IP Helper Address in router configuration manuals. Refer to the router
instructions for more information about setting up DHCP forwarding on a specific
router.
Improve PXE IP Address Assignment Response Time

Check the following elements if it is taking a long time (15–20 seconds) for the
PXE client computer to retrieve an IP address:
 Are the network adapter on the target computer and the switch or router set
to the same speed (automatic, duplex, full, and so on)?

 Is the IP address for the Windows Deployment Services server in the IP

Helper file on the router through which the connection is made? If the list of
IP addresses in the IP Helper file is long, can you move the address for the
Windows Deployment Services server near the top?
Printers
Problem: Even though USMT is able to capture data stored in the
HKEY_CURRENT_USER\Printers registry key, it does not migrate TCP/IP–
based printers.
Possible Solution: Include task sequence steps that use the Windows
Server 2003 Print Migrator 3.1 utility to capture and restore printer configurations.
The utility is available for download from
http://www.microsoft.com/WindowsServer2003/techinfo/overview/printmigrator3.1
.mspx.
Product Keys
Problem: The target computer is running Windows Vista and has an existing
product key. If you run a task sequence on the target computer to perform an
upgrade to Windows 7, the deployment process fails with an error message
stating that an invalid product key was provided.
Possible Solution: During the deployment process, provide a valid Windows 7

product key.
Restarting the Deployment Process

Problem: While testing and troubleshooting a new or modified task sequence,
you may need to restart the target computer so that the deployment process can
start over from the beginning. Unexpected results may occur, because
MDT 2010 keeps track of its progress by writing data to the hard disk; any restart
of the target computer has MDT 2010 resume where it left off at the previous
restart.
Possible Solution: To allow the deployment process to restart from the

beginning, delete the C:\MININT and C:\_SMSTaskSequence folders prior to
restarting the target computer.
Sysprep
Review Sysprep–related problems and solutions:

 The target computer is not joined to the domain as described in Joining a

Domain.
 The target computer is not appearing in the correct AD DS OU as described
in The Computer Account Is in the Wrong OU.
 A Windows product activation error message is displayed, indicating that
Sysprep has been run three times and has exceeded its limit as described in
Execution Limit.
Joining a Domain
Problem: The target computer is not joined to the domain.
Possible Solution 1: If the Sysprep.inf file contains both JoinDomain and

JoinWorkgroup entries, the first one encountered takes precedence.
Possible Solution 2: Verify that the specified credentials have sufficient rights to
join computers to the domain.
The Computer Account Is in the Wrong OU

Problem: The target computer is properly joined to the domain, but the computer
account is in the wrong OU.
Possible Solution 1: If an account pre-exists for the target computer, the

account will remain in its original OU. To move the account to the specified OU,
add a task sequence step that uses an automation tool, such as a Microsoft
Visual Basic® Scripting Edition (VBScript), to move the account.
Possible Solution 2: Verify that the specified OU is in the correct format and
that it exists. The correct OU format should be
OU=Reception,OU=NYC,DC=Woodgrovebank,DC=com.
Execution Limit
Problem: The following Windows product activation error message is displayed
after a master computer has had Sysprep run three times.
Error 0x80040605 Re-arming

Sysprep is limited to being run three times on an installed
operating system. You cannot run Sysprep a fourth time.
Note This limitation does not affect Microsoft Volume Licensing media.
Possible Solution 1: Never run Sysprep on the master image; instead, capture
an image of the computer prior to running Sysprep. When the image requires
updating, restore the master image, make any required changes, and then
recapture the image prior to running Sysprep.

Possible Solution 2: When running Sysprep, use the –activated option to avoid
resetting activations. For more information, see the Microsoft Help and Support
article, “‘Error 0x80040605 Re-arming’ Error Message When You Try to Run
Riprep.exe or Sysprep.exe on Windows XP,” at
System Center Configuration Manager

Problem: The error message shown in Figure 3 is displayed when you attempt
to create a System Center Configuration Manager PXE service point using the
Create self-signed PXE certificate option.
Figure 3. PXE service point error
Possible Solution: If a PXE service point previously existed on the server you
are configuring, the PXE service point may not have deleted the self-created
certificates when you uninstalled it. Delete the PXE certificate folder from
C:\Documents and Settings\user_name\Application Data\Microsoft\Crypto\RSA,
where user_name is the name of the user performing the current configuration or
who performed the previous configuration. The New Site Role wizard in the
Configuration Manager Console should successfully finish when you have
deleted the folder.
Task Sequences
Review task sequence–related problems and solutions:
 The Windows Deployment Wizard displays the error message “Bad Task
Sequence Item (Invalid OS GUID)” as described in Bad Task Sequence Item
(Invalid OS GUID) Message in Windows Deployment Wizard.
 While configuring a network connection name, the message “Please enter a
valid name for the network adapter” is displayed as described in Apply
Network Settings.
 Task sequence steps are missing after upgrading from BDD 2007 as
described in Upgrading from BDD 2007—Missing Task Sequence Steps.

 Problems that may occur as a result of improper configuration of continue on

error configuration settings for task sequence steps as described in Using
Continue on Error.
Bad Task Sequence Item (Invalid OS GUID) Message in

Windows Deployment Wizard
Problem: When running the Windows Deployment Wizard, the wizard displays
the error message “Bad Task Sequence Item (Invalid OS GUID).” The operating
system is listed in the OperatingSystem.xml file, however the operating system is
not displayed in the Deployment Workbench.
Possible Solution: The original operating system source has two or more WIM
files associated. An SKU that is associated with a task sequence is deleted;
however, other SKUs for the operating system source still exist. When the task
sequence that references the deleted SKU is selected on the Select a task
sequence to execute on this computer wizard page in the Windows
Deployment Wizard, the error message “Bad Task Sequence Item (Invalid OS
GUID)" is displayed after you click Next on the wizard page.
To resolve this problem, perform one of the following tasks:
 Remove all SKUs from the operating system source. The Windows
Deployment Wizard behaves normally, and the error message is not
displayed.
 Change the task sequence to use a different operating system image.
Apply Network Settings

Problem: When configuring the network connection name in the Deployment
Workbench, a validation error prompts you with the message, “Please enter a
valid name for the network adapter.”
Possible Solution: Remove any spaces and invalid characters from the
specified connection name.
Upgrading from BDD 2007—Missing Task Sequence Steps

After upgrading a Microsoft Business Desktop Deployment (BDD) 2007
deployment share to MDT 2010, customizations from the BDD 2007 task
sequence are identified and moved to the new MDT 2010 task sequence using
one of the following scenarios:
 If a custom task sequence step specifies an application that is matched to an

application defined in the deployment share and if there is also a match
between the command-line sequence of the step and the command-line

sequence of the deployment share application, that task sequence step is

added to the Custom Tasks group.
 If a custom task sequence step specifies an application that cannot be
matched to an application defined in the deployment share, that task
sequence step is added to the Unknown Tasks group, which is disabled.
Administrative intervention is required to edit the task sequence and move
the step to an appropriate location within the new task sequence.
Note Any custom task sequence steps that call a ZTI script are ignored.
Note Any custom task sequence steps that are relocated to the Custom Tasks or Unknown Tasks
groups in the task sequence are disabled. To continue to use these task sequence steps in
MDT 2010, relocate the task sequence steps to their proper location in the task sequence and
enable them.
Using Continue on Error

If a MDT 2010 task sequence is configured not to continue on error and that task
sequence returns an error, all remaining task sequences in that task sequence
group are skipped. However, the remaining task sequence groups are
processed. Consider the following:
Two task sequence groups have been created, and either group contains more
than one task sequence step:
 Group A
 Step A
 Step B
 Group B
 Step A
 Step B
If Group A\Step A is configured not to continue on error, then Group A\Step B will
not be processed. However, all task sequence steps in Group B will be
processed.
User State Migration Tool

Review USMT–related problems and solutions:
 Shortcuts that point to documents stored in network shared folders may not
be restored properly as described in Missing Desktop Shortcuts.
 USMT error 1618 is displayed while deploying Windows XP images as
described in USMT-related Errors During Deployment—Error 1618.
Missing Desktop Shortcuts

Problem: While using USMT to migrate user data, shortcuts that point to network
documents may not be restored. The shortcuts are captured during Scanstate;
however, they are never restored to the target computer during Loadstate.
Possible Solution: Edit the MigUser.xml file and comment out the following line:
Original:
<include> filter='MigXmlHelper.IgnoreIrrelevantLinks()'>

Modified:
<include> 
USMT-related Errors During Deployment—Error 1618

Problem: While deploying a Windows XP image, the following error messages
may be logged during the State Restore phase when USMT is being installed:
 USMT installer found at

\\Server\Packages$\SMSPKG\E000019B\InstallUSMT301_X86.msi.
ZTIUserState 18/01/2008 16:00:12 0 (0x0000)
 About to run command: msiexec.exe /I

"\\Server\Packages$\SMSPKG\E000019B\InstallUSMT301_X86.msi"
/quiet /passive /norestart ZTIUserState 18/01/2008 16:00:12
0 (0x0000)
 Return code from command = 1618 ZTIUserState

18/01/2008 16:00:15 0 (0x0000)
 Non-zero return code from USMT 3.0.1 installation command, rc =

1618 ZTIUserState 18/01/2008 16:00:15 0 (0x0000)
 FindFile: The file USMT30_X86.cab could not be found in any

standard locations. ZTIUserState 18/01/2008
16:00:15 0 (0x0000)
 ERROR: Unable to find USMT30_X86.cab file so it is not possible

to install USMT 3.0, aborting ZTIUserState
18/01/2008 16:00:15 0 (0x0000)
 ERROR - Unable to install USMT 3.0 to restore user state.

ZTIUserState 18/01/2008 16:00:15 0 (0x0000)
The last three lines of the log file are an attempt at recovering from the initial
behavior—the MDT 2010 scripts have logic that attempts to install USMT by
extracting the bits from a CAB file but only after the initial Windows Installer–
based installation fails.
The problem is a result of a previous task sequence step in the deployment

process. The 1618 message translates to, “Another installation is already in
progress. Complete that installation before proceeding with this install.” This error
is probably the result of an incorrect command that caused execution of
subsequent task sequence steps to continue immediately even though the
installation was just starting.

Possible Solution 1: Check the event log to see what other installations were
initiated at or near the time of the USMT installation, and verify that the
commands for those installations are appropriate.
Possible Solution 2: You can avoid this problem by creating a USMT CAB file,
but you will likely encounter other issues if you do not correct the cause of the
original error.
Because of a bug in the Windows Vista installation program, Wusa.exe (used to

install Microsoft Update Standalone Package [MSU] files), USMT would not
install quietly using the standard /quiet option, which resulted in a workaround
implemented in the ZTIUserState.wsf script.
Repeat the following steps for the x86 and x64 versions of USMT to repackage
the USMT files into CAB files from which MDT 2010 can extract USMT to the
target computer during deployment:
1. Manually install the x86 or x64 version of USMT—whichever is applicable to

the environment—on a computer running Windows XP or Windows Vista.
2. Copy C:\Program Files\Microsoft Deployment
Toolkit\Samples\USMT30_platform.ddf, where platform is either x86 or x64,
from a computer on which MDT 2010 is installed.
Note If USMT is installed in a location other than the default (C:\Program Files\USMT301),
edit USMT30_platform.ddf to indicate the correct path to the USMT program folder.
3. Run the command Makecab /F USMT30_platform.ddf; then, copy the newly

created CAB file (USMT30_platform.cab) to the \Tools\platform folder in the
MDT 2010 deployment share.
Possible Solution 3: An update is available for Windows Vista that may fix the
USMT installation problem. If this update is included in the Windows Vista image,
you may not need to perform the steps outlined in “Possible Solution 2” in this
section. For more information about the update, see the Microsoft Help and
Support article, “When you run Wusa.exe together with the /quiet option to try to
install certain software packages on a Windows Vista–based computer, the
installation fails,” at http://support.microsoft.com/kb/929761.
Windows Deployment Services

Review Windows Deployment Services–related problems and solutions:
 The WDS service does not work as expected after upgrading to MDT 2010 as
described in WDS Service Fails When PXE Filter Is Installed.

WDS Service Fails When PXE Filter Is Installed

Problem: The WDS service does not work as expected after you upgrade from a
previous version of MDT to MDT 2010.
Possible Solution: If the previous installation of MDT used WDS PXE Filter
support, you must remove this support to allow the WDS service to work as
expected. Use the Remove WDS PXE Filter Wizard to remove support.
Note To access the Remove WDS PXE Filter Wizard, click Start, and then point to All Programs.
Point to Microsoft Deployment Toolkit, and then click Remove WDS PXE Filter Wizard.

Windows Imaging Format Files

Review WIM-related problems and solutions:
 LTI and ZTI deployments fail with WIM file errors in the BDD.log file as
described in Corrupt WIM File.
Corrupt WIM File

Problem: When deploying an image, the deployment fails with the following
entries in the BDD.log file:
 The image \\Server\Deployment$\Operating Systems\Windows XP

SP2\version1.wim was not applied successfully by ImageX, rc = 2
 LTIApply COMPLETED. Return Value = 2
 ZTI ERROR - Non-zero return code by LTIApply, rc = 2
Investigate the issue by mounting the WIM file using ImageX results in the error,
“The data is invalid.” Further investigation shows that the date stamp of the WIM
file is many years before the current date. It is possible that another process,
such as a virus scanner, was holding the WIM file open after it was previously
closed at the conclusion of a Read or Write process.
Possible Solution: Restore the WIM file from backup media.
Windows PE
Review Windows PE–related problems and solutions:
 The LTI or ZTI deployment process is not initiated because of insufficient

RAM or wireless network adapters as described in Deployment Process Not
Initiated—Limited RAM or Wireless Network Adapter.
 The LTI or ZTI deployment process is not initiated because of missing
Windows PE components as described in Deployment Process Not Initiated
—Missing Components.
 The LTI or ZTI deployment process is not initiated because of missing or
incorrect device drivers as described in Deployment Process Not Initiated—
Missing or Incorrect Drivers.

Deployment Process Not Initiated—Limited RAM or Wireless

Network Adapter
Problem: When deploying an image to certain target computers, Windows PE
starts, runs wpeinit, opens a Command Prompt window, but does not actually
start the deployment process. Troubleshooting the problem by mapping a
network drive from the target computer indicates that the network adapter drivers
are not loaded.
Possible Solution 1: The Windows Deployment Wizard is not starting, because

there is insufficient RAM. Verify that the target computer has at least 512 MB of
RAM and that no shared video memory consumes more than 64 MB of the
512 MB.
Windows PE 2.0 is unable to run on a target computer that has less than 512 MB
of RAM. Also, because of the nature of LTI in MDT 2010, LTI will not run with
Windows PE 2005.
Possible Solution 2: Do not include the wireless drivers in the Windows PE

image.
Deployment Process Not Initiated—Missing Components

Problem: When troubleshooting a failed deployment, a review of the BDD.log file
lists the following entry:
ERROR - Unable to create ADODB.Connection object, impossible

to query SQL Server: ActiveX component can't create object
(429).
Possible Solution: This error may indicate that the Windows PE image was not
created using MDT 2010. If you are using System Center Configuration Manager,
do not use one of the existing Windows PE images that System Center
Configuration Manager created; instead, create an image using the Import
Microsoft Deployment Task Sequence Wizard.
Note The Windows PE images that System Center Configuration Manager creates contain
components that support scripting, Extensible Markup Language (XML), and Windows
Management Instrumentation (WMI), but they do not contain components that support Microsoft
ActiveX® Data Objects (ADO).
Deployment Process Not Initiated—Missing or Incorrect Drivers

Problem: When deploying to certain target computers, Windows PE starts, runs
wpeinit, opens a Command Prompt window, but does not actually start the
deployment process. Troubleshooting by mapping a network drive from the target
computer indicates that the network adapter drivers are not loaded. A review of
the SetupAPI.log file located in X:\Windows\System32\Inf indicates that

Windows PE generates errors when it is configuring the network adapter, one of

which is, “This driver is not meant for this platform.” The drivers in the Out-of-
Box Drivers list have been injected into the image.
Possible Solution: It is possible that Windows PE is having a driver conflict with

another driver. When configuring the settings for the Windows PE image in the
Deployment Workbench, create a Windows PE drivers group that contains only
network adapter and storage drivers, and then configure the deployment share to
use only the Windows PE driver group. If you have included both Windows XP
and Windows Vista drivers, add the driver for Windows Vista into the
Windows PE drivers group.

Deployment Process Flow Charts

This chapter provides two sets of MDT 2010 flow charts: one for LTI deployments
and one for ZTI deployments with System Center Configuration Manager. Each
flow chart illustrates the tasks executed during that deployment type.
Familiarize yourself with the deployment process flow charts by:
 Reviewing the LTI deployment process flowcharts as described in LTI

Deployment Process Flowcharts.
 Reviewing the ZTI deployment process flowcharts as described in ZTI
Deployment Process Flowcharts.
LTI Deployment Process Flowcharts

Flow charts are provided for the following phases:
 Validation (Figure 4)
 State Capture (Figure 5 and Figure 6)
 Preinstall (Figure 7, Figure 8, and Figure 9)
 Install (Figure 10)
 Postinstall (Figure 11 and Figure 12)
 State Restore (Figure 13, Figure 14, Figure 15, and Figure 16)

Troubleshooting Reference: Flow Charts 45
Figure 4. Flow chart for the Validation Phase

Figure 5. Flow chart for the State Capture Phase (1 of 2)

Figure 6. Flow chart for the State Capture Phase (2 of 2)

Figure 7. Flow chart for the Preinstall Phase (1 of 3)



Figure 10. Flow chart for the Install Phase
Figure 11. Flow chart for the Postinstall Phase (1 of 2)

Figure 12. Flow chart for the Postinstall Phase (2 of 2)

Figure 13. Flow chart for the State Restore Phase (1 of 4)



ZTI Deployment Process Flowcharts

Flow charts are provided for the following phases of ZTI deployment with System
Center Configuration Manager:
 Initialization (Figure 17)
 Validation (Figure 18)
 State Capture (Figure 19)
 Preinstall (Figure 20)
 Install (Figure 21)

 Postinstall (Figure 22)
 State Restore (Figure 23 and Figure 24)
 Capture (Figure 25)

Figure 17. Flow chart for the Initialization Phase
Figure 18. Flow chart for the Validation Phase

Figure 19. Flow chart for the State Capture Phase

Figure 20. Flow chart for the Preinstall Phase

Figure 21. Flow chart for the Install Phase

Figure 22. Flow chart for the Postinstall Phase



Figure 25. Flow chart for the Capture Phase

Finding Additional Help

Find additional help in resolving MDT 2010 deployment problems by:
 Contacting Microsoft Services Premier Support as described in Microsoft

Services Premier Support.
 Obtaining additional support through blogs and other Internet resources as
described in Internet Support.
Microsoft Services Premier Support

The MDT 2010 team has received a number of e-mail messages and questions
about how to receive support from Premier Support for MDT 2010. Several
individuals have been routed to the incorrect support queue while trying to
receive support for MDT 2010. We apologize for their frustration and
inconvenience.
To be routed to the correct support queue, call Premier Support at 1-800-936-

3500, or go online to
http://www.microsoft.com/services/microsoftservices/srv_premier.mspx.
Note When seeking support, clearly state that there is a Business Desktop Deployment/Microsoft
Deployment Toolkit issue. Mentioning “deployment” in general may result in routing to the incorrect
queue.
Note Please note that support for MDT 2010 is done via callback, with response times generally
ranging between 1 and 4 hours depending on the severity of the issue and other issues in the
queue.
Internet Support
Many online sources provide additional troubleshooting assistance for MDT 2010
beyond what is covered in this reference. These online sources include:
 Microsoft-hosted blogs:
 MDT 2010 Team blog at
http://blogs.technet.com/msdeployment/default.aspx
 Deployment Guys blog at http://blogs.technet.com/deploymentguys/
 Ben Hunter’s blog at http://blogs.technet.com/benhunter/default.aspx
(Ben Hunter is a consultant with Microsoft Services–New Zealand.)
 Michael Niehaus’ blog at http://blogs.technet.com/mniehaus/default.aspx
(Michael Niehaus writes on Windows and Microsoft Office deployment.)

Troubleshooting Reference: Finding Additional Help 67
 Richard Smith’s blog at http://blogs.technet.com/richardsmith/default.aspx

(Richard Smith is a consultant with Microsoft Services–United Kingdom.)
 Microsoft-hosted newsgroups and forums:
The following newsgroups and forums are available with support from
Microsoft employees, industry peers, and Microsoft Valued Professionals
(MVPs):
 microsoft.public.deployment.desktop at
news://msnews.microsoft.com/microsoft.public.deployment.desktop
 System Center Configuration Manager at
http://forums.microsoft.com/TechNet/default.aspx?
ForumGroupID=488&SiteID=17
 microsoft.public.office.setup at
news://msnews.microsoft.com/microsoft.public.office.setup
 microsoft.public.usmt at
news://msnews.microsoft.com/microsoft.public.usmt
 microsoft.public.deployment.app_compatibility at
news://msnews.microsoft.com/microsoft.public.deployment.app_compatib
ility
 TechNet forum: Windows Vista Deployment and Imaging at
http://forums.microsoft.com/TechNet/ShowForum.aspx?
ForumID=721&SiteID=17
 Deployment-related information sources from outside Microsoft:
 DeploymentForum.com at http://www.deploymentforum.com
 DeployVista.com at http://www.deployvista.com
 myITforum.com at http://www.myitforum.com

Microsoft Deployment Toolkit 2010: Troubleshooting Reference

Uploaded by

Copyright:

Available Formats

Microsoft Deployment Toolkit 2010: Troubleshooting Reference

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Microsoft Deployment Toolkit 2010: Troubleshooting Reference

Uploaded by

Copyright:

Available Formats

Microsoft Deployment ®

For the latest information, please see

© 2009 Microsoft Corporation. All rights reserved.

MICROSOFT CORPORATION PROVIDES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Known Issues and Workarounds

Adding Custom Windows Vista WIM Files

Error during wizard processing

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Error Message “Access to the path \\...\scripts\Autorun.inf is

Possible Solution: This can be caused by antivirus software preventing access

 Configure the antivirus software to allow access to the file.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

 BDD.log. This is the aggregated MDT 2010 log file that is copied to a

Solution Accelerators microsoft.com/technet/SolutionAccelerators

 Scriptname.log. This file is created by each MDT 2010 script. Scriptname

Operating System Logs

 Netsetup.log. Resides in %WINDIR%\Debug; useful when troubleshooting

 Netsetup.log. Resides in %WINDIR%\Debug; useful when troubleshooting

Solution Accelerators microsoft.com/technet/SolutionAccelerators

 Setupapi.log. Contains information about hardware detection during

System Center Configuration Manager Operating

When executing Windows User State Migration Tool (USMT) operations,

 USMTEstimate.log. Created when estimating the USMT requirements

ZTI USMT <usmt_type> reported <error_count> errors and

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Identifying Error Codes

Table 1. Error Codes and Their Description

Error code Description

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Error code Description

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Error code Description

Error code Description

6745 Check TPM owner.

Error code Description

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Error code Description

Listing 1. Excerpt from an SMSTS.log File That Contains Error Code 5001

Solution Accelerators microsoft.com/technet/SolutionAccelerators

The action "Zero Touch Installation - Validation" failed

Converting Error Codes

Problem: An image capture fails with error code 0x80070040.

Possible Solution 1: The error code presented is in hexadecimal format that

To convert an error code

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Figure 1. Error conversion

Review of Sample Logs

 ERROR - Opening Record Set (Error Number = -2147217911) (Error

 ADO error: The SELECT permission was denied on the object

 ERROR - Unhandled error returned by ZTIGather: Object required

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Figure 2. NTFS data streams

Lost Network Connections