Skip Navigation Links | |
Exit Print View | |
![]() |
Sun Fire X4640 Server Product Documentation Sun Fire X4640 Server Documentation Library |
Get Software and Firmware Downloads
About This Documentation (PDF and HTML)
Hardware Installation and Product Notes
Sun Fire X4640 Server Front and Back Panel Features and Components
Installing the Server Hardware
Removing the Server From the Rack
Getting Service for Your Server
Sun Fire X4640 Server Specifications
Communicating With the ILOM and the System Console
Setting Up Your Operating System
Overview of the Sun Fire X4640 Server Product Notes
Supported Software and Firmware
Solaris Operating System Issues
Windows Operating System Issues
VMware ESX and VMware ESXi Issues
Sun Installation Assistant Issues
MegaRAID Storage Manager (MSM) Issues
Integrated Lights Out Manager (ILOM) Issues
Introduction to Sun Installation Assistant
Getting Started With Sun Installation Assistant
Starting SIA and Preparing for Deployment or Recovery Tasks
Using SIA to Upgrade System Firmware
Using SIA to Recover a Service Processor
Performing an SIA PXE-Based Attended Installation
Performing an SIA PXE-Based Unattended Installation
Observing an SIA PXE-Based Unattended Installation
Creating a Bootable SIA USB Flash Drive
Identifying a Linux Boot Device on a Sun Fire X4500 Server
Introduction to Solaris OS and OpenSolaris Installation
Installing the Solaris 10 Operating System
Installing the OpenSolaris Operating System
Booting From OS Distribution Media
Identifying Logical and Physical Network Interface Names for Solaris OS Installation
Preliminary Tasks Before Installing An OS
Introduction to Linux Installation
Sun Installation Assistant (SIA)
Installing Red Hat Enterprise Linux
Installing and Updating SUSE Linux Enterprise Server
Configuring a Linux Server to Support PXE Installation
Booting From OS Distribution Media
Preliminary Tasks Before Installing An OS
Identifying Logical and Physical Network Interface Names for Linux OS Configuration
Introduction to Windows Installation
Sun Installation Assistant (SIA)
Getting Started With Windows Server 2008 Installation
Supported Windows Operating Systems
Windows Installation Considerations
How to Download Server Software
Selecting a Media Delivery Method
Windows Media Delivery Methods
How to Set Up the JavaRConsole System
Installing Windows Server 2008
How to Install Windows Server 2008
Updating Critical Drivers and Installing Supplemental Software
How to Update the Server-Specific Drivers
How to Install Supplemental Software
Additional Information for Supplemental Software
Incorporating Sun Fire Drivers Into a WIM Image
How to Deploy a WIM Image to Your Server
Identifying Network Interfaces in Windows
To Determine the Server's Active Network Data Ports
Confirm Physical Port MAC Addresses and Match Them to Windows Device Names
Introduction to ESX Installation
Installing VMware ESXi 4.0 Installable
Booting From OS Distribution Media
Preliminary Tasks Before Installing An OS
Administration, Diagnostics, and Service
Overview of the ILOM Supplement
Communicating With the ILOM and the System Console
Using ILOM to Monitor the Host
Overview of the Diagnostics Guide
Introduction to System Diagnostics
Using the ILOM to Monitor the Host
Using SunVTS Diagnostics Software
Creating a Data Collector Snapshot
Sun Fire X4640 Server Service Manual Overview
Controlling Power and Performing Hardware Reset
Removing and Installing Components
Configuring the System Using the BIOS Setup Utilities
Before You Begin
Before creating a WIM image, you need to do the following:
The Windows Automated Installation Kit (Windows AIK or WAIK) must be installed. The kit can be downloaded from Microsoft. Sun recommends using version 2.0 or later of the WAIK.
Read the Windows AIK documentation.
Windows Remote Installation Services must be running on a Windows Server. Read the Windows Deployment Services snap-in documentation.
Locate the DriverPack.zip and OptPack.zip files for Windows Server 2008 you downloaded as described in How to Download Server Software.
\\yourshare\share\DriverPack
|
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
See the Microsoft documentation for the Windows Automated Installation Kit 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\amd64</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\x64</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 deploy your image, proceed to How to Deploy a WIM Image to Your Server.