|C H A P T E R 9|
Incorporate Sun Fire Drivers Into WIM or RIS Images
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.
The server-specific drivers that must be incorporated into a WIM or RIS image are shown in TABLE 9-1.
Disk Controller Driver (server dependant):
For Windows Server 2003, the LSI and Adaptec RAID controller and NVIDIA disk controller drivers must be incorporated for the operating system to be installed. For Windows Server 2008, the LSI and Adaptec RAID controller and NVIDIA 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 creating your WIM image, you need to do the following:
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 Path And Credentials.
A new Path And Credentials 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:
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.
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.zip.
Before creating a RIS image, you need to do the following:
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):
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 server-specific drivers for your Windows platform:
4. Update the %RIS_Image%\$OEM$\textmode folder with the mass storage drivers:
5. Copy the %RIS_Image%\$OEM$\$1\Sun\Drivers\nvidia\sata\idecoi.dll file to the %RIS_Image%\$OEM$\$$OEMDIR folder.
6. Copy the contents of the %RIS_Image%\$OEM$\$1\Sun\Drivers\RIS folder to the %RIS_Image%\$OEM$\textmode folder.
After copying the contents, you can delete the %RIS_Image%\%OEM$\$1\Sun\Drivers\RIS folder.
7. Copy all the files from the %RIS_Image%\$OEM$\$1\Sun\Drivers\nvidia\RIS to the %RIS_Image%\$OEM$\textmode folder.
After copying the files, you can delete the %RIS_Image%\$OEM$\$1\Sun\Drivers\nvidia\RIS folder.
8. 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:
9. Make changes to the .sif file for your mass storage solution as listed in one of the following tables, then proceed to Step 10:
|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.
10. 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
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.