Skip Navigation Links | |
Exit Print View | |
Sun Fire X4640 Server Windows Installation Guide Sun Fire X4640 Server Documentation Library |
About This Documentation (PDF and HTML)
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
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.