Incorporate Sun Fire Server Drivers Into WIM or RIS Images

A P P E N D I X A

This appendix 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 Services (RIS) image.

WIM files are installed using Windows Deployment Services (WDS). RIS images can be deployed using either WDS in legacy mode or RIS. For more information on WDS or RIS, refer to Microsoft documentation.

This appendix includes the following sections:

Determine Required Drivers

Add Drivers to a WIM Image

Add 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 A-1.

TABLE A-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 Network Drivers	Yes	Yes	Yes	Yes
Intel Chipset Drivers	Yes	Yes	No	No
Aspeed Graphic Driver	Yes	Yes	Yes	Yes
Infineon TPM Driver ^[1]	Yes	Yes	No	No
Disk Controller Driver (server dependant): LSI SAS RAID HBA, SG-PCIE8SAS-I (also referred to as LSI-based integrated RAID controller) --or-- Sun StorageTek SAS RAID HBA, SG-XPCIESAS-R (also referred to as Adaptec-based integrated RAID controller) --or-- Intel ICH10 Controller (also referred to as Intel-based integrated disk controller)	Yes	Yes	Yes	Yes

Add Drivers to a WIM Image

For Windows Server 2003, the LSI and Adaptec RAID controller and Intel disk controller drivers must be incorporated for the operating system to be installed. For Windows Server 2008, the LSI and Adaptec RAID controller and Intel disk controller drivers are sufficient to install the system. Sun recommends updating both RAID controller drivers to enable the full functionality of host control of the firmware RAID functionality.

The procedures in the section assume the Windows Deployment Services are running on Windows Server 2003.

Before you Begin

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

Locate DriverPack_x_x_x.zip. You can obtain the DriverPack_x_x_x.zip from the Tools and Drivers CD/DVD or you can download it from the Sun download site. For download instructions, see Downloading Server-Specific Drivers.

Add Drivers to the WIM Image

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

Note - Due to potential driver interaction problems during the installation, after you extract the DriverPack_x_x_x.zip, if you are NOT installing to the Intel ICH10 Controller, you must delete the i386\Intel\hba and amd64\Intel\hba directories.

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 select 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) 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 (AIK) 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 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.

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. Locate the image to service. Right-click the image and select 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 select Enable.

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

Add 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 provided with Windows Server 2003 is not sufficient to install the operating system. Sun recommends updating the RIS image with the mass-storage driver available with DriverPack_x_x_x.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. Refer to the Windows Remote Installation Services documentation for more information.

Locate DriverPack_x_x_x.zip for Windows Server 2003.

You can obtain the DriverPack_x_x_x.zip from the Tools and Drivers CD/DVD or you can download it from the Sun download site. For download instructions, see Downloading Server-Specific Drivers.

Add Drivers to a RIS image

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

1. Create the following directories in %RIS_Image%:

$OEM$\textmode

$OEM$\$$OEMDIR

$OEM$\$1\Sun\Drivers

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

3. Update the %RIS_Image% with the server-specific drivers for your Windows platform:

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

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

4. Update the %RIS_Image%\$OEM$\textmode folder with the mass-storage drivers using one of the following methods:

Method 1:

a. Using the Tools and Drivers CD/DVD, create a Windows 2003 Mass Storage Driver Diskette for Intel ICH10/LSI/SMI using the MKFLOPPY Utility as described in Create Floppy Disk For Device Drivers.

b. Copy the contents of the floppy to the %RIS_Image%\$OEM$\textmode folder.

Method 2:

a. Copy the appropriate floppypack folder on the Tools and Drivers CD/DVD to the %RIS_Image%\$OEM$\textmode folder.

For LSI: \windows\w2k3\packages\ﬂoppypack\ﬁles\LSI

For Sun StorageTek (Adaptec): \windows\w2k3\packages\ﬂoppypack\ﬁles\SMI

For Intel ICH10: \windows\w2k3\packages\ﬂoppypack\ﬁles\intel

5. Copy the contents of the appropriate mass-storage driver directory to the root directory of the textmode directory

For LSI:

If you are installing Windows 2003 32-bit to the LSI controller, copy the contents of %RIS_Image%\$OEM$\textmode\LSI\i386 to %RIS_Image%\$OEM$\textmode.

If you are installing Windows 2003 64-bit to the LSI controller, copy the contents of %RIS_Image%\$OEM$\textmode\LSI\amd64 to %RIS_Image%\$OEM$\textmode.

For Sun StorageTek (Adaptec):

If you are installing Windows 2003 32-bit to the adaptec controller, copy the contents of %RIS_Image%\$OEM$\textmode\smi\i386 to %RIS_Image%\$OEM$\textmode.

If you are installing Windows 2003 64-bit to the adaptec controller, copy the contents of %RIS_Image%\$OEM$\textmode\smi\amd64 to %RIS_Image%\$OEM$\textmode.

For Intel ICH10:

If you are installing Windows 2003 32-bit to the ICH10 controller, copy the contents of %RIS_Image%\$OEM$\textmode\intel\i386 to %RIS_Image%\$OEM$\textmode.

If you are installing Windows 2003 64-bit to the ICH10 controller, copy the contents of %RIS_Image%\$OEM$\textmode\intel\amd64 to %RIS_Image%\$OEM$\textmode.

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

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

For servers with the LSI-based integrated RAID controller see TABLE A-2.

For servers with the Adaptec-based integrated RAID controller see TABLE A-3.

For servers with the Intel-based integrated disk controller see TABLE A-4.

Note - For readability, the OemPnpDriversPath information has been shown on multiple lines; it must be entered on a single line. The three drivers listed in MassStorageDrivers have been shown on multiple lines; each driver
(“driver description” = OEM) should be listed on a separate line. Due to potential driver interaction problems during installation, only include the Sun\Drivers\intel\hba path in the OemPnPDriversPath entry if you are installing to the Intel ICH10 controller. If you are installing to a Sun StorageTek (Adaptec) or LSI Raid Controller, install the Intel ICH10 driver manually after setup has completed. The driver will reside in the Sun\Drivers\intel\hba directory at the root of your installation disk.

TABLE A-2 .sif File Changes for Servers With an LSI-Based Integrated RAID Controller
Windows Server 2003 32-bit	Windows Server 2003 64-bit
`[Unattended]` `OemPreinstall = yes` `OemPnPDriversPath = "\Sun\Drivers\ast;\Sun\Drivers\emulex;\Sun\Drivers\qlogic;\Sun\Drivers\infineon;\Sun\Drivers\intel\chipset;\Sun\Drivers\intel\nic;\Sun\Drivers\ısi;\Sun\Drivers\smi"` `[MassStorageDrivers]` `"LSI Logic Fusion-MPT SAS Storport Driver (32-bit)" = OEM` `[OEMBootFiles]` `txtsetup.oem` `disk4.tag` `lsi_sas.inf` `lsi_sas.sys` `lsinodrv.inf` `s2k332.cat`	`[Unattended]` `OemPreinstall = yes` `OemPnPDriversPath = "\Sun\Drivers\ast;\Sun\Drivers\emulex;\Sun\Drivers\qlogic;\Sun\Drivers\infineon;\Sun\Drivers\intel\chipset;\Sun\Drivers\intel\nic;\Sun\Drivers\ısi;\Sun\Drivers\smi"` `[MassStorageDrivers]` `"LSI Logic Fusion-MPT SAS Storport Driver (64-bit)"= OEM` `[OEMBootFiles]` `txtsetup.oem` `disk4.tag` `lsi_sas.inf` `lsi_sas.sys` `lsinodrv.inf` `s2k3amd64.cat`

TABLE A-3 .sif File Changes for Servers With an Adaptec-Based Integrated RAID Controller
Windows Server 2003 32-bit	Windows Server 2003 64-bit
`[Unattended]` `OemPreinstall = yes` `OemPnPDriversPath = "\Sun\Drivers\ast;\Sun\Drivers\emulex;\Sun\Drivers\qlogic;\Sun\Drivers\infineon;\Sun\Drivers\intel\chipset;\Sun\Drivers\intel\nic;\Sun\Drivers\ısi;\Sun\Drivers\smi"` `[MassStorageDrivers]` `"Adaptec SAS/SATA-II RAID Controller Driver (32-bit)" = OEM` `[OEMBootFiles]` `txtsetup.oem` `disk4.tag` `adpenc.cat` `adpenc.sys` `arcsas.cat` `arcsas.sys` `arcsas.inf` `raiddisk1`	`[Unattended]` `OemPreinstall = yes` `OemPnPDriversPath = "\Sun\Drivers\ast;\Sun\Drivers\emulex;\Sun\Drivers\qlogic;\Sun\Drivers\infineon;\Sun\Drivers\intel\chipset;\Sun\Drivers\intel\nic;\Sun\Drivers\ısi;Sun\Drivers\smi"` `[MassStorageDrivers]` `"Adaptec SAS/SATA-II RAID Controller Driver (64-bit)"= OEM` `[OEMBootFiles]` `txtsetup.oem` `disk4.tag` `adpenc.cat` `adpenc.sys` `arcsas.cat` `arcsas.sys` `arcsas.inf` `raiddisk1`

TABLE A-4 .sif File Changes for Servers Intel-Based Integrated Disk Controller
Windows Server 2003 32-bit	Windows Server 2003 64-bit
`[Unattended]` `OemPreinstall = yes` `OemPnPDriversPath = "\Sun\Drivers\ast;\Sun\Drivers\emulex;\Sun\Drivers\qlogic;\Sun\Drivers\infineon;\Sun\Drivers\intel\chipset;\Sun\Drivers\intel\nic;Sun\Drivers\intel\hba;\Sun\Drivers\ısi;\Sun\Drivers\smi"` `[MassStorageDrivers]` `"Intel Matrix Storage Manager driver (32-bit)" = OEM` `[OEMBootFiles]` `txtsetup.oem` `disk4.tag` `iaAHCI.inf` `iaAHCI.sys` `iaStor.inf` `iaStor.sys` `iaStor.cat`	`[Unattended]` `OemPreinstall = yes` `OemPnPDriversPath = "\Sun\Drivers\ast;\Sun\Drivers\emulex;\Sun\Drivers\qlogic;\Sun\Drivers\infineon;\Sun\Drivers\intel\chipset;\Sun\Drivers\intel\nic;Sun\Drivers\intel\hba;\Sun\Drivers\ısi;\Sun\Drivers\smi"` `[MassStorageDrivers]` `"Intel Matrix Storage Manager driver (64-bit)"= OEM` `[OEMBootFiles]` `txtsetup.oem` `disk4.tag` `iaAHCI.inf` `iaAHCI.sys` `iaStor.inf` `iaStor.sys` `iaStor.cat`

8. Add the Intel Ethernet Drivers to your RIS image.

For the on board Intel 82575EB Gigabit Ethernet Devices, 32-bit:

i. Extract the inf file in the %RIS_Image%\$OEM$\$1\Sun\Drivers\intel\nic\RIS_INF\elq5132.zip to %RIS_Image%\i386.

ii. Copy the elq5132.sys file from %RIS_Image%\$OEM$\$1\Sun\Drivers\intel\nic to %RIS_Image%\i386.

For the on board Intel 82575EB Gigabit Ethernet Devices, 64-bit:

i. Extract the inf file in the %RIS_Image%\$OEM$\$1\Sun\Drivers\intel\nic\RIS_INF\elq51x64.zip to %RIS_Image%\amd64.

ii. Copy the elq51x64.sys file from %RIS_Image%\$OEM$\$1\Sun\Drivers\intel\nic to %RIS_Image%\amd64.

9. Stop and start the Remote Installation Services BINLSVC service 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

^{1 (TableFootnote) You have to configure the Trusted Platform Module (TPM) feature on the server before you can use it. For instructions on configuring TPM, see the Sun Fire X4170, X4270, and X4275 Servers Service Manual.}