Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Active System Manager Release 8.1.1 Installation Guide

PDF

Creating WinPE Image and Updating Install Media for Windows 2008 R2, Windows 2012 and Windows 2012 R2

You should have Windows Assessment and Deployment toolkit that contains the Windows PE environment used to automate the Windows installer installed in the DEFAULT location on a Windows machine. Licensing for Windows PE requires that you build your own customized WinPE WIM image containing the required scripts.

To create customized Windows.iso image for Windows 2008 R2, Windows 2012 and Windows 2012 R2:

  1. Create a build folder on your ADK machine. For example, ADK machine build directory may be “c:\buildpe”.
  2. Within this build folder create a directory called “Drivers”.
    • NOTE:

      • If any additional drivers are required, add the drivers under the “Drivers” folder in the build directory you created on your ADK machine. The drivers are installed into the Windows image, if applicable. The drivers that do not apply to the OS being processed are ignored.

      • If you want deploy Windows to VMWare VMs, the WinPE drivers for the VMXNET3 virtual network adapter from VMWare required. To obtain the VMware Windows drivers: Install VMware tools on a running Windows 2012 or Windows 2012 R2 and on the virtual machine. Go to the C:\Program Files\Common Files\VMware\Drivers directory. Copy the contents in the Drivers folder to the directory that contains your WinPE build scripts.

      • If you deploy Windows 2012 or 2012 R2 to an M420 server, drivers for Broadcom network adapters must be added to the image, as they are not included in Windows. Obtain a copy of the Broadcom Drivers for an m420 server from dell.com and install the driver package on a Windows 2012 or 2012 R2 machine. Locate the Windows drivers on the files system and copy them to the “Drivers” folder. These drivers typically start with "b57".

      • Native driver support for Dell server components in Windows 2008 R2 is limited, so obtain the latest NIC and RAID drivers for Windows 2008 R2 from Dell.com

  3. Log in to the ASM virtual appliance and obtain the script “build-razor-winpe.ps1” from the /opt/razor-server/build-winpe directory and copy this to the build directory created in step 1 on your machine with ADK 8.1.1 or 8.1.1 installed in the default location.
  4. The build-razor-winpe script supports and ASM appliance that uses an external DHCP/PXE server, or using the ASM appliance as your DHCP PXE server. This command to run this script has the following structure: 
    powershell -executionpolicy bypass -file build-razor-winpe.ps1 [ASM appliance IP or “DHCP”] [Your Windows .iso name] [New
                                    Windows .iso name]
    If ASM does not act as the DHCP/PXE server, that is your DHCP/PXE server is external, you will run the script and provide the ASM appliance IP as input. For example, 
    powershell  winpe.ps1 192.168.1.1 Windows2012r2.iso ASMWindows2012r2.iso
    If ASM acts as the DHCP/PXE server you will run the script and provide the input “DHCP” instead of the ASM appliance IP. For example: 
    powershell winpe.ps1 DHCP Windows2012r2.iso ASMWindows2012r2.iso
    • NOTE: This step takes some time to complete. After completion, it creates a new Windows .iso file which is customized for using with ASM. You must go to repositories and upload .iso file.
    • NOTE: If the build script fails or is stopped during execution it may be necessary to clean up files in the build directory before executing again. In some cases, directories may still be mounted and require cleanup. To clean up, delete all files other than the necessary script, starting .iso, and Drivers folder. If any files cannot be deleted, try executing the following commands from a command prompt in the build folder location: C:\buildpe>dism /cleanup-wim

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\