Copying image files to a location for provisioning

You copy the WinPE 2.0 and later image files to a location so the provisioning process can use them. The location to which you copy files depends on the image type of the WinPE image you created (PXE, ISO, or UFD).

To copy image files of the PXE image type

1. Copy the image file to the TFTP server. Perform this step only if you created the image with the CreateWinPE2_x.vbs script. (If you created the image with the image creation wizard, the image creation process copies the image to the TFTP server.)

    Click here for more information on copying image files to the TFTP server.

   You copy the WinPE 2.0 and later boot image to the TFTP server so that the provisioning process can use it with the PXE provisioning technology.

   The "image file" is actually a directory containing several separate files. When you run CreateWinPE2_x.vbs, it creates this directory in the path specified by DestDir. This new directory has the name specified by BootDir and contains the image files.

   For example if you specified a BootDir name of_ boot_2_0 (the recommended name for the directory), the script creates the boot_2_0 image in DestDir:

   C:\BMC_BL\tmp\boot_2_0
   BCD
   boot.sdi
   WinPE.wim
   

   To copy boot image files to the TFTP server

   To place the image files on the TFTP server, copy BootDir and its contents to the tftproot directory on the TFTP server. For example:

   C:\tftproot\boot_2_0
   BCD
   boot.sdi
   WinPE.wim
   

   Note

   The BLAdmin role must be granted Read and Write access to the TFTP root directory and its contents, including boot image folders and all image files in the folders.

2. Extract the boot files and copy them to the TFTP server.

    Click here for more information on extracting boot files for WinPE 2.0 and later images.

   After creating the images with CreateWinPE2_x.vbs, you extract the pxeboot.0 and bootmgr.exe files and copy them to the TFTP server.

   To extract boot files

   1. Create a temporary local directory to store the files you are about to extract.
      For example: C:\BMC_BL\tmpboot
   2. Open a command window and change directories to the \Tools\PETools subdirectory of the Microsoft Windows Automated Installation Kit (WAIK) installation directory.
      For example: C:\Program Files\WinAIK\Tools\PETools
   3. Navigate to the provisioning files that you extracted from provision-files.zip into a temporary directory. In the \provisioning\winpe\ directory, locate the extractpxeboot.vbs script, and copy this file into the \Tools\PETools subdirectory.
   4. Start the WinPE command prompt by typing:
      pesetenv.cmd

   5. Run the extractpxeboot.vbs script to extract pxeboot.0 and bootmgr.exe. Use the following syntax:
      extractpxeboot <DestDir> <WAIK_dir>
      where <DestDir> is the temporary local storage directory that you created at the beginning of this procedure and <WAIK_dir> is the WAIK installation directory.

      Example

      extractpxeboot C:\BMC_BL\tmpboot C:\Program Files\WinAIK

      
      

   6. Look at the contents of C:\BMC_BL\tmpboot. You should see pxeboot.0 and bootmgr.exe.
      Copy these files to the following locations on the TFTP server:
      • Copy pxeboot.0 into <tftproot>\x86pc\pxelinux.
        For example: C:\tftproot\x86\pxelinux\pxeboot.0
      • Copy bootmgr.exe into <tftproot>.
        For example: C:\tftproot\bootmgr.exe

3. If the server that contains your data store does not support the NTLMv2 Level 3 setting for Microsoft NT Lan Manager, change the NTLM settings for the WinPE image on the TFTP server.

    Click here for more information on configuring WinPE security settings.

   If the server that contains your data store does not support the Microsoft NT Lan Manager (NTLM) settings for NTLMv2 Level 3, you must change the NTLM settings for the WinPE image on the TFTP server.

   Before you begin

   The TFTP server must have the Microsoft Windows Automated Installation Kit (WAIK) installed.

   To change the NTLM settings

   The ImageX command-line tool is deprecated in Windows 8. Use the DISM command-line tool.

    For more information, see the following articles:

   • Microsoft TechNet: What is DISM?
   • Microsoft TechNet: DISM - Deployment Image Servicing and Management Technical Reference for Windows).

    

   1. Use the imagex utility to mount the WinPE image to any empty directory. (The imagex utility comes with WAIK.)

      Example

      1. Create an empty directory, for example C:\new. Copy the WinPE image file WinPE.wim to this new directory.
      2. Create a mount directory under C:\new.
         For example: C:\new\mount
      3. Open a command window and change directories to the \Tools\PETools subdirectory of the Windows AIK installation directory.
         For example: C:\Program Files\WinAIK\Tools\PETools
      4. Start the WinPE command prompt by typing pesetenv.cmd.
      5. On the WinPE command line enter:
         imagex /mountrw C:\new\WinPE.wim 1 C:\new\mount
   2. Open the registry editor (regedit).
   3. Click HKEY_LOCAL_MACHINE.
   4. Choose File > Load Hive.
   5. Select the file:
      %Mounted WinPE Image folder in step1%\Windows\System32\config\SYSTEM
   6. Enter the following key name:
      WinPE_Image_SYSTEM
   7. Browse to: HKEY_LOCAL_MACHINE\WinPE_Image_SYSTEM\ControlSet001\Control\Lsa
   8. This step describes how to add an entry if the LMCompatibilityLevel value does not currently exist. If an LMCompatibilityLevel value already exists, you can edit the existing entry to match these values.
      Select Edit > New> DWORD Value, and then add the following registry values:
      Value Name: LMCompatibilityLevel
      Data Type: REG_DWORD
      Value: 3
      Valid Range: 0,3
   9. Click HKEY_LOCAL_MACHINE\WinPE_Image_SYSTEM.
   10. Choose File > Unload Hive.
   11. Use imagex to unmount the mounted WinPE image:
       imagex /unmount /commit MountFolder

To copy image files of the ISO image type

To copy image files of the UFD image type