Incorporating Sun Blade X6250 Server Module Drivers Into WIM or RIS Images

C H A P T E R 9

This chapter is intended for advanced system administrators who need to incorporate the server-specific drivers into a Windows Imaging Format (WIM) image or a Remote Installation Service (RIS) image.

WIM files are installed using Windows Deployment Services (WDS). RIS images can be deployed using either WDS in legacy mode or RIS.

This chapter is not a tutorial on WDS or RIS; it provides guidance on how to incorporate the server-specific drivers into a WIM or RIS image.

Determine Required Drivers

Add Drivers to a WIM Image

Adding Drivers to a RIS Image

Determine Required Drivers

The server-specific drivers that must be incorporated into a WIM or RIS image are shown in TABLE 9-1.

TABLE 9-1 Server-specific Drivers Required for WIM or RIS Images
Driver/Device	Incorporate for Windows Server 2003		Incorporate for Windows Server 2008
Driver/Device	32-bit	64-bit	32-bit	64-bit
Intel Pro/1000 EB Network with I/O Acceleration	Yes	Yes	No	No
Intel(R) 631xESB/6321ESB Chipset drivers	Yes	Yes	No	No
Aspeed Graphics Driver	Yes	Yes	Yes	Yes
Sun Blade RAID 5 Expansion Module (Adaptec-based) driver	Yes	Yes	Yes	Yes

Add Drivers to a WIM Image

For remote installation of Windows Server 2008 using a server running Windows Deployment Services, the mass storage controller drivers provided with Windows Server 2008 are sufficient to install the operating system.

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 are running on a Windows Server. Read the Windows Deployment Services snap-in documentation.

Locate DriverPack.zip for Windows Server 2008, see Downloading Server-Specific Driver Packages.

To Add Drivers to the WIM Image

1. Extract the contents of Windows Server 2008 DriverPack.zip to a network share (for example: \\yourshare\share\DriverPack), making sure to maintain the directory structure.

2. Select the service image to update and export the image.

a. Click Start, click Administrative Tools, and then click Windows Deployment Services.

b. Find the image to service. Right-click the image and then click Disable.

c. Right-click the image and click Export Image. Follow the Wizard directions to export the image to the location of your choice.

3. 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

4. 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.

5. Add the Microsoft-Windows-PnpCustomizationsNonWinPE component to your answer file in the offlineServicing pass.

6. 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.

7. 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>

8. 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\amd64</Path>
               <Credentials>
                  <Domain>MyDomain</Domain>
                  <Username>MyUserName</Username>
                  <Password>MyPassword</Password>
               </Credentials>
            </PathAndCredentials>
         </DriverPaths>
      </component>
   </settings>
</unattend>

9. 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 more information about using Package Manager, see the Microsoft Windows AIK documentation. 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\.

10. 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.

11. Unmount the .wim file and commit the changes. For example:

imagex /unmount /commit C:\wim_mount

12. Replace the service image and Enable the image.

a. If the Windows Deployment Services snap-in is not running, click Start, click Administrative Tools, and then click Windows Deployment Services.

b. 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.

c. 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.

Adding Drivers to a RIS Image

For remote installation of Windows Server 2003 using a server running Windows Remote Installation Services, the mass storage controller driver must be incorporated for the operating system to be installed. You must update the RIS image with the mass storage controller driver available with DriverPack.zip.

Before you Begin

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

Windows Remote Installation Services must be are running on a Windows Server. Read Microsoft’s Windows Remote Installation Services documentation for more information.

Locate DriverPack.zip for Windows Server 2003. For more information, see Downloading Server-Specific Driver Packages.

To Add Drivers to a RIS Image

In the following procedure, %RIS_Image% refers to the root of your Windows image on the RIS server.

1. Create the following directories in RIS_Image (root of your Windows image on the RIS server.):

$OEM$\textmode

$OEM$\$1\Sun\Drivers

2. Extract the contents of DriverPack.zip to a temporary location, making sure to maintain the directory structure.

3. Update the RIS_Image with the platform-specific drivers:

For 32-bit, copy the contents of the DriverPack\32-bit folder to the %RIS_Image%\$OEM$\$1\Sun\Drivers folder, making sure to maintain the directory structure.

For 64-bit, copy the contents of the DriverPack\64-bit folder to the %RIS_Image%\$OEM$\$1\Sun\Drivers folder, making sure to maintain the directory structure.

4. Copy the following files, depending on your installed mass storage solution:

If you are using the Adaptec-based Sun Blade RAID 5 Expansion Module, copy the contents of the %RIS_Image%\$OEM$\$1\Sun\Drivers\adaptec folder to the %RIS_Image%\$OEM$\textmode folder.

After copying the contents, you can delete the %RIS_Image%\$OEM$\$1\Sun\Drivers\adaptec folder.

5. Copy the contents of the %RIS_Image%\$OEM$\$1\Sun\Drivers\RIS folder to the %RIS_Image%\$OEM$\textmode folder.

6. Copy all the files from the %RIS_Image%\$OEM$\$1\Sun\Drivers\intel\RIS to the %RIS_Image%\$OEM$\textmode folder.

After copying the contents, you can delete the %RIS_Image%\$OEM$\$1\Sun\Drivers\intel\RIS folder.

7. Create an answer file using the method described in the Microsoft TechNet article "Creating an Answer File with Setup Manager". The article can be found at:

http://technet2.microsoft.com/WindowsServer/en/library/78421630-6fcc-4604-a888-bd9c84244a5b1033.mspx

8. Make changes to the .sif file for your mass storage solution as listed in one of the following tables, then proceed to Step 9:

For servers with the Sun Blade RAID 5 Expansion Module (Adaptec-based) see TABLE 9-2.

Note - For readability, the OemPnpDriversPath information has been shown on multiple lines. The information must be entered on a single line.

TABLE 9-2 Sun Blade X6250 Server Module `.sif` File Entries for Sun Blade RAID 5 Expansion Module
Windows Server 32-bit	Windows Server 64-bit
`[Unattended] OemPreinstall = yes OemPnpDriversPath=“\Sun\Drivers\intel\chipset;\Sun\Drivers\intel\nic;\Sun\Drivers\adaptec;\Sun\Drivers\ast” [MassStorageDrivers] "Adaptec SAS/SATA-II RAID Controller (32-bit)" = OEM [OEMBootFiles] adpenc.cat adpenc.inf arc.cat arc.inf arc.sys arcsas.cat arcsas.inf arcsas.sys ramdisk1 txtsetup.oem`	`[Unattended] OemPreinstall = yes OemPnpDriversPath=“\Sun\Drivers\intel\chipset;\Sun\Drivers\intel\nic;\Sun\Drivers\adaptec;\Sun\Drivers\ast” [MassStorageDrivers] "Adaptec SAS/SATA-II RAID Controller (64-bit)" = OEM [OEMBootFiles] adpenc.cat adpenc.inf arc.cat arc.inf arc.sys arcsas.cat arcsas.inf arcsas.sys ramdisk1 txtsetup.oem`

9. Stop and start the Remote Installation Service (BINLSVC) on the RIS server.

To do this, type the following commands at the command prompt and press Enter after each command:

net stop binlsvc

net start binlsvc