Troubleshooting New Computer Deployments
The following sections describe issues related to failed new computer deployments.
On This Page
.gif){kind=icon}
Failure to Copy Log Files to Shared Folders
Identify USMT-Related Issues
PXE Boot-Related Issues
Failure to Copy Log Files to Shared Folders
When using the New Computer or Replace Computer deployment scenarios, team members may see a warning message similar to the following, even though the specified share does exist:
Warning - Unable to copy local logfile (C:\MININT\SMSOSD\OSDLOGS\ZeroTouchInstallation.log) because \\SERVERNAMEservername\Logs does not exist.
This message can occur because the SMS 2003 OSD Feature Pack may not have the appropriate credentials to access the \\*servername\*Logs folder when the \\*servername\*Logs folder resides on a server other than the distribution point. For more information on providing the appropriate credentials for the different deployment phases, see the section, “Configure Resource Access,” in the Microsoft Deployment document, Deployment Feature Team Guide.
Identify USMT-Related Issues
The ZeroTouchInstallation.vbs script automatically scans the Windows User State Migration Tool (USMT) progress logs for errors and warnings. During this process, the script writes each error and warning to the ZeroTouchInstallation.log file. (The script writes at least the first 100 errors and warnings while ignoring Failed to locate the file object warnings, because these are too common.) In addition, the script generates event ID 41010 to Microsoft System Center Operations Manager 2007 with the following summary (where <USMTType> is ESTIMATE, SCANSTATE, or LOADSTATE; <ErrorCount> is the total number of errors found; and <WarningCount> is the total number of warnings found):
ZTI USMT <USMTType> reported <ErrorCount> errors and <WarningCount> warnings
If the error count is greater than 0, this event is an Error type. If the warning count is greater than 0 with no errors, then the event is a Warning type. Otherwise, the event is an Informational type.
PXE Boot-Related Issues
In brief, the Pre-Boot Execution Environment (PXE) protocol operates as follows: The client computer initiates the protocol by broadcasting a Dynamic Host Configuration Protocol (DHCP) Discover packet containing an extension that identifies the request as coming from a client computer that implements the PXE protocol. Assuming that a boot server implementing this extended protocol is available, the boot server sends an offer containing the IP address of the server that will service the client. The client uses Trivial File Transfer Protocol (TFTP) to download the executable file from the boot server. Finally, the client computer initiates execution of the downloaded image.
The initial phase of this protocol piggybacks on a subset of the DHCP messages to enable the client to discover a boot server (that is, a server that delivers executable files for new computer setup). The client computer may use the opportunity to obtain an IP address (which is the expected behavior) but is not required to do so.
The second phase of this protocol takes place between the client computer and a boot server and uses the DHCP message format as a convenient format for communication. This second phase of the protocol is otherwise unrelated to the standard DHCP services. The next few pages outline the step-by-step process during PXE client computer initialization.
For more information on troubleshooting PXE boot-related issues in Windows Deployment Services running in Legacy or Mixed mode, see the Microsoft Help and Support article, “Description of PXE Interaction Among PXE Client, DHCP, and RIS Server,” at https://support.microsoft.com/kb/244036/EN-US.
Disable Windows PE Logging on the Windows Deployment Services Server
The first procedure recommended is to make sure that logging to setupapi.log has been disabled. To do so, follow the instructions in the section, “Disable Windows PE Logging on the Windows Deployment Services Server,” in the Microsoft Deployment document, Preparing for Microsoft Systems Management Server 2003.
Ensure the Proper DHCP Configuration
Depending on the router models in use, the specific router configuration of DHCP broadcast forwarding may be supported to either a subnet (or router interface) or a specific host. If the DHCP servers and Windows Deployment Services servers are separate computers, ensure that the routers that forward DHCP broadcasts are designed so that both the DHCP and Windows Deployment Services servers receive the client broadcasts; otherwise, the client computer does not receive a reply to its remote boot request.
Is there a router between the client computer and the remote installation server that is not allowing the DHCP-based requests or responses through? When the Windows Deployment Services client computer and the Windows Deployment Services server are on separate subnets, the router between the two systems must be configured to forward DHCP packets to the Windows Deployment Services server. This arrangement is necessary, because Windows Deployment Services client computers discover a Windows Deployment Services server by using a DHCP broadcast message. Without DHCP forwarding set up on a router, the client computers’ DHCP broadcasts do not reach the Windows Deployment Services server. This DHCP forwarding process is sometimes referred to as DHCP Proxy or IP Helper Address in router configuration manuals. Refer to the router instructions for more information about setting up DHCP forwarding on a specific router.
Improve PXE IP Address Assignment Response Time
Check the following elements if it is taking a long time (15–20 seconds) for the PXE client computer to get an IP address:
Are the network adapter on the target computer and the switch or router set to the same speed (automatic, duplex, full, and so on)?
Is the IP address for the Windows Deployment Services server in the IP Helper file on the router through which the connection is made? If the list of IP addresses in the IP Helper file is long, can the address for the Windows Deployment Services server be moved near the top?
Be sure that Setupapi.log is disabled as described in the section, “Disable Windows PE Logging on the Windows Deployment Services Server,” in Preparing for Microsoft Systems Management Server 2003.
Download
Get the Microsoft Deployment Solution Accelerator
Update Notifications
Sign up to learn about updates and new releases
Feedback