Sun Microsystems X6250 manual MyDriver2.inf are renamed oem0.inf and oem1.inf

Page 70

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.

62 Sun Blade X6250 Server Module Windows Operating System Installation Guide • September 2008

Image 70
Contents Sun Microsystems, Inc Please Recycle Contents Installing Windows Server Configure the JavaRConsole SystemUpdate the Critical Server-Specific Drivers Index Page Related Documentation Third-Party Web SitesTypographic Conventions Sun Welcomes Your CommentsAbout Windows Server Installation Getting StartedImportant Installation Considerations Getting Started Assisted Installation Using Sun Installation Assistant SIA Supported Windows Operating SystemsManual Installation SIA Media Availability, Updates DocumentationPage Downloading Server-Specific Driver Packages Page Selecting the Delivery Methods Select a Mass Storage Drivers Method 1Delivery Methods for Windows 2003 Mass Storage Drivers2Delivery Methods for Windows Server Distribution Media Page Prepare for Mass Storage Driver Delivery Create a Floppy DiskIv. Select FloppyPack.zip Insert a blank floppy disk into drive a when prompted 2Select Driver Disks to Create Copy the Floppy Image File To Copy the Floppy Image FileIv. Select FloppyPack.zip Configure the JavaRConsole System To Set Up the JavaRConsole System for Servers With Ilom Setting Up the JavaRConsole SystemJavaRConsole System Requirements Click Yes URL SampleEnter the user name and password and click Log Click the Remote Control tab in the Ilom WebGUIClick Launch Redirection 5ILOM WebGUI Launch Redirection Screen8JavaRConsole Devices Menu To Set Up the JavaRConsole System for Servers With Elom 9Device Configuration Window Select Storage from the menu bar and click Mount DeviceWhen you have made your selections, click Submit Page Installing Windows Server Installation RequirementsPage Installing the Operating System 1Requirements for Each Installation Method2F8 Prompt Example 4Specify Additional Device Screen Press S to specify additional devices 5Example Select Mass Storage Adapter Screen7Setup Selection Screen Proceed to Updating the Critical Server-Specific Drivers Installing Windows Server Page Installing the Operating System Select CD/DVD from the Boot Device menu and press Enter 4Select Installation Type 5Where to Install Windows Page Example At the Advanced Driver Options page see -6, do the following Page Update the Critical Server-Specific Drivers To Update the Server-Specific Drivers Updating the Server-Specific DriversClick Next to accept the default settings 1Sun Installation Package Dialog Box Example3Sun Installation Wizard Example Click NextSelect I accept this agreement, and then click Next Click FinishInstalling Supplemental Software To Install Supplemental SoftwareAdditional Information for Supplemental Software 7Supplemental Software Dialog BoxManaging RAID Using the StorageTek RAID Manager Using Intel NIC Teaming8Intel NIC Adapter Properties Click Next. The Adapter Selection page is displayed 9New Team WizardFor Windows Server 2003 R2 SP2 Completing the IPMItool InstallationFor Windows Server Click OK Http//ipmitool.sourceforge.net/manpage.html Page A P T E R Add Drivers to a WIM Image Determine Required DriversBefore you Begin To Add Drivers to the WIM Image MyDriver2.inf are renamed oem0.inf and oem1.inf Adding Drivers to a RIS Image To Add Drivers to a RIS ImagePage Net stop binlsvc net start binlsvc Page P E N D I X a Click Start Settings Control Panel- Network Connections Click Start Run Second Ethernet adapter port First Ethernet adapter port Page Page Using the Adaptec Configuration Utility Preparing Sun Blade REM Disks for the Operating SystemAdditional Information Index