Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide ... · PDF fileSun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Windows Operating Systems Part No. 821-0484-11

Sun Fire X4170 M2 and X4270 M2Servers

Installation Guide for Windows Operating Systems

Part No. 821-0484-11June 2010, Revision A

Copyright © 2010 Oracle and/or its affiliates. All rights reserved.This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected byintellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to usin writing.If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, thefollowing notice is applicable:U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are"commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in anyinherently dangerous applications, including applications which may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. OracleCorporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon aretrademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks ofSPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd.This software or hardware and documentation may provide access to or information on content, products, and services from third parties. OracleCorporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, andservices. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-partycontent, products, or services.

Copyright © 2010, Oracle et/ou ses affiliés. Tous droits réservés.Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à desrestrictions d’utilisation et de divulgation. Sauf disposition de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire,diffuser, modifier, breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et parquelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté àdes fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’ellessoient exemptes d’erreurs et vous invite, le cas échéant, à lui en faire part par écrit.Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence dece logiciel ou l’utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s’applique :U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customersare "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pasconçu ni n’est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vousutilisez ce logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, desauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliésdéclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type d’applications.Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés.Tout autre nom mentionné peut correspondre à des marquesappartenant à d’autres propriétaires qu’Oracle.AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. Intel et Intel Xeon sont desmarques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques ou des marquesdéposées de SPARC International, Inc. UNIX est une marque déposée concédée sous licence par X/Open Company, Ltd.Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liens donnant accès à des contenus, des produits etdes services émanant de tiers. Oracle Corporation et ses affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ouservices émanant de tiers. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pour responsables des pertes subies, des coûtsoccasionnés ou des dommages causés par l’accès à des contenus, produits ou services tiers, ou à leur utilisation.

Contents

Preface vii

Part I Windows Server Installations

1. Assisted OS Installation With Sun Installation Assistant (SIA) 3

SIA Task Overview 4

How to Obtain SIA 4

SIA Documentation Resources 4

2. Getting Started 7

Supported Windows Server Operating Systems 8

Windows Installation Prerequisites 9

Windows Server Installation Task Overview 10

SAS PCIe HBAs Requiring LSI Mass Storage Driver for Windows Server 2008SP2 11

3. Installing Windows Server 2008 13

Before You Begin 13

Installing Windows Server Using Local or Remote Media 14

▼ Install Windows Server 2008 (SP2 or R2) Using Local or Remote Media14

Windows Server Installation Using a PXE Network Boot 25

iii

Before You Begin 25

▼ Install Windows Server 2008 (SP2 or R2) Using PXE 26

4. Post Installation of Windows Server 2008 27

Before You Begin 27

Installing Critical Device Drivers and Supplemental Software 28

▼ Install Server-Specific Device Drivers 28

Installing Supplemental Software 29

▼ Install the Supplemental Software 30

Configuring Support for TPM 31

Configuring Intel NIC Teaming 31

Part II Windows Server System Administrator References

A. Supported Installation Methods 35

Console Outputs 35

Installation Boot Media 37

Installation Targets 40

B. Supported Operating Systems 41

Supported Operating Systems 42

C. BIOS Defaults for New Installations 45

Verification of BIOS Factory Defaults 45

Before You Begin 45

▼ View or Edit BIOS Settings for New Installations 46

D. Downloading the ISO Image for the Tools and Drivers DVD 49

ISO Image Download Procedure 49

▼ Download the Tools and Drivers DVD Image 49

iv Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Windows Operating Systems • June 2010

E. Incorporating Device Drivers Into Windows Server 2008 WIM Images forWindows Deployment Services 51

Getting Started 52

Location of Device Drivers on Tools and Drivers DVD 52

Which Device Drivers to Incorporate Into WIM Image(s) 53

Prerequisites and Task Overview 54

Procedures for Incorporating Drivers Into WIM Image(s) 57

Before you Begin 57

▼ Create an ImageUnattend.xml Setup Script – Windows Server 2008(SP2 or R2) 57

▼ Add Device Driver(s) to Boot WIM – Windows Server 2008 SP2 Only62

▼ Map ImageUnattend.xml Setup Script to Windows Server 2008 (SP2or R2) Install Image 65

Index 71

Contents v

vi Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Windows Operating Systems • June 2010

Preface

This installation guide contains procedures for installating the Windows Server 2008and Windows Server 2008R2 operating systems and initial software configurationprocedures for bringing the Sun Fire X4170 M2 and X4270 M2 Servers from Oracle®to a configurable and usable state.

This document is written for technicians, system administrators, authorized serviceproviders (ASPs), and users who have experience with installing operating systems.

The preface contains the following topics:

■ “Product Information” on page vii

■ “Related Documentation” on page viii

■ “Documentation, Support, and Training” on page x

■ “Typographic Conventions” on page x

■ “Documentation Comments” on page x

Product InformationFor information about the Sun Fire X4170 M2 and X4270 M2 Servers, go to thefollowing web sites:

(http://www.oracle.com/goto/x4170m2)


At these sites, you can find links and navigate to the following information anddownloads:

■ Product information and specifications

■ Supported operating systems

vii

■ Software and firmware downloads

■ Supported option cards

■ External storage options

■ Power calculator

■ Systems Handbook

Related DocumentationThe related documents listed in the following table are available online at:

■ (http://docs.sun.com/app/docs/prod/sf.x4170m2#hic)

■ (http://docs.sun.com/app/docs/prod/sf.x4270m2#hic)

Title Content Part Number Format

Sun Fire X4170 M2 and X4270M2 Servers Product Notes

Late-breaking informationabout the servers

821-0482 PDFHTML

Sun Fire X4170 M2 and X4270M2 Servers Getting StartedGuide

Basic installation informationfor setting up the servers

821-0480 PDFPrint

Sun Fire X4170 M2 and X4270M2 Servers Installation Guide

Detailed installationinformation for setting up theservers

821-0481 PDFHTMLPrint option

Sun Fire X4170 M2 and X4270M2 Servers Installation Guidefor Linux, Virtual MachineSoftware, and Oracle SolarisOperating Systems

Installation instructions forLinux, Oracle VM, VMware,and Oracle Solaris operatingsystems

821-0483 PDFHTML

Sun Fire X4170 M2 and X4270M2 Servers Installation Guidefor Windows Operating Systems

Installation instructions forthe Windows Serveroperating systems

821-0484 PDFHTML

Sun Fire X4170 M2 ServerService Manual

Information and proceduresfor maintaining andupgrading the Sun Fire X4170M2 Server

821-0486 PDFHTML

Sun Fire X4270 M2 ServerService Manual

Information and proceduresfor maintaining andupgrading the Sun Fire X4270M2 Server

821-0488 PDFHTML

viii Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Windows Operating Systems • June 2010

Translated versions of some of these documents are available at the web site URLslisted above this table. English documentation is revised more frequently and mightbe more up-to-date than the translated documentation.

Sun Installation Assistant 2.3through 2.4 User’s Guide forx64 Servers

Instructions for usingOracle’s Sun InstallationAssistant to install theWindows and Linuxoperating systems

821-0694 PDFHTML

Sun x64 Servers DiagnosticsGuide

Information for diagnosingand troubleshooting theservers

820-6750 PDFHTML

Sun Server CLI Tools andIPMItool 2.0 User’s Guide

Instructions for using theServer HardwareManagement Packapplications and utilities

821-1600 PDFHTML

Oracle Integrated Lights OutManager (ILOM) 3.0Documentation Collection(formerly called SunIntegrated Lights OutManager)

ILOM features and tasks thatare common to servers andserver modules that supportILOM 3.0

820-5523820-6410820-6411820-6412820-6413

PDFHTML

Oracle Integrated Lights OutManager (ILOM) 3.0Supplement for Sun Fire X4170M2 and X4270 M2 Servers

ILOM 3.0 information that isspecific to the Sun Fire X4170M2 and X4270 M2 Servers

821-0489 PDFHTML

Sun Fire X4170 M2 and X4270M2 Servers Safety andCompliance Guide

Hardware safety andcompliance information forthe servers

821-0490 PDF

Important Safety Informationfor Sun Hardware Systems

Multilingual hardware safetyand compliance informationfor all Sun hardware system

821-1590 Print

Title Content Part Number Format

Preface ix

Documentation, Support, and Training

Typographic Conventions

Documentation CommentsWe are interested in improving product documentation and welcome yourcomments and suggestions. You can submit your comments by clicking theFeedback [+] link at: (http://docs.sun.com).

Please include the title and part number of your document with your feedback:

Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Windows OperatingSystems, part number 821-0484-11

Function URL

Documentation (http://docs.sun.com)

Support (http://www.sun.com/support/)

Training (http://www.sun.com/training/)

Typeface Meaning Examples

AaBbCc123

The names of commands, files, anddirectories; on-screen computeroutput

Edit your.login file.Use ls -a to list all files.% You have mail.

AaBbCc123

What you type, when contrasted withon-screen computer output

% su

Password:

AaBbCc123 Book titles, new words or terms,words to be emphasized. Replacecommand-line variables with realnames or values.

Read Chapter 6 in the User’s Guide.These are called class options.You must be superuser to do this.To delete a file, enter rm filename.

x Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Windows Operating Systems • June 2010

PART I Windows Server Installations

This section lists the topics that describe how to install the Windows 2008 (SP2 orR2) operating systems on your server.

Description Link(s)

Novice or Experienced Users: Use SIA toperform an assisted installation of theWindows operating system. SIA provides theappropriate system drivers andplatform-specific software.

• Chapter 1, Assisted OS InstallationWith Sun Installation Assistant (SIA)

Experienced Users. Manually install theWindows operating system and the requiredsystem drivers.

• Chapter 2, Getting Started• Chapter 3, Windows Server 2008

Installation• Chapter 4, Post Installation of Windows

Server 2008

Experienced Users. Manually install theWindows operating system and the requiredsystem drivers.

• Appendix A, Supported InstallationMethods

• Appendix B, Supported OperatingSystems

• Appendix C, BIOS Defaults For NewInstalls

• Appendix D, Downloading the ISOImage for the Tools and Drivers DVD

• Appendix E, Incorporating DeviceDrivers Into WDS Images

CHAPTER 1

Assisted OS Installation With SunInstallation Assistant (SIA)

Oracle’s SIA makes operating system installation easy. With SIA, all you need tobegin is a licensed copy of Linux or Windows OS distribution media supported foryour server. All software and required server-specific drivers are supplied by SIA.With a graphical wizard interface and flexible installation options, SIA bringssimplicity, speed, and reliability to your server deployments.

To use SIA, simply boot the SIA program from the server's DVD drive, a USB flashdrive, or from a network image. Check for the latest SIA updates available. Selectyour OS distribution from the menu and follow the on-screen instructions. SIA scansyour system to ensure that it has the drivers it needs to configure your servercomponents[1]. It also provides you the option of having SIA check for the latestdrivers available. SIA will prompt you for the appropriate media as needed and anyother required information during the OS installation process (such as license keys).

Note – [1] Some option card drivers are downloaded to the server, but requiremanual installation. Feature enhancements are made to SIA regularly; therefore, youshould check the SIA information page for the latest SIA updates and supportedfeatures (http://www.sun.com/systemmanagement/sia.jsp).

Topics discussed in this chapter include:

■ “SIA Task Overview” on page 4

■ “How to Obtain SIA” on page 4

■ “SIA Documentation Resources” on page 4

3

SIA Task OverviewYou can perform the following tasks using SIA:

Note – The supported SIA installation and recovery tasks listed below areserver-dependent and might vary.

■ Perform an assisted installation of a Linux or Windows operating system on yourx86 server. SIA provides the appropriate drivers and platform-specific software,eliminating the need to create a separate driver disk.

■ Optionally create RAID-1 volumes on internal storage devices.

■ Optionally upgrade your system Integrated Lights Out Manger (ILOM) serviceprocessor (SP), BIOS, and storage device firmware (regardless of the OS on yourserver).

■ Optionally update your SIA session with the latest firmware and drivers.

■ Optionally recover from a corrupt or inaccessible ILOM service processor.

How to Obtain SIASIA is provided on the SIA DVD with most x86 server platforms from Oracle. SIA isalso available as a web download. Regular updates are made available to ensure thatthe latest OS versions are supported. To download the latest version of SIA for yourserver platform, refer to the SIA information page at:

(http://www.sun.com/systemmanagement/sia.jsp)

SIA Documentation ResourcesIf you have determined that you want to install a Windows or Linux operatingsystem on your x86 server using SIA, refer to the following resources for detailedinstallation instructions and forum discussions.

■ Sun Installation Assistant 2.3 through 2.4 User’s Guide for x64 Servers

(http://docs.sun.com/app/docs/prod/install.x64svr?l=en&a=view)

■ Sun BigAdmin Feature Article: How to Use the Sun Installation Assistant

4 Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Windows Operating Systems • June 2010

(http://www.sun.com/bigadmin/features/articles/install_assistant.jsp)

■ General Installation Discussion Forum

(http://forums.sun.com/forum.jspa?forumID=832)

Chapter 1 Assisted OS Installation With Sun Installation Assistant (SIA) 5


CHAPTER 2

Getting Started

This chapter describes how to get started installing the Microsoft Windows Server2008 SP2 and the Microsoft Windows Server 2008 R2 operating systems manually onyour server.

Note – The term “manually” refers to performing the installation by following theinstructions provided in Chapters 2 through 4 of this guide, and not using the SunInstallation Assistant (SIA). If you prefer to perform an assisted Windowsinstallation by using SIA, see Chapter 1 of this guide.

Topics discussed in this chapter include:

■ “Supported Windows Server Operating Systems” on page 8

■ “Windows Installation Prerequisites” on page 9

■ “Windows Server Installation Task Overview” on page 10

■ “SAS PCIe HBAs Requiring LSI Mass Storage Driver for Windows Server 2008SP2” on page 11

7

Supported Windows Server OperatingSystemsThe Sun Fire X4170 M2 and X4270 M2 Servers support the following MicrosoftWindows operating systems:

For a complete and updated list of all the supported operating systems on the SunFire X4170 M2 and X4270 M2 Servers, see the following web sites:

■ (http://www.oracle.com/goto/x4170m2)


Windows OS Edition

• Windows Server 2008 SP2 • Standard Edition (64-bit)• Enterprise Edition (64-bit)• Datacenter edition (64-bit)

• Windows Server 2008 R2 • Standard Edition (64-bit)• Enterprise Edition (64-bit)• Datacenter edition (64-bit)


Windows Installation PrerequisitesRefer to the following important prerequisites before beginning the Windows Server2008 operating system installation on your server.

TABLE 2-1 Windows Installation Prerequisites

Requirement Description For more information, see:

Establisheddeployment methodthat enables you toboot the Windowsinstall program

Guidelines for selecting a local or remote deploymentmethod for installing a Windows operating system.

• Appendix A

RAID volume creation If you are using the LSI mass storage controller and youwant to include your boot drive as part of a RAIDconfiguration, you need to configure a RAID volume onit. Use the LSI integrated RAID controller setup utilitybefore you install Windows.

• LSI MegaRAID SoftwareSAS User’s Guide at:(http://www.lsi.com/support/sun/)

Verification of BIOSsettings for new OSinstallations

Prior to installing the Windows Server 2008 operatingsystem, you should verify that the BIOS factory-defaultproperties are set.

• Appendix C

Installation ofserver-specific devicedrivers and optionalsupplemental software

After performing the Windows Server 2008 installation,you might need to:• Install server-specific device drivers to support

additional hardware.Note the Windows 2008 SP2 does not include the LSImass storage drivers for the SAS PCIe host busadapters (HBAs). If you have a SAS PCIe HBA optioninstalled, the LSI mass storage driver for the SAS PCIeHBA option must be made accessible from the Toolsand Drivers DVD during installation. For a list ofsupported SAS PCIe HBAs, see TABLE 2-2.

• Install Windows Server optional supplemental softwarethat is available for your x86 server.

• Chapter 4• “SAS PCIe HBAs

Requiring LSI MassStorage Driver forWindows Server 2008SP2” on page 11

Incorporateserver-specific devicedrivers in a WIMimage

Advanced users can incorporate the post installationsystem device drivers into WDS boot and install images.

• Appendix E

Access tolate-breakinginformation andpatches for OSinstallations

Review the Sun Fire X4170 M2 and X4270 M2 ServersProduct Notes for late-breaking information aboutsupported operating system software and patches.

• Sun Fire X4170 M2 andX4270 M2 ServersProduct Notes (821-0482)

Chapter 2 Getting Started 9

Windows Server Installation TaskOverviewTo manually install Windows Server 2008 (SP2 or R2), complete the followingprocedures in order:

1. Obtain the Tools and Driver DVD provided or download the latest drivers andutilities available for your server as described in Appendix D.

The install program for the Windows Server 2008 SP2 does not include the LSIdrivers for the Sun Storage SAS PCIe HBA options. Therefore, if you have a SASPCIe HBA configured on your server and you are installing Windows 2008 SP2,the LSI mass storage driver for the SAS PCIe HBA option must be madeaccessible from the Tools and Drivers DVD during the installation process.

For a list of SAS PCIe HBAs supported on the Sun Fire X4170 M2 and X4270 M2Servers, see “SAS PCIe HBAs Requiring LSI Mass Storage Driver for WindowsServer 2008 SP2” on page 11.

Note – Optionally, advanced users might prefer to incorporate the drivers into WDSimages. For instructions on how to incorporate the drivers into WDS images, seeAppendix E.

2. Choose and set up an installation method for deploying the Windows Serverinstallation as described in Appendix A.

3. Follow the instructions for performing a manual installation of the WindowsServer operating system as described in Chapter 3.

4. Follow the instructions for performing the Windows Server post installation tasksas described in Chapter 4.


SAS PCIe HBAs Requiring LSI MassStorage Driver for Windows Server 2008SP2TABLE 2-2 identifies the SAS PCIe host bus adapter (HBA) options that are supportedon the Sun Fire X4170 M2 and X4270 M2 Servers at the time of this publication. Ifyou have one of these SAS PCIe HBA options configured on your server and you areinstalling Windows Server 2008 SP2, you will need to load the LSI mass storagedriver for the PCIe HBA option from the Tools and Drivers DVD during installation.

Instructions for loading the LSI mass storage driver during the Windows Server 2008SP2 installation are provided in Step 8 of the “Install Windows Server 2008 (SP2 orR2) Using Local or Remote Media” on page 14.

If you do not have a copy of the Tools and Drivers DVD, you can download the ISOimage for the Tools and Driver DVD. For details, see Appendix D.

For an up-to-date list of options supported on the Sun Fire X4170 M2 and X4270 M2Servers, see:

■ (http://www.sun.com/servers/x64/X4170/optioncards.jsp).

■ (http://www.sun.com/servers/x64/X4270/optioncards.jsp).

TABLE 2-2 Supported SAS PCIe HBAs Requiring LSI Mass Storage Driver

Supported SAS PCIe HBAs Option Number Driver Required During Installation

Sun Storage 6 Gb/s SAS PCIeRAID HBA, Internal

SG-SAS6-R-INT-Z LSI MegaRAID SAS 92xx-xx

Sun Storage 6 Gb/s SAS PCIeRAID HBA, External

SG-SAS6-R-EXT-Z LSI MegaRAID SAS 92xx-xx

Sun Storage 6 Gb/s SAS PCIeHBA, Internal

SG-SAS6-INT-Z LSI Adapter SAS 2008 Falcon

Sun Storage 6 Gb/s SAS PCIeHBA, External

SG-SAS6-EXT-Z LSI Adapter SAS 2008 Falcon

Chapter 2 Getting Started 11


CHAPTER 3

Installing Windows Server 2008

This chapter provides information about manually installing the Windows Server2008 SP2 or Windows Server 2008 R2 operating system.

Note – The term “manually” refers to performing the installation by following theinstructions provided in Chapters 2 through 4 of this guide, and not using the SunInstallation Assistant (SIA). If you prefer to perform an assisted Windowsinstallation by using SIA, see Chapter 1 of this guide for details.

This chapter includes the following topics:

■ “Before You Begin” on page 13

■ “Installing Windows Server Using Local or Remote Media” on page 14

■ “Windows Server Installation Using a PXE Network Boot” on page 25

Before You BeginEnsure that the following requirements are met before you proceed with theinstructions in this chapter for manually installing the Windows Server operatingsystem.

■ All applicable installation prerequisites for installing an operating system shouldhave been met. For further information about these prerequisites, see “WindowsInstallation Prerequisites” on page 9.

■ An installation method (for example: console output, boot media, and installtarget) should have been chosen and established prior to performing theinstallation. For more information about these setup requirements, see AppendixA.

13

■ Use the Microsoft Windows Server 2008 (SP2 or R2) operating systemdocumentation in conjunction with the Windows Server operating systeminstructions provided in this chapter. You can obtain a copy of Microsoft’sWindows Server 2008 installation documentation at:(http://www.microsoft.com/windowsserver2008/en/us/product-documentation.aspx)

After completing this procedure, you should review and perform the required postinstallation tasks described later in this guide. For more details, see Chapter 4.

Installing Windows Server Using Localor Remote MediaThe procedure in this section describes how to boot the Windows Server 2008 (SP2or R2) operating system from local or remote media. It assumes that you are bootingthe Windows installation media from one of the following sources:

■ Windows Server 2008 SP2 or Windows Server 2008 R2 (or subsequent release) CDor DVD

■ Windows Server 2008 SP2 or Windows Server 2008 R2 (or subsequent release) ISOimage

Note – The Windows Server 2008 (SP 2 or R2) ISO image can be used for remoteinstallation or for creating an installation CD or DVD.

Note – If you are booting the installation media from a PXE environment, refer to“Windows Server Installation Using a PXE Network Boot” on page 25 forinstructions.

▼ Install Windows Server 2008 (SP2 or R2) UsingLocal or Remote Media1. Ensure that the installation media is available to boot.

■ For Distribution CD/DVD. Insert the Windows 2008 Distribution media (CDlabeled number 1 or the single DVD) into the local or remote USBCD/DVD-ROM drive.


■ For ISO image. Ensure that the ISO images are available and that the ILOMRemote Console application is aware of the first ISO image location.

For additional information about how to set up the installation media, see“Boot Media Options for Performing an OS Installation” on page 37.

2. Reset or power on the server.

For example:

■ From the ILOM web interface, select Remote Control --> Remote PowerControl tab, then select Reset from the Select Action list box.

■ From the local server, press the Power button on the front panel of the serverto power off the server, then press the Power button again to power on theserver.

■ From the ILOM CLI, type: reset /SYS

The BIOS screen appears.

Note – The next events occur very quickly; therefore, focused attention is neededfor the following steps. Watch carefully for these messages as they appear on thescreen for a brief time. You might want to enlarge the size of your screen to eliminatescroll bars.

3. In the BIOS power-on self-test screen, press F8 to specify a temporary bootdevice for the Windows installation.

The Please Select Boot Device menu appears.

Note – The menu that appears in your installation might differ depending on thetype of disk controller installed in your server.

Chapter 3 Installing Windows Server 2008 15

4. In the Please Select Boot Device menu, select the menu item according to theWindows media installation method you elected to use, then press Enter.

For example:

■ If you elected to use the Windows local delivery method, select TEAC as thephysical DVD device (or select CD/DVD if this option is shown in boot devicemenu).

■ If you elected to use the ILOM Remote Console delivery method, selectVirtual CDROM.

5. When prompted with Press any key to boot from CD, press any key.

The Windows installation wizard starts.

Continue the Windows installation wizard until the Installation Type dialogappears.

6. In the Installation Type dialog, click Custom (advanced).

The Where Do You Want to Install Windows dialog appears.



7. In the Where Do You Want to Install Windows dialog, perform one of thefollowing tasks in the table below to specify a storage target for the WindowsServer operating system edition.

8. (Load Driver) In the Load Drive dialog, do the following:

For Windows Server Edition Task

Windows Server 2008 SP2(or subsequent Windows 2008SP release)

Perform one of the following:• If you do not see any storage targets listed and have

a Sun Storage SAS PCIe RAID HBA optionconfigured on your server, click Load Driver thenproceed to Step 8.- or -

• If you see the storage target where you want toinstall the operating system but want to change thedefault partition settings associated with that target,select the target, click Drive Options, thenproceed to Step 9.- or -

• If you see the storage target where you want toinstall the operating system and do not want tochange the default partition settings for that target,select the target and click Next, then proceed toStep 10.

Windows Server 2008 R2(or subsequent Windows 2008R2 release)

Prior to proceeding with the Windows Server 2008 R2installation, you must install the network driver forthe on-board Intel 82576 Gigabit Network Device.• Click Load Driver, then proceed to Step 8.


a. Ensure the driver(s) are accessible according to the installation methodchosen (described in Appendix A).

For example:

■ Floppy Disk Local. Storage driver(s) on a floppy disk in floppy drive A onthe server.

■ Floppy Disk Remote. Storage driver(s) on a floppy disk in a floppy drivemounted as a device from the ILOM Remote Console.

■ Floppy Image. Storage driver floppy.img file is mounted as a device fromthe ILOM Remote Console.

■ Non-floppy Media. Storage driver(s) are on a local physical storage media(USB flash drive or CD/DVD) or virtual media mounted from the ILOMRemote Console.

b. In the Load Driver dialog, click Browse to navigate to the appropriate drivermedia folder as described below.

■ For systems configured with either of these SAS PCIe RAID HBA optionsSG-SAS6-R-INT or SG-SAS6-R-EXT-Z, navigate to the following directory onthe Tools and Drivers DVD to load the appropriate LSI driver:windows/w2k8/drivers/64bit/hba/lsi/megaraid

■ For a system configured with either of these SAS PCIe HBA optionsSG-SAS6-INT or SG-SAS6-EXT-Z, navigate to the following directory on theTools and Driver DVD to load the appropriate LSI driver:windows/w2k8/drivers/64bit/hba/lsi/mpt2


■ For Intel network driver installation (required for Windows Server 2008R2), navigate to the following directory on the Tools and Driver DVD toload appropriate Intel driver:windows/w2k8R2/drivers/64bit/NIC/Intel

c. In the Browse for Folder dialog, select the appropriate driver, then click OKto load the driver.

The selected driver appears in the Select the Driver to Be Installed dialog.

For example:

■ Two example dialogs follow showing the selected driver to be installed forthe two SAS PCIe HBA options. Note that the SAS PCIe HBA drivers arerequired only for Windows Server 2008 SP2 installations.

■ A third example dialog follows showing the selected driver for the on-boardIntel Gigabit Network Device Driver. Note that the Intel Gigabit NetworkDevice driver is required only for Windows Server 2008 R2 installations.



d. In the Select the Driver to Be Installed dialog, click Next to install thedriver.

The Where Do You Want to Install Windows dialog appears.


Note – If you previously removed or unmounted the Windows Server install mediato load the drivers from the Tools and Drivers DVD, you might see the followingmessage: Windows Cannot be installed to this disk. If this message appears, insertor re-mount the Windows install media, then click Refresh.

e. In the Where Do You Want to Install Windows dialog, do one of following:

■ Select the storage target listed and click Next to install the operatingsystem, then proceed to Step 10.

- or -

■ Select the storage target listed and click Drive Options (Advanced) toview and change the default partition settings, then proceed to Step 9.

The partition settings for the selected target appear at the bottom of theWhere Do You Want to Install Windows dialog.

9. (Partition Drive, advanced) In the lower portion of the Where Do You Want toInstall Windows dialog, do the following:


a. Click Delete to delete the selected storage target existing partitionconfiguration.

A confirmation window appears.

b. Click OK to confirm the partition deletion.

c. Click New to create a new partition on the selected storage target.

d. In the Size scroll box, increase or decrease the partition size as needed, thenclick Apply.

The partition is created.

e. Click Next to install the operating system to the selected storage target.

10. The Windows installation program begins and will reboot the server multipletimes during the installation process.

11. When the Windows installation is complete, Windows starts and prompts youto change the user password.

12. In the user password dialog, click OK and set up the initial user login account.


Note – Windows Server 2008 enforces stricter password schemes for user accounts.Password standards include restrictions on length, complexity, and history. For moredetails, click the Accessibility link at the account creation page.

After the initial user account is created, the Windows Server 2008 desktopappears.

13. Proceed to Chapter 4 to perform the post installation tasks.

Windows Server Installation Using aPXE Network BootThis section explains the initial information you will need to install the WindowsServer 2008 (SP2 or R2) operating system over an established PXE-based networkusing a customer-provided Windows Imaging Format (WIM) image.

Topics included in this section:

■ “Before You Begin” on page 25

■ “Install Windows Server 2008 (SP2 or R2) Using PXE” on page 26

Note that the procedure presented in this section documents the initial steps toinstall Windows 2008 over the network using a Windows Deployment Services(WDS). Specifically, it explains the steps for selecting the server PXE networkinterface card that will communicate with your WDS installation server. For furtherinformation about using WDS to install the Windows Server 2008 operating system,see Microsoft’s Windows Deployment Services documentation.

Before You Begin■ To use PXE to boot the installation media over the network, you must:

■ Configure the network (NFS, FTP, HTTP) server to export the installation tree.

■ Configure the files on the TFTP server that are necessary for PXE booting.

■ Configure the server’s MAC network port address to boot from the PXEconfiguration.

■ Configure Dynamic Host Configuration Protocol (DHCP).

■ To use WDS to perform the installation, you must:

■ Add the required system device drivers to the install.wim image and, ifnecessary, the boot.wim image.


For guidelines for adding drivers to the WIM installation image(s), seeAppendix E.

■ Obtain the WIM Administrator password.

▼ Install Windows Server 2008 (SP2 or R2) Using PXE1. Reset or power on the server.

■ From the ILOM web interface, select Remote Control --> Remote PowerControl tab, then select Reset from the Select Action list box.

■ From the local server, press the Power button on the front panel of the serverto turn off the server, then press the Power button again to power on theserver.



Note – The next events occur very quickly; therefore, focused attention is neededfor the following steps. Watch carefully for these messages as they appear on thescreen for a brief time. You might want to enlarge the size of your screen to eliminatescroll bars.

2. Press F8 to specify a temporary boot device.

The Please Select Boot Device menu appears.

3. In the Please Select Boot Device menu, select the appropriate PXE installationboot device and press Enter.

The PXE installation boot device is the physical network port configured tocommunicate with your network installation server.

The Boot Agent dialog appears.

4. In the Boot Agent dialog, press F12 for a network service boot.

5. Continue the normal Windows Server 2008 SP2 or 2008 R2 WDS networkinstallation.

For additional information, consult Microsoft’s Windows Deployment Servicesproduct documentation.

6. When the installation completes, proceed to Chapter 4 to perform the postinstallation tasks.


CHAPTER 4

Post Installation of Windows Server2008

After completing the installation of the Windows Server 2008 (SP2 or R2) operatingsystem and rebooting the server, you should review the following post installationtasks and, if necessary, perform the tasks that are applicable to your server.

■ “Installing Critical Device Drivers and Supplemental Software” on page 28

■ “Installing Supplemental Software” on page 29

■ “Configuring Support for TPM” on page 31

■ “Configuring Intel NIC Teaming” on page 31

Before You BeginThe procedures in this chapter assume that you have:

■ Installed the Microsoft Windows Server operating system

■ Obtained a copy of the Tools and Drivers DVD

If you do not have a copy of the Tools and Drivers DVD, you can download thelatest ISO image of the Tools and Drivers DVD from the product download site.For Instructions see, Appendix D.

27

Installing Critical Device Drivers andSupplemental SoftwareAn installation wizard is provided on the Tools and Drivers DVD to installserver-specific device drivers and Supplemental Software. The server-specific devicedrivers are provided to support optional hardware devices that can be installed onyour server.

▼ Install Server-Specific Device Drivers1. Insert the Tools and Drivers DVD into a local or remote USB DVD drive and do

one of the following:

■ If the DVD automatically starts, click Install Drivers andSupplemental Software.

■ If the DVD does not automatically start, navigate to one of the followingfolders containing the appropriate InstallPack file (for example,InstallPack_1_0_1.exe), and double-click it.

■ <DVD>/Windows/W2K8/Packages

■ <DVD>/Windows/W2K8R2/Packages

The Server Installation Package dialog appears.

2. In the Install Pack dialog, click Next to accept the default installable items.

Note – You should always accept the “default installable items” to ensure that themost recent versions of the drivers are installed.

The Install Pack notice dialog appears.

3. In the Install Pack notice dialog, read the message, then click Next.

The Welcome to the Sun Fire Installation Wizard appears.

4. In the Welcome to the Sun Fire Installation Wizard dialog, click Next.

The End User License Agreement page appears.

5. In the End User License Agreement page, select I Accept This Agreement,then click Next.

The platform-specific drivers are installed. A green check mark verifies that eachdriver was installed successfully.


6. In the Driver Installation Pack dialog, click Finish.

The System Settings Change dialog appears.

Note – If you plan on installing Supplemental Software (highly recommended), donot restart your system at this time. Once the Supplemental Software has beeninstalled, you will be prompted to restart the system.

7. Perform one of the following:

■ If you accepted the default installable settings in Step 2, click No to proceedto “Installing Supplemental Software” on page 29.

■ If you are not installing the Supplemental Software, click Yes to restart yourcomputer.

Installing Supplemental SoftwareThere are several Supplemental Software components available for your Sun FireX4170 M2 or X4270 M2 Server. You have two options for installation:

■ Typical: Installs all Supplemental Software applicable for your server.

■ Custom: Installs only the Supplement Software selected for installation.

Chapter 4 Post Installation of Windows Server 2008 29

TABLE 4-1 identifies the optional Supplemental Software components available foryour server.

▼ Install the Supplemental Software

Caution – If you have already installed the Supplemental Software, running theinstallation again will not necessarily reinstall the Supplemental Software. It mightresult in the components being removed. Carefully review the dialog boxes duringSupplemental Software installation to ensure that the results are as expected.

1. Do one of the following:

■ If you did not select the Supplemental Software when you ran the procedure“Installing Critical Device Drivers and Supplemental Software” on page 28,refer back to that procedure and run it again, but this time accept the defaultsettings in Step 2 (the default is to install the supplemental software), andselect No in Step 7.

■ If you did select Supplemental Software at the Server Installation Packagedialog box in Step 2 of “Installing Critical Device Drivers and SupplementalSoftware” on page 28, and selected No in Step 7, the Install Pack SupplementalSoftware dialog appears. Proceed to Step 2.

TABLE 4-1 Install Pack Optional Supplemental Software

Available Supplemental Software Components

Servers With LSIIntegrated RAID

Controller

Servers With IntelIntegrated Disk

Controller

LSI MegaRAID Storage Manager, click Yes to restart yourcomputerEnables you to configure, monitor, and maintain RAID on the SASinternal RAID host bus adapter.

Typical Not applicable

IPMItool command-line utilityThe IMPItool command-line utility reads the sensor data repository(SDR) and displays sensor values, system event log (SEL), and field-replaceable unit (FRU) inventory information; gets and sets LANconfiguration parameters; and performs chassis power controloperations via the BMC (also called the service processor (SP)).

Typical Typical

Intel NIC TeamingEnables the network interfaces on a server to be grouped togetherinto a team of physical ports called a virtual interface.

Typical Typical


2. In the Install Pack Supplemental Software dialog, click Next to accept thetypical settings; or select Custom to choose the options to install (seedescriptions of the Supplemental Software in TABLE 4-1.

The Component Installation wizard will guide you through the installation ofeach of the selected Supplemental Software components.

3. After the Supplemental Software has been installed, click Finish.

4. Click Yes at the System Setting Change dialog to restart your system.

If you ran the Sun Server Installation Package software from the Tools andDrivers DVD, remove the DVD from your system.

Configuring Support for TPMIf you intend to use the Trusted Platform Module (TPM) feature set that is providedin Windows 2008, you must configure the Sun Fire X4170 M2 and X4270 M2 Serversto support this feature. For instructions, see the configuring support for TPMinformation in the service manual applicable to your server:

■ Sun Fire X4170 M2 Server Service Manual (821-0486)


Note – TPM enables you to administer the TPM security hardware in your server.For additional information about implementing this feature, refer to the WindowsTrusted Platform Module Management documentation provided by Microsoft.

Configuring Intel NIC TeamingFor more information on setting up NIC teaming for your environment, refer to theIntel Connectivity web page on Advanced Networking Services Teaming at:

(http://support.intel.com/support/network/sb/CS-009747.htm)

Additionally, you can download the complete set of Intel Network Connections UserGuides for your server’s network adapters at:

(http://support.intel.com/support/network/sb/cs-009715.htm)

Chapter 4 Post Installation of Windows Server 2008 31


PART II Windows Server System AdministratorReferences

Refer to the following system administrator references as needed to perform orcomplete the installation of the Windows Server 2008 (SP2 or R2) operating system.

Description Link

Guidelines for selecting and setting up an installationenvironment for deploying the Windows Server installationprogram

Appendix A

A complete list of operating systems supported on the SunFire X4170 M2 and X4270 M2 Servers at the time of thispublication

Appendix B

Instructions for ensuring that the BIOS default properties areset prior to performing the Windows Server installation

Appendix C

Instructions for downloading the latest version of the ISOimage for the Tools and Drivers DVD

Appendix D

Instructions for advanced users who prefer to incorporate theserver-specific drivers in a Windows Imaging Format (WIM)file

Appendix E

APPENDIX A

Supported Installation Methods

To determine which installation method is best for you when installing Windows onyour server, consider the following options summarized in this appendix:

■ “Console Outputs” on page 35

■ “Installation Boot Media” on page 37

■ “Installation Targets” on page 40

Console OutputsTABLE A-1 lists the consoles you can use to capture the output and input of theoperating system installation.

TABLE A-1 Console Options for Performing an OS Installation

Console Description Setup Requirement

Local console You can install the OS andadminister the server byattaching a local console directlyto the server SP.Examples of local consolesinclude:• Serial console• VGA console, with USB

keyboard and mouse

1. Attach a local console to the server.For details, see the “Setting Up the Server” in the SunFire X4170 M2 and X4270 M2 Servers Installation Guide(821-0481).

2. At the ILOM prompt, type your ILOM user name andpassword.

3. For serial console connections only, establish aconnection to the host serial port by typing start/SP/console.The video output is automatically routed to the localconsole.

For further details about establishing a connection to theserver SP, see the Oracle Integrated Lights Out Manager(ILOM) 3.0 Concepts Guide (820-6410).

35

Remote console You can install the OS andadminister the server from aremote console by establishing anetwork connection to the serverSP.Examples of remote consolesinclude:• Web-based client connection

using the ILOM RemoteConsole application

• SSH client connection using aserial console

1. View or establish an IP address for the server SP.For details, see the “Setting Up the Server” in the SunFire X4170 M2 and X4270 M2 Servers Installation Guide(821-0481).

2. View or establish a connection between a remoteconsole and the server SP:

• For web-based client connection, perform these steps:1) In a web browser, type the IP address for the serverSP; 2) log in to the ILOM web interface; 3) redirect thevideo output from the server to the web client bylaunching the ILOM Remote Console; 4) enable deviceredirection (mouse, keyboard, etc.) in the Devicemenu.

• For SSH client connection, perform these steps:1) From a serial console, establish an SSH connectionto the server SP (ssh root@hostname, if using DNS, orssh root@ipaddress); 2) log in to ILOM; 3) redirect theserial output from the server to the SSH client bytyping start /SP/console.

For additional information about establishing a remoteconnection to the ILOM SP or using the ILOM RemoteConsole, see the Oracle Integrated Lights Out Manager(ILOM) 3.0 Concepts Guide (820-6410).

TABLE A-1 Console Options for Performing an OS Installation (Continued)

Console Description Setup Requirement


Installation Boot MediaYou can start the operating system installation to a server by booting a local orremote installation media source. TABLE A-2 identifies the supported media sourcesand the setup requirements for each source.

TABLE A-2 Boot Media Options for Performing an OS Installation

Installation Media Description Setup Requirement

Local boot media Local boot media requires a built-instorage device on the server, or anexternal storage device attached tothe server.Supported OS local boot mediasources can include:• CD/DVD-ROM installation

media, and, if applicable, floppydevice driver media

1. If your server does not contain a built-in storagedevice, attach the appropriate storage device to thefront or rear panel of the server.

2. For more information about how to attached localdevices to the server, see “Setting Up the Server” inthe in the Sun Fire X4170 M2 and X4270 M2 ServersInstallation Guide (821-0481).

Appendix A Supported Installation Methods 37

Remote bootmedia

Remote media requires you to bootthe install over the network. Youcan start the network install from aredirected boot storage device oranother networked system thatexports the installation over thenetwork using a Pre-Boot eXecutionenvironment (PXE).

To redirect the boot media from a remote storagedevice, perform these steps:1. Insert the boot media into the storage device, for

example:For CD/DVD-ROM, insert media into the built-in orexternal CD/DVD-ROM drive.For CD/DVD-ROM ISO image, ensure that ISOimage(s) are readily available on a network sharedlocation.For device driver floppy ISO image, ensure that ISOimage, if applicable, is readily available on anetwork shared location or on a thumb drive.

2. Establish a web-based client connection to the serverILOM SP and launch the ILOM Remote Consoleapplication. For more details, see the SetupRequirements for web-based client connection inTABLE A-1.

3. In the Device menu of the ILOM Remote Consoleapplication, specify the location of the boot media,for example:For CD/DVD-ROM boot media, select CD-ROM.For CD/DVD-ROM ISO image boot media, selectCD-ROM Image.For floppy device driver boot media, if applicable,select Floppy.For floppy image device driver boot media, ifapplicable, select Floppy Image.

For more information about the ILOM RemoteConsole, see the Oracle Integrated Lights Out Manager(ILOM) 3.0 Concepts Guide (820-6410).

Supported OS remote media sourcescan include:• CD/DVD-ROM installation

media, and, if applicable, floppydevice driver media

• CD/DVD-ROM ISO installationimage and, if applicable, floppyISO device driver media

• Automated installation image(requires PXE boot)

TABLE A-2 Boot Media Options for Performing an OS Installation (Continued)



Remote BootMedia(continued)

Note - An automated installationimage enables you to perform theOS installation on multiple servers.By using an automated image, youcan ensure configuration uniformityamong many systems.

Automated installations use aPre-boot eXecution Environment(PXE) technology to enable theclients without an operating systemto boot remotely to the automatedinstall server that performs theinstallation of the operating system.

To perform the installation using PXE, perform thesesteps:1. Configure the network server to export the

installation via PXE boot.2. Make the OS install media available for PXE boot.

If you are using an automated OS installation image,you will need to create and provide the automatedOS install image, for example:

• Solaris JumpStart Image• RHEL KickStart Image• SLES AutoYaST Image• Windows WDS ImageFor detailed instructions for automating theinstallation setup process, consult the operatingsystem vendor documentation.1. To boot the installation media, select the PXE boot

interface card as the temporary boot device.For details, see “Windows Server Installation Usinga PXE Network Boot” on page 25.

TABLE A-2 Boot Media Options for Performing an OS Installation (Continued)


Appendix A Supported Installation Methods 39

Installation TargetsTABLE A-3 identifies the supported installation targets you can use to install anoperating system.

TABLE A-3 Installation Targets for OS Installation

Install Target Description Setup Requirement Supported OS

Local hard diskdrive (HDD)orSolid state drive(SSD)

You can choose to install theoperating system to any of thehard disk drives or solid statedrives installed in the server.

• Ensure that the HDD or SSD isproperly installed and powered-on inthe server.

For more information about installingand powering on an HDD or SDD, referto the service manual applicable to yourserver:• Sun Fire X4170 M2 Server Service

Manual (821-0486)• Sun Fire X4270 M2 Server Service

Manual (821-0488)

• All supportedoperatingsystems listedin AppendixB.

Fibre Channel(FC) StorageArea Network(SAN) device

For servers equipped with FibreChannel PCIe host bus adapters(HBAs), you can choose toinstall the operating system toan external FC storage device.

• Ensure that the FC PCIe HBA isproperly installed in the server.

For more information about installing aPCIe HBA option in your server, refer tothe service manual applicable to yourserver:• Sun Fire X4170 M2 Server Service

Manual (821-0486)• Sun Fire X4270 M2 Server Service

Manual (821-0488)

• All operatingsystems listedin AppendixB.


APPENDIX B

Supported Operating Systems

TABLE B-1 in this appendix describes the operating systems supported on the SunFire X4170 M2 and X4270 M2 Servers at the time this document was published.

For an up-to-date list of the latest operating systems supported on the servers, seethe following web sites:



41

Supported Operating SystemsThe Sun Fire X4170 M2 and X4270 M2 Servers support the installation and use of thefollowing operating systems, or a subsequent release of the operating system.

TABLE B-1 Supported Operating Systems

OperatingSystem Supported Version Additional Information

Windows • Microsoft Windows Server 2008 SP2, StandardEdition (64-bit)

• Microsoft Windows Server 2008 SP2, EnterpriseEdition (64-bit)

• Microsoft Windows Server 2008 SP2, DatacenterEdition (64-bit)

• Microsoft Windows Server 2008 R2, StandardEdition (64-bit)

• Microsoft Windows Server 2008 R2, EnterpriseEdition (64-bit)

• Microsoft Windows Server 2008 R2, DatacenterEdition (64-bit)

• Chapter 3

Linux • Oracle Enterprise Linux 5.4• SUSE Linux Enterprise Server (SLES) 10 SP 3

(64-bit)• SUSE Linux Enterprise Server (SLES) 11 (64-bit)• Red Hat Enterprise Linux Server (RHEL) 5.4

(64-bit)

• Sun Fire X4170 M2and X4270 M2Servers InstallationGuide for Linux,Virtual MachineSoftware, and OracleSolaris OperatingSystems (821-0483)

Solaris • Oracle Solaris 10 10/09 • Sun Fire X4170 M2and X4270 M2Servers InstallationGuide for Linux,Virtual MachineSoftware, and OracleSolaris OperatingSystems (821-0483)


VirtualMachineSoftware

• Oracle VM 2.2.1• VMware ESX Server 4.0 Update 1• VMware ESXi Server 4.0 Update 1

• Sun Fire X4170 M2and X4270 M2Servers InstallationGuide for Linux,Virtual MachineSoftware, and OracleSolaris OperatingSystems (821-0483)

TABLE B-1 Supported Operating Systems (Continued)

OperatingSystem Supported Version Additional Information

Appendix B Supported Operating Systems 43


APPENDIX C

BIOS Defaults for New Installations

When installing a new operating system on a disk drive, you should verify that thefollowing BIOS settings are properly configured before you perform the operatingsystem installation:

■ System time

■ System date

■ Boot order

Verification of BIOS Factory DefaultsIn the BIOS Setup Utility, you can set optimal defaults, as well as view and edit BIOSsettings as needed. Any changes you make in the BIOS Setup Utility (by pressing F2)are permanent until the next time you change them.

In addition to using the F2 key to view or edit the system’s BIOS settings, you canuse F8 during the BIOS start-up to specify a temporary boot device. If you use F8 toset a temporary boot device, this change is only in effect for the current system boot.The permanent boot device specified through F2 will be in effect after booting fromthe temporary boot device.

Before You BeginEnsure that the following requirements are met prior to accessing the BIOS SetupUtility.

■ The server is equipped with a hard disk drive (HDD) or solid state drive (SSD).

■ The HDD or SSD is properly installed in the server. For details, see the servicemanual applicable to your server:

45



■ A console connection is established to the server. For details, see “ConsoleOptions for Performing an OS Installation” on page 35.

▼ View or Edit BIOS Settings for New Installations1. Reset the power on the server.

For example:

■ From the ILOM web interface, select Remote Control --> Remote PowerControl, then select the Reset option from the Select Action list box.

■ From the local server, press the Power button on the front panel of the serverto turn the server off, then press the Power button again to power-on theserver.



2. When prompted in the BIOS screen, press F2 to access the BIOS Setup Utility.

After a few moments, the BIOS Setup Utility appears.

3. To ensure that the factory defaults are set, do the following:

a. Press F9 to automatically load the optimal factory default settings.

A message appears prompting you to continue this operation by selecting OKor to cancel this operation by selecting CANCEL.

b. In the message, highlight OK then press Enter.

The BIOS Setup Utility screen appears with the cursor highlighting the firstvalue in the system time field.

4. In the BIOS Setup Utility, do the following to edit the values associated withthe system time or date.

a. Highlight the values you want to change.

Use up or down arrow keys to change between the system time and dateselection

b. To change the values in the highlighted fields, use these keys:

■ PLUS (+) to increment the current value shown

■ MINUS (-) to decrement the current value shown

■ ENTER to move the cursor to the next value field


5. To access the boot settings, select the Boot menu.

The Boot Settings menu appears.

6. In the Boot Settings menu, use the down arrow key to select Boot DevicePriority, then press Enter.

The Boot Device Priority menu appears listing the order of the known bootabledevices. The first device in the list has the highest boot priority.

7. In the Boot Device Priority menu, do the following to edit the first boot deviceentry in the list:

a. Use the up and down arrow keys to select the first entry in the list, thenpress Enter.

b. In the Options menu, use the up and down arrow keys to select the defaultpermanent boot device, then press Enter.

Note – You can change the boot order for other devices in the list by repeating Steps7a and 7b for each device entry you want to change.

The device strings listed on the Boot Device Priority menu and Options menu arein the format of: device type, slot indicator, and product ID string.

8. To save changes and exit the BIOS Setup Utility, press F10.

Alternatively, you can save the changes and exit the BIOS Setup Utility byselecting Save on the Exit menu. A message appears prompting you to savechanges and exit setup.

In the message dialog, select OK, then press Enter.

Note – When using the ILOM Remote Console, F10 is trapped by the local OS. Youmust use the F10 option listed in the Keyboard drop-down menu that is available atthe top of the console.

Appendix C BIOS Defaults for New Installations 47


APPENDIX D

Downloading the ISO Image for theTools and Drivers DVD

Use the download instructions in this appendix if a Tools and Driver DVD was notshipped with your server or, if you need to verify that the Tools and Drivers DVDshipped with your server contains the latest tools and firmware for your server.

ISO Image Download ProcedureFollow the steps in the procedure below to download the ISO image for the Toolsand Drivers DVD.

▼ Download the Tools and Drivers DVD Image1. Go to the software download site for your server platform:



2. Select and download the ISO image for the Tools and Drivers DVD to anaccessible network location or local storage location.

3. Prepare the ISO image for installation by using one of the following methods:

■ Create a Tools and Drivers DVD using third-party software.

■ Use remote KVMs (ILOM Remote Console) to mount the ISO image.

49


APPENDIX E

Incorporating Device Drivers IntoWindows Server 2008 WIM Imagesfor Windows Deployment Services

This section is for advanced system administrators who need to incorporateWindows Server 2008 (SP2 or R2) device drivers into Windows Imaging Format(WIM) files.

This appendix assumes that the system administrator is using Microsoft’s WindowsDeployment Services (WDS) to deploy the installation of Windows Server 2008 (SP2or R2) over a network.

Note – This appendix is not intended as a tutorial for WDS or Microsoft’s WindowsSystem Imaging Manager (WSIM). For detailed information about WDS or WSIM,refer to Microsoft’s WDS and WSIM documentation.

Topics in this section include:

■ “Getting Started” on page 52

■ “Location of Device Drivers on Tools and Drivers DVD” on page 52

■ “Which Device Drivers to Incorporate Into WIM Image(s)” on page 53

■ “Prerequisites and Task Overview” on page 54

■ “Procedures for Incorporating Drivers Into WIM Image(s)” on page 57

■ “Create an ImageUnattend.xml Setup Script – Windows Server 2008 (SP2 orR2)” on page 57

■ “Add Device Driver(s) to Boot WIM – Windows Server 2008 SP2 Only” onpage 62

■ “Map ImageUnattend.xml Setup Script to Windows Server 2008 (SP2 or R2)Install Image” on page 65

51

Getting StartedTopics included in this section include:

■ “Location of Device Drivers on Tools and Drivers DVD” on page 52

■ “Which Device Drivers to Incorporate Into WIM Image(s)” on page 53

■ “Prerequisites and Task Overview” on page 54

Location of Device Drivers on Tools and DriversDVDTABLE E-1 identifies the location of the device driver directories on the Tools andDrivers DVD.

Note – If you do not have a copy of the Tools and Drivers DVD, you can downloadthe ISO image for the Tools and Driver DVD. For details, see Appendix D

TABLE E-1 Device Driver Directory Location on Tools and Drivers DVD

Device Drivers Directory Location on Tools and Driver DVD

Intel Network Driver • For Windows 2008 R2:windows\W2K8R2\drivers\NIC\intel

• For Windows 2008 SP2:windows\w2K8\drivers\NIC\intel

Aspeed Driver • For Windows 2008 R2:windows\W2K8R2\drivers\display\aspeed

• For Windows 2008 SP2:windows\w2K8\drivers\display\aspeed


Which Device Drivers to Incorporate Into WIMImage(s)TABLE E-2 identifies the device drivers to incorporate in the Windows Server 2008(SP2 or R2) WIM image(s). Note, the boot WIM image identified in the table is onlyrequired for Windows Server 2008 SP2 installations, and the install WIM imageidentified in the table is required for both Windows Server 2008 SP2 and WindowsServer 2008 R2 installations.

LSI MegRAID Driver:• Sun Storage 6 Gb/s SAS PCIe RAID

HBA, SG-SAS6-R-INT-Z• Sun Storage 6 Gb/s SAS PCIe RAID

HBA, SG-SAS6-R-EXT-Z

• windows/w2k8/drivers/64bit/hba/lsi/megaraid

LSI MPT2 Driver:• Sun Storage 6 Gb/s SAS PCIe HBA,

SG-SAS6-INT-Z• Sun Storage 6 Gb/s SAS PCIe HBA,

SG-SAS6-EXT-Z

• windows/w2k8/drivers/64bit/hba/lsi/mpt2

Intel ICH10 Controller • For Windows 2008 R2:windows\W2K8R2\drivers\64bit\HBA\intel

• For Windows 2008 SP2:windows\w2K8\drivers\64bit\HBA\intel

TABLE E-1 Device Driver Directory Location on Tools and Drivers DVD (Continued)

Device Drivers Directory Location on Tools and Driver DVD

Appendix E Incorporating Device Drivers Into Windows Server 2008 WIM Images for Windows Deployment Services 53

Note – Some of the SAS PCIe HBA option cards listed in TABLE E-2 might not beavailable for purchase at the time of this publication. To determine which SAS PCIeHBA options card are supported and available for purschase on the Sun Fire X4170M2 and X4270 M2 Servers, go the one of the following Web sites, as apprpropriatefor your server model, and navigate to the appropriate page:(http://www.oracle.com/goto/x4170m2)(http://www.oracle.com/goto/x4270m2)

Prerequisites and Task OverviewPrior to creating the device driver WIM image(s) for Windows Server 2008 (SP2 orR2), ensure that the following tasks are completed in the order specified.

1. Install and configure the Windows Deployment Services on a server in yournetwork. For details, you can download Microsoft’s Windows Deployment ServicesStep-by-Step Guide at:

(http://www.microsoft.com/downloads/details.aspx?familyid=14CA18B1-B433-4F62-8586-B0A2096460EB&displaylang=en).

2. Install the Windows Automated Installation Kit (WAIK). The WAIK containsapplications to mount and modify WIM images as well as applications to createand modify XML unattended setup scripts.

TABLE E-2 Device Drivers to Add to WIM Image(s)

Device Drivers to Incorporate

Windows Server 2008 (SP2and R2)Add to install.wim

Windows Server 2008 SP2OnlyAdd to boot.wim

Intel Network Drivers X X

Aspeed Graphic Driver X

SAS PCIe HBA option installed onserver:• Sun Storage 6 Gb/s SAS PCIe

RAID HBA, SG-SAS6-R-INT-Z• Sun Storage 6 Gb/s SAS PCIe

RAID HBA, SG-SAS6-R-EXT-Z• Sun Storage 6 Gb/s SAS PCIe HBA,

SG-SAS6-INT• Sun Storage 6 Gb/s SAS PCIe HBA,

SG-SAS6-EXT-Z

X X

Intel ICH10 Controller X


Microsoft provides separate WAIK downloads for Windows Server 2008 SP2 andWindows Server 2008 R2. The URLs for these downloads are as follows:

■ Windows Server 2008 SP2 at:

(http://www.microsoft.com/downloads/details.aspx?FamilyID=94BB6E34-D890-4932-81A5-5B50C657DE08&displaylang=en)

■ Windows Server 2008 R2 at:(http://www.microsoft.com/downloads/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en)

3. Locate the Windows device drivers on the Tools and Driver DVD. For informationabout where the device drivers on the Tools and Drivers DVD are located, see“Location of Device Drivers on Tools and Drivers DVD” on page 52.

4. Establish a network-shared device driver repository. For example:

■ Create a device driver repository containing the Windows Server 2008 (SP2 orR2) device drivers.

Note that for Windows Server 2008 WDS installation environments, a devicedriver repository is provided, which you can modify. For Windows Server 2003SP2 WDS installation environments, a device driver repository is not providedand you must manually create one. The following is an example of how youmight want to set up the directory structure for a new device driver repository:

C:\unattend\drivers\{w2K8|W2k8R2}\catalogs\vendor\version

Where:

– unattend is the unattend device driver store

– drivers is the name for device driver directory

– {W2K8 or W2K8R2} is the name for Windows Server 2008 (SP2 or R2)device drivers directory

– catalogs is the name for Windows Server 2008 (SP2 or R2) catalog files

– vendor is the name of directory for device driver vendor

– version is the name of directory for device driver version

■ Ensure that the directories (folders) in the device driver repository are sharedand accessible to the Windows Deployment Services (WDS) during thenetwork installation.

For example, the device driver repository network shares referenced in thisappendix are setup as follows:

Repository Folder Network Shares

C:\Unattended\Drivers\W2K8 \\wds-server\W2K8-Drivers

C:\Unattended\Drivers\W2K8R2 \\wds-server\W2K8R2-Drivers


■ Extract the Windows Server 2008 device drivers on the Tools and Drivers DVDand place them into the device driver repository.

For details about where the Windows Server 2008 device drivers are located onthe Tools and Driver DVD, see “Location of Device Drivers on Tools andDrivers DVD” on page 52.

If you do not have a copy of the Tools and Drivers DVD, you can download theISO image for the Tools and Driver DVD. For details, see Appendix D.

The following example demonstrates the directory structure of the devicedriver repository after copying a SAS PCIe HBA driver (example versionnumber: 1.19.2.64) from the Tools and Drivers DVD to the device driverrepository:

5. Create an imageunattend.xml Setup Script for Windows Server 2008 (SP2 orR2. For details, see“Create an ImageUnattend.xml Setup Script – WindowsServer 2008 (SP2 or R2)” on page 57.

6. For Windows Server 2008 SP2 (only) installations, add the required boot devicedrivers described in TABLE E-2 to boot.wim. For details about adding the devicedrivers to the boot.wim, see “Add Device Driver(s) to Boot WIM – WindowsServer 2008 SP2 Only” on page 62.

7. Map the imageunattend.xml Setup Script to the Windows Server 2008 image.For details, see “Map ImageUnattend.xml Setup Script to Windows Server 2008(SP2 or R2) Install Image” on page 65.

8. For Windows Server 2008 SP2 and Windows Server 2008 R2 installations, add therequired device drivers described in TABLE E-2 to the install.wim image.

Operating System Tools and Driver DVD Device Driver Repository

Windows Server 2008SP2

DVDDevice:\windows\W2K8\drivers\64bit\hba\lsi\mpt2

C:\unattend\drivers\W2K8\lsi\1.19.2.64

Windows Server 2008 R2 DVDDevice:\windows\W2K8R2\drivers\64bit\hba\lsi\mpt2

C:\unattend\drivers\W2K8R2\lsi\1.19.2.64


Procedures for Incorporating DriversInto WIM Image(s)The following procedures presented are guidelines you can use to add devicedrivers to the WIM image file(s). These procedures should be performed in the orderdescribed.

■ “Create an ImageUnattend.xml Setup Script – Windows Server 2008 (SP2 orR2)” on page 57

■ “Add Device Driver(s) to Boot WIM – Windows Server 2008 SP2 Only” onpage 62

■ “Map ImageUnattend.xml Setup Script to Windows Server 2008 (SP2 or R2)Install Image” on page 65

Before you BeginPrior to performing the procedures in this section, you should ensure that all theprerequisites as described in “Prerequisites and Task Overview” on page 54 havebeen met.

▼ Create an ImageUnattend.xml Setup Script –Windows Server 2008 (SP2 or R2)Follow these steps to create an ImageUnattend.xml Setup Script for a WindowsServer 2008 (SP2 or R2) installation. After the setup script is generated, it will besaved to the device driver repository.

Note – The ImageUnattend.xml Setup Script (in a later procedure described inthis section) will be mapped to a Windows Server 2008 (SP2 or R2) install image.After the setup script is mapped to the install image, the install image will install thespecified device drivers during the Windows Server 2008 (SP2 or R2) networkinstallation.

1. Insert the Windows Server 2008 (SP2 or R2) DVD media into the DVD reader ofthe system that is hosting the Windows Deployment Services.


2. Copy all the Windows Server 2008 (SP2 or R2) catalog files into the Catalogsfolder of the device driver repository.

For example:

copy DVDDrive:\source\*.clg C:\Unattend\Drivers\{WSK8|W28R2}\Catalogs

3. Launch the Windows System Manager application and create a newImageUnattend.xml Setup Script by doing the following:

a. Click Start-->All Programs -->Microsoft Windows AIK -->WindowsSystem Image Manager.

b. In the Answer File pane, right-click and select New Answer File.

c. If a message dialog appears asking to open a new Windows image now, clickNo.

4. Do the following to specify the Windows Server 2008 (SP2 or R2) Catalog filethat matches the Windows Server 2008 (SP2 or R2) edition (Standard,Datacenter, or Enterprise) that you are installing:

a. In the Windows Image pane, right-click and select Select WindowsImage.

b. In the Files Type list box, select Catalog files (*.clg), then click Browse tospecify the Catalogs folder in the device driver repository.

Ensure that you select the Catalog file that matches the Windows Server 2008(SP2 or R2) edition you are installing.

For example, for Windows Server 2008 SP2 Datacenter, select:

C:\Unattend\Drivers\{W2K8|W2K8R2}\Catalogs\install_Windows_Server_2008_SERVERDATACENTER.clg


5. Do the following to set the component packages topass 2 offlineServing.

a. In the Windows Image pane, click and expand thearchitecture_Microsoft-Windows-PnPCustomizationNonWinPE_version.

b. Right -click PathAndCredientials and select Add Setting to Pass 2OfflineServing.


6. Repeat Step 5 for each device driver you want installed during the WindowsServer 2008 (SP2 or R2) installation.

Refer to TABLE E-2 for the list of device drivers to include in the install.wimfile.

7. Do the following to specify an installation key value.

a. In the Answer File pane, click and expand2 offlineServicing,architecture_Microsoft-Windows-PnPCustomizationsNonWinPE_version.

b. Click and expand PathAndCredentials and enter a sequence key value aswell as the UNC device driver path in the repository.

For example, to add the device driver for the Sun Storage PCIe SAS RAID HBAoption, enter:

Key 1

Path \\wds-server\W2K8-Drivers\Lsi\1.19.2.64


c. In the Credential section for each PathAndCredentials component, clickand expand the component to insert the UNC domain, logon, and password(if required), which allow access to the device drivers stored in therepository.

For example:

d. Repeat Steps 7a through 7c for each device driver you want installed duringthe Windows Server 2008 (SP2 or R2) installation.

8. Validate the ImageUnattend.xml file using the Windows System ImageManager application:

■ In the Windows System Image Manager application, click the Tools menuand select Validate Answer File.

A message appears in the Message pane indicating that No Warnings or Errorsare found.

Domain UNC_domain

Password UNC_password

Username UNC_username


9. Save the .xml Setup Script as ImageUnattend.xml using the WindowsSystem Image Manager application:

a. In the Windows System Image Manager application, click the File menuand select Save Answer File as.

b. Save the .xml Setup Script in the device driver repository as:

c:\Unattend\Drivers\W2K8\Catalogs\ImageUnattend.xml

c. Exit the Windows System Image Manager application.

10. The creation of the ImageUnattend.xml Setup Script is complete, proceed toone of the following:

■ For Windows Server 2008 R2 installation, proceed to “MapImageUnattend.xml Setup Script to Windows Server 2008 (SP2 or R2) InstallImage” on page 65.

■ For Windows Server 2008 SP2 installations, proceed to “Add Device Driver(s)to Boot WIM – Windows Server 2008 SP2 Only” on page 62 prior to mappingthe ImageUnattend.xml Setup Script to the install.wim image.

▼ Add Device Driver(s) to Boot WIM – Windows Server2008 SP2 Only

Note – If you are performing a Windows Server 2008 R2 installation, skip thisprocedure. Device drivers are not required at boot time for Windows Server 2008 R2installations.

For Windows Server 2008 SP2 installations only, perform the following steps to addthe appropriate PCIe SAS HBA LSI device driver (MegaRAID or MPT2) to theboot.wim image. Note that if the required PCIe SAS HBA device driver (asdescribed in TABLE E-1 and TABLE E-2) is not added to the boot.wim image, theWindows Server 2008 SP2 installation will fail.

1. Insert the Windows Server 2008 SP2 DVD media into the DVD reader of thesystem that is hosting the Windows Deployment Services.

2. Perform the following to launch the Windows Deployment ServicesAdministration tool and import the Windows Server 2008 SP2 Boot WIM.

a. Click Start -->All Programs -->Windows Deployment Services.

b. Right-click Boot Images and select Add a Boot Image, then click Browseto specify the Windows Server 2008 SP2 boot WIM file.

For example: DVDDrive:\sources\boot.wim


c. Click Open then Next.

3. To import the Windows Server 2008 SP2 boot image, click Next twice thenclick Finish.

4. Disable the Windows Server 2008 SP2 boot WIM using the WindowsDeployment Services Administration:

■ Click and expand Boot Images, right-click Microsoft Windows Server(Setup)x64, then select Disable.

5. Launch and run the Deployment Tools Command Prompt as Administrator.

For example:

■ Click Start-->All Programs-->Microsoft Windows AIK, thenright-click Deployment Tools Command Prompt, and select Run asAdministrator.


6. In the Deployment Tools Command Prompt, perform the following:

a. Use the mkdir command to create a temporary directory mount point tomount the Windows Server 2008 SP2 boot WIM image.

For example:

mkdir C:\Mnt

b. Use the cd command to change the directory to the folder containing theWindows Server 2008 SP2 boot WIM.

For example:

cd DVDDrive:\RemoteInstall\Boot\x64\images

c. Use the imagex command to mount the Windows Server 2008 SP2 boot WIMwith read/write permissions to the temporary directory mount point.

For example:

imagex /mountrw boot.wim 2 C:\Mnt

d. Use the cd command to change the directory to the device driver repositorycontaining the Windows Server 2008 SP2 device driver for the Sun Storage 6Gb/s SAS PCIe RAID HBA option (SG-SAS-R-INT-Z or SG-SAS-R-EXT-Z):

For example, to change to the directory containing the LSI device driver for theSun Storage 6 Gb/s SAS PCIe RAID HBA option (SG-SAS-R-INT-Z orSG-SAS-R-EXT-Z), type:

cd C:\Unattend\Drivers\W2K8\lsi\1.19.2.64


e. Use the peimg command to add the LSI MegaRAID device driver for theSun Storage 6 Gb/s SAS PCIe RAID HBA option (SG-SAS-R-INT-Z orSG-SAS-R-EXT-Z) to the Windows Server 2008 SP2 boot WIM image.

For example, to add the LSI MegaRAID device driver for the Sun Storage 6Gb/s SAS PCIe RAID HBA option (SG-SAS-R-INT-Z or SG-SAS-R-EXT-Z),type:

peimg /INF=*.inf C:\Mnt\Windows

f. Repeat Steps 7d and 7e for each additional device driver (as described inTABLE E-2) that is required in the boot WIM image:

■ Sun Storage 6 Gb/s SAS PCIe HBA option (SG-SAS-INT-Z orSG-SAS-EXT-Z).

■ Intel Network Driver

g. Use the imagex command to unmount and commit the modified WindowsServer 2008 SP2 boot WIM image.

For example:

imagex /unmount/commit C:\Mnt

7. To enable the Windows Server 2008 SP2 boot WIM image, do the following.

a. Launch the Windows Deployment Services administration tool.

Click Start-->All Programs-->Windows Deployment Services.

b. In the Windows Deployment Services (WDS) Administration tool, click andexpand Boot Images.

c. Right-click Microsoft Windows Server (Setup) x64 and select Enable.

8. The modifications to include the device drivers into the boot.wim image arecomplete, exit the Deployment Tools Command Prompt and the WDSAdministration tool, then proceed to “Map ImageUnattend.xml Setup Scriptto Windows Server 2008 (SP2 or R2) Install Image” on page 65.

▼ Map ImageUnattend.xml Setup Script to WindowsServer 2008 (SP2 or R2) Install ImageFollow the steps in this procedure to map the ImageUnattend.xml Setup Script(created in an earlier procedure in this section) to the Windows Server 2008 (SP2 orR2) install.wim.

1. Insert the Windows Server 2008 SP2 DVD media into the DVD reader of thesystem that is hosting the Windows Deployment Services.


2. Perform the following to launch the Windows Deployment ServicesAdministration tool and import the Windows Server 2008 SP2 install WIM.

a. Click Start-->All Programs-->Windows Deployment Services.

b. Right-click Install Images and select Add Install Image.

Note that if no image groups exist, create a new image group named WindowsServer 2008 SP2 or Windows Server 2008 R2 and click Next.

c. Click Browse to select the Windows Server 2008 SP2 Install WIM imagelocated at: DVDDrive:\sources\install.wim; then proceed by clickingOpen then Next.

d. Select the Windows Server 2008 (SP2 or R2) edition (Data Center, Standard,or Enterprise) to import into Windows Deployment Services, then clickNext.


e. To import the specified Windows Server 2008 (SP2 or R2) edition installimage, click Next twice, then click Finish.

3. Launch the Deployment Tools Command Prompt as Administrator, forexample:

■ Click Start-->All Programs-->Microsoft Windows AIK, thenright-click Deployment Tools Command Prompt, and select Run asAdministrator.

4. In the Deployment Tools Command Prompt, perform the following:

a. Use the cd command to change the directory to the folder containing theWindows Server 2008 SP2 install WIM image.

For example, the Windows Server 2008 SP2 Datacenter (x64) edition WIMimage would be located at:

cd Drive:\RemoteInstall\images\Windows Server 2008 SP2

b. Use the mkdir command to create a directory with the exact same spellingand case as the imported Windows Server 2008 (SP2 or R2) WIM image.

mkdir install

Note – Selecting the defaults when importing the install image for Windows Server2008 (SP2 or R2) will create an installation WIM file called install.wim.


c. Use the cd command to change the directory to the imported WindowsServer 2008 (SP2 or R2) folder, then use the mkdir command to create anUnattend directory.

For example:

cd install

mkdir Unattend

d. Use the cd command to change the directory to the Unattend directory, thenuse the copy command to copy the ImageUnattend.xml Setup Script(created in an earlier procedure in this appendix) to the Unattend directory.

For example:

cd Unattend

copy C:\Unattend\Drivers\{W2K8|W2k8R2}\Catalogs\ImageUnattend.xml

5. Perform the following steps to open the Windows Server 2008 (SP2 or R2)image properties.

a. Launch the Windows Deployment Services Administration tool.

Click Start-->All Programs-->Windows Deployment Services.

b. In the Windows Deployment Services (WDS) Administration tool, click andexpand the Windows Server 2008 (SP2 or R2) image group.

c. Right-click Microsoft Windows Server (SP2 or R2) and selectProperties.

6. Perform the following steps to map the ImageUnattend.xml Setup Script tothe Windows Server 2008 (SP2 or R2) image.

a. In the General Tab of the Windows Server 2008 (SP2 or R2) image properties,check Allow image to install in unattended mode and clickSelect File.

b. Browse to the following location (specified in Step 4d) then click OK.

Drive:\RemoteInstall\images\{W2K8|W2K8R2}\install\Unattend\ImageUnattend.xml


c. Click OK to map the ImageUnattend.xml Setup Script to the WindowsServer 2008 (SP2 or R2) WIM image.

The Windows Server 2008 (SP2 or R2) WIM image is ready to be installed usingWindows Deployment Services.

d. Exit the Deployment Tools Command Prompt and the Windows DeploymentServices Administration tool.

7. To deploy the Windows Server 2008 (SP2 or R2), refer to the followingprocedure:

“Install Windows Server 2008 (SP2 or R2) Using PXE” on page 26.



Index

BBIOS

defaults for new installations, 45view or edit BIOS settings, 46

Ddevice drivers

location on Tools and Drivers DVD, 52

post installation, 28

prerequisite, 9

SAS PCIe HBAs requiring drivers, 11

IInstall Boot Media, 37installation

using local or remote media, 14

using PXE network boot, 25installation methods

boot media options, 37

console outputs, 35

installation targets, 40installation targets

, 40overview

, 35

Intel NIC teaming configurationpost installation

, 31

Ooperating systems supported

, 41

Ppost installation tasks

configuring Intel NIC teaming, 31configuring TPM, 31install device drivers, 28installing supplemental software, 29overview, 27

SSIA, 4

install and recovery tasks, 4

overview, 3

software download URL, 4

supplemental softwarepost installation, 30

support and training, ix

TTools and Driver DVD

device driver locations, 52download, 49

71

TPM configurationpost installation, 31

trainingwhere to find, x

WWindows Deployment Services

boot WIM driver procedure, 62create imageunattend.xml script, 57device drivers for WIM images, 54device drivers on Tools and Driver DVD, 52getting started, 52install WIM driver procedure, 57map imageunattend.xml script, 65network install overview, 51procedures, 57task overview, 54

Windows Server 2008before you begin, 13installation considerations, 9installation overview tasks, 10media installation, 14PXE network installation

, 25

supported operating systems, 8


Documents

Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide ... · PDF fileSun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Windows Operating Systems Part No. 821-0484-11