Skip Navigation Links
Exit Print View
| Sun Fire X4640 Server Windows Installation Guide Sun Fire X4640 Server Documentation Library

Search Scope:

- This Document
- Entire Library

## How to Add Drivers to a WIM Image

Before You Begin

Before creating a WIM image, you need to do the following:

- The Windows Automated Installation Kit (Windows AIK or WAIK) must be installed. The kit can be downloaded from Microsoft. Sun recommends using version 2.0 or later of the WAIK.

- Read the Windows AIK documentation.

- Windows Remote Installation Services must be running on a Windows Server. Read the Windows Deployment Services snap-in documentation.

- Locate the `DriverPack.zip` and `OptPack.zip` files for Windows Server 2008 you downloaded as described in How to Download Server Software.

1. Extract the contents of the `DriverPack.zip` and `OptPack.zip` packages to a temporary folder.
2. Create a network share accessible to the WDS server to which the drivers will be copied. For example:

   \\yourshare\share\`DriverPack`

3. Create a folder structure under the `DriverPack` folder on the network share and copy over the specific 64–bit driver files from the downloaded packages. For example:

   Copy Contents of Package Folder | To Network Share Driver Folder
   --- | ---
   DriverPack\amd64\ami | Driverpack\amd64\ami
   DriverPack\amd64\ati | DriverPack\amd64\ati
   DriverPack\amd64\lsi | DriverPack\amd64\lsi

4. Select the service image to update and export the image.
   1. Click Start, click Administrative Tools, and then click Windows Deployment Services.
   2. Find the image to service. Right-click the image and then click Disable.
   3. Right-click the image and click Export Image. Follow the Wizard directions to export the image to the location of your choice.
5. Mount the Windows image you just exported. For example,

   `imagex /mountrw C:\windows_distribution\sources\install.wim 1 C:\win_mount`

   The first Windows image in the `Install.wim` file is mounted to `C:\wim_mount`

6. Use Windows System Image Manager (Windows SIM, available in Windows AIK) to create an answer file that contains the paths to the device drivers that you intend to install.

   See the Microsoft documentation for the Windows Automated Installation Kit for the details of starting the Windows SIM application.

7. Add the `Microsoft-Windows-PnpCustomizationsNonWinPE` component to your answer file in the `offlineServicing` pass.
8. Expand the `Microsoft-Windows-PnpCustomizationsNonWinPE` node in the answer file. Right-click `DevicePaths`, and then select Insert New PathAndCredentials.

   A new PathAndCredentials list item appears.

9. In the `Microsoft-Windows-PnpCustomizationsNonWinPE` component, specify the path to the architecture folder in the DriverPack folder on the network share and the credentials used to access the network share.

   For example, the path and credentials for a 64-bit image might be:

       <Path>\\yourshare\share\DriverPack\amd64</Path>
       <Credentials>
          <Domain>MyDomain</Domain>
          <Username>MyUserName</Username>
          <Password>MyPassword</Password>
       </Credentials>

10. Save the answer file and exit Windows SIM. The answer file must be similar to the following sample. The sample assumes the architecture is 64-bit.

        <?xml version="1.0" ?>
        <unattend xmlns="urn:schemas-microsoft-com:asm.v3" xmlns:wcm=
        "http://schemas.microsoft.com/WMIConfig/2002/State">
           <settings pass="offlineServicing">
              <component name="Microsoft-Windows-PnpCustomizationsNonWinPE"
        processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35"
        language="neutral" versionScope="nonSxS">
                 <DriverPaths>
                    <PathAndCredentials wcm:keyValue="1">
                       <Path>\\yourshare\share\DriverPack\x64</Path>
                       <Credentials>
                          <Domain>MyDomain</Domain>
                          <Username>MyUserName</Username>
                          <Password>MyPassword</Password>
                       </Credentials>
                    </PathAndCredentials>
                 </DriverPaths>
              </component>
           </settings>
        </unattend>

11. Use Package Manager to apply the unattended installation answer file to the mounted Windows image. Specify a location for the log file to create. For example,

    `pkgmgr /o:"C:\wim_mount\;C:\wim_mount\Windows" /n:"C:\unattend.xml" /l:"C:\pkgmgrlogs\logfile.txt"`

    The `.inf` files referenced in the path in the answer file are added to the Windows image. A log file is created in the directory `C:\Pkgmgrlogs\`.

    For more information about using Package Manager, see the Microsoft Windows AIK documentation.

12. Review the contents of the `%WINDIR%\Inf\` directory in the mounted Windows image to ensure that the `.inf` files were installed.

    Drivers added to the Windows image are named `oem*.inf`. This is to ensure unique naming for new drivers added to the computer. For example, the files `MyDriver1.inf` and `MyDriver2.inf` are renamed `oem0.inf` and `oem1.inf`.

13. Unmount the `.wim` file and commit the changes. For example:

    `imagex /unmount /commit C:\wim_mount`

14. Replace the service image and enable the image.
    1. If the Windows Deployment Services snap-in is not running, click Start, click Administrative Tools, and then click Windows Deployment Services.
    2. Find the image to service. Right-click the image and then click Replace Image. Follow the Wizard directions to replace the service image with the Windows image that was updated.
    3. Right-click the service image and then click Enable.

       The service image is now available and all the server-specific drivers are added to the image.

Next Steps

To deploy your image, proceed to How to Deploy a WIM Image to Your Server.

Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |