{"id":2940,"date":"2011-07-07T11:00:00","date_gmt":"2011-07-07T09:00:00","guid":{"rendered":"https:\/\/ingmarverheij.com\/?p=2940"},"modified":"2011-07-07T13:20:34","modified_gmt":"2011-07-07T11:20:34","slug":"winpe-restarting-dhcp-client-service","status":"publish","type":"post","link":"https:\/\/ingmarverheij.com\/en\/winpe-restarting-dhcp-client-service\/","title":{"rendered":"WinPE: Restarting DHCP client service"},"content":{"rendered":"

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\u2019t seem to get an IP address from the DHCP server (Restarting DHCP client service: retry x<\/em>).<\/p>\n

\"WinPE<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

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.<\/p>\n

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

<\/p>\n

Wrong driver<\/h4>\n

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\u2019t working properly which results in the message seen above.<\/p>\n

By adding the correct driver to the WinPE driver repository the problem is probably solved.<\/p>\n

<\/h4>\n

Determine NIC installed<\/h4>\n

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\u2019. <\/em><\/p>\n

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 \u2018Details\u2019 tab of the properties of the NIC by selecting\u00a0 \u2018Hardware-ID\u2019s\u2019 in the combo box. In this case the vendor ID is 10EC (Realtek<\/a>) and the Device ID is 8168. The device contains the \u2018RTL8167\u2019chipset according to the PCI database<\/a>.<\/p>\n

\"Realtek<\/a><\/p>\n

\"Realtek<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Finding the correct driver<\/h4>\n

Now we know the NIC (and chipset) we can find a driver for WinPE 2.1. Since WinPE 2.1<\/a> is used we\u2019re 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<\/a> site.<\/p>\n

\"Realtek<\/a><\/p>\n

 <\/p>\n

Adding driver to WinPE driver repository<\/h4>\n

The boot image for Windows PE can be altered from the Altiris Deployment Solutions console via \u2018Tools \u2013> PXE Configuration\u2019. This will open the \u2018PXE Configuration Utility\u2019 showing all boot options.<\/p>\n

    \n
  1. Select the WinPE2.1 boot image and click \u2018Edit\u2019. This will open the \u2018Edit Shared Configuration\u2019 dialog.<\/li>\n
  2. This will open the \u2018Boot Disk Creator\u2019 dialog.<\/li>\n
  3. Select the root node and open the context menu (right mouse click) and select \u2018Edit Configuration\u2026\u2019<\/li>\n
  4. Click Next until you reach ‘Step 2 of 12 : Windows PE Hardware Device Drivers\u2019<\/li>\n
  5. Deselect \u2018Auto-detect all device drivers\u2019 (if selected)<\/li>\n
  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.<\/em><\/li>\n
  7. Click \u2018Have Disk\u2019<\/li>\n
  8. Add the driver you downloaded before (both x86 and x64 if required)<\/li>\n
  9. Select \u2018Auto-detect all device drivers\u2019 (if it was selected in step 4)<\/li>\n
  10. Click Next until you reach \u2018Step 11 of 12: Edit configuration\u2019<\/li>\n
  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).<\/li>\n
  12. Wait until \u2018Step 12 of 12: Boot Disk Creation Complete\u2019 is shown and click \u2018Finish\u2019<\/li>\n
  13. Close the \u2018Edit Shared Configuration\u2019 dialog<\/li>\n
  14. Click \u2018Save\u2019 in the \u2018PXE Configuration Utility\u2019<\/li>\n
  15. Select the tab \u2018Status\u2019 and wait until the status of all PXE servers change from \u2018Updating\u2019 to \u2018Ready\u2019.<\/li>\n<\/ol>\n

    \"Alitris<\/a><\/p>\n

    \"PXE<\/a><\/p>\n

    \"Edit<\/a><\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    \"Boot<\/a><\/p>\n

    \"Boot<\/a><\/p>\n

    \"Boot<\/a><\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    \"Boot<\/a><\/p>\n

    \"Boot<\/a><\/p>\n

    \"PXE<\/a><\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    \"PXE<\/a><\/p>\n

    \"PXE<\/a><\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    <\/h4>\n

    And you\u2019re done! Replacing the driver solved the problem, the client got an IP address and continued to perform the task it was given.<\/p>\n

     <\/p>\n

     <\/p>\n

    Ingmar Verheij<\/p>","protected":false},"excerpt":{"rendered":"

    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\u2019t seem to get an IP address from the DHCP server (Restarting DHCP client service: retry x).             […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-container-style":"default","site-container-layout":"default","site-sidebar-layout":"default","disable-article-header":"default","disable-site-header":"default","disable-site-footer":"default","disable-content-area-spacing":"default","footnotes":""},"categories":[289],"tags":[219,355,356,354],"class_list":["post-2940","post","type-post","status-publish","format-standard","hentry","category-deployment-others","tag-altiris","tag-dhcp","tag-driver","tag-winpe"],"_links":{"self":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts\/2940","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/comments?post=2940"}],"version-history":[{"count":4,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts\/2940\/revisions"}],"predecessor-version":[{"id":2946,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts\/2940\/revisions\/2946"}],"wp:attachment":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/media?parent=2940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/categories?post=2940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/tags?post=2940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}