Creating a Windows PE 3.0 Disk with Networking Support.

Creating a Windows PE 3.0 Disk with Networking Support.

This article provides the information on "Creating a Windows PE image with networking support on Dell systems: Updated for Windows Deployment Services using PE 3.0".

How do I create a Windows PE 3.0 Disk for Dell systems?

Hardware needed:

Two systems

  • One Host system
  • One Target system (Suggested target platform of imaging, i.e. Latitude E6510)

Software needed:

  • Windows XP / Vista
  • Windows Automated Installation Kit for Windows 7
  • Daemon Tools Lite (for mounting the WinAIK.ISO) (optional, saves the need to burn a CD for AIK setup)
  • ISO / CD Burning Program (Active ISO or Deep Burner)
  • GHOST32 11.0 or above

Creating a Windows PE 3.0 Disk with Networking Support

  1. On Host system: Download and install Daemon Tools Lite: (after a reboot you will see a lightning bolt Icon in the task tray)

  1. Download Microsoft Windows AIK for Windows 7 (KB3AIK_EN.iso Version: 1 Date Published: 8/6/2009 Language:English Download Size: 1706.6 MB)
  2. Mount KB3AIK_EN.iso image by right clicking on the lightning bolt and choosing Virtual CD, Device 0:

  1. Run STARTCD.EXE (on the E: drive)

NOTE: If you want to extract the files from the driver packages, you can rename the .exe to .zip extension or use a program like Winzip. Otherwise you can run the driver package, allow it to extract the files, and then cancel the setup program that executes.
  1. Run MSXML 6.0 SP1 Setup
  2. Run .NET setup (if you receive an error about .NET versions, .NET is probably already installed and this message can be ignored)
  3. Run Windows AIK Setup
  4. Download the appropriate NIC drivers for your platform(s):
    • (Intel E1K for the Latitude E4310, 6410, 6510, etc..) systems:
    • (Intel E1Y for the Latitude E4300, 6400, 6500, OptiPlex 755, 760, 780, etc..) systems:
    • (Broadcom B57 for the Latitude D620, D630, D830, etc…) systems: :
    • (Broadcom K57 for the Latitude E5400, OptiPlex 380, PWS T7500, etc..) systems:
  5. Start, Run, Microsoft Windows AIK, Windows PE Tools Command Prompt

NOTE: Ghost32 may hang or perform slowly if IRRT is enabled; it may be faster to place the system in ATA or AHCI mode prior to booting Windows PE (be sure to put the SATA setting back to the original state).

  1. Create the Windows PE environment
    • Copype.cmd x86 c:\petemp\x86pe
  2. Mount the Windows PE image (winpe.wim)
    • Imagex /mountrw c:\petemp\x86pe\winpe.wim 1 c:\petemp\x86pe\mount
  3. Add the Windows 7 32‐bit drivers for your appropriate platform to the Windows PE environment:
    • Intel E1K (Extract INTEL_825XX-GIGABIT-PLATFORM_A06_R290983.exe files to C:\Dell\Drivers\R290983)
      • Dism /image:c:\dc\petemp\mount /add‐driver /driver:c:\dell\drivers\R290983\win7‐ 32\e1k6232.inf
    • Intel E1Y (Extract INTEL_825XX‐GIGABIT‐PLATFORM_A01_R235484.exe files to C:\Dell\Drivers\R235484)
      • Dism /image:c:\dc\petemp\mount /add‐driver /driver:c:\dell\drivers\R235484\win7‐ 32\e1y6232.inf
    • Broadcom B57 (Extract R239862.exe files to C:\Dell\Drivers\R239862)
      • Dism /image:c:\dc\petemp\mount /add‐driver /driver:c:\dell\drivers\ R239862\win7~1\b57nd60x.inf
    • Broadcom K57 (Extract R239862.exe files to C:\Dell\Drivers\R239862)
      • Dism /image:c:\dc\petemp\mount /add‐driver /driver:c:\dell\drivers\ R239862\win7~1\k57nd60x.inf
  4. Edit the Startnet.cmd file (located at c:\dc\petemp\x86pe\mount\Windows\System32) to add desired commands that execute when the Windows PE environment loads (make sure to keep wpeinit as the first command)
  5. Copy Ghost32.exe (and any other desired files) to C:\dc\petemp\x86pe\mount\Windows\System32
  6. Unmount the Windows PE image (use /commit to keep changes to the winpe.wim)
    • Dism /unmount‐wim /mountdir:c:\dc\petemp\mount /commit
  7. Replace the WIM to C:\dc\f1_winpe.wim in Windows Deployment Services

Article ID: SLN70877

Last Date Modified: 04/04/2016 08:53 AM

Rate this article

Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.