none
Client getting an IP lease on the 64-bit LiteTouch boot image, but not the 32-bit version. RRS feed

  • Question

  • MDT 2012 U1.  No problem with PXE booting so WDS is not the issue.

    The NIC in question is the Intel I217-LM, which resides on both the new Dell Optiplex 9020 and the Latitude E7440.  I downloaded the Dell drivers and then the Intel drivers and imported them into the WindowsPE drivers folder in the workbench.  Updated the boot images to make sure the new drivers were injected.  Both yielded the same result.  I can do everything I need to do when booting to the 64-bit LiteTouchPE_x64.wim boot image,  but not the 32-bit version.  When booting to the 32-bit version, I get no IP configuration info at all.  

    When looking at the drivers in MDT, I see only one difference:  the supported OS versions.  The 64-bit driver supports 6.1, 6.1.1, and 6.2.  The 32-bit driver supports only 6.1.1 and 6.2.  Not sure if that's the issue.

    Tried using drvload within 32-bit WinPE to manually inject the NIC driver.  Still no luck.  Ipconfig yields no configuration at all.

    If I can't get these machines to boot to the 32-bit boot images, I can't deploy 32-bit images, unless there's a way of which I'm unaware.

    EDIT:  A little extra background.  My WindowsPE folder has two subfolders called x86 and x64.  Obviously, 32-bit drivers go into the x86 folder and 64-bit drivers go into the x64 folder.  Then in the properties of the deployment share a selection profile is selected which points to the architecture-specific folders.


    • Edited by Atreus21 Monday, October 28, 2013 4:49 PM
    Monday, October 28, 2013 4:33 PM

Answers

All replies

  • Every time I've seen this it's because of a driver issue. Have you tried pulling the latest driver from Intel's site instead of Dell's? Every few months I find I have to go to Intel instead of Dell for drivers.

    -Nick O.

    • Proposed as answer by Brian Gonzalez Monday, October 28, 2013 5:58 PM
    • Unproposed as answer by Atreus21 Monday, October 28, 2013 6:55 PM
    Monday, October 28, 2013 5:04 PM
  • Every time I've seen this it's because of a driver issue. Have you tried pulling the latest driver from Intel's site instead of Dell's? Every few months I find I have to go to Intel instead of Dell for drivers.

    -Nick O.

    Nick is on target.. Here is a link to jump to the latest intel driver download page for WinPE 4x

    Intel LAN v18.7

    /Brian G


    -BrianG (http://supportishere.com)

    Monday, October 28, 2013 6:00 PM
  • This is PE 3.0.  I will try the link.
    Monday, October 28, 2013 6:34 PM
  • Specifically what do you see when you are in WinPE, press the F8 button, and run ipconfig.

    1. ipconfig shows no network adapters (see: http://myitforum.com/cs2/blogs/rpedersen/clip_image002_53DA17D4.jpg ). This means you still have not loaded the correct device drivers, check the c:\windows\system32\wpeinit.log file.

    2. ipconfig shows an "autoconfiguration IPv4 Address" with a netmastk of 255.255.0.0. This means that the client did not get an IP address from the DHCP server. Double check the connection between the client and the DHCP server.

    3. ipconfig shows a correct address. There is no problem. :^)


    Keith Garner - keithga.wordpress.com

    Monday, October 28, 2013 6:41 PM
    Moderator
  • Same result.

    Extracted the contents of the PROWin32.exe file from the Intel site linked.  Imported them into the x86 folder of the the WinPE folder and updated the boot images.  PXE booted to the 32-bit boot image.  No luck; still not getting any IP information.

    Are there any logs anywhere that might be consulted?

    Monday, October 28, 2013 6:54 PM
  • I refer the right honorable gentleman to the reply I gave some moments ago.

    Keith Garner - keithga.wordpress.com

    Monday, October 28, 2013 6:55 PM
    Moderator
  • Specifically what do you see when you are in WinPE, press the F8 button, and run ipconfig.

    1. ipconfig shows no network adapters (see: http://myitforum.com/cs2/blogs/rpedersen/clip_image002_53DA17D4.jpg ). This means you still have not loaded the correct device drivers, check the c:\windows\system32\wpeinit.log file.

    2. ipconfig shows an "autoconfiguration IPv4 Address" with a netmastk of 255.255.0.0. This means that the client did not get an IP address from the DHCP server. Double check the connection between the client and the DHCP server.

    3. ipconfig shows a correct address. There is no problem. :^)


    Keith Garner - keithga.wordpress.com

    I get the first result.  Absolutely no network adapters, which I assumed indicated no appropriate device driver.

    This is the result of the wpeinit.log from the machine booting to the 32-bit boot image:

    Info      WPEINIT is processing the unattend file [X:\unattend.xml]
    Info      Spent 1747ms initializing removable media before unattend search
    Info      ==== Initializing Display Settings ====
    Info      Setting display resolution 1024x768x32@60: 0x00000000
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Initializing Computer Name ====
    Info      Generating a random computer name
    Info      No computer name specified, generating a random name.
    Info      Renaming computer to MININT-TFRU2BT.
    Info      Acquired profiling mutex
    Info      Service winmgmt disable: 0x00000000
    Info      Service winmgmt stop: 0x00000000
    Info      Service winmgmt enable: 0x00000000
    Info      Released profiling mutex
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Initializing Virtual Memory Paging File ====
    Info      No WinPE page file setting specified
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Initializing Optional Components ====
    Info      WinPE optional component 'Microsoft-WinPE-HTA' is present
    Info      WinPE optional component 'Microsoft-WinPE-MDAC' is present
    Info      WinPE optional component 'Microsoft-WinPE-WMI' is present
    Info      WinPE optional component 'Microsoft-WinPE-WSH' is present
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Initializing Network Access and Applying Configuration ====
    Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
    Info      Acquired profiling mutex
    Info      Install MS_MSCLIENT: 0x0004a020
    Info      Install MS_NETBIOS: 0x0004a020
    Info      Install MS_SMB: 0x0004a020
    Info      Install MS_TCPIP6: 0x0004a020
    Info      Install MS_TCPIP: 0x0004a020
    Info      Service dhcp start: 0x00000000
    Info      Service lmhosts start: 0x00000000
    Info      Service ikeext start: 0x00000000
    Info      Service mpssvc start: 0x00000000
    Info      Released profiling mutex
    Info      Spent 749ms installing network components
    Info      Spent 1669ms installing network drivers
    Error     QueryAdapterStatus: no adapters found.
    Info      Spent 0ms confirming network initialization; status 0x80004005
    Info      WaitForNetworkToInitialize failed; ignoring error
    Info      STATUS: SUCCESS (0x003d0001)
    Info      ==== Applying Firewall Settings ====
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Executing Synchronous User-Provided Commands ====
    Info      Parsing RunSynchronousCommand: 1 entries
    Info        Command 0: 0x00000000
    Info      Successfully executed command 'wscript.exe X:\Deploy\Scripts\LiteTouch.wsf' (exit code 0x00000000)
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Executing Asynchronous User-Provided Commands ====
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Applying Shutdown Settings ====
    Info      No shutdown setting was specified
    Info      STATUS: SUCCESS (0x00000001)

    At first I thought the first bolded section might be relevant, but when I booted to the x64 boot image, which works fine, I get the same message in its wpeinit.log file.  The only difference between the two log files is that the x64 boot image actually shows successful installation of a driver where the second bolded section is.

    Monday, October 28, 2013 7:13 PM
  • Upgrading to MDT 2013 resolved this problem.
    • Marked as answer by Atreus21 Monday, October 27, 2014 6:24 PM
    Monday, October 27, 2014 6:24 PM