Sun Microsystems X6275 manual Appendix a Incorporate Sun Blade Server Drivers Into WIM

Page 35

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.

Appendix A Incorporate Sun Blade Server Drivers Into WIM

27

Image 35
Contents Sun Microsystems, Inc Page Contents Index Post InstallationIncorporate Sun Blade Server Drivers Into WIM Related Documentation Product UpdatesHtml Sun Welcomes Your Comments Documentation, Support, and TrainingPage Overview What to Do Next PrerequisitesThings You Must Decide Select the DVD drive or the ISO file Using a Remote Control Application RkvmTo Mount a DVD or Equivalent ISO Image Dongle Cable Connections To Connect the Dongle for a Local InstallationFigure Legend Page Installing Windows Server Operating System 1Task Map for the Windows 2008 Installation Task Map for the Windows Server 2008 InstallationReset or power on the server. For example Installing Windows Server 2008 Using Local or Remote MediaTo Install Windows Server 2008 Using Local or Remote Media Boot Device dialog appears Installation Type dialog, click Custom advanced Where do you want to Install Windows dialog appears Proceed to Post Installation on Before You Begin Installing Windows Server 2008 Using a PXE NetworkReset or power on the server, for example To Install Windows Server 2008 Using PXEBoot Agent dialog appears Post Installation To Download the Server-Specific Drivers Downloading Server-Specific DriversInstalling Server-Specific Device Drivers To Install the Server-Specific Device Drivers Post Installation Do one of the following Installing Supplemental SoftwareInstall the Supplemental Software Perform one of the followingPost Installation Page Before you Begin Incorporate Sun Blade Server Drivers Into WIMAdding Drivers to a WIM Image PathAndCredentials To Add Drivers to the WIM ImageAppendix a Incorporate Sun Blade Server Drivers Into WIM Page Index