Troubleshooting Reference

Microsoft® Deployment Toolkit 2010Troubleshooting 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/bync/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 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 Solution Accelerators microsoft.com/technet/SolutionAccelerators .............................................................................................iv Microsoft Deployment Toolkit 2010 Failure to Copy Log Files to Shared Folders ................ 31 Bad Task Sequence Item (Invalid OS GUID) Message in Windows Deployment Wizard .................... 60 Solution Accelerators microsoft... 30 System Center Configuration Manager ..................................................................................... 29 Product Keys ....................................................... 27 PXE Boot ............................................................................................................................................ 36 Corrupt WIM File ....................................................................................................................................... 38 LTI Deployment Process Flowcharts .................................................................................................................................................................................................................... 32 Using Continue on Error ........................... 29 Restarting the Deployment Process ... 32 Apply Network Settings.................................... 29 Sysprep ............................................................................................ 35 WDS Service Fails When PXE Filter Is Installed ............................................................................................. 30 Execution Limit ...................................................................................................................com/technet/SolutionAccelerators ............................................................................................................................................................... 33 User State Migration Tool ........................................................................ 60 Internet Support ................................................................................................. 35 Windows Imaging Format Files .............................................................................. 38 ZTI Deployment Process Flowcharts....................................................................................... 33 Missing Desktop Shortcuts .................................................................................... 36 Deployment Process Not Initiated²Missing Components .................................................................................................................................................................................................................... 31 Task Sequences ...................................... 34 Windows Deployment Services.......... 30 The Computer Account Is in the Wrong OU ................................................................. 37 Deployment Process Flow Charts .................................... 60 Microsoft Services Premier Support ...... 32 Upgrading from BDD 2007²Missing Task Sequence Steps ....................................................................................................................................... 36 Windows PE .................... 30 Joining a Domain ............................................................................ 36 Deployment Process Not Initiated²Limited RAM or Wireless Network Adapter ............................................................................................................................................................................................................................................................................................................................................................. 50 Finding Additional Help ................................ 33 USMT-related Errors During Deployment²Error 1618........................................................................................ 27 Printers ............................... 37 Deployment Process Not Initiated²Missing or Incorrect Drivers .......................................... com/fwlink/?LinkID=132579. you can start the client computer containing the image by using ERD Commander²a diagnostic environment.microsoft. 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. To learn more about DaRT. if a built image fails to start correctly.mspx. Then. change operating system settings. For example. You can use DaRT to determine the cause of a crash. This reference. Windows XP Professional. Windows Server 2008.microsoft. remove updates. which is part of Microsoft® Deployment Toolkit (MDT) 2010. Please provide feedback on the usefulness of this guide by filling out the survey at http://go. Note In this document. restore lost files. provides information on current known issues. Windows applies to the Windows® 7.com. Windows Server® 2008 R2. and so on. possible workarounds for those issues. even when you are equipped with appropriate tools and guidance. and so on.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.com/technet/SolutionAccelerators . You can also use DaRT as a troubleshooting tool when developing and deploying a Windows operating system. DaRT is part of the Microsoft Desktop Optimization Pack (MDOP) for Software Assurance.com/windows/products/windowsvista/enterprise/dart. view the event log. you can explore the client computer¶s hard disk. and Windows Server 2003 operating systems unless otherwise noted. Solution Accelerators microsoft. Windows Vista®. Windows XP Tablet PC Edition. Feedback Please direct questions and comments about this guide to satfdbk@microsoft. see Microsoft Diagnostics and Recovery Toolset at http://www. and troubleshooting guidance. 2 Microsoft Deployment Toolkit 2010 Known Issues and Workarounds This chapter describes known issues you may encounter while using MDT 2010. Possible Solution: You can resolve this issue by applying the update mentioned in the Microsoft Knowledge Base article. Collection was modified. enumeration operation may not execute. Solution Accelerators microsoft.microsoft.com/kb/941595. Deployment Workbench The following are possible solutions for issues that may arise with the Deployment Workbench.com/technet/SolutionAccelerators . ³You cannot create a Windows Vistabased WIM build in Solution Accelerator for Business Desktop Deployment.´ at http://support. 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. Solution Accelerators microsoft..inf is denied´ is displayed when running the Deployment Workbench.inf file from these folders.. Remove the Autorun..com/technet/SolutionAccelerators .\scripts\Autorun. you will need to manually copy the Autorun. You can resolve this issue using one of the following methods: y y Configure the antivirus software to allow access to the file. Possible Solution: This can be caused by antivirus software preventing access to the Autorun.inf file from the: y y installation_folder\Templates\Distribution folder (where installation_folder is the folder where you installed MDT 2010).inf file to media folders created in Media in the Deployment Workbench.\scripts\Autorun.inf is denied´ Is Displayed Problem: The error message ³Access to the path \\..inf file. deployment_share\Scripts folder (where deployment_share is the deployment share affected). Note When you remove the Autorun.Troubleshooting Reference: Known Issues and Workarounds 3 Error Message ³Access to the path \\. microsoft.ini file. This file is created when deployment shares are updated or when updating Windows Preinstallation Environment (Windows PE).com/downloads/details. issues that were once mysterious and difficult to understand may become clear and understandable.log. This file is created during Lite Touch Installation (LTI) deployments. MDT 2010 log files reside in C:\MININT\SMSOSD\OSDLOGS during the deployment process. This file is created by each MDT 2010 script. Use this tool whenever possible to read the log files. The names of these log files match the name of the script²for example. DeployUpdates_Platform. the log files are moved at the completion of the deployment to either %WINDIR%\SMSOSD or %WINDIR%\TEMP\SMSOSD. Depending on the deployment scenario. Platform represents the platform being updated²either 32 bit (x86) or 64 bit (x64). This file is created by the Task Sequencer and describes all Task Sequencer transactions. LiteTouch.wsf creates a log file named ZTIGather.log files used during an operating system deployment.log.log. It resides in %WINDIR%\Temp\BDDLogs unless you specify the /debug:true option. SMSTS. This section also provides examples of when to use the files for troubleshooting. Depending on the type of deployment being conducted. which is part of the Microsoft Systems Management Server (SMS) 2003 Toolkit 2. MDT 2010 creates the following log files: y BDD. Each script also updates a common master log file (BDD.com/technet/SolutionAccelerators .log. Scriptname.4 Microsoft Deployment Toolkit 2010 Understanding Logs Before effective troubleshooting of MDT 2010 can begin.log.log) that aggregates the contents of the log files that MDT 2010 scripts create.aspx?FamilyID=61e4e21f-265242dd-a04d-b67f0573751d. you must have a clear understanding of the many . When you know which log files to research for what failure condition and at what time. Scriptname represents the name of the script in question. This log file is useful when troubleshooting Windows PE driver-integration issues.log. available for download from http://www. It resides in the %TEMP% folder. 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. The MDT 2010 log file format is designed to be read by Trace32. it may y y y y Solution Accelerators microsoft. MDT 2010 Logs Each MDT 2010 script automatically creates log files during its execution. The rest of this section details the log files created during deployment as well as during Windows Setup. ZTIGather. because it makes finding errors much easier. log. lists installation actions and is useful when investigating failed installations Setupapi. useful when troubleshooting domain join issues Setupact.log. Resides in %WINDIR%\panther. useful when investigating failed installations Setupapi. y y y y Netsetup. ³Windows Vista setup log file locations.com/technet/SolutionAccelerators . are the most useful when troubleshooting Windows XP with Service Pack 2 (SP2): y y y y y y Netsetup.dev. located in %WINDIR%.txt. WPEinit. y y Wizard. This file is created during the Windows PE initialization process and is useful for troubleshooting errors encountered while starting Windows PE.log. Operating System Logs Review Windows Setup log files during troubleshooting activities.´ at http://support. Resides in %WINDIR%\panther. Contains information about Setup errors during the installation Setuperr. useful when troubleshooting domain join issues Setupact.log.log. useful when investigating failed driver installations Setuperr.log. Resides in %WINDIR%\Debug.com/kb/927521.log.log. useful for investigating failed driver installations Setuperr.log. or C:\SMSTSLog. Contains information about hardware detection during installation. Resides in %WINDIR%\inf. Resides in %WINDIR%\Debug. The deployment wizards create and update this file. For more detailed information about Windows Vista Setup log files. details errors that occurred during installation Windows XP The following log files. or C:\_SMSTaskSequence.log. Windows Vista The following list is a subset of the Windows Setup log files that are most useful for troubleshooting deployment issues.txt.Troubleshooting Reference: Understanding Logs 5 reside in %TEMP%. %WINDIR%\System32\ccm\logs. Lists installation actions. Contains information about Setup actions during the installation Solution Accelerators microsoft.microsoft. see the Microsoft Help and Support article. Details errors that occurred during installation Setuplog. 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.log.log.) In addition. error_count is the total number of errors found. Solution Accelerators microsoft. the script generates event ID 41010 to System Center Operations Manager with the following summary (where usmt_type is ESTIMATE. Created by the USMT when capturing data USMTRestore.6 Microsoft Deployment Toolkit 2010 System Center Configuration Manager Operating System Deployment Logs For information about which operating system deployment log files Microsoft System Center Configuration Manager 2007 creates.microsoft. Created when estimating the USMT requirements USMTCapture. Created by the USMT when restoring data The ZeroTouchInstallation. SCANSTATE. because these are too common.com/en-us/library/bb932135.com/technet/SolutionAccelerators . When executing Windows User State Migration Tool (USMT) operations.vbs script automatically scans the USMT progress log files for errors and warnings. During this process. MDT 2010 automatically adds the logging options to save the USMT log files to the MDT 2010 log file locations. the script writes each error and warning to the ZeroTouchInstallation. Otherwise. or LOADSTATE. The log files and when they are created are as follows: y y y USMTEstimate. the event is an Informational type.aspx. If the warning count is greater than 0 with no errors. this event is an Error type. (The script writes at least the first 100 errors and warnings while ignoring ³Failed to locate the file object´ warnings.log. then the event is a Warning type. see Log Files for Operating System Deployment at http://technet.log file. LoadControlFile.exe.exe. Verify file. These error codes are recorded in the BDD. The Deployment Wizard was canceled or did not complete successfully.log file. Unable to find the SMS Task Sequencer. Must set some value for SkipWizard. The deployment will not proceed. DeploymentType is not set. Verify file: ImagePath. The deployment will not proceed.FindFile: ConfigFile Verify OS guid: %OSGUID% exists.ErrCode. Create object: Set class_instance = New class_name Create MSXML2.DOMDocument. The deployment will not proceed. Solution Accelerators microsoft. Create MSXML2. The deployment will not proceed.DOMDocument. A connection to the deployment share could not be made. The deployment will not proceed. A connection to the deployment share could not be made. Open XML with OSGUID: %OSGUID%. Verify file: ImagePath. Error Codes and Their Description Error code 5201 5203 5205 5206 5207 5208 5208 5400 5490 5495 5496 5601 5602 5610 5630 5640 5641 5643 5650 5651 5652 Description A connection to the deployment share could not be made.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. Verify directory: SourcePath.exe.com/technet/SolutionAccelerators . Table 1. FindFile: bootsect. A connection to the deployment share could not be made. Find BootSect. Verify directory: SourcePath\Platform. FindFile: ImageX.ParseErr. The deployment will not proceed. Moved boot files. Encrypting the disk. Configured protectors. Encrypt the disk. Connect to MicrosoftVolumeEncryption WMI provider. Expand Sysprep files from DEPLOY. Create BDE partition. BackupDir) specified. Test for SystemSetupInProgress in registry to verify Sysprep completed. Defragment drive. Authorized DHCP server. Test for CloneTag in registry to verify Sysprep completed. Run Sysprep.CAB. Testing for more than 1 partition. Robocopy returned value: Value.Unable to locate IMAGEX.8 Microsoft Deployment Toolkit 2010 Error code 6001 6002 6010 6020 6021 6101 6102 6111 6121 6191 6192 6401 6501 6502 6601 6602 6701 6702 6703 6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 Description Verify drive. ProtectKeyWithTPM.com/technet/SolutionAccelerators . ERROR . GetObject(. unable to perform backup. Run Sysprep.OpenStore (BCDStore). Check for file: DeployCab. Test for TSGUID. Create boot files. BCD. Computer backup not possible. Verify drive. ProtectKeyWithTPMAndStartupKey. no network path (BackupShare. Solution Accelerators microsoft. ProtectKeyWithTPMAndPIN.exe... Robocopy returned value: Value. root/wmi:BCDStore). Shrink drive. Solution Accelerators microsoft. Check to see if TPM is enabled. Get TPM instance. Open DiskPartFile.log 2>&1 Find bcdboot. Create text file DiskPartFile.EXE /s DiskPartFile >> LogPath\ZTIMarkActive_diskpart. Check to see if TPM is enabled. Check to see if TPM is activated. Encrypt the drive. Save external key to file. Get a TPM instance in the provider class. Check to see if TPM ownership is allowed. Check to see if TPM is activated. Check to see if TPM is owned. Create partition.Troubleshooting Reference: Identifying Error Codes 9 Error code 6714 6715 6716 6717 6718 6718 6719 6720 6721 6722 6723 6724 6727 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739 6740 6741 6741 6742 6743 6744 Description Save external key to file. Attempt to open DiskPartFile.exe.com/technet/SolutionAccelerators . Save password to file. Check to see if TPM is enabled. Execute cmd /c DISKPART. GetKeyProtectorNumberialP@ssword. Check to see if TPM is owned and ownership is allowed. Get existing BDE drive. Protect with external key. Connect to Microsoft TPM provider. Open PasswordFile. Open DiskPartFile. Set TPM Owner P@ssword to value. Protect key with numerical password. TPM Owner Password set TPM Owner P@ssword set to AdminP@ssword. Mandatory properties for creating a new forest were not specified. Convert owner p@ssword to owner authorization. Configure BitLocker policy. ERROR . Protect key with TPM.com/technet/SolutionAccelerators . Protect with external key. ProtectKeyWithTpmAndStartupKey. Validate TPM. Looking for unattend AnswerFile. Find removable media for BDEKeyLocation. Check to see if TPM is activated.xml.Mandatory properties for creating a new child domain were not specified. ERROR . Create endorsement key pair. aborting.Mandatory properties for creating a new replica DC were not specified. ERROR .Not enough values supplied for generating DCPromo answer file. Recovery P@ssword being saved to PasswordFile. Change owner authorization. Run Cmd. Protect key with TPM and Pin. Check for endorsement key pair.This script should only run in the full OS. Check to see if TPM ownership is allowed. ERROR . ERROR .10 Microsoft Deployment Toolkit 2010 Error code 6745 6746 6747 6748 6749 6750 6751 6752 6753 6754 6755 6756 6757 6758 6759 6760 6761 6762 6764 7000 7001 7100 7101 7102 7103 7104 7105 Description Check TPM owner. Get BDE instance. Solution Accelerators microsoft.Mandatory properties for creating a new forest were not specified. Check for removable media to configure. Protect key with TPM and startup key. Unable to locate ZTIConfigure. ERROR . Look for BDE pin. Verify Drive/Volume Drive is present. Format. ERROR .Attempting to deploy a client operating system to a machine running a server operating system. aborting. Nonzero return code from USMT estimate. Findfile: Microsoft. No valid command line option was specified. Running an OEM Scenario: Skip.BDD. Findfile(PkgMgr. DeployRoot is on disk # DiskIndex. rc = Error. Not a New Computer scenario. insufficient local space and no network path (UDShare. Disk is not large enough for System and WinRE partitions. Disk is not large enough for System and BDE partitions.Exists("GUID").5 GB. Solution Accelerators microsoft.PnpEnum. rc = Error.exe. ERROR . AllDrivers. GetScopeDetails() failed.Exists("GUID"). Not enough values provided to set the IP range for this scope.com/technet/SolutionAccelerators . exiting disk partition. UDDir) specified. User state capture not possible. Running an OEM Scenario: Skip.exe). Required = 10 GB.ZTITatoo state restore task should be running in the full OS. aborting. Unable to read the scope details.Machine is not authorized for upgrading (OSInstall=OSInstall).Attempting to deploy a server operating system to a machine running a client operating system. Required = 1. ERROR . ERROR . Nonzero return code from USMT capture.Troubleshooting Reference: Identifying Error Codes 11 Error code 7200 7201 7202 7203 7204 7300 7700 7701 7702 7703 7704 7704 7712 7900 7901 7904 9200 9601 9701 9702 9703 9704 9801 9802 9803 Description Unable to configure DHCP server because the service is not installed. AllDrivers. No value specified for scope exclusion range. Not enough values specified for scope creation. Extended and logical partitions are not allowed with BitLocker. Unable to issue DNS commands. 12 Microsoft Deployment Toolkit 2010 Error code 9804 9805 Description ERROR .Memory MB of memory is insufficient. Stop installation.wsf). . Failed to create object: Microsoft.log File That Contains Error Code 5001 .insufficient space is available on Drive. All the wizard parameters are not set. Please contact your system administrator for assistance. . Run ImageX. The operating system installation failed. . An additional Size MB is required.com/technet/SolutionAccelerators . ZTIWindowsUpdate has run and failed too many times. At least a ProcessorSpeed MHz processor is required. ERROR . 9806 9807 9901 9902 9903 9904 9905 9906 10000 10201 10203 10204 41024 52012 Listing 1 provides an excerpt from a log file that illustrates how to find the error code.Session. Unexpected issue installing the updated Windows Update Agent. FindFile(LTISuspend. Critical file File was not found. Create object: Set oLTICleanup = New LTICleanup.Processor speed of ProcessorSpeed MHz is insufficient. Count = Count.Update. The ZTIWindowsUpdate script should not run in Windows PE. the error code reported is 5001. Solution Accelerators microsoft. aborting.UpdateColl. Excerpt from an SMSTS. ERROR . In this excerpt. Unable to Join Domain Domain. Failed to create object: Microsoft. Run Program LTISuspend. An additional Size MB is required. At least Memory MB of memory is required.Update. Listing 1. ERROR . rc = Error.insufficient space is available on Drive. The action "Zero Touch Installation .Validation" failed with exit code 5001 . and then click Calculator. Problem: An image capture fails with error code 0x80070040. Converting Error Codes Many error codes presented in the log files seem cryptic and difficult to correlate to an actual error condition. 3. Select Hex. as shown in Figure 1. you need a scientific calculator. 2. Select Dec. To do this. Possible Solution 1: The error code presented is in hexadecimal format that you need to convert to decimal format.Troubleshooting Reference: Identifying Error Codes 13 . and the calculator included with Windows operating systems is well suited to this task. From the View menu. However.com/technet/SolutionAccelerators . 4. Point to Accessories. Error conversion Notice that leading zeros are not displayed while the calculator is in Hexadecimal mode. 0040. click Scientific. To convert an error code 1. and then enter the last four digits of the code²in this case. Figure 1. Click Start. and then point to All Programs. the following process demonstrates how to convert an error code and obtain meaningful information that may assist in problem resolution. Solution Accelerators microsoft. Source: Microsoft OLE DB Provider for SQL Server. As a result. Possible Solution 2: Use the Microsoft Exchange Server Error Code Look-up utility.) ADO error: The SELECT permission was denied on the object 'ComputerAdministrators'.aspx?familyid=be596899-7bb84208-b7fc-09e02a13696c. type NET HELPMSG 64. Open a Command Prompt window.Unhandled error returned by ZTIGather: Object required (424) y y Note For clarity.´ 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. the priority of each section to be processed. it translates to ³The specified network name is no longer available. NativeError: 229 ERROR . schema 'dbo'. possibly because a user ID and password were not available. (Error #-2147217911.com/technet/SolutionAccelerators . Therefore. the log file contents above have been represented as they appear while being viewed using the Trace32 program. database access was attempted using the computer account. the script cannot establish a secure connection to the database.log contains the following error messages: y ERROR . These problems might include network drivers not being installed properly or a mismatch in speed and duplex settings. database 'AdminDB'. and then press ENTER. This command-line utility is valuable in assisting with error code translation. Review of Sample Logs Failure to Access the Database Problem: An error occurs while executing a deployment that used a CustomSettings.microsoft. The NET HELPMSG command translates the numerical error code into meaningful text. The easiest way to work around this issue is to grant everyone Read access to the database. SQL State: 42000.com/downloads/details.14 Microsoft Deployment Toolkit 2010 The hexadecimal value 40 is converted to a decimal value of 64. BDD. with the Priority property. as pointed out on the first line of the log file sample.ini file containing numerous sections and specifying. It is available for download from Microsoft Download Center at http://www. schema 'dbo'. Possible Solution: The issue. database 'AdminDB'. In the case of the error code provided here. Solution Accelerators microsoft. is that permission to access the database was denied.Opening Record Set (Error Number = -2147217911) (Error Description: The SELECT permission was denied on the object 'ComputerAdministrators'. 5. MDT 2010 will find the Deploy. it is likely that they will be marked with one or more NTFS file system data streams.cab file as part of the LTI process. Solution Accelerators microsoft. For more information about NTFS data streams. 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.aspx. Loss of network connectivity as described in Lost Network Connections. where deployment_share is the name of the share and platform is the name of the platform folder.com/technet/SolutionAccelerators . The installation will not proceed until you click Run at the prompt. Application Installation Review the problems and solutions for application installation issues: y y y Installation source files that are blocked for security reasons as described in Blocked Executables.85).com/en-us/library/aa364404(VS.cab file and extract the necessary files.microsoft.cab file into the deployment_share\Tools\platform folder.com/en-us/sysinternals/bb897440.aspx. which is available for download from http://technet.microsoft. As Figure 2 shows. MDT 2010 uses the tools from the Windows XP Deploy. The existence of NTFS file system data streams might cause an Open File ± Security Warning prompt to be displayed.Troubleshooting Reference: Troubleshooting 15 Troubleshooting Prior to embarking on in-depth troubleshooting processes. you can view NTFS file system data streams using the More command and the Streams utility. review the following items and ensure that any associated requirements have been met: y y Installation issues can result if all software and hardware prerequisites have not been met. Copy the Deploy. Installation error 30029 while installing the 2007 Microsoft Office system or related files as described in The 2007 Microsoft Office System. see File Streams at http://msdn2. Blocked Executables Problem: If installation source files are downloaded from the Internet. to remove the NTFS file system data streams from the installation source file.com/technet/SolutionAccelerators Solution Accelerators . The Streams utility can remove NTFS file system data streams from one or more files or folders at once. Click Unblock. Further investigation in the ZTIApplications. and then click Properties. These changes may result in a lapse in network connectivity that causes the installation to fail. and then click OK to remove the NTFS file system data streams from the file. At the same time. Possible Solution: Implement the ZTICacheUtil. Possible Solution 2: Use the Streams utility. Repeat this process for each installation source file that is blocked by the existence of one or more NTFS file system data streams. Lost Network Connections Problem: An installation may fail if it installs device drivers or alters device and network configurations. This script is designed to tweak the advertisement to enable download and execute. The 2007 Microsoft Office System Problem: While deploying the 2007 Office system and including a Windows Installer patch (MSP) file.exe microsoft.log shows the following messages: y About to run command: \\Server\Deployment$\Tools\X86\bddrun. NTFS data streams Possible Solution 1: Right-click the installation source file.vbs script first.exe \\Server\Share\Microsoft\Office\2007\Professional\setup. as Figure 2 shows. which makes sure the program doesn¶t delete itself during the deployment process. it modifies System Center Configuration Manager to run the ZTICache.vbs script to enable download and execution for the installation.16 Microsoft Deployment Toolkit 2010 Figure 2. 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. the installation may fail with error code 30029. Possible Solution 2: Verify that the MSP file does not have the Suppress modal box selected.microsoft.com/enus/library/bb490141. For more information about configuring this setting. AutoLogon Review the problems and solutions for automatic logon issues: y y Interruption of the LTI and ZTI deployment processes because of logon security banners as described in Logon Security Banners. Prompted for User Credentials Problem: You created an image of a computer that was joined to the domain.Troubleshooting Reference: Troubleshooting 17 /adminfile \\Server\Share\Microsoft\Office\2007\Professional\file. include as one of the last task sequence steps a script that relocates the computer account to the desired OU. If a Group Policy object (GPO) is in place that enforces a logon security banner. you have relocated the target computer¶s account to an OU that is not affected by the GPO that enforces the security logon banner. specify that they be added to an OU that is not affected by a GPO that enforces a logon security banner.com/technet/SolutionAccelerators .msp y y 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. which requires that the target computer be allowed to log on automatically using a specified administrative account. see ³Deploying the 2007 Office system´ at http://technet2. Possible Solution: Be sure that the GPO is applied to specific organizational units (OUs) and not included in the default domain GPO.aspx.microsoft. Logon Security Banners Problem: MDT 2010 task sequences are processed during an interactive user session. prior to deploying to the target computer. While deploying the new image to a target computer. and then run setup. Note If you are reusing existing Active Directory® Domain Services (AD DS) accounts.exe without specifying the /adminfile option. see Overview of 2007 Office System Deployment at http://technet. the deployment process Solution Accelerators microsoft. Interruption of the LTI and ZTI deployment processes because of prompts for user credentials as described in Prompted for User Credentials. When you add computers to the domain. ensure that.mspx. because the security banner halts the logon process while it waits for a user to accept the stated policy.com/Office/en-us/library/78ad4dd8-f15e41a9-8bf1-92cfeaac47801033. In the Task Sequence Editor. For more information about deploying updates during the installation. this automatic logon will not be allowed to proceed. inf prior to MDT 2010 customizations: [UserData] . If the computer was joined to a domain.com/technet/SolutionAccelerators . because auto-logon does not occur and the user is prompted to enter appropriate credentials. the target computer does not start. BIOS Problem: While deploying to a target computer that is equipped with Intel vPro technology. certain Windows operating systems do not support AHCI by default. 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).18 Microsoft Deployment Toolkit 2010 halts. Solution Accelerators microsoft. The user is prompted during MiniSetup for this information. only the first [UserData] section sets the FullName and OrgName properties but does not set the ComputerName or ProductKey properties.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. Possible Solution: When capturing images. This can cause issues when deploying the image. Unfortunately. Even though all updated drivers have been included as out-of-box drivers in the Deployment Workbench. MDT 2010 appends a section with just the information provided by MDT 2010 instead of adding the information to the INF file.For Windows XP a Volume License Key is required to avoid activation FullName=My Test Name OrgName=My Test Organization Sysprep. the deployment may end with a stop error. not the new section that MDT 2010 added. because Sysprep sees only the first occurrence of the commented section. The deployment process resumes when the credentials are provided and the user is logged on. re-capture the image. join the computer to a workgroup. Configuration Files Problem: While deploying Windows XP using a customized Sysprep. the source computer should not be joined to a domain.inf file within MDT 2010 as shown below.inf after MDT 2010 customizations: [UserData] . and attempt the deployment to a target computer to determine whether the issue is resolved. Sysprep. errors might be generated that relate to an improperly configured firewall on the database server. In the case of LTI deployments. However. To access an instance of SQL Server that is behind the firewall. you can then establish the named pipe connection to the database. the network access account connects to the database.com/kb/968872.com/technet/SolutionAccelerators . specify the SQLShare property. Blocked SQL Browser Requests Problem: During the MDT 2010 deployment process. Errors generated as a result of broken connections with the database server as described in Named Pipe Connections. However. Possible Solution: To resolve these problems. Solution Accelerators microsoft. When the connection is made. use integrated security to make the connection to the database. you must make a network connection to the database server to establish a security context for the user who will be making the connection. However.Troubleshooting Reference: Troubleshooting 19 Possible Solution: Do not use inline comments in INF files for MDT 2010 to customize.microsoft. The SQLShare property is not needed and should not be used when making a TCP/IP connection to the database. Possible Solution: The Windows Firewall in Windows Server 2008 helps prevent unauthorized access to computer resources. errors might be generated that relate to broken SQL Server connections. if the firewall is configured incorrectly. Database Problems Review database-related problems and solutions: y y Errors generated as a result of improperly configured firewalls on database server as described in Blocked SQL Browser Requests. When connecting using named pipes. the user account that you specify makes the connection to the database. Also. Because Windows PE has no security context by default. For more information on configuring firewall ports for SQL Server. information can be retrieved from SQL Server databases. attempts to connect to a SQL Server instance may be blocked. For Zero Touch Installation (ZTI) deployments that use System Center Configuration Manager. enable named pipes in SQL Server. ³How do I open the firewall port for SQL Server on Windows Server 2008?. which it is required when making a connection to an external database using named pipes. Named Pipe Connections Problem: During the MDT 2010 deployment process. information can be retrieved from Microsoft SQL Server® databases. configure the firewall on the computer that is running SQL Server. The network share that the SQLShare property specifies provides a means to connect to the server to gain a proper security context. see the Microsoft Help and Support article. You must have Read access to the share. These can be caused by not enabling named pipe connections in Microsoft SQL Server 2005 or SQL Server 2000.´ at http://support. Click Stop. Solution Accelerators microsoft.20 Microsoft Deployment Toolkit 2010 Enable named pipe connections by performing the following tasks based on the version of SQL Server you are using: y y Enable named pipe connections for SQL Server 2005 as described in Enable Named Pipe Connections in SQL Server 2005. ³How to configure SQL Server 2005 to allow remote connections. 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). 4. In the SQL Server 2005 Surface Area Configuration dialog box.com/kb/914277. 9. and then click Service. go to MSSQLSERVER\Database Engine. Enable named pipe connections for SQL Server 2000 as described in Enable Named Pipe Connections in SQL Server 2000. 7. 3. Click Start. click Using both TCP/IP and named pipes. 5. 2. click Start. and then point to All Programs. in Select a component and then configure its services and connections. On the computer running SQL Server 2005 that hosts the database to be queried. click Surface Area Configuration for Services and Connections. 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). and then click SQL Server Surface Area Configuration. Close SQL Server 2005 Surface Area Configuration. 6.microsoft.com/technet/SolutionAccelerators . see the Microsoft Help and Support article. in Select a component and then configure its services and connections. 8. Point to Microsoft SQL Server 2005. and then click Remote Connections. go to MSSQLSERVER\Database Engine. perform the following steps: 1. Click OK. and then click Apply. For additional information. The MSSQLSERVER service stops. The MSSQLSERVER service starts.´ at http://support. Click Local and remote connections. point to Configuration Tools. Enable Named Pipe Connections in SQL Server 2005 To enable named pipe connections in SQL Server 2005. click Start. download the binaries for Solution Accelerators microsoft. on the General tab. ZTIWindowsUpdate Problem: If you use the ZTIWindowsUpdate. and then run RD MININT and RD _SMSTaskSequence. 2. In the SQL Server Service Manager dialog box. perform the following steps: 1. and then click Server Network Utility.cab not found´ appears as described in ZTIWindowsUpdate. and then click SQL Server Service Manager. click Start. 3. scan for applicable software updates. Deployment Scripts Review MDT 2010±related problems and solutions: y y Prompted for user credentials and may receive error 0x80070035 as described in Credentials_script. which indicates that the network path was not found. ensure that Named Pipes is in the Enabled protocols list.com/technet/SolutionAccelerators . and then click OK. and then point to All Programs. and then click Stop. click Enable. Error message ³Wuredist. Point to Microsoft SQL Server. Point to Microsoft SQL Server. To delete these folders. Credentials_script Problem: During the last start-up of a newly deployed computer. If Named Pipes is in the Disabled protocols list. On the computer running SQL Server 2000 that hosts the database being queried. first use the ImageX utility to mount the WIM file. Close SQL Server Service Manager.wsf script to apply software updates during deployment. switch to the root of the image contained in the WIM file. open a Command Prompt window. and then point to All Programs. the user is prompted to provide user credentials and may receive error 0x80070035. click Named Pipes. in Services. In the SQL Server Service Manager dialog box. select SQL Server. and then delete the folders. 4. In the SQL Server Network Utility dialog box. Note If an Access Denied error occurs when you attempt to delete the folders from the WIM file. note that this script may communicate directly with the Microsoft Update Web site to download and install the required Windows Update Agent binaries. Possible Solution: Be sure that the WIM file does not include a MININT or _SMSTaskSequence folder. 6.Troubleshooting Reference: Troubleshooting 21 Enable Named Pipe Connections in SQL Server 2000 To enable named pipe connections in SQL Server 2000. Click Start. 5. com/technet/SolutionAccelerators . MDT 2010 locates WIMGAPI.wim files did not succeed. such as System Center Configuration Manager. and then install the downloaded binaries. even on a 64-bit operating system. ensure that the property also matches the operating system build number. Toolkit Reference. which should be in the system PATH.DLL.22 Microsoft Deployment Toolkit 2010 the applicable software updates.log and BDD. only that file should be in the system PATH.DLL must match the version (build) of the operating system. but MDT 2010 rarely uses it from that location. Possible Solution: Open a Command Prompt window and run where WIMGAPI. Possible Solution: Follow the steps outlined in ³ZTIWindowsUpdate. Failure to Update WIM Files In a ³simple´ environment: y For Windows XP. On Windows 7 or Windows Server 2008 R2 machines. but they manage and install that version.wsf. For Windows 7 and Windows Server 2008.cab not found´ is reported in the ZTIWindowsUpdate. If the deployment share does not contain the Windows Update Agent installation files and the target computer does not have appropriate Internet access. Solution Accelerators microsoft. and Windows Server 2008.DLL. the user will be informed that the mounting of one or more . Deployment Shares Review deployment share±related problems and solutions: y Updating WIM files fails when updating a deployment share as described in Failure to Update WIM Files.DLL should not reside in C:\Windows\system32: It will be present in the C:\Program Files\Windows AIK directory tree. The WIMGAPI. Windows Vista. MDT 2010 always uses the x86 WIMGAPI. On a 64-bit operating system. (Other products. Windows Server 2003. use the 32-bit version of WIMGAPI.) y y Problem: When attempting to update a deployment share.DLL file. only that file should be in the system PATH. ensure that the Version property matches the build of the Windows Automated Installation Kit (Windows AIK) that is installed.DLL from C:\Windows\system32 (always in the path).log files.DLL in C:\Program Files\Windows Imaging. MDT 2010 always uses the x64 WIMGAPI. The version of this WIMGAPI. For the first entry in the list (the first location found by searching the path). On a 32-bit operating system. error ³wuredist. This process requires that your networking infrastructure be configured to allow the target computer to gain access to the Microsoft Update Web site. MDT 2010 typically picks up WIMGAPI.DLL file.´ located in the ³Scripts´ section of the MDT 2010 document. The following potential problems may be related to the configuration of the target computer: y USB devices. For more information about which properties are required to ensure that a wizard page is skipped. Failures during Refresh Computer deployment scenarios caused by logical or dynamic disks as described in Support for Logical and Dynamic Disks. CD drives. Shrinking drive C on the target computer to provide sufficient unallocated disk space as described in Problems with Shrinking Disks. In some cases. Windows may assign the same device drive letters A and B for floppy disk emulation and F for Solution Accelerators microsoft. DVD drives. Therefore.´ in the MDT 2010 document. as described in Devices Appear as Multiple Drive Letters. Possible Solution: To properly skip a wizard page. If a property is configured improperly for a skipped wizard page. Disk partitioning errors as described in Disk Partitioning Errors. y Devices Appear as Multiple Drive Letters Problem: Some devices can appear as multiple logical drive letters. include all properties that would be specified on that wizard page where appropriate in the MDT DB or CustomSettings.com/technet/SolutionAccelerators . see the section. Disks and Partitioning Review disk partitioning problems and solutions: y y y BitLockerŒ Drive Encryption issues as described in BitLocker Drive Encryption. BitLocker Drive Encryption Using LTI to deploy BitLocker Drive Encryption requires a specific configuration for proper deployment.44-megabyte (MB) floppy disk drive and a memory storage drive. depending on how they are partitioned. ³Providing Properties for Skipped Windows Deployment Wizard Pages.ini file specify that the wizard should be skipped. Toolkit Reference.ini file along with appropriate values.Troubleshooting Reference: Troubleshooting 23 Deployment Wizard Review Windows Deployment Wizard±related problems and solutions: y Windows Deployment Wizard pages are displayed even when LTI is configured to skip the wizard pages as described in Wizard Pages Are Not Skipped. that page will be shown. or other removable media devices on the target computer that appear as multiple drive letters. Wizard Pages Are Not Skipped Problem: A wizard page is displayed even though the MDT database (MDT DB) or CustomSettings. they can emulate a 1. log and ZTIBDE. Run the Diskpart shrink querymax command again to verify that more than 2 GB of disk space can be unallocated. possibly because of fragmented disk space within drive C. The system volume is the volume that contains the hardware-specific files needed to load Windows after the BIOS has booted the computer. though. the BDD. the Diskpart tool may not be able to shrink drive C sufficiently to provide 2 GB of unallocated disk space. if necessary. One possible solution to this problem is to defragment drive C. If the value returned in step 1 is less than 2 GB. In some instances. 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. modifying the MDT 2010 scripts is not recommended. A). To deploy BitLocker Drive Encryption on a target computer. You can customize the ZTIBDE. Problems with Shrinking Disks Problem: Not enough unallocated disk space exists on the target computer to enable BitLocker Drive Encryption. perform the following steps: 1.com/technet/SolutionAccelerators . If the value returned in step 3 is still less than 2 GB. perform one of the following tasks: y y Defragment drive C multiple times to ensure that it is fully optimized. By default. Run the Diskpart shrink querymax command to identify the maximum amount of disk space that can be unallocated. In addition. MDT 2010 scripts use the lowest drive letter (in this example. Solution Accelerators microsoft. Possible Solution 2: The ZTIBDE. and then restore the data to the new partition. use the Diskpart tool to shrink drive C so that the system volume can be created. delete the existing partition.24 Microsoft Deployment Toolkit 2010 the memory storage drive.wsf script to change the default. Back up the data on drive C.exe) and configures the system volume partition size to 2 GB by default.wsf script runs the Disk Preparation Tool (bdehdcfg. 3. 4. To do so. create a new partition. clean drive C of any unnecessary files.log files record the removable media devices detected and which device was selected to store the BitLocker Drive Encryption recovery information. at least 2 gigabytes (GB) of unallocated disk space is required to create the system volume. Possible Solution 1: On existing computers. 2. and then defragment it. However. ´ at http://support. If the target computer is located on a network segment that does not have Dynamic Host Configuration Solution Accelerators microsoft.0 to create partitions on a hard disk. Possible Solution 2: Add data and values to the registry of Windows PE version 2. ³You cannot install Windows XP successfully after you use Windows Vista or Windows PE 2. and static IP configuration. you can see that the system has not joined the domain and is still in a workgroup.0. which describes the problem and provides an update for Windows XP that can serve as a workaround for the issue. the deployment process may fail when deploying to a target computer that is using logical drives or dynamic disks. Add the following settings to the Windows PE registry to work around the issue: [HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\A LIGNMENT] "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. These settings change how Windows PE partitions and formats the hard disk before the Windows XP image is applied.Troubleshooting Reference: Troubleshooting 25 Disk Partitioning Errors Problem: When using LTI to deploy Windows XP on some hardware. Possible Solution: An LTI deployment of MDT 2010 configures the static IP information after the operating system is up and running. you use the Windows Deployment Wizard to provide all the necessary information for the target computer. Domain Join Problem: During deployment. domain join information. the computer halts with a stop error or stops responding while loading Mup. Possible Solution 1: See the Microsoft Help and Support article.com/technet/SolutionAccelerators . 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.com/kb/931760/enus. including credentials.microsoft.sys after the computer attempts to start in mini-setup. Possible Solution: MDT 2010 does not support deploying operating systems to logical drives or dynamic disks. This problem occurs only on computers that use certain BIOS firmware. When Setup finishes. This problem occurs because Windows Vista and Windows PE version 2.0 create disk partitions differently than Windows XP does. For example.log The white paper.log as described in Troubleshooting Device Installation with SetupAPI.wsf will not copy over any existing Txtsetup.com/whdc/driver/install/setupapilog.microsoft.com/whdc/driver/install/default. an automated domain join specified in Unattend.´ at http://www. Then. Configure Unattend. ³Troubleshooting Device Installation with the SetupAPI Log File. Windows XP and later Windows versions log system operations more extensively than previous versions of Windows. because ZTIStorageDrivers.oem file on the local machine. One of the most useful log files for debugging purposes is the SetupAPI. Possible Solution: Do not combine $OEM$ mass storage drivers with the massstorage logic that MDT 2010 uses. the paper provides guidelines for driver developers and testers to interpret the SetupAPI log file.26 Microsoft Deployment Toolkit 2010 Protocol (DHCP). For general information about driver installation. Ensure that there are no mass storage drivers in the $OEM$ directory of any Windows XP or Windows Server 2003 source directory. installation of hardware devices and software drivers should run as seamlessly as possible. 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. y 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. Microsoft provides tools and guidelines to help create installation packages that meet this goal. if the driver package \Distribution\Operating Systems\Windows XP\$OEM$\txtsetup.mspx. Review device driver installation±related problems and solutions: y 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.mspx provides information about debugging device installation for Windows XP and later versions of Windows. see Driver Lifecycle at http://www.xml to join a workgroup. Specifically. This plain-text file maintains the Solution Accelerators microsoft. Troubleshooting device driver installation issues using the SetupAPI.wsf script. it causes installation of the new driver to fail.log file. Troubleshooting Device Installation with SetupAPI.log.com/technet/SolutionAccelerators . Driver Installation To ensure the best possible user experience.oem (or similar) is present. with little or no user intervention.microsoft.xml will fail when no DHCP is present. a warning message may appear similar to the following. Finally. a server that delivers executable files for new computer setup). This paper focuses on using the SetupAPI log file to troubleshoot device installation. Using the Microsoft Deployment Toolkit. see the MDT 2010 document. even though the specified share does exist: Warning .com/technet/SolutionAccelerators . Failure to Copy Log Files to Shared Folders Problem: When using the New Computer or Replace Computer deployment scenario. 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. New Computer Deployments Review the problems and solutions for New Computer deployment scenarios: y y Error messages that indicate a shared folder does not exist as described in Failure to Copy Log Files to Shared Folders. it does not describe the log file sections that are associated with service pack and update installations.Troubleshooting Reference: Troubleshooting 27 information that SetupAPI records about device installation. and update installation. 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. the client computer initiates execution of the downloaded image. service pack installation. 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. The client uses Trivial File Transfer Protocol (TFTP) to download the executable file from the boot server. For more information on providing the appropriate credentials for the different deployment phases. PXE Boot In brief. the boot server sends an offer containing the IP address of the server that will service the client. Solution Accelerators microsoft. Assuming that a boot server implementing this extended protocol is available.Unable to copy local logfile (C:\MININT\SMSOSD\OSDLOGS\ZeroTouchInstallation.log) because \\servername\Logs does not exist. the file maintains a record of device and driver changes as well as major system changes beginning from the most recent Windows installation. The client computer may use the opportunity to obtain an IP address (which is the expected behavior) but is not required to do so. Specifically. Problems starting the deployment process using Pre-Boot Execution Environment (PXE) boot as described in PXE Boot. ensure that the routers that forward DHCP broadcasts are designed so that both the DHCP and Windows Deployment Services servers receive the client broadcasts. If the DHCP servers and the computer running Windows Deployment Services are separate computers. Ensure that DHCP is configured properly as described in Ensure the Proper DHCP Configuration. Refer to the router instructions for more information about setting up DHCP forwarding on a specific router. because Windows Deployment Services client computers discover a Windows Deployment Services server by using a DHCP broadcast message.microsoft. the client computers¶ DHCP broadcasts do not reach the Windows Deployment Services server. 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. otherwise. This arrangement is necessary. Improve the response times for assigning IP addresses to PXE client computers as described in Improve PXE IP Address Assignment Response Time. This second phase is otherwise unrelated to the standard DHCP services. ³Description of PXE Interaction Among PXE Client.com/kb/244036. the client computer does not receive a reply to its remote boot request. Ensure the Proper DHCP Configuration Depending on the router models in use. Disable Windows PE Logging in Windows Deployment Services The first procedure recommended is to make sure that logging to setupapi. see the Microsoft Help and Support article.´ at http://support. Without DHCP forwarding set up on a router. configure the router between the two systems to forward DHCP packets to the Windows Deployment Services server. For more information on troubleshooting PXE boot-related issues in Windows Deployment Services running in Legacy or Mixed mode. the specific router configuration of DHCP broadcast forwarding may be supported to either a subnet (or router interface) or a specific host. DHCP.log has been disabled. The next few pages outline the step-by-step process during PXE client computer initialization.log as described in Disable Windows PE Logging in Windows Deployment Services. Review the following solutions for PXE boot issues: y y y Disable Windows PE logging to SetupAPI. This DHCP forwarding process is sometimes referred to as DHCP Proxy or IP Helper Address in router configuration manuals. and RIS Server.28 Microsoft Deployment Toolkit 2010 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.com/technet/SolutionAccelerators . Solution Accelerators microsoft. any restart of the target computer has MDT 2010 resume where it left off at the previous restart. Possible Solution: During the deployment process.com/technet/SolutionAccelerators .1 . 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. Product Keys Problem: The target computer is running Windows Vista and has an existing product key. Possible Solution: To allow the deployment process to restart from the beginning. The utility is available for download from http://www. full. Restarting the Deployment Process Problem: While testing and troubleshooting a new or modified task sequence.com/WindowsServer2003/techinfo/overview/printmigrator3. 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.1 utility to capture and restore printer configurations. it does not migrate TCP/IP± based printers.Troubleshooting Reference: Troubleshooting 29 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: y y Are the network adapter on the target computer and the switch or router set to the same speed (automatic. Possible Solution: Include task sequence steps that use the Windows Server 2003 Print Migrator 3. because MDT 2010 keeps track of its progress by writing data to the hard disk. you may need to restart the target computer so that the deployment process can start over from the beginning. If you run a task sequence on the target computer to perform an upgrade to Windows 7. delete the C:\MININT and C:\_SMSTaskSequence folders prior to restarting the target computer. duplex. the deployment process fails with an error message stating that an invalid product key was provided. Solution Accelerators microsoft. Unexpected results may occur.microsoft. provide a valid Windows 7 product key.mspx. Possible Solution 2: Verify that the specified credentials have sufficient rights to join computers to the domain. You cannot run Sysprep a fourth time. Possible Solution 2: Verify that the specified OU is in the correct format and that it exists. capture an image of the computer prior to running Sysprep. make any required changes. The Computer Account Is in the Wrong OU Problem: The target computer is properly joined to the domain. restore the master image. add a task sequence step that uses an automation tool. The target computer is not appearing in the correct AD DS OU as described in The Computer Account Is in the Wrong OU. Note This limitation does not affect Microsoft Volume Licensing media.DC=com. When the image requires updating. Possible Solution 1: If an account pre-exists for the target computer.inf file contains both JoinDomain and JoinWorkgroup entries. and then recapture the image prior to running Sysprep. To move the account to the specified OU. instead. such as a Microsoft Visual Basic® Scripting Edition (VBScript). Error 0x80040605 Re-arming Sysprep is limited to being run three times on an installed operating system.com/technet/SolutionAccelerators . Execution Limit Problem: The following Windows product activation error message is displayed after a master computer has had Sysprep run three times. Possible Solution 1: Never run Sysprep on the master image.30 Microsoft Deployment Toolkit 2010 Sysprep Review Sysprep±related problems and solutions: y y y The target computer is not joined to the domain as described in Joining a Domain. but the computer account is in the wrong OU.DC=Woodgrovebank.OU=NYC. Joining a Domain Problem: The target computer is not joined to the domain. to move the account. A Windows product activation error message is displayed. Solution Accelerators microsoft. the first one encountered takes precedence. the account will remain in its original OU. Possible Solution 1: If the Sysprep. The correct OU format should be OU=Reception. indicating that Sysprep has been run three times and has exceeded its limit as described in Execution Limit. Troubleshooting Reference: Troubleshooting 31 Possible Solution 2: When running Sysprep. The New Site Role wizard in the Configuration Manager Console should successfully finish when you have deleted the folder. For more information.com/technet/SolutionAccelerators . y y y Solution Accelerators microsoft. ³µError 0x80040605 Re-arming¶ Error Message When You Try to Run Riprep. Delete the PXE certificate folder from C:\Documents and Settings\user_name\Application Data\Microsoft\Crypto\RSA.´ at http://support. 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. 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. the message ³Please enter a valid name for the network adapter´ is displayed as described in Apply Network Settings.exe on Windows XP. Task Sequences Review task sequence±related problems and solutions: y 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.microsoft.com/kb/308554. While configuring a network connection name. the PXE service point may not have deleted the self-created certificates when you uninstalled it.exe or Sysprep. see the Microsoft Help and Support article. PXE service point error Possible Solution: If a PXE service point previously existed on the server you are configuring. where user_name is the name of the user performing the current configuration or who performed the previous configuration. use the ±activated option to avoid resetting activations. Task sequence steps are missing after upgrading from BDD 2007 as described in Upgrading from BDD 2007²Missing Task Sequence Steps. Figure 3. that task sequence step is added to the Unknown Tasks group. other SKUs for the operating system source still exist. Upgrading from BDD 2007²Missing Task Sequence Steps After upgrading a Microsoft Business Desktop Deployment (BDD) 2007 deployment share to MDT 2010. Administrative intervention is required to edit the task sequence and move the step to an appropriate location within the new task sequence. Possible Solution: The original operating system source has two or more WIM files associated. If a custom task sequence step specifies an application that cannot be matched to an application defined in the deployment share. however the operating system is not displayed in the Deployment Workbench.32 Microsoft Deployment Toolkit 2010 Bad Task Sequence Item (Invalid OS GUID) Message in Windows Deployment Wizard Problem: When running the Windows Deployment Wizard. Change the task sequence to use a different operating system image. 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.´ Possible Solution: Remove any spaces and invalid characters from the specified connection name. y Apply Network Settings Problem: When configuring the network connection name in the Deployment Workbench.´ The operating system is listed in the OperatingSystem. which is disabled. The Windows Deployment Wizard behaves normally. Solution Accelerators microsoft.com/technet/SolutionAccelerators y .xml file. customizations from the BDD 2007 task sequence are identified and moved to the new MDT 2010 task sequence using one of the following scenarios: y 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. the error message ³Bad Task Sequence Item (Invalid OS GUID)" is displayed after you click Next on the wizard page. An SKU that is associated with a task sequence is deleted. perform one of the following tasks: y Remove all SKUs from the operating system source. a validation error prompts you with the message. ³Please enter a valid name for the network adapter. Note Any custom task sequence steps that call a ZTI script are ignored. the wizard displays the error message ³Bad Task Sequence Item (Invalid OS GUID). and the error message is not displayed. To resolve this problem. however. com/technet/SolutionAccelerators . then Group A\Step B will not be processed. The shortcuts are captured during Scanstate. Consider the following: Two task sequence groups have been created. however. Missing Desktop Shortcuts Problem: While using USMT to migrate user data.IgnoreIrrelevantLinks()'> Solution Accelerators microsoft. To continue to use these task sequence steps in MDT 2010. and either group contains more than one task sequence step: y Group A y y y Step A Step B Group B y y Step A Step B If Group A\Step A is configured not to continue on error. relocate the task sequence steps to their proper location in the task sequence and enable them. User State Migration Tool Review USMT±related problems and solutions: y y Shortcuts that point to documents stored in network shared folders may not be restored properly as described in Missing Desktop Shortcuts. However. Using Continue on Error If a MDT 2010 task sequence is configured not to continue on error and that task sequence returns an error. the remaining task sequence groups are processed.Troubleshooting Reference: Troubleshooting 33 Note Any custom task sequence steps that are relocated to the Custom Tasks or Unknown Tasks groups in the task sequence are disabled. Possible Solution: Edit the MigUser. they are never restored to the target computer during Loadstate.xml file and comment out the following line: Original: <include> filter='MigXmlHelper. USMT error 1618 is displayed while deploying Windows XP images as described in USMT-related Errors During Deployment²Error 1618. However. all task sequence steps in Group B will be processed. all remaining task sequences in that task sequence group are skipped. shortcuts that point to network documents may not be restored. aborting ZTIUserState 18/01/2008 16:00:15 0 (0x0000) ERROR . but you will likely encounter other issues if you do not correct the cause of the original error.IgnoreIrrelevantLinks()'> --> USMT-related Errors During Deployment²Error 1618 Problem: While deploying a Windows XP image.0 to restore user state. Solution Accelerators microsoft. the following error messages may be logged during the State Restore phase when USMT is being installed: y USMT installer found at \\Server\Packages$\SMSPKG\E000019B\InstallUSMT301_X86.0.´ 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. The 1618 message translates to.com/technet/SolutionAccelerators .exe /I "\\Server\Packages$\SMSPKG\E000019B\InstallUSMT301_X86.msi.cab file so it is not possible to install USMT 3.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. ³Another installation is already in progress. The problem is a result of a previous task sequence step in the deployment process. ZTIUserState 18/01/2008 16:00:15 0 (0x0000) ERROR: Unable to find USMT30_X86.Unable to install USMT 3. and verify that the commands for those installations are appropriate. Possible Solution 2: You can avoid this problem by creating a USMT CAB file.34 Microsoft Deployment Toolkit 2010 Modified: <include> <!-filter='MigXmlHelper. ZTIUserState 18/01/2008 16:00:12 0 (0x0000) About to run command: msiexec. ZTIUserState 18/01/2008 16:00:15 0 (0x0000) y y 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.0.msi" /quiet /passive /norestart ZTIUserState 18/01/2008 16:00:12 0 (0x0000) Return code from command = 1618 18/01/2008 16:00:15 0 (0x0000) ZTIUserState y y y y Non-zero return code from USMT 3. Complete that installation before proceeding with this install. Point to Microsoft Deployment Toolkit. Possible Solution 3: An update is available for Windows Vista that may fix the USMT installation problem. Use the Remove WDS PXE Filter Wizard to remove support. you must remove this support to allow the WDS service to work as expected. which resulted in a workaround implemented in the ZTIUserState.microsoft. Possible Solution: If the previous installation of MDT used WDS PXE Filter support. Run the command Makecab /F USMT30_platform. 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. and then click Remove WDS PXE Filter Wizard. For more information about the update. copy the newly created CAB file (USMT30_platform. Note To access the Remove WDS PXE Filter Wizard.ddf. 3. the installation fails. 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. If this update is included in the Windows Vista image.exe together with the /quiet option to try to install certain software packages on a Windows Vista±based computer. see the Microsoft Help and Support article. Note If USMT is installed in a location other than the default (C:\Program Files\USMT301). Solution Accelerators microsoft.cab) to the \Tools\platform folder in the MDT 2010 deployment share. then.com/kb/929761. you may not need to perform the steps outlined in ³Possible Solution 2´ in this section. ³When you run Wusa. USMT would not install quietly using the standard /quiet option. edit USMT30_platform. Copy C:\Program Files\Microsoft Deployment Toolkit\Samples\USMT30_platform. 2. where platform is either x86 or x64. click Start. from a computer on which MDT 2010 is installed.com/technet/SolutionAccelerators . Wusa.ddf to indicate the correct path to the USMT program folder.ddf. Windows Deployment Services Review Windows Deployment Services±related problems and solutions: y The WDS service does not work as expected after upgrading to MDT 2010 as described in WDS Service Fails When PXE Filter Is Installed. Manually install the x86 or x64 version of USMT²whichever is applicable to the environment²on a computer running Windows XP or Windows Vista. and then point to All Programs.´ at http://support.Troubleshooting Reference: Troubleshooting 35 Because of a bug in the Windows Vista installation program.wsf script.exe (used to install Microsoft Update Standalone Package [MSU] files). ³The data is invalid. 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.´ Further investigation shows that the date stamp of the WIM file is many years before the current date.log file as described in Corrupt WIM File. opens a Command Prompt window.com/technet/SolutionAccelerators . It is possible that another process. y y Deployment Process Not Initiated²Limited RAM or Wireless Network Adapter Problem: When deploying an image to certain target computers. rc = 2 Investigate the issue by mounting the WIM file using ImageX results in the error. The LTI or ZTI deployment process is not initiated because of missing Windows PE components as described in Deployment Process Not Initiated²Missing Components. Solution Accelerators microsoft.Non-zero return code by LTIApply. Windows PE starts. Windows PE Review Windows PE±related problems and solutions: y 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. such as a virus scanner. Return Value = 2 y y ZTI ERROR . Corrupt WIM File Problem: When deploying an image. but does not actually start the deployment process. rc = 2 LTIApply COMPLETED.wim was not applied successfully by ImageX.log file: y The image \\Server\Deployment$\Operating Systems\Windows XP SP2\version1. the deployment fails with the following entries in the BDD. runs wpeinit. Troubleshooting the problem by mapping a network drive from the target computer indicates that the network adapter drivers are not loaded. Possible Solution: Restore the WIM file from backup media. was holding the WIM file open after it was previously closed at the conclusion of a Read or Write process.36 Microsoft Deployment Toolkit 2010 Windows Imaging Format Files Review WIM-related problems and solutions: y LTI and ZTI deployments fail with WIM file errors in the BDD. Windows PE 2. Note The Windows PE images that System Center Configuration Manager creates contain components that support scripting. and Windows Management Instrumentation (WMI). instead. Solution Accelerators microsoft. because there is insufficient RAM. Windows PE starts. Deployment Process Not Initiated²Missing or Incorrect Drivers Problem: When deploying to certain target computers. because of the nature of LTI in MDT 2010. Also.´ The drivers in the Out-ofBox Drivers list have been injected into the image. 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.Troubleshooting Reference: Troubleshooting 37 Possible Solution 1: The Windows Deployment Wizard is not starting. runs wpeinit. impossible to query SQL Server: ActiveX component can't create object (429). If you are using System Center Configuration Manager. Deployment Process Not Initiated²Missing Components Problem: When troubleshooting a failed deployment.log file located in X:\Windows\System32\Inf indicates that Windows PE generates errors when it is configuring the network adapter. do not use one of the existing Windows PE images that System Center Configuration Manager created.Unable to create ADODB. create a Windows PE drivers group that contains only network adapter and storage drivers. Possible Solution 2: Do not include the wireless drivers in the Windows PE image. A review of the SetupAPI.log file lists the following entry: ERROR . create an image using the Import Microsoft Deployment Task Sequence Wizard. but they do not contain components that support Microsoft ActiveX® Data Objects (ADO). ³This driver is not meant for this platform.Connection object. Extensible Markup Language (XML). one of which is. opens a Command Prompt window. If you have included both Windows XP and Windows Vista drivers.com/technet/SolutionAccelerators . add the driver for Windows Vista into the Windows PE drivers group. Troubleshooting by mapping a network drive from the target computer indicates that the network adapter drivers are not loaded. but does not actually start the deployment process. Possible Solution: It is possible that Windows PE is having a driver conflict with another driver. LTI will not run with Windows PE 2005. and then configure the deployment share to use only the Windows PE driver group. When configuring the settings for the Windows PE image in the Deployment Workbench. a review of the BDD. Possible Solution: This error may indicate that the Windows PE image was not created using MDT 2010.0 is unable to run on a target computer that has less than 512 MB of RAM. com/technet/SolutionAccelerators .38 Microsoft Deployment Toolkit 2010 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. Figure 8. LTI Deployment Process Flowcharts Flow charts are provided for the following phases: y y y y y y Validation (Figure 4) State Capture (Figure 5 and Figure 6) Preinstall (Figure 7. Figure 15. Reviewing the ZTI deployment process flowcharts as described in ZTI Deployment Process Flowcharts. Figure 14. Each flow chart illustrates the tasks executed during that deployment type. and Figure 16) Solution Accelerators microsoft. and Figure 9) Install (Figure 10) Postinstall (Figure 11 and Figure 12) State Restore (Figure 13. Familiarize yourself with the deployment process flow charts by: y y Reviewing the LTI deployment process flowcharts as described in LTI Deployment Process Flowcharts. Troubleshooting Reference: Flow Charts 39 Figure 4. Flow chart for the Validation Phase Solution Accelerators microsoft.com/technet/SolutionAccelerators . 40 Microsoft Deployment Toolkit 2010 Figure 5. Flow chart for the State Capture Phase (1 of 2) Solution Accelerators microsoft.com/technet/SolutionAccelerators . com/technet/SolutionAccelerators .Troubleshooting Reference: Flow Charts 41 Figure 6. Flow chart for the State Capture Phase (2 of 2) Solution Accelerators microsoft. 42 Microsoft Deployment Toolkit 2010 Figure 7.com/technet/SolutionAccelerators . Flow chart for the Preinstall Phase (1 of 3) Solution Accelerators microsoft. Troubleshooting Reference: Flow Charts 43 Figure 8.com/technet/SolutionAccelerators . Flow chart for the Preinstall Phase (2 of 3) Solution Accelerators microsoft. 44 Microsoft Deployment Toolkit 2010 Figure 9.com/technet/SolutionAccelerators . Flow chart for the Preinstall Phase (3 of 3) Solution Accelerators microsoft. com/technet/SolutionAccelerators . Flow chart for the Install Phase Figure 11. Flow chart for the Postinstall Phase (1 of 2) Solution Accelerators microsoft.Troubleshooting Reference: Flow Charts 45 Figure 10. 46 Microsoft Deployment Toolkit 2010 Figure 12. Flow chart for the Postinstall Phase (2 of 2) Solution Accelerators microsoft.com/technet/SolutionAccelerators Troubleshooting Reference: Flow Charts 47 Figure 13. Flow chart for the State Restore Phase (1 of 4) Solution Accelerators microsoft.com/technet/SolutionAccelerators 48 Microsoft Deployment Toolkit 2010 Figure 14. Flow chart for the State Restore Phase (2 of 4) Solution Accelerators microsoft.com/technet/SolutionAccelerators Troubleshooting Reference: Flow Charts 49 Figure 15. Flow chart for the State Restore Phase (3 of 4) Solution Accelerators microsoft.com/technet/SolutionAccelerators . com/technet/SolutionAccelerators Solution Accelerators .50 Microsoft Deployment Toolkit 2010 Figure 16. Flow chart for the State Restore Phase (4 of 4) ZTI Deployment Process Flowcharts Flow charts are provided for the following phases of ZTI deployment with System Center Configuration Manager: y y y y y y Initialization (Figure 17) Validation (Figure 18) State Capture (Figure 19) Preinstall (Figure 20) Install (Figure 21) Postinstall (Figure 22) microsoft. com/technet/SolutionAccelerators . Flow chart for the Initialization Phase Solution Accelerators microsoft.Troubleshooting Reference: Flow Charts 51 y y State Restore (Figure 23 and Figure 24) Capture (Figure 25) Figure 17. 52 Microsoft Deployment Toolkit 2010 Figure 18. Flow chart for the Validation Phase Solution Accelerators microsoft.com/technet/SolutionAccelerators . Flow chart for the State Capture Phase Solution Accelerators microsoft.Troubleshooting Reference: Flow Charts 53 Figure 19.com/technet/SolutionAccelerators . 54 Microsoft Deployment Toolkit 2010 Figure 20. Flow chart for the Preinstall Phase Solution Accelerators microsoft.com/technet/SolutionAccelerators . Troubleshooting Reference: Flow Charts 55 Figure 21. Flow chart for the Install Phase Solution Accelerators microsoft.com/technet/SolutionAccelerators . com/technet/SolutionAccelerators .56 Microsoft Deployment Toolkit 2010 Figure 22. Flow chart for the Postinstall Phase Solution Accelerators microsoft. Troubleshooting Reference: Flow Charts 57 Figure 23. Flow chart for the State Restore Phase (1 of 2) Solution Accelerators microsoft.com/technet/SolutionAccelerators . 58 Microsoft Deployment Toolkit 2010 Figure 24.com/technet/SolutionAccelerators . Flow chart for the State Restore Phase (2 of 2) Solution Accelerators microsoft. Troubleshooting Reference: Flow Charts 59 Figure 25.com/technet/SolutionAccelerators . Flow chart for the Capture Phase Solution Accelerators microsoft. aspx Deployment Guys blog at http://blogs. or go online to http://www. Mentioning ³deployment´ in general may result in routing to the incorrect queue.) Microsoft-hosted newsgroups and forums: Solution Accelerators microsoft. Note When seeking support. Obtaining additional support through blogs and other Internet resources as described in Internet Support.60 Microsoft Deployment Toolkit 2010 Finding Additional Help Find additional help in resolving MDT 2010 deployment problems by: y y Contacting Microsoft Services Premier Support as described in Microsoft Services Premier Support.com/benhunter/default.com/richardsmith/default.) Michael Niehaus¶ blog at http://blogs.com/mniehaus/default. Internet Support Many online sources provide additional troubleshooting assistance for MDT 2010 beyond what is covered in this reference.technet. Several individuals have been routed to the incorrect support queue while trying to receive support for MDT 2010.com/services/microsoftservices/srv_premier. 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. call Premier Support at 1-800-9363500. To be routed to the correct support queue.) Richard Smith¶s blog at http://blogs. We apologize for their frustration and inconvenience. clearly state that there is a Business Desktop Deployment/Microsoft Deployment Toolkit issue.com/deploymentguys/ Ben Hunter¶s blog at http://blogs.aspx (Michael Niehaus writes on Windows and Microsoft Office deployment. Note Please note that support for MDT 2010 is done via callback.microsoft. These online sources include: y Microsoft-hosted blogs: y y y y y y MDT 2010 Team blog at http://blogs. with response times generally ranging between 1 and 4 hours depending on the severity of the issue and other issues in the queue.technet.technet.aspx (Ben Hunter is a consultant with Microsoft Services±New Zealand.mspx.technet.com/technet/SolutionAccelerators .aspx (Richard Smith is a consultant with Microsoft Services±United Kingdom.technet.com/msdeployment/default. public.com/microsoft.usmt at news://msnews.public.microsoft.microsoft.deploymentforum.com at http://www.com at http://www.setup microsoft.microsoft.deployment.com/microsoft.com/TechNet/ShowForum.com/microsoft.com DeployVista.office.microsoft.deployvista.office.desktop System Center Configuration Manager at http://forums.com at http://www.com/microsoft.app_compatib ility TechNet forum: Windows Vista Deployment and Imaging at http://forums.public.deployment.public.aspx?ForumGroupID=488&S iteID=17 microsoft. industry peers.deployment.com Solution Accelerators microsoft.myitforum.microsoft.setup at news://msnews.com/TechNet/default.usmt microsoft.app_compatibility at news://msnews.public.aspx?ForumID=721&Sit eID=17 y y y y y Deployment-related information sources from outside Microsoft: y y y DeploymentForum.Troubleshooting Reference: Finding Additional Help 61 The following newsgroups and forums are available with support from Microsoft employees.desktop at news://msnews.public.com myITforum.deployment.public.public.com/technet/SolutionAccelerators . and Microsoft Valued Professionals (MVPs): y y microsoft.microsoft.