About This Documentation (PDF and HTML)
Hardware Installation and Product Notes
Overview of the Sun Blade X6275 M2 Server Module
Installing and Powering On the Server Module
Overview of the Sun Blade X6275 M2 Server Module Product Notes
System Software Release Features
Hardware, Firmware, and BIOS Issues
Installing the Oracle Solaris Operating System
Installing Red Hat Enterprise Linux
Installing the SLES Operating System
Introduction to Oracle VM Installation
Creating a PXE Installation Image for Oracle VM
Introduction to Windows Installation
Getting Started With Windows Server 2008 Installation
Supported Windows Operating Systems
Windows Installation Considerations
Windows Media Delivery Methods
How to Download Server Software
Installing the Windows Server 2008 R2 Operating System
How to Install Windows Server 2008 R2 Using Local or Remote Media
Updating Critical Drivers and Installing Supplemental Software
Installing Server-Specific Device Drivers
How to Install the Server-Specific Device Drivers
Installing Supplemental Software
How to Install the Supplemental Software
Incorporating Device Drivers into a WIM Image for WDS
How to Install Windows Server 2008 R2 Using PXE
Administration, Diagnostics, and Service
Overview of the ILOM Supplement
Managing Power Usage and Monitoring Power Consumption
Configuring the Server Power Restore Policy
Switching the Default Serial Port Output Between SP and Host Console
Indicators, Sensors, and Traps
Introduction to Diagnostic Tools
U-Boot Diagnostic Startup Tests
Accessing the Pc-Check Diagnostics Utility on the Tools and Drivers CD/DVD
Server Module and Components Overview
Preparation Procedures for Service and Operation
Component Removal and Installation Procedures
Use this procedure to add drivers to the WIM image for 1GbE systems.
Note - For 10GbE systems, you cannot add drivers to the WIM image. Instead you must wait until the OS has been installed, and use the .msi tool on the Tools and Drivers CD/DVD ISO image to install the drivers manually.
Before You Begin
You should have already obtained the necessary drivers as described in Downloading Server Software.
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.
Refer to the Microsoft documentation for the Windows Automated Installation Kit (AIK) for the details of starting the Windows SIM application.
A new PathAndCredentials list item appears.
For example, the path and credentials for a 64-bit image might be:
<PATH>\\yourshare\share\DriverPack\64bit/</Path> <Credentials> <Domain>MyDomain</Domain> <Username>MyUserName</Username> <Password>MyPassword</Password> </Credentials>
<?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\64bit</Path> <Credentials> <Domain>MyDomain</Domain> <Username>MyUserName</Username> <Password>MyPassword</Password> </Credentials> </PathAndCredentials> </DriverPaths> </component> </settings> </unattend>
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.
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.
imagex /unmount /commit C:\wim_mount
The service image is now available, and all the server-specific drivers are added to the image.
Next Steps
To boot from the WIM image, see How to Install Windows Server 2008 R2 Using PXE.