ConfigMgr 2007: OSD deployment errors out within a few seconds after WinPE loads and then automatically reboots

ConfigMgr 2007: OSD deployment errors out within a few seconds after WinPE loads and then automatically reboots

  • Comments 2
  • Likes

Here's another great OSD related tip from Frank Rojas, a Senior Support Engineer in our Charlotte, NC office.  If you're seeing strange reboots with your deployments then maybe what you really have is a network problem:

========

Issue: When performing a deployment via System Center Configuration Manager 2007 OSD on a client PC, the client PC may boot into WinPE but within a few seconds it automatically reboots and does not perform the Task Sequence advertised to the PC, or it does not give the option to select a Task Sequence advertised for that PC. Examining the SMSTS.log obtained from X:\Windows\Temp when the Command Support option is enabled, we see the following error message:

If booting from PXE:

Failed to download pxe variable file. Code(0x00000001)    TSPxe
PxeGetPxeData failed with 0x80004005    TSPxe

If booting from boot media (CD/DVD/USB Flash Drive):

Error. Received 0x80072ee7 from WinHttpSendRequest.    TSMBootstrap
unknown host (gethostbyname failed)    TSMBootstrap
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)    TSMBootstrap
sending with winhttp failed; 80072ee7    TSMBootstrap
Will retry in 6 second(s)    TSMBootstrap

or

Failed to find a valid network adapter. Please ensure that this machine has a network adapter and appropiate network drivers.
Unspecified error (Error: 80004005; Source: Windows)    TSMBootstrap
Failed to find a valid network adapter.
For more information, please contact your system administrator or helpdesk operator.    TSMBootstrap

Cause: These errors may be caused by no network connectivity on the client PC, usually caused by no network drivers for the PC being loaded into the WinPE Boot Image.

Resolution: To resolve this issue make sure that the following actions are taken:

  1. Load Windows Vista or Windows Server 2008 32-bit drivers into the x86 Boot Image
  2. Load Windows Vista or Windows Server 2008 64-bit drivers into the x64 Boot Image
  3. Make sure network cable is plugged into the Client PC

To Check Network Connectivity:

  1. Make sure that "Enable command support" is enabled in the Boot Image
  2. Attempt the deployment
  3. When the WinPE desktop appears and you see the Microsoft System Center Configuration Manager 2007 wallpaper, hit F8 to open the command prompt window
  4. In the command prompt window, type IPCONFIG

Results of IPCONFIG:

a) If you only see the title "Windows IP Configuration", then there probably are no NIC drivers loaded in WinPE. Load the proper NIC drivers into the WinPE Boot Images (see additional notes and tips below).

b) If you see additional information, including IP information, but it may say "Media Disconnected" and the IP is either 0.0.0.0 or 169.x.x.x, then the NIC drivers are probably loaded correctly in WinPE, but there is no network connectivity to the network port on the client PC. Check cables and connections and make sure there is network connectivity to the port.

Additional Information:

Notes & Tips When Loading Drivers Into The WinPE Boot Images:

  1. Windows XP or Windows Server 2003 drivers do not always work in WinPE 2.x used by SCCM 2007 OSD, so always try to use Windows Vista or Windows Server 2008 drivers first.
  2. If there are no Windows Vista or Windows Server 2008 drivers available, you can try and use Windows XP or Windows Server 2003 drivers as they will usually work in the majority of cases.
  3. Make sure that ONLY 32-bit drivers are loaded into the x86 Boot Image and that ONLY 64-bit drivers are loaded into the x64 Boot Image.
  4. Only load NIC and Mass Storage Drivers into a Boot Image. No other drivers (audio, chipset, video, etc.) should be necessary and may only cause problems.
  5. If not needed, do not load any NIC drivers labeled as "Virtual" as they tend to cause problems. Usually they are not necessary as long as the normal NIC driver is loaded.

How To Check What Operating System And What Architecture (x86 or x64) A Particular Driver Supports:

  1. In the SCCM 2007 Admin console, go to Site Database --> Computer Management --> Operating System Deployment --> Drivers.
  2. On the right pane, find the driver you want to obtain more information from and click once on it. If the drivers have been grouped into folders under Drivers, you will first need to click on the folder before the drivers show up on the right hand side.
  3. On the window pane the appears at the bottom of the console, click on the Applicability tab. This screen will tell you what Supported Platforms(Operating System and Architecture) and what Supported Models the driver is made for.

How To Easily Add 32-bit And 64-bit Drivers To The Appropriate WinPE Boot Image:

  1. First follow the steps in the above section "How To Check What Operating System And What Architecture (x86 or x64) A Particular Driver Supports" to determine what architecture (x86 or x64) the driver supports.
  2. Right click on the driver and choose "Add or Remove Drivers to Boot Images".
  3. Based on the information determined in step 1, choose the appropriate Boot Image. Do not select both Boot Images. Only select the Boot Image whose architecture matches that of the driver, and the select OK.

========

Thanks Frank!

J.C. Hornbeck | Manageability Knowledge Engineer

Comments
  • Here's another great OSD related tip from Frank Rojas, a Senior Support Engineer in our Charlotte

  • thank you

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment