Incorporating Sun Fire Drivers Into a RIS Image

C H A P T E R 9

This chapter is intended for advanced system administrators who need to incorporate the Sun Fire X4600 server driver package into a Remote Installation Service (RIS) image.

This chapter is not a tutorial on RIS; it provides guidance on how to incorporate the Sun Fire X4600 server-specific drivers into a RIS image.

Determine Required Drivers

Add Drivers to the RIS Image

Determine Required Drivers

The server-specific drivers that must be incorporated into a RIS image are shown in TABLE 9-1 for Sun Fire X4600 server.

TABLE 9-1 Server-specific Drivers Required for Sun Fire X4600 Server RIS
Device	Required for 32-bit Windows Server 2003	Required for 64-bit Windows Server 2003
AMD-8132 HyperTransport IOAPIC Controller	Yes	Yes
AMD K8 Processor	Yes	Yes
AMI Virtual Floppy	Yes	Yes
LSI 1064 HBA	Yes	Yes
NVIDIA nForce PCI System Management	Yes	Yes
NVIDIA nForce4 HyperTransport Bridge	Yes	Yes
NVIDIA nForce4 Low Pin Count Controller	Yes	No

Add Drivers to the RIS Image

In the following procedure, RemoteInstall\Setup\Language\Images\Dir_name\Arch refers to the image located on the RIS server where the drivers will be added.

Language is the language of the installed operating system (English, for example)

Dir_name is the directory where the RIS image installed.

Arch is either i386 or amd64 for the 32-bit or 64-bit images respectively.

The following procedure describes a method of incorporating the drivers into a RIS image.

1. At the same level as the RemoteInstall\Setup\Language\Images\Dir_name\Arch folder on the RIS image, create a $OEM$ folder.

2. In the $OEM$ folder, create a Sun\Drivers folder.

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

4. Depending on the architecture (Arch) of your RIS image, copy the contents of the 32-bit or the 64-bit folder from the temporary location to the $OEM$\Sun\Drivers folder in the RIS image.

For i386 use the 32-bit folder, for amd64 use the 64-bit folder.

5. Copy the $OEM$\Sun\Drivers\lsi\lsi_sas.sys file to the
RemoteInstall\Setup\Language\Images\Dir_name\Arch folder.

6. Add the following text into the RemoteInstall\Setup\Language\Images\Dir_name\Arch\txtsetup.sif file, at the end of the visible text.

[SourceDisksFiles] lsi_sas.sys = 1,,,,,,3_,4,1 HardwareIdsDatabase] PCI\VEN_1000&DEV_0050 = "lsi_sas" PCI\VEN_1000&DEV_0054 = "lsi_sas" PCI\VEN_1000&DEV_005E = "lsi_sas" [SCSI.load] lsi_sas = lsi_sas.sys,4 [SCSI] lsi_sas = "LSI Logic Fusion-MPT SAS Driver (Server 2003 32-bit)"

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 the following changes to the .sif file that is used for installation.

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

TABLE 9-2 Sun Fire X4600 Server .sif File Changes
32-bit	64-bit
`[Unattended] OemPreinstall = yes OemPnpDriversPath=“\Sun\Drivers\amd\8132\ioapic;\Sun\Drivers\ami;\Sun\Drivers\lsi;\Sun\Drivers\nvidia\smbus`	`[Unattended] OemPreinstall = yes OemPnpDriversPath=“\Sun\Drivers\amd\8132\ioapic;\Sun\Drivers\amd\cpu;\Sun\Drivers\ami;\Sun\Drivers\lsi;\Sun\Drivers\nvidia\smbus`

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