WinPE: Restarting DHCP client service

Written by Ingmar Verheij on July 7th, 2011. Posted in Deployment

A bare-metal deployment is build using Altiris Deployment Solutions (HP Rapid Deployment Pack, to be precise). When a client boots Windows PE 2.1 to execute a job (installation of operating system) it doesn’t seem to get an IP address from the DHCP server (Restarting DHCP client service: retry x).

WinPE : Restarting DHCP client service: retry

 

 

 

 

 

 

 

 

 

This is strange since the WinPE 2.1 image is downloaded via a PXE boot which acquired a IP address from the DHCP server without problems, the DHCP mechanism is working.

This caused me some serious headache a few months ago (at another customer). I investigated the problem and found the cause of the problem.

Wrong driver

The problem is caused by a missing / wrong driver for the network interface card. Since no message is displayed that a driver is missing, I assume a wrong driver is loaded. Because the wrong driver is loaded the TCP/IP stack isn’t working properly which results in the message seen above.

By adding the correct driver to the WinPE driver repository the problem is probably solved.

Determine NIC installed

Since the machine is provisioned with a Windows 7 installation out-of-the-box it is easy to determine the NIC installed. In this case a ‘Realtek RTL8168D/8111D-Family PCE-E Gigabit Ethernet NIC’.

To determine if the driver is already present in the driver repository of the WinPE image I need the Vendor and Device ID.These are visible in the ‘Details’ tab of the properties of the NIC by selecting  ‘Hardware-ID’s’ in the combo box. In this case the vendor ID is 10EC (Realtek) and the Device ID is 8168. The device contains the ‘RTL8167’chipset according to the PCI database.

Realtek RTL8168D/8111D-Family PCE-E Gigabit Ethernet NIC

Realtek RTL8168D/8111D-Family PCE-E Gigabit Ethernet NIC - Hardware ID

 

 

 

 

 

 

 

 

 

Finding the correct driver

Now we know the NIC (and chipset) we can find a driver for WinPE 2.1. Since WinPE 2.1 is used we’re looking for a Windows Server 2008 / Windows Vista SP1 driver. A quick Google search (for Vista drivers) led me to a driver on the Realtek site.

Realtek RTL8168-D8111D driver on Realtek site

 

Adding driver to WinPE driver repository

The boot image for Windows PE can be altered from the Altiris Deployment Solutions console via ‘Tools –> PXE Configuration’. This will open the ‘PXE Configuration Utility’ showing all boot options.

  1. Select the WinPE2.1 boot image and click ‘Edit’. This will open the ‘Edit Shared Configuration’ dialog.
  2. This will open the ‘Boot Disk Creator’ dialog.
  3. Select the root node and open the context menu (right mouse click) and select ‘Edit Configuration…’
  4. Click Next until you reach ‘Step 2 of 12 : Windows PE Hardware Device Drivers’
  5. Deselect ‘Auto-detect all device drivers’ (if selected)
  6. Check if a driver for the device (Vendor ID / Device ID) is already present. In my case it was and I decided to replace it with a new driver.
  7. Click ‘Have Disk’
  8. Add the driver you downloaded before (both x86 and x64 if required)
  9. Select ‘Auto-detect all device drivers’ (if it was selected in step 4)
  10. Click Next until you reach ‘Step 11 of 12: Edit configuration’
  11. During step 11 the WinPE boot image will be re-created by extracting the WIM images, injecting drivers and scripts, and rebuilding (and optionally compressing) the WIM image. This is done for all selected architectures (X86 / X64 / IA64).
  12. Wait until ‘Step 12 of 12: Boot Disk Creation Complete’ is shown and click ‘Finish’
  13. Close the ‘Edit Shared Configuration’ dialog
  14. Click ‘Save’ in the ‘PXE Configuration Utility’
  15. Select the tab ‘Status’ and wait until the status of all PXE servers change from ‘Updating’ to ‘Ready’.

Alitris menu - PXE Configuration

PXE Configuration Utility - Before

Edit Shared Menu Option

 

 

 

 

 

Boot Disk Creator - Edit Configuration

Boot Disk Creator - Step 2a

Boot Disk Creator - Step 2b

 

 

 

 

Boot Disk Creator - Step 11

Boot Disk Creator - Step 12

PXE Configuration Utility - Post

 

 

 

 

PXE Servers Status - Updating

PXE Servers Status - Ready

 

 

 

 

And you’re done! Replacing the driver solved the problem, the client got an IP address and continued to perform the task it was given.

 

 

Ingmar Verheij

Ingmar Verheij

At the time Ingmar wrote this article he worked for PepperByte as a Senior Consultant (up to May 2014). His work consisted of designing, migrating and troubleshooting Microsoft and Citrix infrastructures. He was working with technologies like Microsoft RDS, user environment management and (performance) monitoring. Ingmar is User Group leader of the Dutch Citrix User Group (DuCUG). RES Software named Ingmar RES Software Valued Professional in 2014.

More Posts - Website

Follow Me:
TwitterLinkedInGoogle Plus

Tags: , , ,

Trackback from your site.

Comments (3)

  • Ørjan
    18 November 2011 at 10:58 |

    My “Edit Configuration…” button is gray, but I can press “<< Edit" button next to "Next" button and navigate to the same place, but when I add drivers, the number of drivers in the list, does not increece. the Intel(R) 82579LM Gigabit Network Connection driver is there, but only E1C6232, not E1C62x64. I try to add those but no luck.

    • Ingmar Verheij
      18 November 2011 at 12:19 |

      Hi Ørjan,

      What version of Altiris DS are you using?
      If you can add drivers in the list, how did you get there? Can you send me some screenshots of the steps so I can help you troubleshoot?
      A solution to your problem might be that you should first remove the Intel 82579LM drivers before you add your new drivers, an alternative is that you create to drivers. One for x86 and one for x64.

  • 18 November 2011 at 14:10 |

    http://tinypic.com/view.php?pic=2uqer5u&s=5 is what I did from step 3 to 8. How do I delete a driver from the list? What is Altiris DS

Leave a comment

*

Donate

%d bloggers like this: