Bigdata - Moonshot m400

Operating System Deployment on HP
ProLiant Moonshot Server Cartridges

User Guide
Abstract
This document provides the procedures for installing Microsoft Windows or Linux on the HP ProLiant m800, HP ProLiant m710,
HP ProLiant m700, HP ProLiant m400, HP ProLiant m350, and HP ProLiant m300 server cartridges in a Moonshot 1500 chassis.
The Windows section describes the installation of Microsoft Windows Server and Microsoft Windows client in a network based
installation. It also includes an example of using Microsoft Windows Deployment Services. The Linux section describes the
installation of RHEL, Ubuntu and SLES, including an example RHEL server installation.
HP Part Number: 742543-003b

Published: January 2015
Edition: 1
© Copyright 2013, 2015 Hewlett-Packard Development Company, L.P.
Notices
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor’s standard commercial license.
Acknowledgements
Microsoft®, Windows®, and Windows Server® are U.S. registered trademarks of the Microsoft group of companies.
UNIX® is a registered trademark of The Open Group.
UBUNTU®, CANONICAL®, and JUJU® are registered trademarks of Canonical Ltd.
SUSE® is a registered trademarks of SUSE LLC in the United States and other countries.
RED HAT® and ENTERPRISE LINUX® are registered trademarks of Red Hat, Inc. in the United States and other countries.
Contents
1 Introduction...............................................................................................6
Overview................................................................................................................................6
Related documentation and videos..............................................................................................6
Supported platforms and operating systems.................................................................................8
2 Microsoft Windows preparation and deployment............................................9
Customizing a Windows image for Moonshot..............................................................................9
Deployment infrastructure......................................................................................................9
Prerequisites......................................................................................................................11
Enabling Windows Emergency Management Services (EMS)...................................................12
About the HP Moonshot Windows Deployment Pack (HP MWDP).............................................14
Using the HP MWDP to customize a Windows image for HP Moonshot server cartridge nodes....16
Example deployment using Microsoft Windows Deployment Services (WDS)..................................18
Deploying the Windows image............................................................................................19
Adding boot images for ProLiant Moonshot server cartridges..............................................19
Enabling EMS in Boot Configuration Data files..................................................................22
Adding install images for ProLiant Moonshot server cartridges.............................................24
Customizing sample XML unattend files............................................................................25
Example HP ProLiant m300 server cartridge installation with Windows Server 2012 R2.....26
Configuring pre-staged devices.......................................................................................27
Deploying an image using WDS.....................................................................................31
First phase installation (WinPE boot)...........................................................................34
Second phase..........................................................................................................36
Check installation (login)...........................................................................................37
Capturing a custom Windows image....................................................................................37
Prerequisites.................................................................................................................37
Preparing answer files....................................................................................................38
Creating a WinPE capture image....................................................................................39
Preparing the reference node using sysprep......................................................................41
Capturing the golden image and uploading it to the WDS store..........................................42
Deploying the captured golden image.............................................................................43
Tips and best practices for Windows OS deployment..................................................................43
Basic image and WDS troubleshooting.................................................................................44
3 Linux preparation and deployment..............................................................46
Setting up a network installation server......................................................................................46
Installation server requirements and base configuration...........................................................46
Installation server components.............................................................................................48
Configuring DHCP service...................................................................................................48
TFTP server configuration....................................................................................................49
HTTP server for OS installation files......................................................................................49
OS installation files............................................................................................................49
RHEL (CentOS, Scientific Linux, Fedora)............................................................................50
Ubuntu........................................................................................................................50
SLES............................................................................................................................50
PXE boot files....................................................................................................................51
RHEL...........................................................................................................................51
Ubuntu........................................................................................................................51
SLES............................................................................................................................52
PXE configuration files........................................................................................................52
Preparing to install Linux on HP ProLiant m710 server cartridges...............................................53
RHEL 6.5.....................................................................................................................53
Contents 3
Update the PXE configuration.....................................................................................54
Preparing to install other Linux operating systems...............................................................54
Preparing to reinstall Ubuntu on HP ProLiant m400 and m800 server cartridges.........................54
Downloading ARM-based Ubuntu 14.04.1 installation files.................................................54
Update the PXE configuration..........................................................................................55
Performing an interactive Linux installation..................................................................................56
Managing your cartridge node............................................................................................57
Configuring a node to boot from the network....................................................................57
Controlling a server node’s power state............................................................................57
Performing an automated Linux installation.................................................................................58
Automatic installation configuration files................................................................................58
RHEL...........................................................................................................................58
Update the Kickstart configuration for the HP ProLiant m710 server cartridge....................59
Ubuntu........................................................................................................................59
SLES............................................................................................................................60
PXE configuration...............................................................................................................60
Server-specific PXE configuration files...............................................................................61
Moonshot and traditional network installation co-existence.................................................62
Post deployment.....................................................................................................................62
Installing MCSDK-HPC on HP ProLiant m800 server cartridge nodes.........................................64
Preparing to fetch TI packages from PPA...........................................................................64
Installing MSCSDK-HPC.................................................................................................64
Verifying installation......................................................................................................64
Installing MAAS support on HP ProLiant m400 and m800 server cartridge nodes......................65
4 Support and other resources......................................................................66
Information to collect before contacting HP.................................................................................66
How to contact HP..................................................................................................................66
Security bulletin and alert policy for non-HP owned software components......................................66
Registering for software technical support and update service.......................................................66
How to use your software technical support and update service...............................................67
HP authorized resellers............................................................................................................67
Subscription service................................................................................................................67
Typographic conventions.........................................................................................................67
A Frequently used Windows EMS commands..................................................69
EMS Commands.....................................................................................................................69
SAC commands......................................................................................................................69
Channel-management commands.............................................................................................70
B Microsoft Windows Deployment Services installation.....................................71
WDS requirements..................................................................................................................71
Installing WDS..................................................................................................................72
Installing the WDS role on the system..............................................................................72
Configuring WDS.........................................................................................................73
Configuring the WDS server in stand-alone mode.........................................................73
First time configuration..............................................................................................74
Adding Windows media images to the WDS store............................................................74
C Sample WDScapture.inf file entries.............................................................76
D Enabling EMS in the Windows Recovery Environment (WinRE).......................77
Enabling EMS in the WinRE bootloader from a running operating system......................................77
Programmatically enabling EMS in the WinRE bootloader during Windows installation...................77
Detecting WinRE environment at SAC on boot............................................................................77
4 Contents
E Preseed template for non-ARM based server cartridges..................................79
F Preseed template for ARM based server cartridges........................................80
G SLES configuration file..............................................................................81
Glossary....................................................................................................84
Index.........................................................................................................85
Contents 5
1 Introduction
This document covers the deployment of the Windows and Linux Operating Systems on HP ProLiant
Moonshot Server Cartridges. The document uses Microsoft Windows Server Deployment Services
(WDS) as an example for deploying Microsoft Windows on HP ProLiant Moonshot server cartridges.
It also covers the preparation of a Linux PXE server to deploy Linux to HP ProLiant Moonshot server
cartridges. HP offers the HP Insight Cluster Management Utility (CMU) as an alternative for
large-scale image deployments but this alternative is not discussed here. See the information on
HP Insight CMU features and links to technical documentation, Quickspecs, and a product demo
at http://www.hp.com/go/cmu.
A basic knowledge of the HP Moonshot iLO chassis management firmware (Moonshot iLO CM
firmware) as a single point of access to the chassis is required. The HP Moonshot chassis does not
have a keyboard, pointing device, console, DVD or USB ports. Therefore, all interaction with the
system is done using either serial ports or the network. The installation examples in this guide are
through a network using Pre-boot execution Environment (PXE), in addition, current HP Moonshot
cartridges only support local disk boot, they do not support SAN boot.
This document assumes that the HP Moonshot 1500 Chassis is ready for the OS, has been updated
to the latest firmware, and meets the specific requirements for a network based Microsoft Windows
and Linux operating system installation. The focus here is on PXE boot for both Linux and Windows
environments. Windows installations include instructions to specifically modify Windows images
for cases where there is a lack of in-box driver support. Examples will show configuration, updates,
and operation for the HP Moonshot server via CLI, and remote serial console access using a secure
Virtual Serial Port (VSP).
Overview
This guide includes the following information:
• “Related documentation and videos” (page 6) where you can find more detailed information
or visualize what is described in this manual.
• “Supported platforms and operating systems” (page 8)
• “Microsoft Windows preparation and deployment” (page 9) includes Microsoft Windows
operating systems installation procedures on the HP Moonshot ProLiant Server m300 series
and m700 series server cartridges, and information on additional tools provided by HP that
support the installation.
• “Linux preparation and deployment” (page 46) describes the environment prerequisites,
preparation, and configuration needed to successfully deploy Linux from a Linux PXE server
to HP Moonshot ProLiant servers, based on an example that uses RHEL on the deployment
server.
• Appendices covering the following:
◦ “Frequently used Windows EMS commands” (page 69)
◦ “Microsoft Windows Deployment Services installation” (page 71)
◦ “Sample WDScapture.inf file entries” (page 76)
◦ “Enabling EMS in the Windows Recovery Environment (WinRE)” (page 77)
Related documentation and videos

The HP Moonshot Information Library at http://www.hp.com/go/moonshot/docs is a task-based
repository that includes installation instructions, user guides, maintenance and service guides, best
practices, videos, and other useful links. Use this website to obtain the latest documentation.
6 Introduction
The following table gives links to HP documentation and Microsoft reference guides, including
downloads to help with deployments. HP does not control and is not responsible for information
that is not hosted on HP websites.
Description Location
HP Moonshot Information Library http://www.hp.com/go/moonshot/docs
Video: Updating Firmware on HP Moonshot (ProLiant m300 http://h20324.www2.hp.com/SDP/Content/

example) ContentDetails.aspx?ID=4216
Video :Deploying Microsoft Windows on HP Moonshot http://h20324.www2.hp.com/SDP/Content/

(ProLiant m300 example using MS Windows Deployment ContentDetails.aspx?ID=4214
Services)
Video: Deploying Linux on HP Moonshot (ProLiant m300 http://h20324.www2.hp.com/SDP/Content/

example) ContentDetails.aspx?ID=4215
Operating System Deployment on HP ProLiant Moonshot http://www.hp.com/support/moonshot_os_deployment_en

Servers User Guide
Windows Deployment Services Getting Started Guide for http://technet.microsoft.com/en-us/library/jj648426.aspx

Windows Server 2012
Windows Assessment and Deployment Kit (Windows ADK) http://www.microsoft.com/en-us/download/details.aspx?

for Windows 8 id=30652
Windows Assessment and Deployment Kit (Windows ADK) http://www.microsoft.com/en-us/download/details.aspx?

for Windows 8.1 id=39982
Unattend Windows Setup Reference http://technet.microsoft.com/en-us/library/ff699026.aspx
DISM How-to Topics (Deployment Image Servicing and http://technet.microsoft.com/en-us/library/

Management) hh825176.aspx
PuTTY Download Page http://www.chiark.greenend.org.uk/~sgtatham/putty/

download.html
BCDedit command (Windows Dev Center) http://msdn.microsoft.com/en-us/windows/

ff542202(v=vs.71).aspx
Microsoft EMS and SAC reference technet.microsoft.com/en-us/library/

cc786105(v=ws.10).aspx
Using Windows PowerShell http://technet.microsoft.com/en-us/library/

dn425048.aspx
Common Management Tasks and Navigation in Windows http://technet.microsoft.com/en-us/library/

Server 2012 R2 and Windows Server 2012 hh831491.aspx
Windows Recovery Environment (Windows RE) http://technet.microsoft.com/en-us/library/

cc765966(v=ws.10).aspx
Windows RE technical reference for Windows Server 2012 http://technet.microsoft.com/en-us/library/

and 2012 R2 hh825051.aspx
Related documentation and videos 7

Supported platforms and operating systems
Table 1 HP Moonshot ProLiant server cartridges and supported OS and version
Cartridge CPU Architecture Microsoft Client OS Microsoft Server OS Linux OS (min. level)
HP ProLiant Intel Atom N/A • Red Hat Enterprise Linux

m300 Server Processor C2750 • Microsoft 6.5 with Errata Kernel1
Cartridge single node Windows Server
• SUSE Linux Enterprise
2012
HP ProLiant Intel Atom Server 11 SP3 with
m350 Server Processor C2730 • Microsoft kISO
Cartridge quad nodes Windows Server
• Ubuntu 12.04.4
2012 R2
• CentOS 6.52
HP ProLiant AMD Opteron • Microsoft Windows 7 • Microsoft N/A

m700 Server X2150 APU quad Enterprise with Service Windows Server
Cartridge nodes Pack 1 (x64) 2012
• Microsoft Windows 7
Professional with Service
Pack 1 (x64)
Enterprise with Service
Pack 1 (x86)
Professional with Service
Pack 1 (x86)
• Microsoft Windows 8.1
Enterprise (x64)
• Microsoft Windows 8.1
Professional (x64)
HP ProLiant Intel Xeon E3- N/A • Microsoft • Red Hat Enterprise Linux
m710 Server 1284Lv3 with Intel Windows Server 6.5 with Errata Kernel
Cartridge Iris Pro 5200 2012 and DUP
“GT3e” GPU
• Microsoft • RHEL7
Windows Server
• SUSE Linux Enterprise
2012 R2
Server 11 SP3 with
kISO
• Ubuntu 14.04
HP ProLiant TI Keystone 32-bit N/A N/A Ubuntu 14.04.1

m800 Server ARM + DSP quad (Preinstalled)
Cartridge nodes
HP ProLiant APM 64-bit ARM N/A N/A

m400 Server single node
Cartridge
1
This server requires minimum of kernel 2.6.32-431.1.2.el6.x86_64 from Red Hat
2
This server requires minimum of the CentOS equivalent to errata kernel 2.6.32-431.1.2.el6.x86_64 from Red Hat
NOTE: The OS support matrix is updated often. See the most up to date information at:
http://h17007.www1.hp.com/us/en/enterprise/servers/management/operating-environments/
index.aspx
Throughout this document, Microsoft Windows 7 with Service Pack 1 is referenced to enhance
readability. Assume these references include both Microsoft Windows 7 Enterprise with Service
Pack 1 and Microsoft Windows 7 Professional with Service Pack 1 (x86 and x64) support.
8 Introduction
2 Microsoft Windows preparation and deployment
Key windows drivers are required for HP ProLiant Moonshot servers. A network based installation
method is required to deploy HP Moonshot Server cartridge nodes, which includes the need for a
deployment server. Each node console can be accessed using the HP iLO Virtual Serial Port (VSP)
which is a feature of the HP Moonshot iLO CM firmware. An SSH connection is established to the
node and allows headless access to the Windows environment.
Customizing a Windows image for Moonshot

To deploy Windows, add an HP Moonshot Windows Deployment Pack (MWDP) to the images
that you are using with your deployment server. This facilitates Windows deployment, since some
components might not be included in the Windows setup images. The following HP Software
download packages are available:
• HP Moonshot Windows Deployment Pack (HP MWDP) for HP ProLiant m300 and m350 server
cartridge
• HP Moonshot Windows Deployment Pack (HP MWDP) for HP ProLiant m700 server cartridge
• HP Moonshot Windows Deployment Pack (HP MWDP) for HP ProLiant m710 server cartridge
The download packages contain software drivers, scripts, sample unattend files, and read me files.
Download a package from:
http://www.hp.com/support/moonshot/1500chassis-software-download.
There are additional packages (provided as HP Smart Components) you must use to install drivers
after Windows is installed:
• The AMD Catalyst package for Microsoft Windows which includes the AMD graphics driver
for the ProLiant m700 server cartridge
• The HP ProLiant m710 Intel Iris Pro 5200 integrated graphics processor driver for the ProLiant
m710 server cartridge
• A Mellanox network driver update for the HP ProLiant m710 Mellanox
These drivers are available from the HP support page at http://www.hp.com/support. On the
support page, choose your country (if needed). Click Drivers and Downloads and enter a search
term (for example, ProLiant m700.)
The main steps required to customize your Windows image include the following:
1. Add appropriate drivers to a Windows image.
NOTE: This step is unnecessary for the HP ProLiant m710 server cartridge since the drivers
included in the Windows image. Remember to check for any updates to these drivers after
Windows installation is complete.
2. Modify Windows boot entries to enable headless access.

3. Customize unattend files for automated installation.
HP created a video that steps through the Windows deployment steps found in this guide. HP
recommends viewing the Windows deployment training video before starting a Windows
deployment. Download the video at:
http://h20324.www2.hp.com/SDP/Content/ContentDetails.aspx?ID=4214
Deployment infrastructure
The architectural design of the HP Moonshot system is unique; the environment relies on networking
components with client/server deployment services. Installing the Windows operating system
requires PXE boot with headless support.
Customizing a Windows image for Moonshot 9

Table 2 Required components
Networking components
Windows Deployment Server The deployment server must:

(PXE boot server) • Be accessible from the network
• Store operating system images
• Store unattend files containing image and server specific information
• Store scripts
• Store drivers
• Transfer software components to servers over the network
• Respond to PXE client requests
• Execute the network boot program
DHCP server The DHCP server is responsible for providing TCP/IP based network devices (deployed
servers) with valid IP addresses. The DHCP role can be provided by the deployment
server or can be a standalone server, depending your on network infrastructure and
topology.
DNS server The DNS server allows name resolution in a TCP/IP based network environment.
Server cartridges (PXE clients) Cartridge types:

to deploy • HP ProLiant m710 server cartridge
• HP ProLiant m700 server cartridge
Technician computer to drive The technician computer enables remote access to the cartridge via SSH over the iLO
deployment VSP to manage deployment, and is usually used to access the deployment console.
Network infrastructure By default, all cartridges are configured for the default VLAN and need to be configured
to allow PXE clients to connect to the deployment server, obtain IP addresses and make
DNS requests.

Figure 1 Example deployment infrastructure
1. Technician computer Workstation used for HP Moonshot system management and as a deployment console
2. Deployment server Provides PXE server, DHCP/DNS, and storage for OS images, drivers, scripts, and
unattend files
3. HP Moonshot System Contains PXE clients to be deployed
Prerequisites
As shown in Figure 1 (page 11), operating systems are installed through the network using a PXE
server. HP recommends the following for a successful installation:
• Infrastructure
◦ HP Moonshot 1500 Chassis installed and configured.
– Ensure the latest firmware is installed.
– The latest HP Moonshot Component Pack is available for download at http://
www.hp.com/go/moonshot/download.
◦ Networks must be configured to allow a Windows network based installation (PXE

deployment server, DHCP and DNS servers, firewall, VLAN, and so on.)

◦ A Technician computer to perform the deployment.
◦ A user account authorized to perform deployment.

• Software
◦ Microsoft Windows Operating System ISO images (or product DVD) and licenses, from
which you must extract the following:
– boot.wim containing a Windows PE image setup.
– install.wim containing the Windows Operating System image for installation.
◦ Download the appropriate HP Moonshot Windows Deployment Pack (HP MWDP) from
http://www.hp.com/support/moonshot/1500chassis-software-download
– The HP Moonshot Windows Deployment Pack (HP MWDP) for HP ProLiant m300
and m350 server cartridges, if deploying an m300 and m350 server cartridges.
server cartridge, if deploying m700 server cartridges.
server cartridge, if deploying m710 server cartridges.
◦ A terminal emulator such as PuTTY to connect to the iLO CM of the Moonshot 1500
Chassis using SSH.
◦ Windows Assessment and Deployment Kit (ADK)
ADK contains deployment tools such as the Deployment Imaging Servicing and
Management (DISM) command line tool, DISM PowerShell cmdlets, Windows System
Image Manager (Windows SIM), and so on. ADK is provided as a free download from
the Microsoft download site. DISM can be used to modify WIM files; Windows SIM is a
GUI based utility used to create and modify unattend.xml files.
– ADK 8 provides support for Windows 7 with SP1 and Windows Server 2012 (http://
www.microsoft.com/en-us/download/details.aspx?id=30652).
– ADK 8.1 is the minimum required version for Windows Server 2012 R2 and Windows
8.1, and supports Windows 7 with SP1 as well as Windows Server 2012 (http://
www.microsoft.com/en-us/download/details.aspx?id=39982)
IMPORTANT: HP recommends that you run at least the minimum version of ADK
that matches the OS you are deploying. The minimum version supported is ADK 8.
Versions are backward compatible and often new operating systems bring features
requiring a minimum version to fully support the latest changes, so it is good practice
to use the latest version.
Enabling Windows Emergency Management Services (EMS)

Windows EMS provides remote management and system recovery options when other server
administrative options are not available; it is also necessary for headless systems where there is
no keyboard, video, mouse or iLO Remote Console available. EMS capability is supported on
Moonshot and implemented through the iLO VSP of each node.
EMS uses the Special Administration Console (SAC) feature of Windows Server. The SAC can be
used to manage the server during Windows deployment and runtime operations. Additionally, the
SAC provides administrative capability such as the viewing or setting of the OS IP address, shutting
down and restarting of the OS, viewing a list of currently running processes, and opening a
command shell (cmd.exe) interface to the OS. EMS functionality is available during a node’s PXE
boot using built-in Windows boot programs allowing the user to interact with the PXE boot process,

as well as selecting from a menu of different boot programs. This functionality must be enabled on
the PXE boot server such as WDS prior to deploy HP ProLiant Moonshot nodes.
To enable EMS redirection on a WDS server, modify two boot configuration data files (BCD files)
using the Windows BCDEdit.exe utility:
On 64-bit systems:
• %Path%\RemoteInstall\Boot\x64\default.bcd
• %Path%\RemoteInstall\Boot\x64\images\boot-(#).wim.bcd
On 32-bit systems:
• %Path%\RemoteInstall\Boot\x86\default.bcd
• %Path%\RemoteInstall\Boot\x86\images\boot-(#).wim.bcd
Enabling OS deployment and runtime support of EMS requires several changes to the BCD files.
Enter the BCDedit commands at an elevated command prompt using the Windows command shell
(a command prompt window started with administrative privileges using “Run as Administrator”).
NOTE: Installing Windows ADK on Windows Server 2012 and 2012 R2 creates a shortcut tile
for Administrators named Deployment and Imaging Tools Environment which you can also use to
start an administrator-level command prompt to enter BCDedit commands:
Modifying BCD files to enable EMS

1. In the \RemoteInstall\Boot\x86\images\ or \RemoteInstall\Boot\x64\images\
enter the following commands:
a. >bcdedit.exe /store .\boot-(#).wim.bcd /enum /v
This lists boot entries from the BCD store (in this case boot-(#).wim.bcd) and helps
identify the Windows Boot Loader identifier.
b. >bcdedit.exe /store .\boot-(#).wim.bcd /set {GUID} bootems on
This option enables Emergency Management Services (EMS) for the specified boot entry
in a BCD store (boot-(#).wim.bcd).
c. >bcdedit.exe /store .\boot-(#).wim.bcd /set {GUID} ems on
This option enables Emergency Management Services (EMS) for the specified operating
system boot entry in a BCD store (boot-(#).wim.bcd).
d. >bcdedit.exe /store .\boot-(#).wim.bcd /set {GUID} novga on
This option disables the use of VGA modes in the OS. The option is available starting in
Windows 8 and Windows Server 2012.
IMPORTANT: The novga option does not apply to Windows 7. Do not use it for ProLiant
m700 server cartridge deployments with Windows 7 with SP1 (regardless of architecture).
The option is available in Windows 8 and Windows Server 2012 and later versions.

2. In the \RemoteInstall\Boot\x64\ or \RemoteInstall\Boot\x86\ directory, enter
the following command:
>bcdedit.exe /store .\default.bcd /set {bootmgr} bootems on
This command enables EMS for the default boot manager.
NOTE: This is not valid PowerShell syntax. See Microsoft PowerShell documentation for proper
BCD editing methods.
As mentioned, EMS support during the PXE boot phase allows the user to select from a list of boot
images installed on the WDS server as shown in the figure below.
Figure 2 Windows Boot Manager from an HP Moonshot Server cartridge — booted over the network
to a WDS Server
See “Adding boot images for ProLiant Moonshot server cartridges” (page 19) for complete
instructions.
About the HP Moonshot Windows Deployment Pack (HP MWDP)

To deploy Microsoft Windows on HP ProLiant Moonshot server cartridges, HP provides software
bundles called HP Moonshot Windows Deployment Packs (HP MWDP).
HP ProLiant Moonshot servers are headless, and do not have USB connectivity. Therefore, it is
critical that the network interface(s) and EMS are operational after installation. The HP MWDP
contains the minimum set of drivers, typically the network driver, chipset drivers and configuration
scripts for updating the boot.wim and install.wim files as well as SAC support in Windows
7 with SP1 or Windows 8.1 to deploy a functional Windows image. The package includes sample
unattend files that can be customized and used as the client and image unattend files in your
configuration.
IMPORTANT: Using the HP Moonshot Windows Deployment Pack (or similar processes) is critical
to performing a successful deployment of the Microsoft Windows Operating System because
images supplied by Microsoft do not necessarily have the required drivers for the HP ProLiant
Moonshot Server cartridges.

Bundles contain:
• hpeula-en.html: HP end-user license agreement (English)
• hpeula-ja.html: HP end-user license agreement (Japanese)
• MWDP_m#00_README.txt: MWDP read me file.
• A directory containing drivers that can be added to the Windows deployment boot.wim
and install.wim files, particularly the boot-critical NIC driver essential for network based
deployments.
Note that the drivers folder contains HP ProLiant Moonshot cartridge-specific drivers for
supported Microsoft operating systems. If you use custom Windows deployment files, you must
include the drivers appropriate for your hardware.
• A scripts directory with script(s) to configure Windows deployment boot and install WIM files.
• An unattend directory with sample answer files for unattended Windows deployment. These
files are necessary for automating the Windows installation and a requirement for the
cartridges. Customize these sample files for your own environment according to your
organization’s requirements and policies.
HP ProLiant Moonshot server cartridges have different OS support. The following bundles are
required.
HP Moonshot Windows Deployment Pack for HP ProLiant m300 and m350 Server
Cartridges
This bundle is designed specifically for the ProLiant m300 and m350 server cartridges and is used
to assist with the deployment of Microsoft Windows Server 2012 or Microsoft Windows Server
2012 R2.
Table 3 Bundle contents
Drivers Chipset — Drivers that support the ProLiant m300 and m350 server cartridge platforms and
eliminate yellow bangs in Windows Device Manager.
Ethernet — Folder containing NIC drivers for Windows deployment on the ProLiant m300 and
m350 server cartridge.
Scripts Scripts used for customizing BOOT.WIM and INSTALL.WIM files from Windows Server 2012
and Windows Server 2012 R2 media.
Unattend Answer files used for automating Windows Server 2012 and Windows Server 2012 R2 installation.
The files are OS specific.
Using the provided scripts, drivers and unattend files from the Windows Deployment Pack for HP
ProLiant m300 and m350 Server Cartridge, the deployed instance of Windows will have SAC
and RDP enabled.
HP Moonshot Windows Deployment Pack for HP ProLiant m700 Server Cartridge

This bundle is specifically designed for the ProLiant m700 server cartridge and used to assist with
the deployment of Microsoft Windows 7 with SP1 (x64 or x86), Windows 8.1, and Windows
Server 2012 and 2012 R2.
Drivers Chipset — Drivers that support the ProLiant m700 server cartridge platform and eliminate yellow
bangs in Windows Device Manager.

Table 4 Bundle contents (continued)
Ethernet — Folder containing NIC drivers for Windows deployment on the ProLiant m700 server
cartridge.
Scripts Scripts for customizing BOOT.WIM and INSTALL.WIM files from the Windows 7 with SP1 media
or Windows 8.1 or Windows Server 2012 and Windows Server 2012 R2 media.
Unattend Answer files for automating Microsoft Windows 7 with SP1 (x64 or x86) installation, or Windows
8.1 or Windows Server 2012 and Windows Server 2012 R2. The files are OS specific.
Using the provided scripts, drivers and unattend files from the HP MWDP for HP ProLiant m700
Server Cartridge, the deployed instance of Windows will have SAC and RDP enabled.
HP Moonshot Windows Deployment Pack for HP ProLiant m710 Server Cartridge

This bundle is specifically designed for the ProLiant m710 server cartridge and used to assist with
the deployment of Microsoft Windows Server 2012 and Windows Server 2012 R2, Windows 7
SP1 (x64) and Windows 8.1 (x64).
Drivers Ethernet — Folder containing NIC drivers for Windows deployment on the ProLiant m710 server
cartridge.
Scripts Scripts for customizing BOOT.WIM and INSTALL.WIM files from the Windows 7 with SP1 media
or Windows 8.1 or Windows Server 2012 and Windows Server 2012 R2 media.
Unattend Answer files used for automating Windows 7 SP1 (x64), Windows 8.1 (x64), Windows Server
2012 and Windows Server 2012 R2 installation. The files are OS specific.
Using the provided scripts, drivers and unattend files from the HP MWDP for HP ProLiant m710
Server Cartridge, the deployed instance of Windows will have SAC and RDP enabled.
Using the HP MWDP to customize a Windows image for HP Moonshot server cartridge
nodes
The design and purpose of HP ProLiant Moonshot cartridges are distinct, and Microsoft Operating
Systems have different capabilities, therefore, operations required to deploy Windows might differ
from one version to another. For example, Windows 7 does not include drivers for headless
operations. HP MWDP is a comprehensive software solution used to configure and deploy the
supported Operating Systems on ProLiant Moonshot servers. HP MWDP has been tested with
Microsoft Windows Deployment Services.
The following instructions help you prepare images for supported Operating Systems installation
through network based deployments:
1. Download the appropriate HP MWDP from:
http://www.hp.com/support/moonshot/1500chassis-software-download
2. On a system running Windows, either on the deployment server or the technician computer,
create a temporary folder to store the image files. The examples below use:
C:\imageprep

3. Create subfolders for each type of cartridge you are deploying:
a. M300 or M350 for the ProLiant m300 and m350 server cartridge — Copy the full contents
of the Windows Deployment Pack for the server cartridge to be deployed to the M300
or M350 folder. For example, for the ProLiant m300 server cartridge, the folders would
match the following:
• C:\imageprep\m300\drivers\
• C:\imageprep\m300\scripts\
• C:\imageprep\m300\unattend\
b. M700 for the HP ProLiant m700 server cartridge — Similar to the m300 server cartridge,
copy the full contents of the Windows Deployment Pack for HP ProLiant m700 server
cartridge to the M700 folder so the contents match the following:
c. M710 for the HP ProLiant m710 server cartridge — You can copy the contents of the
Deployment Pack for the HP ProLiant m710 server cartridge to the m710 folder so that
you have a copy of the unattend files to customize later.
4. Supply a Windows ISO image or installation media.
5. From the supplied media, extract and copy BOOT.WIM and INSTALL.WIM from the source
folder to the appropriate m300, m350, m700, or m710 scripts folder for the image you are
deploying (see above for script folder paths). Alternatively, copy your own custom deployment
files to the appropriate scripts folder.
NOTE: Using this structure assumes a single OS installation. To install multiple OS installations
where supported (such as Windows Server 2012 and 2012 R2), create third level folders
below the \mXXX folder to have a directory structure for each OS. As an example, create a
folder named c:\imageprep\m300\scripts.ws2012 for the Windows Server 2012 files
and another named c:\imageprep\m300\scripts.ws2012r2 for Windows Server 2012
R2 files. Copy the hpdrvadd.cmd script file into each of the folders.
The HP ProLiant m700 server cartridge supports both bit versions of Windows 7 with SP1
(x64 and x86). To install both bit versions, create third level folders below the \m700 folder
to have a folder for each version of Windows 7 with SP1. For example, create folders named
c:\imageprep\m700\scripts.x64 and c:\imageprep\m700\scripts.x86. Copy
the hpdrvadd.cmd script file into each of the folders.
The \scripts folder should now contain script(s) from the HP MWDP, the BOOT.WIM and
INSTALL.WIM files from your Windows installation media.
6. Open an elevated ADK command prompt to the scripts folder.
IMPORTANT: Assuming that Microsoft Windows ADK was installed prior to manipulating
files, the Windows ADK provides a shortcut to a command shell environment with elevated
privileges. The shell environment has path settings to tools such as dism.exe used by the
hpdrvadd.cmd script. HP recommends using the ADK command prompt environment (also
called Administrator: deployment and Imaging tool environment). The hpdrvadd.cmd script
requires a current version of dism.exe; for example a Windows 7 deployment requires, at
minimum, Windows ADK 8.

7. Run hpdrvadd.cmd from the scripts folder.
This step modifies the BOOT.WIM and INSTALL.WIM files by adding the NIC drivers essential
for network based Windows installations. In addition, the chipset drivers are added to the
INSTALL.WIM file that completes driver installation.
HP ProLiant m300 and m350 server cartridge notes:

• Windows Server 2012 and Windows Server 2012 R2 contain 4 different Windows
SKUs. See “Microsoft OS SKUs” (page 71) in the WDS section. SKUs are defined in the
INSTALL.WIM file by index number.
• The hpdrvadd.cmd can be used to modify all SKUs in a single operation or each index
individually by passing the target index number to the script.
• By default hpdrvadd.cmd script (no arguments) updates all 4 SKU indexes contained
in the INSTALL.WIM file.
• It is possible to operate on a single index by modifying the script variable section. Refer
to the script usage for details. Script usage can be invoked using the /? argument.
• For a list of the SKUs and corresponding index number, use the Microsoft dism.exe
command:
dism /get-imageinfo /imagefile:<path>\install.wim
HP ProLiant m700 server cartridge notes:

• In addition to adding NIC and chipset package drivers to the BOOT.WIM and
INSTALL.WIM files as described above, the hpdrvadd.cmd file also modifies the
INSTALL.WIM file to add EMS support to the Windows installation. This is a necessary
additional step because the Windows Client operating system does not support EMS by
default.
No special customization is required for this additional step.
• The Windows 7 with SP1INSTALL.WIM file only contains a single Windows SKU, no
argument is needed for the hpdrvadd.cmd script.
8. After script execution completes, check the output for error messages. If errors are found,
follow the steps above again and check the output. If no errors are found, add the images to
the WDS store as described in the next section.
Example deployment using Microsoft Windows Deployment Services (WDS)

This section describes using Microsoft Windows Deployment Services (WDS) to perform a Windows
network based installation. While this deployment example includes the essential steps for deploying
Windows on Moonshot server cartridges using Microsoft WDS, other deployment tools can be
used.
Microsoft WDS can deploy the base OS images onto HP ProLiant Moonshot server cartridges.
Alternatively, you might want to customize a reference computer by:
• Installing an OS
• Downloading and installing the latest Microsoft updates
• Adding applications and files required for your target environment
Then capture a gold master image from the sample computer to be used as a reference for further
deployment on similar nodes.
In the example used in this section, Windows Server 2012 WDS is configured in stand-alone mode
because it does not require Active Directory, which would imply additional requirements for the
infrastructure. Windows Server 2012 WDS supports all versions of Microsoft Windows OS tested
on HP ProLiant Moonshot Servers, including Windows 7 with SP1, Windows 8.1, Windows Server

2012, and Windows Server 2012 R2. Other WDS versions may be used and can be integrated
into an Active Directory environment.
NOTE: For initial Windows Deployment Services setup, see “Microsoft Windows Deployment
Services installation” (page 71).
For more information and details concerning WDS, refer to the Microsoft technical documentation
in the “Related documentation and videos” (page 6) section.
Deploying the Windows image

Follow the procedures in this section to deploy the base Microsoft OS onto HP ProLiant Moonshot
server cartridges. The procedures involved include:
• “Adding boot images for ProLiant Moonshot server cartridges” (page 19)
• “Adding install images for ProLiant Moonshot server cartridges” (page 24)
• “Customizing sample XML unattend files” (page 25)
• “Deploying an image using WDS” (page 31)
Adding boot images for ProLiant Moonshot server cartridges

This step consists of adding the boot.wim file(s) that were modified in the “Using the HP MWDP
to customize a Windows image for HP Moonshot server cartridge nodes” (page 16) section, and
modifying the WDS BCD store to enable headless support of our customized boot.wim files(s).
In addition, headless support must be added to the boot entries.
1. In the left pane of the Windows Deployment Services console, right-click the Boot Images node,
and then click Add Boot Image.
2. Browse to choose the boot image (boot.wim) that you modified earlier, see the section on
“Using the HP MWDP to customize a Windows image for HP Moonshot server cartridge
nodes” (page 16) to prepare the Windows deployment.
NOTE: Boot images should be located either on the WDS server or on the technician machine
in the following directories:
HP ProLiant m300 server cartridge — \imageprep\m300\scripts\
3. Click Open, and then click Next.
Example deployment using Microsoft Windows Deployment Services (WDS) 19

Figure 3 Add custom boot image in WDS boot container
4. On the Image Metadata page, enter an image name and description that is meaningful to
your environment, for this example we are using WS2012R2–Moonshot-M300.
Figure 4 Customize image name and image description
5. Click Next.

Figure 5 Add boot image complete
6. Click Finish when the progress bar shows that the operation is complete and the following
message appears:
The selected images were successfully added to the server
7. Repeat this procedure to add other custom boot images.
NOTE: For HP Moonshot server cartridges, remember to enable EMS (for headless Windows
support) which is not enabled by default. The procedure for this is described in the next section,
“Enabling EMS in Boot Configuration Data files” (page 22).
NOTE: The .\boot\x64 folder contains various boot files and is used for 64-bit operating
systems, whereas the .\boot\x86 folder contains similar files for clients deploying 32-bit OS
versions. The Images subfolder contains the boot images added to the WDS during the process
described above. For each boot image added, a corresponding BCD file is created which
defines and controls boot settings applied during Windows deployment. When more than
one boot file with the same name is added to the boot container, the dash and number symbol
in parenthesis: –(#) is added to the file name. For example, a second boot.wim file added
to the store is named boot-(2).wim.

8. Determine the name of the added boot files, which you will need when you add EMS support
in the next section.
a. Left click on a new entry in the Boot Image pane to select it.
b. Right click the entry.
c. Select Properties. The file name is shown in the Image Properties window. See the example
in“Boot image name” (page 22) where the boot image name is boot-(2).wim. Note
that the architecture is also shown in this window, in this example the boot image
architecture is 64-bit (x64).
Figure 6 Boot image name
Enabling EMS in Boot Configuration Data files

HP recommends that you modify the BCD files to be used to boot the HP ProLiant Moonshot server
cartridge nodes (on the WDS server) to ensure that text based console monitoring is enabled. This
section describes modifying newly added and default BCD files.

Modifying newly added BCD files
1. Save the existing BCD files as backup in case of an error:
Open an elevated command prompt (cmd.exe) and go to the \RemoteInstall\boot\x64
folder (or the \RemoteInstall\boot\x86 folder for 32-bit versions), and enter the following
command:
>Copy boot.wim.bcd bootwim.bcd.orig
For example, from the \RemoteInstall\boot\x64\image folder enter the following
command (assuming that the file being modified is boot-(2).wim.bcd):
>Copy boot-(2).wim.bcd boot-(2)wim.bcd.orig
2. In the \RemoteInstall\boot\x64\images folder, alter the entry by typing:
>bcdedit.exe /store ".\boot-(#).wim.bcd" /enum /v
NOTE: If the file is in a different folder than the one from which you run the command, and
contains special characters (such as spaces), HP recommends entering double-quotes around
the fully qualified path. For example (in this case RemoteInstall is on the C: drive):
>bcdedit.exe /store
"C:\RemoteInstall\boot\x64\Images\boot-(2).wim.bcd" /enum /v
This is not valid PowerShell syntax, and applies only to an elevated Windows command
prompt. See Microsoft PowerShell documentation for proper PowerShell syntax.
Figure 7 Boot entry identifier
Make a note of the identifier (GUID).

3. Add BOOTEMS and EMS support to the BCD file added earlier (boot-(#).wim.bcd with its
identifier GUID) by entering the following commands:
>bcdedit.exe /store ".\boot-(#).wim.bcd" /set {GUID} bootems on
>bcdedit.exe /store ".\boot-(#).wim.bcd" /set {GUID} ems on
>bcdedit.exe /store ".\boot-(#).wim.bcd" /set {GUID} novga on
For example, using information from “Boot entry identifier” (page 23), you might enter:
>bcdedit.exe /store ".\boot-(2).wim.bcd" /set
{959451b3-49fa-447f-9342-41b2c395b8c9} bootems on
{959451b3-49fa-447f-9342-41b2c395b8c9} ems on
{959451b3-49fa-447f-9342-41b2c395b8c9} novga on
>bcdedit.exe /store ".\boot-(2).wim.bcd" /enum /v

The final command lists the entries in the store so you can verify EMS support was added.
IMPORTANT: The novga option does not apply to Windows 7. Do not use it for ProLiant
m700 server cartridge deployments with Windows 7 Enterprise with SP1 (regardless of
architecture). The option is available in Windows 8 and Windows Server 2012 and later
versions.
4. Repeat this procedure to enable BOOTEMS and EMS on any additional ProLiant Moonshot
server custom boot images, and then continue to “Modifying default BCD files”.
Modifying default BCD files
1. Open an elevated command prompt, navigate to \RemoteInstall\Boot\x64 or
\RemoteInstall\Boot\x86 (depending on the architecture being deployed).
2. Enter the following command to create a backup copy of the Default.bcd file:
>Copy default.bcd default.bcd.orig
3. Enter the following command to display the store entries:
>bcdedit.exe /store ".\default.bcd /enum all
Notice that bootems is not present.
4. Enter the following command to enable bootems:
>bcdedit.exe /store ".\default.bcd" /set {bootmgr} bootems on
5. Enter the following command to display the store entries again:
>bcdedit /store ".\default.bcd" /enum all
Notice that bootems is set to yes.
6. Enter the following:
>sc control wdsserver 129
The final command restarts WDS. The restart is necessary so that WDS reads the newly modified
files, and concatenates the default.bcd from the \RemoteInstall\boot\x64 (or
\RemoteInstall\boot\x86) directory with boot-(#).wim.bcd from the \RemoteInstall\
boot\x64\image or \RemoteInstall\boot\x86\image folder.
TIP: WDS can also be restarted using the WDS management console.
Adding install images for ProLiant Moonshot server cartridges
NOTE: HP recommends creating a new boot image container, such as HP ProLiant Moonshot
Servers, in the WDS Management console to store the modified install.wim file.
1. Using the WDS management console, right-click the Install Images container and click Add
Image group. For example, HP ProLiant Moonshot Servers.
2. Right-click the newly created container and select Add Install image.
3. Next, click Browse to locate the install.wim file that was modified earlier in “Using the
HP MWDP to customize a Windows image for HP Moonshot server cartridge nodes” (page 16).
The image name appears in the management applet image group and is displayed to the
user during the PXE installation process.

NOTE: For the HP ProLiant m300 server cartridge — \imageprep\m300\scripts\
For the HP ProLiant m350 server cartridge — \imageprep\m350\scripts\
Either on the WDS server or on the technician machine as suggested in the procedure.
TIP: Rename the file with a descriptive name (all Microsoft operating systems have
install.wim files and they are all different). There are four images installed in this process
in the case of Windows Server 2012 and Windows Server 2012 R2, one for Windows 7
with SP1 (x64), and one for Windows 7 with SP1 (x86).
Figure 8 Adding custom install.wim from the HP ProLiant Moonshot servers group
4. Click Open, and then click Next.

5. Continue following the instructions on the remaining screens.
Customizing sample XML unattend files

There are two unattend files per OS, a clientUnattend and an ImageUnattend. The HP
MWDP contains samples that must be customized for your environment. They are standard unattend
XML files in which the fields with values set to “XXXXXXXX” are the values to change.
Copy the two unattend files based on cartridge type and OS version from the HP MWDP unattend
folder to the RemoteInstall\WdsClientUnattend folder on the WDS server. Then customize
the content of the files by replacing the XXXXXXX values with your own data.

NOTE: You can copy the files onto either the WDS server Imageprep or onto the Technician
machine as suggested in the procedure. All files must be placed in the proper unattend directory
by cartridge (see Table 6 (page 26).)
Table 6 Files to copy to \imageprep\mXXX\unattend based on OS
Operating System Compatible Cartridge Files to copy to \imageprep\mXXX\unattend
Windows Server 2012 ProLiant m300 server cartridge ClientUnattend_WS2012.xml

ProLiant m350 server cartridge ImageUnattend_WS2012.xml
ProLiant m700 server cartridge
Windows Server 2012 R2 ProLiant m300 server cartridge ClientUnattend_WS2012R2.xml

ProLiant m350 server cartridge ImageUnattend_WS2012R2.xml
Windows 7 (32–bit) ProLiant m700 server cartridge ClientUnattend_Win7_x86.xml

ImageUnattend_Win7_x86.xml
Windows 7 (64–bit) ProLiant m700 server cartridge ClientUnattend_Win7.xml

ProLiant m710 server cartridge ImageUnattend_Win7.xml
Windows 8.1 (64-bit) ProLiant m700 server cartridge ClientUnattend_Win8.1.xml

ProLiant m710 server cartridge ImageUnattend_Win8.1.xml
Example HP ProLiant m300 server cartridge installation with Windows Server 2012 R2
The following example describes a Windows Server 2012 R2 installation on an HP ProLiant m300
server cartridge. It is a single node cartridge and recognized as C3N1 by the iLO CM firmware.
Network adapter 1 with Mac Address 38-EA-A7-0F-7D-11 is the network interface used for
deployment.
1. In the folder RemoteInstall\WdsClientUnattend, copy the file
ClientUnattend_WS2012R2.xml and paste to create a new file called
m300-ClientUnattend_WS2012R2.xml
2. In the folder RemoteInstall\WdsClientUnattend, copy the file
ImageUnattend_WS2012R2.xml and paste to create a new file called
m300-ImageUnattend_WS2012R2.xml
NOTE: Only one instance each of ImageUnattend.xml and ClientUnattend.xml is

required for each server cartridge of the same type. That is, one for the ProLiant m300 server
cartridge, one for the ProLiant m350 server cartridges, one for the ProLiant m700 server
cartridge, one for the ProLiant m710 server cartridge, and so on.

3. Modify all of the “XXXXXXXX” values from each of the XML files to match your target
environment using either an XML editor, or the Microsoft Windows System Image (SIM) tool
from the Microsoft Assessment and Deployment Kit (ADK). If needed, download and install
the Windows ADK for Windows 8 or the ADK for Windows 8.1.
ADK 8.1 is mandatory for Windows Server 2012 R2 and provides backward compatibility
for older version of Microsoft Operating Systems supported on HP ProLiant Moonshot Server
cartridges.
NOTE: When using Windows SIM, you must open each unattend XML file, which might
require you to locate the Install.wim file. Browse to the imageprep\scripts folder
and then select the file. After locating the correct Install.wim file, Windows SIM might
need to create a new catalog file, which can take from 15 to 20 minutes. When you save the
file the new location for the Install.wim is also saved.
TIP: The following table shows the field names to be modified as an example for deploying
Windows Server 2012 R2 Standard on an HP ProLiant m300 Server Cartridge. Replace each
XXXXXXXX field name entry in the sample files with the appropriate information for your
environment. You can print this page and complete the following table as a reference for
editing these files.
Field name Your value Example
Logon domain or WDS server Name of WDS server

name
Logon password ABC123xyz
Image group HP ProLiant Moonshot Servers
Image name Windows server 2012 R2

standard m300
WIM filename Windows server 2012 R2

standard m300.wim
Registered organization my-organization
Registered owner IT-DPT
Target cartridge administrator ABC123xyz

auto logon password
Product key Microsoft product key
IMPORTANT: Ensure that the Product key is appropriate for the installation. For example,
an MSDN product key cannot be used with a volume license ISO file.
Configuring pre-staged devices

Pre-staging devices provides granular control and customization, and it is recommended for HP
ProLiant Moonshot server cartridge deployment. It requires adding the MAC address or GUID of
the client to the WDS store (or Active Directory prior to deployment using the WDS management
console or from the wdsutil.exe command line tool).
NOTE: Adding devices to Active Directory is beyond our scope; refer to the Microsoft Technical
documentation for Active Directory information.
This section requires knowledge of the cartridge network adapters’ address.

1. Connect to the iLO Chassis Manager CLI over SSH using a terminal program like PuTTY. Log
in using the default administrator credentials (administrator/password) to reach the hpiLO—>
prompt. At the hpiLO-> prompt, enter the following command:
hpiLO->show node macaddr <CxNy>
Where x is the cartridge ID and y is the node ID.
For example:
hpiLO->show node macaddr C3N1
The MAC address for the specified node (for example, 38:EA:A7:0F:7D:11) is displayed.
IMPORTANT: Replace colons (:) with dashes (–) when entering MAC addresses into WDS.
2. Open the WDS Management Console, select Pre-stage Devices, right-click and then select Add
device. The Add Pre-staged Device Wizard starts.
3. On the Identity screen, enter a name (for example, c3n1–Nic1) in the Name field and then
complete the Device ID field with the network adapter’s MAC address for PXE boot. Remember
to use dashes instead of colons as separators for the MAC address.
Figure 9 Pre-staged device wizard — general identity
4. Click Next to move to the Boot page.

5. In the PXE Prompt Policy section, select Use the following boot program, click Select and
browse to \RemoteInstall\Boot\x64\hdlscom1.n12
NOTE: You must select the hdlscom1.n12 boot program to have headless support within
PXE boot.

In the Boot Image section, click Select and browse to your boot-(#).wim file in the
\RemoteInstall\boot folder structure. For example, choose \RemoteInstall\boot\
x64\images\boot-(2).wim, and then click Next.
Figure 10 Add prestaged device wizard — boot program and boot image
6. On the Client unattend page, click Browse, locate and select the client unattend file, click
Open.
For example:
\RemoteInstall\WdsClientUnattend\m300–ClientUnattend_WS2012R2.xml

Figure 11 Add a prestaged device — client unattend file
Click Next and the Join Rights page appears.

7. On the Join Rights page, clear the Join the domain with this device when it is deployed box
in the Device Settings section if the computer under deployment is not joining a domain during
its setup. Click Finish.
NOTE: The path is always related to the WDS store and so the path will always be drive\
path\RemoteInstall. In the case of this example, the path is C:\RemoteInstall.
Figure 12 Add prestaged device wizard — Join Rights

NOTE: Review or change your settings by selecting the device name from the Prestaged
Devices – right pane, and right click to launch properties. Select each tab that you want to
review or modify.
A client unattend file is now associated with the pre-staged device. The next step associates
an image unattend file with the OS image being deployed.
8. Open the Install Images container, select the Group Name folder that has the installation image
file of the Windows version being installed. In our example, ProLiant Moonshot servers is the
image group, and the image file is Windows Server 2012 R2 Standard M300.wim
9. Select Allow image to install in unattended mode, click Select File to browse to the install
image. In the example, the image file is: \RemoteInstall\WdsClientUnattend\
m300–ImageUnattend_WS2012R2.xml
Figure 13 Image properties — select image unattend file
10. Click Open, and then click OK to continue.

11. Click Apply and then OK to complete this operation.
TIP: If you change the unattend file in the future, perform steps 9 –12 to activate the changes on
the WDS server structure. This is because WDS is using a copy of the file and saves it under
\RemoteInstall\Images\Group-x\install-(x)\Unattend.
The pre-staged device and Windows image are now configured for automated deployment and
the device can PXE boot to install Windows.
Deploying an image using WDS

The steps in this section consist of PXE booting the ProLiant Moonshot server node.

NOTE: This section assumes that the ProLiant Moonshot server cartridge nodes are pre-staged
in WDS.
Ensure the cartridge being deployed boots on the hard disk by default, in addition, you must issue
a PXE bootonce command before powering on.
1. Connect to the iLO CM firmware IP address using PuTTY or another terminal program that
supports SSH connections.
2. Log in using the default administrator credentials (administrator/password) to reach the
hpiLO—> prompt.
Figure 14 iLO SSH session
In this procedure, this session is referred to as Terminal 1.

3. Right-click the top left corner to see the putty menu and choose Duplicate session, enter user
credentials in the second window that appears.
TIP: HP recommends that you duplicate the session to manage the cartridge, with one session
for entering commands at the hpiLO-> prompt and the other for connecting to a node in a
VSP session to view the Windows deployment.
In this procedure, this session is referred to as Terminal 2.
4. This example shows a deployment to cartridge 8, node 1 (C8N1).
From Terminal 1, display the MAC address of the node connected to the network using the
command:
hpiLO->show node macaddr c8n1.
Figure 15 (page 33) shows an example of the MAC addresses corresponding to the network
adapters for c8n1. You must boot from the NIC that you configured when you added this
node to the pre-staged device list in WDS.

Figure 15 show node macaddr c8n1
5. Terminal 1: Check the cartridge node power status using the command:
hpiLO->show node status c8n1
6. Terminal 2: Connect to the virtual serial port of c8n1 to watch the cartridge boot and initiate
PXE with the command:
hpiLO->connect node vsp c8n1
7. Terminal 1:Ensure the default boot for the cartridge is set to HDD:
hpiLO->set node boot hdd c8n1
To check the default boot device, enter: hpiLO->show node boot c8n1
8. Terminal 1: Ensure the node is turned off:
a. If Windows is running enter:
hpiLO->set node power off shutdown c8n1
b. If WinPE is running enter:
hpiLO->set node power off force c8n1
9. Terminal 1: Set the next boot parameter to PXE:
hpiLO->set node bootonce pxe c8n1
10. Terminal 1: Power on cartridge:
hpiLO->set node power on c8n1
11. Terminal 2: Verify that it is powering on.
12. Watch the screen carefully. If the target cartridge receives its TCP/IP parameters from a DHCP
server and is configured to boot from the WDS boot image \RemoteInstall\boot\x64\
hdlscom1.n12 you will see the boot process.
Figure 16 PXE boot process
WARNING! HP strongly advises that you change the default settings to use the
hdlscom1.n12 boot program for cartridges.

NOTE: The \RemoteInstall\Boot\x64 folder contains boot configuration and images for
x64 images stored on the WDS and responds to a PXE boot request with an architectural discovery
process.
The \RemoteInstall\Boot\x86 folder contains boot configuration and images for x86 images
stored on the WDS and responds to a PXE boot request with that architectural discovery process.
Once the PXE boot is successful and WinPE is running, a Microsoft Special Administration Console
(SAC) screen appears.
First phase installation (WinPE boot)

WinPE boots and prepares the computer to be imaged with Windows.
Example 1 VSP console with Microsoft SAC

Computer is booting, SAC started and initialized.
Use the “ch —?” command for information about using channels.
Use the “?” command for general help.
SAC>
EVENT: The CMD command is now available.
SAC>
This is followed by the creation of several SAC Channels that follow installation.
Example 2 VSP console with Microsoft SAC channels allowing Windows setup
Computer is booting, SAC started and initialized.
Use the “ch —?” command for information about using channels.
Use the “?” command for general help.
SAC>
EVENT: The CMD command is now available.
SAC>
EVENT: A new channel has been created. Use “ch —?” for channel help.
Channel: SACSetupAct
SAC>
EVENT: A new channel has been created. Use “ch —?” for channel help.
Channel: SACSetupErr
You can switch from one channel to the other using Esc+Tab keys in sequence. SACSetupAct
channel is a great resource for monitoring the progress of a Windows installation. In particular it
is helpful in troubleshooting failed installations.

Figure 17 Installation progress output during the early phase
During the latter phase of Windows setup, and prior to the first reboot, the Windows image is
applied and the initial SAC SetupAct channel will close, another channel opens — Press the key
combination Esc+Tab and select the SACSetupAct channel option to see the installation progress.
To connect to one of the SAC channels, to channel 1 for example, type ch -si 1
(SACSetupAct), this can be used in place of Esc+Tab for switching between SAC channels.
After the process of applying the image is complete, Windows setup reboots.
NOTE: If the default boot policy is not set to HDD, you may experience an unintentional PXE
boot.
TIP: You may remove the node from the WDS pre-staging area once it is deployed.

Figure 18 SAC — SetupAct channel
Second phase
During the second phase of Windows setup, another SACSetupAct channel is created.
Figure 19 SAC — SetupAct Channel

Windows setup reboots one more time and the SAC> prompt appears in the EMS console.
Check installation (login)

1. On the VSP console, type i at the SAC> prompt to see the IP addresses assigned to your
installed server. Make a note of these IP addresses. You can use them with the remote desktop
client or Microsoft Terminal service Client to access your server remotely.
2. Type cmd at the SAC> prompt to open a new command channel.
3. Press Esc+Tab+Enter
4. Enter the administrator username and password as prompted. Once authenticated at the
C:\Windows\system32> prompt you can initiate any valid Windows command including
starting a PowerShell session.
NOTE: Commands that attempt to launch a GUI window are not shown because this is a
text based console.
5. Try accessing your server using MSTSC /v:IP Address if your technician computer is
running Windows.
6. You will be prompted to enter logon credentials to the newly installed server.
Repeat the procedure in this section, starting at “Deploying an image using WDS” (page 31), for
each pre-staged node.
Capturing a custom Windows image

Follow the procedures in this section to capture a gold image of a completed HP ProLiant Moonshot
server cartridge OS installation which can then be used for deployment on equivalent cartridges.
The procedures involved include:
• Preparing the answer files
• Creating a WINPE capture image
• Preparing the reference node using sysprep
• Capturing the golden image and uploading it to the WDS store
• Deploying the golden image
Prerequisites
The procedures in this section assume:
• You have already deployed a Windows base image on a node and customized it (for example
by updating the OS to the latest Microsoft hotfixes, installing the required applications and
files for the target environment).
• This node (reference) has enough space to create a capture file (at least 6 GB, but it is
dependent on what you have installed).
• The node can be accessed using Microsoft remote desktop (MSTSC.exe).
• You have an SSH connection to the HP Moonshot 1500 chassis, and can use iLO CM with
administrative privileges so that you can control cartridges and access their VSP.
• The WDS server already contains a modified boot image (boot.wim) to support HP ProLiant
Moonshot server cartridges. If not, see “Using the HP MWDP to customize a Windows image
for HP Moonshot server cartridge nodes” (page 16).
• Microsoft ADK installed on WDS (not required but strongly recommended)
• The creation of an WDSCapture.inf file. You can create one by copying the text from “Sample
WDScapture.inf file entries” (page 76).
• An ImageUnattend.inf file.

Preparing answer files
This section describes how to create a WDSCapture.inf file, and how to use the HP MWDP
Image_Unattend.xml to create a Sysprep.xml file to be used later.
1. WDSCapture.inf
On the WDS server, create a folder and subfolder named Deploy\Capture_Image.
For example : C:\Deploy\Capture_Image\
2. Create a second subfolder in the Deploy directory named mount.
For example : C:\Deploy\mount\
3. Copy and paste the entries from “Sample WDScapture.inf file entries” (page 76) into a new
text file, and then save the file as WDSCapture.inf in the .\Capture_Image directory.
4. Customize the WDSCapture.inf entries to match the settings of the reference node to be
captured. Table 7 (page 38) explains the minimum required settings that the WDSCapture.inf
must contain in the [Capture], [ExclusionList], and [WDS] sections.
Table 7 Required WDSCapture.inf settings
Section of wdscapture.info Setting explanation
[Capture] 1 1 The Capture section contains information about the

Unattended=Yes 2 settings for the Image Capture Wizard.
VolumeToCapture=D: 3 2 Must be set to yes to automate the image capture
SystemRoot=windows 4 process.
ImageName="MoonshotWin7Capture" 5 3 This is the volume to capture into a WIM file. The volume
ImageDescription="Moonshot Win7 Ent depends on how many partitions reside on your reference
SP1 & WinUpdate, AMD" 6 computer. For example, if you used the sample XML files
DestinationFile=D:\MoonshotWin7Capture.wim from the MWDP package, there will be two partitions.
7
Under WinPE the first partition should be the 350MB
Overwrite=Yes 8
C:\ system partition, and the second should be the
Windows partition D:\. In this case, VolumeToCapture
isD:
4 This is Windows by default (unless your target image is
configured differently).
5 Enter the name of the image, enclosed in quotes.
6 Enter a clear description of the image, enclosed in
quotes.
7 This is the name and location of the captured image. This
must reside on a partition on the target (or sysprep'd
node), large enough to contain the file. In this example,
it is stored on the same volume as the one that is
captured. Note that ImageName, ImageDescription,
and DestinationFile are used to store the image on
the WDS server.
8 Designates whether the destination WIM file will
overwrite an existing file in the specified location.
[ExclusionList] 1 1 ExclusionList section: Enter any folders or files you don't

$ntfs.log want stored in the captured image in the ExclusionList
hiberfil.sys section. Note that there is a default list that is populated
pagefile.sys (including Windows Pagefile.sys, hiberfil.sys, and so
"System Volume Information" on).
RECYCLER
winpepge.sys
%SYSTEMROOT%\CSC
[WDS] 1 1 The WDS section contains configuration settings for

UploadToWDSServer=Yes 2 automatically uploading the captured Image to the WDS
WDSServerName=hp-wds01 3 server. The fields must match your environment.
WDSImageGroup="Moonshot Win7 Ent 2 Enter Yes if you want to automatically add the captured
SP1" 4 image to the WDS server. If set to No, the remaining
Username=ris [WDS] values are ignored.
Domain=hpaddev.com 5 4 The name of an existing install image group on the WDS
server, enclosed in quotes.

Table 7 Required WDSCapture.inf settings (continued)
Section of wdscapture.info Setting explanation
Password=Abcdef12 5 Used only if the WDS server is an Active Directory

DeleteLocalWimOnSuccess=No 6 member server.
6 Determines if the captured WIM file is deleted from the
sysprep’d system following a successful upload to the
WDS server. HP recommends entering No here, until all
testing is finished.
5. ImageUnattend and Sysprep.xml

Copy the appropriate C:\ImagePrep\ImageUnattend_<WindowsVersion>.xml file
to the \Deploy\Capture_Image\ directory and rename the file Sysprep.xml. From a
command line, you can copy and rename the file with a single command.
For example:
Copy C:\ImagePrep\Image_Unattend_win7.xml
C:\Deploy\Capture_Image\Sysprep.xml
6. Customize Sysprep.xml as needed for unattended installation.
Creating a WinPE capture image

The WinPE image is used to boot the reference system and generate the golden image from the
installed (but not running) instance of Windows.
1. Open the WDS management console on the WDS server.
2. Open the Boot Images container to display all the available boot images.
3. Right-click the custom boot image that is used to deploy the desired operating system on the
target HP ProLiant Moonshot server and select Create Capture Image. The Create Capture
Image Wizard appears.
4. Follow the steps of the wizard, which include:

a. Name the capture image with an easily recognized name. For example, Moonshot
m700 Microsoft Windows Setup (x64).
b. Enter an Image description.
c. Enter the desired path and filename of the WinPE capture image (for example, C:\
Deploy\Capture_Image\CaptureImageWin7.wim). You will add the image to the
WDS store in later steps.
d. Click Next, and the Task Progress page appears. The image is extracted from the source
image file and captured to the destination file. When complete, it updates the metadata
on the WDS server.
e. Do not select Add image to the Windows Deployment Server now. You must still modify
the capture image before adding it to the WDS store.
NOTE: If you do add the image to the WDS now, you will have to export it using the
WDS export option, since it must be modified as shown in the following steps.
f. Click Finish to close the Image Capture Wizard.

5. Open the Deployment and Tools Image cmd.exe shell (also referred to as ADK command
prompt) or open the Deployment and Tools Imaging window to the folder containing the
captured image created in the steps above.
6. If needed, create a subfolder named mount in the directory that contains the captured image.
For example:
C:\Deploy\Capture_Image\mount
7. Mount the WinPE captured image using the dism.exe command:
dism.exe /mount-wim /wimfile:.\<captureimage.wim> /mountdir:.\mount
/index:1
For example:
dism.exe /mount-wim /wimfile:.\CaptureImageWin7.wim /mountdir:.\mount
/index:1

8. After the image is mounted, copy C:\Deploy\Capture_Image\WDSCapture.inf into
the .\mount\Windows\System32\ directory. For example:
copy .\Capture_Image\WDSCapture.inf .\mount\Windows\System32
9. Enter the dism.exe command to save and unmount the image:
dism.exe /unmount-wim /mountdir:.\mount /commit
10. Import the modified capture image WIM file to the Boot images container on the WDS server
(see “Adding boot images for ProLiant Moonshot server cartridges” (page 19) for instructions.)
11. Enable EMS support in the captured image boot file. Do this by opening an elevated command
prompt (cmd.exe shell) to the \RemoteInstall\Boot\x64\Images folder and enable
bootems and ems in the corresponding BCD file. See “Enabling Windows Emergency
Management Services (EMS)” (page 12) for instructions.
For example:
>Cd \RemoteInstall\boot\x64\Images
\RemoteInstall\boot\x64\Images>Bcdedit.exe /store “.\CaptureImageWin7.wim.bcd” /enum all
\RemoteInstall\boot\x64\Images>bcdedit.exe /store “.\CaptureImageWin7.wim.bcd” /set {Windows Boot Loader

GUID} bootems ON
\RemoteInstall\boot\x64\Images>bcdedit.exe /store “.\CaptureImageWin7.wim.bcd” /set {Windows Boot Loader

GUID} ems ON
NOTE: Copy the Windows Boot Loader identifier GUID shown after the /enum all
command to use in the last two commands.
12. Restart the WDS service.
Preparing the reference node using sysprep

To prepare the reference system with everything to be duplicated to the target nodes, and remove
all parameters that are unique to the node. Because this involves the use of the sysprep command,
Windows stops at the Welcome screen the next time the OS reboots the prepared image. This
renders the Moonshot cartridge node unusable since there is no way to remotely connect into the
node. To prevent this, add an XML answer file to the sysprep image as part of the sysprep process:
1. Make all the necessary customizations to the image you plan to use as your golden image on
the reference system. For example, install Windows updates, driver and application packages,
and so on.
2. Verify that there is enough room on the Windows system drive to create the golden image
file. If necessary, reduce the size of pagefile.sys.
3. Customize an answer file to automate the selections on the Windows welcome screen. Microsoft
recommends that you use the Windows System Image Manager (Windows SIM) to create
and manage answer files. Windows SIM is included with the Windows ADK. Alternatively,
use the appropriate ImageUnattend_<WindowsVersion>.xml sample file found in the HP
MWDP unattend folder (see Step 5 of “Preparing answer files” (page 38) for more information).
4. Open the file with Windows SIM and replace“XXXXXXXX” field values with values for the
target computer (see “Customizing sample XML unattend files” (page 25)).
5. Save the answer file to a folder on your system, such as C:\temp\Sysprep.xml.
6. Open an administrative cmd.exe shell to the %windir%\system32\sysprep folder on the
reference computer.
7. Enter the sysprep command to remove unique computer information from the reference system
and shut down the node. For example:
C:\Windows\System32\sysprep>sysprep.exe /generalize /oobe /shutdown
/unattend:c:\temp\unattend.xml

NOTE: If the answer file altered in this step is valid, after the reference node reboots it will
automatically bypass the Windows Welcome screen and boot the operating system. If not, then
there was a problem with the answer file. You must resolve this before deploying the OS image.
There is no way to access the OS at the Windows Welcome screen due to the headless nature of
Moonshot cartridges, and remote desktop is unavailable at that point in a Windows installation.
Capturing the golden image and uploading it to the WDS store

After preparing the node with sysprep and powering it off, capture the prepared volume and
upload it to the WDS image store. Capture the golden image by PXE booting the reference node
using the WDS Capture image you made in “Creating a WinPE capture image” (page 39). Ensure
the target node boots the WDS Capture image. Note that you must ensure there are no unattend
answer files associated with the node during this image capture.
1. Open the WDS Management Console, right–click Pre-stage Devices, and then select Add
device. The Add Pre-staged Device Wizard appears.
2. On the Identity screen, enter the Name, and then enter the network adapter’s MAC address
for the Device ID.
3. Click Next and then do the following:
a. In the PXE Prompt Policy section, select Use the following boot program, click Select, and
browse to the appropriate hdlscom1.n12 file.
b. Under Boot Image, click Select and then browse to the WinPE capture image created
earlier.
NOTE: Leave the fields in the rest of the wizard empty. Click Next until you can click Finish.

4. Open an SSH connection to the Moonshot iLO CM firmware.
5. If necessary, do one of the following to power the node off:
• If Windows is running, enter the graceful shutdown command:
hpiLO-> set node power off shutdown <CxNy>
• If WinPE is running, enter the for power off command:
hpiLO-> set node power off force <CxNy>
6. Set the boot option for the reference node to boot once from PXE on the next boot:
hpiLO-> set node bootonce pxe <CxNy>
7. Power on the reference node, which performs a PXE boot:
hpiLO-> set node power on <CxNy>
8. Connect to the reference node’s VSP.
9. On the Special Administrator Console, when you see EVENT:The CMD command is now
available, start monitoring the progress of the capture by entering the t command. In other
words, at the SAC> prompt, type the letter t and then press Enter.
TIP: Verify the user time counter continually increments. The image capture and upload
process takes approximately 15–20 minutes, depending on the size of the volume being
captured. When finished, the node should reboot automatically.
10. After the node reboots, verify that the captured golden image was added to the WDS store
according to the settings in the WDSCapture.inf file.
11. If the install image is present, it is ready to be deployed. However, you must update your XML
files to point to the new install image (the example explained in “Example HP ProLiant m300
server cartridge installation with Windows Server 2012 R2” (page 26) is similar to other
Windows OS versions and cartridges).
12. (Optional) Power on the reference node used to create the golden image, verify it boots into
the OS, and that you can connect to it using MSTSC (Remote Desktop Protocol). If not, there
is a problem with the sysprep state, most likely in the answer file.
Deploying the captured golden image

After capturing and saving the golden image to the WDS store, it is ready to deploy to other nodes:
1. Find the image that was automatically added to the WDS store in the previous procedure. In
our example, the image group name is “Moonshot Win7 Enterprise SP1” and the image name
is MoonshotWin7Capture.wim.
Right-click the image to display the properties. Record the image group name and the image
name. You will need this to modify the answer XML files to deploy the new golden image.
2. Deploy the golden image using automated unattended installation processes (see “Deploying
the Windows image” (page 19)).
3. After the golden image deployment is finished, verify that you can connect through remote
desktop to the newly installed nodes.
Tips and best practices for Windows OS deployment

Include the drivers
Ensure the WinPE capture image (the example in this guide is named CaptureImageWin7.wim)
used to create the WDS capture image includes Moonshot drivers.
Tips and best practices for Windows OS deployment 43

Enable EMS
Be sure to enable bootems in the WinPE capture image BCD file (the example in this guide is
named CaptureImageWin7.wim.bcd.)
Verify available space
Ensure the reference node used to create the golden image has sufficient free disk space to hold
the captured image prior to sysprep. The minimum recommended free space size is 6GB.
Use a working ImageUnattend file as a template
Customize a working ImageUnattend_<WindowsVersion>.xml file as a template for the
sysprep.xml file
HP ProLiant m710 and DHCP option 67
Windows deployment services (WDS) on the HP ProLiant m710 does not currently work when the
DHCP server is configured with option 67 pointing to the network boot program (NBP)
hdlscom1.n12. HP recommends that you do not use DHCP option 67 with WDS, as documented
in the Microsoft technical article http://support.microsoft.com/kb/926172. If DHCP option 67
must be used, please point to the NBP wdsnbp.com instead of hdlscom1.n12. HP is working
to fix this with a future update.
Shutting down a Windows OS node

An HP ProLiant server cartridge node running Windows, deployed without using MWDP sample
answer files (ImageUnattend_OS.xml), may continue to run even after entering a set node
power off shutdown <CxNy> command on the ILO CM firmware command line. This is due
to a display timeout in Windows power schemes.
To fix this issue, enter the following command from a Windows command prompt:
1. powercfg.exe -setacvalueindex scheme_min sub_video videoidle 0
2. powercfg.exe -setacvalueindex scheme_max sub_video videoidle 0
3. powercfg.exe -setacvalueindex scheme_balanced sub_video videoidle
0
HP recommends that you used the Unattend.xml samples from the MWDP for Windows
deployments, which include these commands by default.
Basic image and WDS troubleshooting

See the basic WDS troubleshooting table below for common issues and solutions related to image
captures and WDS.
Table 8 Basic image and WDS troubleshooting
Issue Installation fails while applying unattend answer file; hrResult = 0x8030000b
Message
Date Time, Info [setup.exe] [Action Queue] : Executing command "C:\WINDOWS\SYSTEM32\RUNDLL32.EXE"

shsetup.dll,SHUnattendedSetup specialize
Date Time, Info [setup.exe] [Action Queue] : process exit code = 4
Date Time, Error [setup.exe] [Action Queue] : Unattend action failed with exit code 4
Date Time, Info [setup.exe] [Action Queue] : ProcessActionQueue finish (hr = 0x1f2000)
Date Time, Error [setup.exe] Execution of unattend GCs failed; hr = 0x0; pResults->hrResult = 0x8030000b
Date Time, Info [0x0606cc] IBS Flushing registry to disk...
Date Time, Info [0x0606cc] IBS Flush took 468 ms.
Date Time, Warning IBS Callback_Unattend_InitiatePass: Runtime error occurred while applying
unattend answer file; hrResult = 0x8030000b
Solution • Ensure that both client and image unattend files contain identical values for <ComputerName>
• Use an asterisk in the unattend files (*) to automatically generate a name:
<ComputerName>*</ComputerName>
Issue Image capture was successful but image is not present on the WDS server.

Table 8 Basic image and WDS troubleshooting (continued)
Solution • Verify the WDS server settings in the WDScapture.inf file are correct.
• If the WDS server is operating in stand-alone mode, verify that the Domain field in the WDSCapture.inf
file is set to the WDS server name.
Issue The node prepared with sysprep booted, but is inaccessible using remote desktop (MSTSC.exe) after the
WDS capture process.
Solution Check the sysprep.xml file for any errors that might prevent the OS from bypassing the Windows
Welcome screen.
Tips and best practices for Windows OS deployment 45

3 Linux preparation and deployment
This chapters covers the setup of a basic Linux server to allow Linux OS deployment to Moonshot
cartridges using PXE.
Setting up a network installation server

A network installation server is a collection of network services, installation and configuration files,
which work together to enable the diskless booting and/or installation of a Linux distribution onto
a computer system using only a network, without the use of local media such as CD-ROM, DVD
or Blu Ray discs. This chapter will walk you through the process of setting up a single server with
all of the required network services and files necessary to install a Linux operating system onto an
HP ProLiant server cartridge.
HP ProLiant server cartridges do not offer the ability to install using local media. As with Windows,
you must use a network installation server to get the system up and running with Linux.
HP ProLiant server cartridges also differ from standard servers in that they have no VGA-based
console connections for monitors, nor USB ports for keyboards or mice. The specific adjustments
for these are discussed in later sections.
This chapter contains the procedures for building a Linux installation server on a clean installation
of RHEL 6.5. Other RHEL variants, such as CentOS, Fedora and Scientific Linux should work equally
well, without having to modify the commands, and configurations presented. If you are using a
different Linux distribution, such as SUSE, or Ubuntu, you will need to use different commands to
install packages, and in many cases, the names of packages, and paths to configuration files may
be different. Refer to the documentation in your distribution to identify these differences, and make
the adjustments necessary.
Installation server requirements and base configuration

The physical requirements for the installation server are basic enough that it can run on a Virtual
Machine or Moonshot server. Note that the performance of your installation server will affect the
speed of the installation to one or more servers.
Install your chosen hardware with RHEL6.5, and include at least the Base and Core package
groups. Other required packages will be installed in later sections.
You must have a dedicated network interface which your server will use to provide DHCP and
other services to your installation targets. Take care when attaching this interface to a
network—avoid using a network on which another DHCP server is present to avoid DHCP addressing
problems.
For the purposes of this document, in the file /etc/sysconfig/network-scripts/
ifcfg-eth0, configure the first NIC (eth0) on the installation server as follows:
• Static IP address: 192.168.1.1
• Network mask: 255.255.255.0
Example 3 Sample /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=”eth0”
BOOTPROTO=”static”
HWADDR=”aa:bb:cc:dd:ee:ff”
NM_CONTROLLED=”no”
ONBOOT=”yes”
TYPE=”Ethernet”
IPADDR=”192.168.1.1”
NETMASK=”255.255.255.0”

This NIC will be used to install Linux onto the Moonshot cartridge nodes, and must be connected
to the Moonshot chassis using one of the uplink ports (See the HP Moonshot Switch Module
Administrator’s Guide for information on how to configure the chassis switch, and uplink ports,
particularly if you are connecting at 1Gbps speeds, rather than the default 10Gbps speeds of the
uplink ports.)
If you use a different address space from 192.168.1.0/24, adjust your settings accordingly from
those in the example configurations below.
Figure 20 Base configuration
1. Public Network
2. Private Network (192.168.1.0/24)
1. Enter the following two commands to disable the system firewall:

• ~]# chkconfig iptables off
• ~]# service iptables stop
2. Disable SELinux by entering the command setenforce 0.
3. Edit the file /etc/sysconfig/selinux, changing the value of the SELINUX variable from
enforcing to disabled.
Setting up a network installation server 47

IMPORTANT: These settings make it easier to set up your installation server, but also disable the
firewall and Security-Enhanced Linux (SELinux). Ensure that your installation server is running within
a private environment before making these changes. If you must have your installation server
accessible via the Internet, refer to your Linux distribution’s documentation on how to configure
these services, rather than disabling them.
Installation server components

Beyond the basic operating system of your server, an installation server also uses the following:
• DHCP Server
• TFTP Server
• PXE Boot and Configuration Files
• OS Installation Files
• HTTP, NFS or FTP server for OS Installation Files
• (Optional) Automatic Installation Configuration Files (Kickstart, AutoYaST, Preseed)
While you can host these components on different physical (or virtual) systems, for the simplicity
of this guide we will be hosting them all on a single system.
Because HP ProLiant server cartridges support only network installation, you cannot install an
operating system on a cartridge without these services.
Configuring DHCP service

The first service to set up is the ISC DHCP daemon. The purpose of DHCP is to provide IP addresses
to your servers along with other information necessary to the network installation process.
1. Install the service with the command yum install dhcp.
2. Edit the file /etc/dhcp/dhcpd.conf and replace the current contents with the following:
option domain-name "moonshotnet";
default-lease-time 600;
max-lease-time 7200;
authoritative;
allow booting;
subnet 192.168.1.0 netmask 255.255.255.0 {

range 192.168.1.150 192.168.1.249;
option bootfile-name "pxelinux.0";
next-server 192.168.1.1;
}
This configures the DHCP daemon to provide IP addresses to any computer system on your
network. The allow booting, option bootfile-name, and next-server parameters
also gives any system which is PXE booting the details necessary to obtain the required
installation files.
3. Edit /etc/sysconfig/dhcpd and set the value of DHCPARGS to eth0. This restricts the
DHCP daemon to provide the DHCP service only on the eth0 interface.
4. Enter the following commands to enable the DHCP service:
chkconfig dhcpd on
service dhcpd start
IMPORTANT:
If you adapt settings such as the domain-name and IP address to your environment, make sure to
understand their impact to other parts of this installation guide and make adjustments accordingly.

TFTP server configuration
The Trivial File Transfer Protocol (TFTP) service is used to provide a small number of files to your
network booting system. The next-server parameter provided in the DHCP configuration
specifies the IP address of the TFTP server to access, and the option bootfile-nameparameter
defines the name of the boot file that the PXE client should request.
To setup the base TFTP server configuration:
1. Enter the following commands:
~]# yum install tftp-server syslinux
~]# chkconfig tftp on
~]# chkconfig xinetd on
~]# service xinetd start
This creates and configures the TFTP server to use a directory on your system to service TFTP
requests, by default /var/lib/tftpboot.
2. Populate the newly created directory with the first set of required files by entering the following
commands:
~]# cd /usr/share/syslinux
~]# cp pxelinux.0 menu.c32 chain.c32 /var/lib/tftpboot
~]# mkdir /var/lib/tftpboot/pxelinux.cfg
HTTP server for OS installation files

While TFTP is used to provide the starting set of files (the Kernel and Ramdisk, specifically) for a
network installation, other protocols are used for the bulk of the files used to deploy Linux. Most
Linux distributions support installation using HTTP, NFS and/or FTP. The following procedure installs
and configures the Apache web server so that it can provide the installation files over HTTP.
Installing Apache/httpd
1. Install Apache by entering the following command:
~]# yum install httpd
2. Start Apache/httpd:
~]# chkconfig httpd on
3. Set the service to start automatically at boot time:
~]# service httpd on
By default, this configures a directory found at /var/www/html to provide files via your web
server.
OS installation files
The next task is to extract the operating system installation files from your Linux distribution installation
media. In most cases, you will be working with an ISO file containing the operating system to be
installed.
Each model of HP ProLiant server cartridge requires a specific minimum version of certain Linux
distributions, due to certain device and driver requirements. See the interactive OS Support Matrix
for specific details on which Linux distribution versions are supported on the different HP ProLiant
server cartridges, available at:
http://h17007.www1.hp.com/us/en/enterprise/servers/management/operating-environments/
index.aspx
The process for copying the installation files is essentially the same for all Linux distributions (create
a directory for the files, mount the ISO, copy the files, and unmount the ISO.) The names of the
ISO files which you have may vary from those used in the following examples.

To install a single Linux distribution, perform the steps applicable to your chosen Linux distribution
below. There is no need to perform the steps for every mentioned distribution.
NOTE: There are special procedures for certain HP ProLiant server cartridges that are noted in
the following sections:
• “Preparing to install Linux on HP ProLiant m710 server cartridges” (page 53)
• “Preparing to reinstall Ubuntu on HP ProLiant m400 and m800 server cartridges” (page 54)
RHEL (CentOS, Scientific Linux, Fedora)

Red Hat Enterprise Linux (RHEL) has a number of associated Linux distributions, all of which are
configured in a similar fashion. These instructions work equally well for the corresponding versions
of CentOS, Scientific Linux and Fedora. Remember to change the names as appropriate. The
examples here use RHEL-6.5.
1. Make a directory for the extracted files:
~]# mkdir –p /var/www/html/os/rhel-6.5
2. Mount the installation ISO:
~]# mount -o ro,loop RHEL6.5-20131111.0-Server-x86_64-DVD1.iso /mnt
3. Copy the files from the ISO to the directory you made:
~]# cp -a /mnt/* /var/www/html/os/rhel-6.5
4. Unmount the ISO:
~]# umount /mnt
Ubuntu
Ubuntu is a Debian-based Linux distribution, and uses a different packaging format than RHEL or
its variants. Extracting the installation media, however, is performed in a similar fashion.
1. Make a directory for the extracted files:
~]# mkdir –p /var/www/html/os/ubuntu-14.04
2. Mount the installation ISO:
~]# mount -o ro,loop ubuntu-14.04-server-amd64.iso /mnt
3. Copy the files from the ISO to the directory you made:
~]# cp -a /mnt/* /var/www/html/os/ubuntu-14.04
4. Unmount the ISO:
~]# umount /mnt
SLES
Extracting files from SLES installation media is essentially the same process as other distributions.
However, certain HP ProLiant server cartridges require a special Kernel, Ramdisk and/or packages
for required device drivers. SUSE provides these using an image format called a kISO. You must
extract the contents of the kISO in addition to the standard installation media.
If your Moonshot cartridge requires the use of a kISO with SLES11SP3, obtain the image from
SUSE, at http://drivers.suse.com/hp/HP-ProLiant-Moonshot/

1. Extract the standard installation files from the media:
a. Make a directory for the extracted files:
~]# mkdir /var/www/html/os/sles-11sp3
b. Mount the installation ISO:
~]# mount -o ro,loop SLES-11-SP3-DVD-x86_64-GM-DVD1.iso /mnt
c. Copy the files from the ISO to the directory you made:
~]# cp -a /mnt/* /var/www/html/os/sles-11sp3
d. Unmount the ISO:
~]# umount /mnt
2. Extract the kISO files:
NOTE: The example kISO used here is for the HP ProLiant m300 Server Cartridge. The name
of the kISO file you use may vary.
a. Make a directory for the extracted files:
~]# mkdir /var/www/html/os/m300-kiso-1.0
b. Mount the kISO:
~]# mount -o ro,loop hp_proliant_m300-sle11sp3-x86_64-1.0.iso
/mnt
c. Copy the files from the kISO to the directory you made:
~]# cp -a /mnt/* /var/www/html/os/m300-kiso-1.0
d. Unmount the kISO:
~]# umount /mnt
PXE boot files

In addition to copying the OS installation files, you must also copy the Kernel and Ramdisk image
files to your TFTP server. Only complete the steps for the Linux distributions you wish to be able to
install.
RHEL
1. Make a directory for the files:
~]# mkdir /var/lib/tftpboot/rhel-6.5
2. Change directories:
~]# cd /var/www/html/os/rhel-6.5/images/pxeboot
3. Copy the files:
~]# cp initrd.img vmlinuz /var/lib/tftpboot/rhel-6.5
Ubuntu
1. Make a directory for the files:
~]# mkdir /var/lib/tftpboot/ubuntu-14.04
2. Change directories:
~]# cd
/var/www/html/os/ubuntu-14.04/install/netboot/ubuntu-installer/amd64
3. Copy the files:
~]# cp initrd.gz linux /var/lib/tftpboot/ubuntu-14.04

NOTE: Installing Ubuntu 14.04.1 on HP ProLiant m400 and m800 server cartridges requires
installation files compatible with ARM-based CPUs that are not present in typical installation media.
See “Preparing to reinstall Ubuntu on HP ProLiant m400 and m800 server cartridges” (page 54).
SLES
1. a. Make a directory for the files:
~]# mkdir /var/lib/tftpboot/sles-11sp3
b. Change directories:
~]# cd /var/www/html/os/sles-11sp3/boot/x86_64/loader
c. Copy the files:
~]# cp linux initrd /var/lib/tftpboot/sles-11sp3/
2. If your Moonshot cartridge requires a kISO, perform these steps:
NOTE: The example kISO used here is for the HP ProLiant m300 Server Cartridge. The name
of the kISO file you use may vary.
a. Make a directory for the files:
~]# mkdir /var/lib/tftpboot/sles-11sp3/m300-kiso-1.0
b. Change directories:
~]# cd /var/www/html/os/m300-kiso-1.0
c. Copy the files:
~]# cp linux initrd /var/lib/tftpboot/sles-11sp3/m300-kiso-1.0
PXE configuration files

Create the base network booting configuration file which ties all the pieces we have setup together.
Create a PXE configuration directory, and the default configuration file:
1. Create a PXE configuration directory, and the default configuration file:
~]# cd /var/lib/tftpboot
~]# mkdir pxelinux.cfg
2. Create the file default in the /var/lib/tftpboot/pxelinux.cfg/ directory:
3. Add the following lines to /var/lib/tftpboot/pxelinux.cfg/default:
SERIAL 0 9600
CONSOLE 0
PROMPT 0
ONTIMEOUT local
TIMEOUT 300
DEFAULT menu.c32
LABEL local
kernel chain.c32
append hd0 0
LABEL rhel-6.5
kernel rhel-6.5/vmlinuz
append initrd=rhel-6.5/initrd.img repo=http://192.168.1.1/os/rhel-6.5 console=ttyS0,9600n8
LABEL ubuntu-14.04
kernel ubuntu-14.04/linux
append initrd=ubuntu-14.04/initrd.gz console=ttyS0,9600n8
LABEL sles-11sp3
kernel sles-11sp3/m300-kiso-1.0/linux
append initrd=sles-11sp3/m300-kiso-1.0/initrd install=http://192.168.1.1/os/sles-11sp3
addon=http://192.168.1.1/os/m300-kiso-1.0 console=ttyS0,9600n8
This is a relatively standard network installation server setup. However, there are a few settings
which are specifically required by ProLiant server cartridges (notice the shaded type.) ProLiant

server cartridges are headless; they do not provide graphical output. Instead, they provide a basic
serial console.
To enable Linux to provide input/output to a serial console, the configuration file must include the
statements SERIAL 0 9600 and CONSOLE 0. These two statements configure the PXE environment
to use the serial port, and disable any graphical console.
Additionally, each boot entry has console=ttyS0,9600n8 in its append entry. This instructs
the Linux kernel to use the serial console after the PXE environment exits.
IMPORTANT: The SERIAL and CONSOLE statements, and the console= parameters in each
append entry, are REQUIRED to network boot a ProLiant server cartridge and direct it to use the
appropriate console device. However, if you were to network boot a traditional server on your
installation network, it also would be instructed to use its serial ports. For some ideas on compatibility
with traditional equipment, see “Moonshot and traditional network installation co-existence” (page
62).
Preparing to install Linux on HP ProLiant m710 server cartridges

The HP ProLiant m710 server cartridge includes the Mellanox 10Gbps NIC. To enable the use the
these NICs, some supported operating systems require additional components to be installed.
RHEL 6.5
A network installation of Red Hat Enterprise Linux 6.5 onto an HP ProLiant m710 server cartridge
requires a Red Hat Driver Update Package (DUP). Download the DUP from the Red Hat Network
(RHN). For more information about the DUP, see https://access.redhat.com/articles/64322.
The DUP is provided in ISO format, and must be packaged into an initrd-appendable image, and
extracted to a web server for use during the OS installation.
Preparing the DUP initrd image
1. Create a directory named /tmp/dup:
~]# mkdir /tmp/dup
2. Copy the ISO file downloaded from RHN into the new directory.
3. Change to the new directory:
~]# cd /tmp/dup
4. Rename the ISO file to dd.img:
/tmp/dup# cp <DUP_ISO> dd.img
5. Create the initrd image:
/tmp/dup# find . | cpio –quiet –o –H newc | gzip -9 >/tmp/m710.dup
This bundles the ISO image into a cpio archive which can be loaded with the initrd.
6. Copy m710.dup to the top level of your tftp server (for example, /var/lib/tftpboot.)
Extracting the DUP ISO
1. Make a directory for the files to be extracted from the DUP ISO:
~]# mkdir /var/www/html/m170-dup
2. Mount the DUP ISO (this makes the files available under /mnt):
~]# mount –o ro,loop /path/to/ISO/file /mnt
3. Copy the files from the DUP ISO to the directory you made:
~]# cp –a /mnt/* /var/www/html/m710-dup
4. Unmount the DUP ISO:
~]# umount /mnt

Update the PXE configuration
With the DUP image prepared, modify the RHEL6.5 PXE entries you created earlier (see “PXE
configuration files” (page 52)) to include values for an HP ProLiant m710 server cartridge.
Existing RHEL6.5 PXE entries:
LABEL rhel-6.5-auto
append initrd=rhel-6.5/initrd.img ksdevice=eth0 ks=http://192.168.1.1/answers/rhel-6.5.cfg console=ttyS0,9600n8
LABEL rhel-6.5-interactive
Modified RHEL6.5 PXE entries:

LABEL rhel-6.5-auto
append initrd=rhel-6.5/initrd.img,m710.dup ksdevice=eth0 ks=http://192.168.1.1/answers/rhel-6.5.cfg
console=ttyS0,9600n8
append initrd=rhel-6.5/initrd.img,m710.dup repo=http://192.168.1.1/os/rhel-6.5 console=ttyS0,9600n8
NOTE: The append statements are continuous lines. Do not add line breaks.
Preparing to install other Linux operating systems

To install other Linux operating systems onto an HP ProLiant m710 server cartridge:
• SLES11SP3—The ProLiant m710 server cartridge requires the use of a kISO to integrate the
updated drivers. The kISO is available from SUSE at http://drivers.suse.com/hp/
HP-ProLiant-Moonshot/. The SLES11SP3 installation process for the ProLiant m710 server
cartridge is similar to the ProLiant m300 server cartridge installation process. However, the
m710 does not require an <addon> section to be added to the autoyast.xml file.
Incorporate the included kernel and ramdisk as documented for the ProLiant m300 server
cartridge.
• RHEL7—Includes the required drivers for the HP ProLiant m710. Will install without additional
modification.
• Ubuntu 14.04—Includes the required drivers for the HP ProLiant m710. Will install without
additional modification.
Preparing to reinstall Ubuntu on HP ProLiant m400 and m800 server cartridges

The HP ProLiant m800 server cartridge has four 32–bit ARM processors, while the ProLiant m400
has one ARM processor. Both server cartridges support Ubuntu 14.04.1 with a 3.13 Linux kernel.
The operating system must have the following installer components and configurations to successfully
install and operate.
NOTE: All HP ProLiant m400 and m800 server cartridges come preinstalled with Ubuntu 14.04.1.
The default username and password are as follows:
• Username: ubuntu
• Password: ubuntu
The installation instructions included here are for reinstalling Ubuntu 14.04.1 if needed.
Downloading ARM-based Ubuntu 14.04.1 installation files

Typical Ubuntu 14.04 installation media does not contain installation files for the 32–bit TI Keystone
ARM processor. Follow these steps to download compatible versions of vmlinuz and initrd.gz
into the correct directory:

1. Make a directory for the files according to the server cartridge model:
~]# mkdir /var/lib/tftpboot/ubuntu-14.04.1/m<XXX>
Where m<XXX> is either m400 or m800.
2. Change to the newly created directory:
~]# cd /var/lib/tftpboot/ubuntu-14.04.1/m<XXX>
3. Enter the wget command to download the compatible kernel and RAMdisk files into the current
directory:
HP ProLiant m400 server cartridge
~]# wget http://ports.ubuntu.com/dists/trusty-updates/main/
installer-arm64/current/images/generic/netboot/xgene/uImage
installer-arm64/current/images/generic/netboot/xgene/uInitrd
The file size total is approximately 21 MB.
HP ProLiant m800 server cartridge
installer-armhf/current/images/keystone/netboot/vmlinuz
installer-armhf/current/images/keystone/netboot/initrd.gz
The file size total is approximately 15 MB.
Update the PXE configuration

Modify the PXE configuration you created earlier (see “PXE configuration files” (page 52)) or create
a new pxelinux.cfg file. See the following samples, which show entries for automatic or interactive
installation using a preseed file:

Example 4 HP ProLiant m400 server cartridge
MENU TITLE HP ProLiant m400 PXE Menu
PROMPT 1
TIMEOUT 300
ONTIMEOUT m400-Trusty-Installer-auto
LABEL m400-Trusty-Installer
MENU LABEL Ubuntu Trusty Installer Manual
KERNEL ubuntu-14.04.1/m400/uImage
APPEND initrd=ubuntu-14.04.1/m400/uImage console=ttyS0,9600n8r
LABEL m400-Trusty-Installer-auto
MENU LABEL Ubuntu Trusty Installer Automated Regular
APPEND initrd= ubuntu-14.04.1/m400/uInitrd
preseed/url=http://<hosting IP address>/ubuntu-14.04.1.cfg interface=auto
auto=true priority=critical console=ttyS0,9600n8r
Example 5 HP ProLiant m800 server cartridge
MENU TITLE HP ProLiant m800 PXE Menu

PROMPT 1
TIMEOUT 300
ONTIMEOUT m800-Trusty-Installer-auto
KERNEL ubuntu-14.04.1/m800/vmlinuz
APPEND initrd= ubuntu-14.04/m800/initrd.gz console=ttyS0,9600
APPEND initrd= ubuntu-14.04.1/m800/initrd.gz
preseed/url=http://<hosting IP address>/ubuntu-14.04.1.cfg interface=eth0
auto=true priority=critical console=ttyS0,9600n8
Performing an interactive Linux installation

Now that you have set up a network installation server, you are ready to deploy a Linux distribution
to your ProLiant server cartridge. The primary method for interacting with a ProLiant server cartridge
is using the Moonshot iLO CM firmware, which resides on the HP Moonshot 1500 Chassis
Management Module.
The Moonshot 1500 CM module has its own uplink which should be connected to your network.
If your network already provides DHCP, the Moonshot 1500 CM module automatically obtains
an IP address. Determine the IP address assigned either by reviewing your DHCP server’s logs, or
by connecting a DB9 Serial console to the DB9 port of the Moonshot 1500 CM module and running
the command show chassis info.
You can also configure a static IP address using the serial port. See the HP Moonshot iLO Chassis
Management CLI User Guide for additional details on interacting with the Moonshot iLO CM
firmware.
Once you have determined the IP address of your Moonshot 1500 CM module, you can use the
SSH protocol to login over the network. The default credentials for the Moonshot iLO CM firmware
are:
Username: Administrator

Password: password
Managing your cartridge node

Each cartridge in a chassis is identified by a number between 1 and 45. Each ProLiant server
cartridge can host one or four independent servers, depending on the model of cartridge. These
nodes are numbered between 1 and 4. A specific server node is identified by both the cartridge
and node designation. So, the first node on cartridge 14 would be identified as c14n1. Likewise,
the third node on cartridge 45 could be identified as c45n3.
Many commands in the Moonshot iLO CM firmware accept ranges for both the cartridge and
node designations.
For example, to display the power states of the first node on cartridges 1 through 9, enter this
command:
hpiLO-> show node power c1-9n1.
Or, to show the boot states of all four nodes on a four-server cartridge in slot 5, enter this command:
hpiLO-> show node boot c5n1-4.
Cartridge and node ranges can be used together in a single identifier, such as c1-45n1-4.
Configuring a node to boot from the network

To enable a network installation, a server node must be configured to boot from the network. For
the remaining examples, assume that you are working with a single node cartridge in slot 1 (c1n1).
There are two methods for setting the boot device for a Moonshot server. One method sets a
persistent setting, the other transient (one-time only.)
1. Configure c1n1 to persistently boot from the network, enter this command:
hpiLO-> set node boot pxe c1n1.
2. (Optional) To only boot from the network once (on the next boot), enter this command:
hpiLO-> set node bootonce pxe c1n1.
3. View the current boot settings of the cartridge:
hpiLO-> show node boot c1n1.
Be aware of what boot settings a cartridge is using at any given time. This becomes more important
later, when we discuss automated installations for multiple ProLiant server cartridges at once, where
data could be lost by network booting a previously established node.
Controlling a server node’s power state

1. Ensure that your node is powered off by entering this command:
hpiLO-> set node power off force c1n1.
2. View the power state of the cartridge to verify the cartridge is powered down:
hpiLO-> show node power c1n1
3. Power c1n1 back on:
hpiLO-> set node power on c1n1.
4. Clone your session, and in that cloned session connect to the serial console to view the progress
of the node as it boots from the network:
hpiLO-> connect node vsp c1n1
When the server node boots from the network, you should see a menu similar to the following:
Performing an interactive Linux installation 57

Figure 21 Server boot menu
5. Select the Linux distribution to install, and follow the prompts to complete the installation.
See the distribution’s documentation for additional details on the steps of an interactive
installation.
Performing an automated Linux installation

HP Moonshot System is focused on a high server density, single chassis approach. Interactively
installing Linux on 45 or 180 nodes within a single chassis is not practical. All Linux distributions
have a mechanism to automate their installation, using simple modification to the parameters used
during installation, and a text-based installation configuration file. This will enables users to install
a large number of servers simultaneously, without having to walk through the lengthy process for
each node.
The only special requirement for Moonshot is that the installation configuration files must specify
the use of the serial console for input and output.
Automatic installation configuration files

Store and serve installation configuration files the same way that you store operating system
installation files, using the Apache HTTP server installed earlier.
NOTE: On the installation server, create a directory to contain and serve the installation
configuration files:
~]# mkdir /var/www/html/answers
Any files you place in this directory are accessible through the URL http://192.168.1.1/answers/.
RHEL
RHEL, and its variants, use a mechanism called a Kickstart file to automate the installation process.
Kickstart files can be small, providing only the minimum amount of information required to complete
the installation (such as passwords, disk partitioning, software selection.)
1. Create a basic RHEL kickstart file named /var/www/html/answers/rhel-6.5.cfg.
2. Add the following lines to the file:
install
text
url --url=http://192.168.1.1/os/rhel-6.5/
lang en_US.UTF-8
keyboard us
network --device eth0 --noipv6 --bootproto dhcp
network --device eth1 --noipv6 --bootproto dhcp
rootpw --plaintext moonshot

user --name="moonshot" --gecos="moonshot" --shell="/bin/bash" --plaintext --password=moonshot
authconfig --enableshadow --passalgo=sha512 --enablefingerprint
firewall --disabled
selinux --disabled
timezone America/Chicago
bootloader --location=mbr --driveorder=sda --append="crashkernel=auto console=ttyS0n8"
poweroff
#reboot
zerombr
clearpart --all --drives=sda
part /boot --fstype=ext4 --size=700
part swap --recommended
part / --fstype=ext4 --size=1 --grow
%post
cat >>/etc/sudoers <<EOF
moonshot ALL=(ALL) ALL
EOF
%end
%packages
@base
@core
%end
3. Customize this configuration file as needed for your environment.

See additional information about the contents of a Kickstart file at http://fedoraproject.org/wiki/
Anaconda/Kickstart.
Update the Kickstart configuration for the HP ProLiant m710 server cartridge
To modify the Kickstart file for RHEL onto an HP ProLiant m710 server cartridge, do the following:
1. Add this line to the start of the file:
driverdisk –source=http://<your.install.server.ip>/m710-dup/
2. In the package section, add this line:
libmlx4
3. Create a %post section of the file with these lines:
%post
yum localinstall -y /root/DD-0/*mellanox*.rpm
sed -i -e 's/^blacklist mlx4_core/#blacklist mlx4_core/' –e 's/^blacklist mlx4_en/#blacklist mlx4_en/'
/etc/modprobe.d/mlx4.conf
%end
NOTE: The sed statement (shaded) is a continuous line. Do not add line breaks.
Ubuntu
Ubuntu uses a configuration file named a Preseed, which “seeds” configuration values in the
installer.
Creating a Preseed file for non-ARM based server cartridges
1. Create a file named /var/www/html/answers/ubuntu-14.04.cfg.
2. Add the preseed template lines found in the appendix to the file. See “Preseed template for
non-ARM based server cartridges” (page 79)
3. Customize the configuration file as needed for your environment.
See additional information about the contents of a Preseed file at https://help.ubuntu.com/
14.04/installation-guide/amd64/apb.html.
Creating a Preseed file for ARM-based server cartridges
Follow these steps to create a Preseed file for HP ProLiant m400 and m800 server cartridges:
1. Create a file named /var/www/html/answers/m<XXX>/ubuntu-14.04.1.cfg.
NOTE: In the automated installation portion of the PXE configuration menu, be sure to have
the correct URL to the Preseed file.
Performing an automated Linux installation 59

2. Add the preseed template lines found in the appendix to the file. See “Preseed template for
ARM based server cartridges” (page 80)
3. Customize the configuration file as needed for your environment.
See additional information about automating installation using preseeding at https://
help.ubuntu.com/14.04/installation-guide/armhf/apb.html.
SLES
The SLES configuration file, known as an AutoYaST file, is written in XML, and is more complex
than a Kickstart or Preseed file.
1. Create a file named /var/www/html/answers/sles-11sp3.xml.
2. Add the lines from “SLES configuration file” (page 81) to the file, modifying them as needed
for your environment.
Using this configuration, the system node powers off after the initial installation.
NOTE: The automated installation of SLES11SP3 onto an HP ProLiant m710 server cartridge
does not require the <addon> section (shaded) in the example linked above. Do not include
the <addon> section when installing SLES11SP3 onto an HP ProLiant m710.
3. After initial installation, configure the node to boot from HDD with the set node boot
command (unless you used the bootonce command for a single network boot.)
4. Power the node on.
Once the node boots, it will complete some additional configuration steps, and then power
off again. After this final power off, the node is ready for use.
See additional information about the contents of an AutoYaST file at http://users.suse.com/~ug/
autoyast_doc/.
PXE configuration
After setting up one or more automatic installation files, remember to add corresponding entries
in the pxelinux.cfg/default file to enable them:
SERIAL 0 9600
CONSOLE 0
PROMPT 0
ONTIMEOUT local
TIMEOUT 300
DEFAULT menu.c32
LABEL local
kernel chain.c32
append hd0 0
LABEL rhel-6.5-auto
append initrd=rhel-6.5/initrd.img ksdevice=eth0 ks=http://192.168.1.1/answers/rhel-6.5.cfg
console=ttyS0,9600n8
LABEL ubuntu-14.04-auto
append initrd=ubuntu-14.04/initrd.gz priority=critical auto=true
preseed/url=http://16.84.217.164/answers/ubuntu-14.04.cfg interface=em2 console=ttyS0,9600n8
LABEL ubuntu-14.04-interactive
append initrd=ubuntu-14.04/initrd.gz console=ttyS0,9600n8
APPEND initrd= ubuntu-14.04.1/m400/uInitrd
preseed/url=http://<hosting IP address>/m400_trusty.cfg interface=auto
auto=true priority=critical console=ttyS0,9600n8r

APPEND initrd=ubuntu-14.04.1/m400/uImage console=ttyS0,9600n8r
APPEND initrd= ubuntu-14.04.1/m800/initrd.gz
preseed/url=http://<hosting URL>/ubuntu-14.04.1.cfg interface=eth0
auto=true priority=critical console=ttyS0,9600n8
APPEND initrd= ubuntu-14.04.1/m800/initrd.gz console=ttyS0,9600
LABEL sles-11sp3-auto
addon=http://192.168.1.1/os/m300-kiso-1.0 autoyast=http://192.168.1.1/answers/sles-11sp3.xml console=ttyS0,9600n8
LABEL sles-11sp3-interactive
addon=http://192.168.1.1/os/m300-kiso-1.0 console=ttyS0,9600n8
The new entries are shaded in the example above. If you network boot a node on an HP ProLiant
server cartridge, three additional entries now display. Choosing an entry will complete an installation
of your chosen Linux distribution without user intervention, other than to select which OS to install.
However, for large scale deployments of 45 or even 180 server cartridge nodes, even that single
interaction requires you to open a console session to each and every server to select which entry
to boot.
Enabling large scale deployments

To enable the completely automatic and unattended installation of a given Linux distribution, modify
the pxelinux.cfg/default file:
1. Open pxelinux.cfg/default for editing.
2. Change the ONTIMEOUT parameter to match one of the new LABEL values.
For example, to install RHEL6.5 automatically, change the value as follows:
ONTIMEOUT rhel-6.5-auto
WARNING! By choosing a label entry for the ONTIMEOUT value as shown above, all systems
that network boot from your installation network will now automatically start to install RHEL6.5,
erasing any data present. This potentially even includes systems that are not hosted in the Moonshot
1500 Chassis, if they are set to network boot from your installation network.
NOTE: If your installation configuration file causes the system to reboot after installation, the OS
installation will start all over again, in a loop. The example configuration files provided in this
guide all power the system down after installation. This gives you the opportunity to either change
the boot order of the nodes, or modify the ONTIMEOUT value in the pxelinux.cfg/default
file.
Server-specific PXE configuration files

The default network boot process (for HP Moonshot System or otherwise) checks for a sequence
of configuration files, and if none are found, the process loads the pxelinux.cfg/default.
This file check makes it possible to configure your installation server to direct network booted
machines to perform different tasks/installations on boot. For example, you might create a specific
configuration file for a given server to install RHEL, but then direct any other system which network
boots to skip the installation and boot instead from HDD.
The PXE ROM searches for the following files in the sequence shown:
1. pxelinux.cfg/01-88-99-aa-bb-cc-dd (MAC address)
2. pxelinux.cfg/C000025B (IP address in hex)
3. pxelinux.cfg/C000025
Performing an automated Linux installation 61

7. pxelinux.cfg/C00
8. pxelinux.cfg/C0
9. pxelinux.cfg/C
10. pxelinux.cfg/default
The first file searched for is named representing the MAC address of the network boot interface
of the system being installed (notice the use of dashes instead of colons). In this example, the MAC
address of the network boot interface is 88:99:aa:bb:cc:dd.
This makes it possible to create a single configuration file for a specific server, and not affect any
other system which may network boot at the same time. For example, to create a configuration
that automatically directs a server with the MAC address used above to install RHEL6.5, copy the
default file you previously created and rename it with the network boot interface MAC address
of an HP ProLiant server cartridge node (this can be done with a single command). For example:
~]# cp pxelinux.cfg/default pxelinux.cfg/01-88-99-aa-bb-cc-dd
Then edit the new file to change the ONTIMEOUT value as suggested previously (see “Enabling
large scale deployments” (page 61). Now when that server network boots, it will find the matching
configuration file and load it. Other servers will continue to load the default file.
The other files in the search pattern described above are the hexadecimal representation of the IP
address assigned to the system by your DHCP server, from most specific to less specific. It is possible
to configure a DHCP server to assign specific IP address ranges to certain servers, and then use
this capability to cause those same servers to load a common configuration file. More details on
this capability are available at http://www.syslinux.org/wiki/index.php/PXELINUX.
Moonshot and traditional network installation co-existence

Now that you have configured an HP Moonshot System to network boot, you can see that there’s
not that much difference between it and other servers, such as HP ProLiant DL/SL/BL systems. The
only HP Moonshot-specific configurations we made is the serial port configurations. It is important
to note that if you were to network boot a non-HP Moonshot server on your installation network,
it would be instructed to send its console output to its first serial port. And if you were to remove
the serial configuration parameters from pxelinux.cfg/default and the installation
configuration files, a traditional server would boot normally but HP ProLiant server cartridge nodes
would no longer be able to output to the console.
An HP Moonshot system can coexist with other servers on the installation network using the feature
discussed in “Server-specific PXE configuration files” (page 61).
For example, if you had only a few other types of servers on your network, but several Moonshot
1500 Chassis, you would likely want to configure the pxelinux.cfg/default file with the
Moonshot configurations as discussed is the sections above, and then create server-specific
configuration files based on the MAC address or hex-encoded IP address values for each of the
other servers.
If you have an equal amount of non-HP Moonshot servers as HP ProLiant server cartridge nodes
on your network, the decision of which to make the default configuration is up to you. Alternatively,
you might to explore the option of setting up a separate installation server and installation network
for each type of server (HP Moonshot Systems on one, all others separate).
Post deployment
The first step, post installation, is to prevent the system from installing again. If you keep a specific
system booting from the network by default, and have set your pxelinux.cfg/default file to
automatically install, then your system will reinstall the operating system again on its next boot.

To prevent reinstallation on boot:
1. Do one of the following:
• Edit pxelinux.cfg/default and set the value for ONTIMEOUT to local.
• Set your nodes to boot directly from the hard drive by entering the set node boot
command while logged into the Moonshot iLO CM firmware CLI. For example:
hpiLO-> set node boot hdd c1n1.
Replace c1n1 with the appropriate node designation or range.
2. Then power the node back on with the set node power command:
hpiLO-> set node power on c1n1.
After a few minutes, your system will have booted into the Linux operating system.
3. Connect to the console using the connect node VSP command:
hpiLO-> connect node vsp c1n1
You should receive a login prompt.
4. If you used the configuration examples provided above, login to your system using the
credentials:
Username: moonshot
Password: moonshot
NOTE: The root password has also been configured to moonshot as well. HP recommends
that you change these password values in the configuration files used above or shortly after
installation using the passwd command on your system
5. (HP ProLiant m800/m400 Server Cartridge, optional) Change kernel boot parameters.
Since the HP ProLiant m400 and m800 server cartridges have ARM processor based servers,
they do not have support for typical boot-loaders like GRUB. Instead, the BIOS (U-boot) acts
as both the BIOS and a boot-loader. Use the U-Boot environment variable bootargs to hold
the list of parameter options passed to the Linux kernel, as the kernel's command line
parameters. Typical users will not have to change boot parameters.
a. Create this file on the new operating system install:
$ sudo vi /usr/share/flash-kernel/ubootenv.d/m<XXX>
Where m<XXX> is either m400 or m800.
b. Add lines to the file that set boot parameters using the following style:
setenv bootargs $args_vendor foo=bar
For example, to increase the kernel logging level, add the following:
setenv bootargs $args_vendor loglevel=7
c. Invoke the flash kernel and then reboot:
$ sudo flash-kernel
$ sudo reboot
Flash-kernel is a Linux OS utility that takes the kernel (/boot/vmlinuz) and RAMdisk
(/boot/initrd.img) and generates U-boot images uImage, uInitrd, and boot.scr
with the help of mkimage. This step is required because U-boot cannot load the kernel
and RAMdisk directly and requires special images made with mkimage.
You do not need to continue to use the Virtual Serial Port as your only method of logging into your
system. Instead, enter the ipconfig command to determine the IP address of your system, and
then use an SSH client to connect directly to the system.
Post deployment 63
You are now ready to load additional software and workloads as you would with any traditional
Linux system. Refer to your Linux distribution’s documentation for details on further configuration.
Installing MCSDK-HPC on HP ProLiant m800 server cartridge nodes

The Texas Instruments Multicore Software Development Kit for High Performance Computing
(MCSDK-HPC) is an add-on to the MCSDK, and provides HPC specific software modules and
algorithm libraries. This provides a development environment to offload HPC applications to
multi-core DSPs.
NOTE: Portions of this section were adapted from the guide MCSDK HPC 3.x Getting Started
Guide for HP ProLiant m800 available at http://processors.wiki.ti.com/index.php/
MCSDK_HPC_3.x_Getting_Started_Guide_for_HP_ProLiant_m800. The material used here (and
only in this section) is covered under Creative Commons Attribution-Share Alike 3.0 license.
Preparing to fetch TI packages from PPA

Add the required repositories to fetch and install MCSDK-HPC software.
1. Enter an http proxy:
# export http_proxy=http://<your_proxy>:<port>
2. Enter an https proxy:
# export https_proxy=http://<your_proxy>:<port>
3. If necessary, install python:
# sudo apt-get install python-software-properties
4. Add the PPA repository:
# sudo -E add-apt-repository ppa:<ppa name>
Installing MSCSDK-HPC
To install MSCSDK-HPC, refresh the package lists from the repositories and then install new
repository package:
1. Refresh the package lists:
# sudo apt-get update
2. Install the Keystone-HPC from the repository:
# sudo apt-get-install keystone-hpc
3. When the installation is complete, reboot the node.
# reboot
Verifying installation
After a reboot, the state of the CMEM kernel module can be used to determine the success of the
installation. Upon successful installation, the CMEM module will be automatically inserted and
given the proper permissions.
1. Verify the CMEM module was automatically inserted. Use the lsmod command to displays
a list of all kernel modules:
# lsmod
Module Size Used by
cmemk 25691 0
uio_module_drv 5020 0
If cmemk is not listed, then there was an issue with installation.
2. Verify that CMEM has the correct permissions.
Default installation gives CMEM world read/write permissions:

# ls -l /dev/cmem
crw-rw-rw- 1 root root 250, 0 Apr 30 08:46 /dev/cmem
These permissions are controlled by the UDEV rules found in the file /etc/udev/rules.d/
20-tci6636k2h.rules, and may be modified to suit system security requirements.
3. Verify that mpmsrv is running.
Default installation configures an upstart job to start mpmsrv (etc/init/mpm.conf)
# ps ax | grep "mpmsrv"
The mpmsrv service needs to be started prior to the /etc/init/keystone-hpc.conf
upstart task, since it is used to enable and configure hyperlink ports.
Installing MAAS support on HP ProLiant m400 and m800 server cartridge nodes
Canonical’s Metal As A Service (MAAS) allows HP ProLiant m400 and m800 server cartridge
nodes to be a pool of resources in a dynamic environment. MAAS can provide OS deployment
and application Charm deployments, particularly for Cloud-based solutions. In conjunction with
the Juju service orchestration software (see https://juju.ubuntu.com/docs/), and a MAAS server,
MAAS enables you to maximise the performance of your physical hardware and dynamically
deploy complex services.
For MAAS support installation instructions (including enabling at deployment or enabling
post-deployment) see http://maas.ubuntu.com/docs/install.html.
Post deployment 65
4 Support and other resources
Information to collect before contacting HP
Be sure to have the following information available before you contact HP:
• Software product name
• Hardware product model number
• Operating system type and version
• Applicable error message
• Third-party hardware or software
• Technical support registration number (if applicable)
How to contact HP
Use the following methods to contact HP technical support:
• In the United States, see the Customer Service / Contact HP United States website for contact
options:
http://welcome.hp.com/country/us/en/contact_us.html
• In the United States, call 1-800-HP-INVENT (1-800-474-6836) to contact HP by telephone.
This service is available 24 hours a day, 7 days a week. For continuous quality improvement,
conversations might be recorded or monitored.
• In other locations, see the Contact HP Worldwide website for contact options:
http://welcome.hp.com/country/us/en/wwcontact.html
Security bulletin and alert policy for non-HP owned software components
Open source software (such as OpenSSL) or third-party software (such as Java) are sometimes
included in HP products. HP discloses that the non-HP owned software components listed in the
Matrix Operating Environment end user license agreement (EULA) are included with Matrix OE.
To view the EULA, use a text editor to open the /opt/vse/src/README file on an HP-UX CMS,
or the <installation-directory>\src\README file on a Windows CMS. (The default
installation directory on a Windows CMS is C:\Program Files\HP\Virtual Server
Environment, but this directory can be changed at installation time.)
HP addresses security bulletins for the software components listed in the EULA with the same level
of support afforded HP products.
HP is committed to reducing security defects and helping you mitigate the risks associated with
security defects when they do occur. HP has a well defined process when a security defect is found
that culminates with the publication of a security bulletin. The security bulletin provides you with a
high level description of the problem and explains how to mitigate the security defect.
Registering for software technical support and update service

Insight Management includes one year of 24 x 7 HP Software Technical Support and Update
Service. This service provides access to HP technical resources for assistance in resolving software
implementation or operations problems.
The service also provides access to software updates and reference manuals in electronic form as
they are made available from HP.

With this service, Insight Management software customers benefit from expedited problem resolution
as well as proactive notification and delivery of software updates. For more information about this
service, see the following website:
http://www.hp.com/services/insight
Registration for this service takes place following online redemption of the license certificate.
How to use your software technical support and update service

As HP releases updates to software, the latest versions of the software and documentation are
made available to you. The Software Updates and Licensing portal gives you access to software,
documentation and license updates for products on your HP software support agreement.
You can access this portal from the HP Support Center:
http://www.hp.com/go/hpsc
After creating your profile and linking your support agreements to your profile, see the Software
Updates and Licensing portal at http://www.hp.com/go/hpsoftwareupdatesupport to obtain
software, documentation, and license updates.
HP authorized resellers
For the name of the nearest HP authorized reseller, see the following sources:
• In the United States, see the HP U.S. service locator web site:
http://www.hp.com/service_locator
• In other locations, see the Contact HP worldwide web site:
http://welcome.hp.com/country/us/en/wwcontact.html
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/country/us/en/contact_us.html
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Typographic conventions
This document uses the following typographical conventions:
Book title The title of a book. On the web, this can be a hyperlink to the book itself.
Command A command name or command phrase, for example ls -a.
Filename The name of a file or the path to a file location.
Computer output Information displayed by the computer.
Ctrl-x or Ctrl-x A key sequence that indicates you must hold down the keyboard key labeled
Ctrl while you press the letter x.
ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH.
Key The name of a keyboard key. Return and Enter both refer to the same key.
Term A term or phrase that is defined in the body text of the document, not in a
glossary.
User input Indicates commands and text that you type exactly as shown.
<Replaceable> The name of a placeholder that you replace with an actual value.
HP authorized resellers 67
[] In command syntax statements, these characters enclose optional content.
{} In command syntax statements, these characters enclose required content.
| The character that separates items in a linear list of choices.
... Indicates that the preceding element can be repeated one or more times.
WARNING An alert that calls attention to important information that, if not understood
or followed, results in personal injury.
CAUTION An alert that calls attention to important information that, if not understood
or followed, results in data loss, data corruption, or damage to hardware
or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.

A Frequently used Windows EMS commands
EMS Commands
List of available EMS commands
EMS command Description
il Get the OS IP address.
id Get hardware information.
t Get a list of running processes.
? Get help.
cmd Launch a cmd.exe shell.
SAC commands
The following list describes SAC commands for remote management tasks.
SAC command Description
ch Lists all channels
cmd Creates Windows command-prompt channels. To use a

command-prompt channel, you must provide valid logon credentials.
You must log on to each command-prompt instance.
crashdump Manually generates a Stop error message and forces a memory dump
file to be created.
D Dumps the current kernel log.
F Toggles the information output by the t-list command, which shows

processes only, or shows processes and threads
I If no parameters are passed, this command lists IP information.

You can configure IP parameters to display or set the IP address, subnet
mask, and gateway of a given network interface device by providing
the network number, IP address, and subnet information. To do so, use
the following format: <network#><IPaddress><subnet>
Id Displays identification information about the server
K<PID> Ends the given process. PID is the process identification number.
L<PID> Lowers the priority of a process (and any associated child processes)
to the lowest possible level. Lock Restricts access to EMS
command-prompt channels. You must provide valid logon credentials
to unlock a channel.
M<PID> Limits the memory usage of a process (and any associated child
MB-allow processes) to a specified number of megabytes. MB is the number of
megabytes you specify.
P Causes t-list command output to pause after displaying one full screen
of information.
R<PID> Raises the priority of a process and any associated child processes up
by one level.
restart Restarts the computer.
EMS Commands 69
SAC command Description
S If no parameters are passed, this command displays the current date

using the 24-hour clock format. You can set the system time by providing
the date and, optionally, the time in this format: mm/dd/yyyyhh:mm.
shutdown Shuts down the computer. Do not use this command unless you can be
physically present at the computer when you are ready to restart it.
T Lists the processes and threads that are currently running.
? or help Lists the available commands.
Channel-management commands
The following list describes the subset of SAC commands available for managing channels.
Command Description
ch Lists all channels
ch -si <n> Changes to the channel with the number, n, which you
specify.
ch -sn <name> Changes to the channel with the name you specify.
ch -ci <n> Closes the channel with the number, n, which you specify
ch -cn <name> Closes the channel with the name you specify.
Esc+Tab Enables you to change channels.
Esc+Tab 0 Returns you to the SAC channel.
ch -? Displays the channel-management commands Help.
70 Frequently used Windows EMS commands

B Microsoft Windows Deployment Services installation
The information in this section describes the initial setup of a Windows Deployment Server.
WDS requirements
In this example, WDS requires a system running Microsoft Windows Server 2012 or later in
stand-alone mode.
WDS requires the following network components:

• A DHCP server for providing IP addresses to PXE clients.
• A DNS server.
NOTE: The network configuration should allow cartridges to acquire IP addresses from the DHCP
server, and access the WDS Server.
WDS Volume
• The volume that provides storage must be NTFS with enough space to hold a number of
Windows images depending on need. Images are compressed, but as options are added to
the server more disk space is required. Microsoft does not recommend using a system volume
as the WDS store.
• The default Windows media is approximately 4 GB in size and may contain different Windows
products or SKUs and options (for example, Server Core or Server with a GUI). All options
are included in the INSTALL.WIM file.
Microsoft OS SKUs
Below is the OS package list included into the Microsoft Windows Images (Install.WIM) that may
be deployed to the Moonshot cartridges. HP MWDP script uses Microsoft Deployment Image
Servicing and Management (DISM.exe) to build an image which can be deployed as a base OS
. Windows Server 2012, for example, has four different SKUs (referred to as Indexes by DISM).
• Windows Server 2012 — four server SKUs:
◦ Windows Server Standard
◦ Windows Server Standard Core
◦ Windows Server Datacenter
◦ Windows Server Datacenter Core
• Windows Server 2012 RS — four server SKUs:
◦ Windows Server Standard
◦ Windows Server Standard Core
◦ Windows Server Datacenter
◦ Windows Server Datacenter Core
• Windows 7 Enterprise with SP1 (x64)
• Windows 7 Professional with SP1 (x64)
• Windows 7 Enterprise with SP1 (x86)
• Windows 7 Professional with SP1 (x86)
WDS requirements 71
Installing WDS
IMPORTANT: This describes a WDS server in stand-alone mode only, and does not require Active
Directory.
Follow these steps to perform an installation on the Windows Server 2012 computer targeted as
the deployment server, running in stand-alone mode:
Installing the WDS role on the system

1. Sign in to the server as a member of the local Administrators group.
2. Server Manager starts automatically. If it does not start, click Start, type server manager,
and then click Server Manager.
3. Click Manage.
4. Click Add Roles and Features, and then click Next.
5. On the Before You Begin page of the Add Roles and Features Wizard, click Next.
Figure 22 Microsoft Windows Server 2012 — Add roles and features
6. On the Select Installation Type page, click Role-based or Feature-based Installation and then
click Next.
7. On the Select Destination Server page, select the appropriate server, and then click Next. The
local server is selected by default.
8. On the Select Server Roles page, scroll down and select the Windows Deployment Services
check box. Click Next. (Remote Server Administration Tools are required to manage this
feature.)
9. Select Include Management Tools (if applicable). Click Add Features. Click Next.
10. On the Select Features page, click Next.
11. On the Select Role Services page, by default both the Deployment Server and Transport Server
are selected, leave these role services selected and click Next.
12. On the Confirm Installation Selections page, click Install.
13. Windows Deployment Services is added to the server. Installation progress is illustrated in the
Add Roles and Features Wizard.
NOTE: Alternatively you can use the PowerShell command:
Install-WindowsFeature-Name WDS-IncludeAllSubFeature-IncludeManagementTools
72 Microsoft Windows Deployment Services installation

The default installation folder of WDS is \RemoteInstall and is referred to as the WDS store.
It is shared as REMINST.
WDS creates several sub-directories containing:
• .\Boot — containing boot images.
• .\Images — containing OS install images.
• .\WdsClientUnattend — containing unattend files to deploy clients.
Configuring WDS
There are two ways to configure and manage WDS. The first uses the GUI interface installed with
the role. The second uses the WDSUtil.exe command line interface available in either a CMD
or PowerShell environment.
Configuring the WDS server in stand-alone mode

1. Sign in to the server as a member of the local Administrators group.
2. Server Manager starts automatically.
3. If it does not automatically start, click Start, type server manager, and then click Server
Manager.
4. Click Tools, and then click Windows Deployment Services to launch the Windows Deployment
Services MMC snap-in (or console).
5. In the left pane of the Windows Deployment Services MMC snap-in, expand the list of servers.
6. Right-click the desired server, click Configure Server.
7. Click Next on the Before you Begin page.
8. On the Install Options page, choose Standalone server.
9. On the Remote Installation Folder Locations page, choose an NTFS volume. The volume must
be NTFS with enough space to accommodate all your images, including customized images.
On this volume create a folder called RemoteInstall and select it as the Remote Installation
folder. Alternatively, choose the default path if the server does not have additional volumes.
10. Click Next.
NOTE: If your server is running as a DHCP Server, you will see the Proxy DHCP Server page.
The default options selected are: Do not listen on DHCP and DHCPv6 ports and Configure
DHCP options for Proxy DHCP. Click Next.
11. On the PXE Server Initial Settings page, choose Respond to Only known clients, choose the
option to define known client computers.
12. Click Next to complete WDS configuration.
13. You are prompted to add images to the server. If you wish to add images later, clear the Add
Images to Server now checkbox, and then click Finish. The next section walks you through the
process for adding images to WDS.
If you are not prompted to add images:
Your server might have failed to start due to timeouts. In this case, open Windows Server
Manager and do the following:
1. Select your "Local Server"
2. Select Tools.
3. Select Windows Deployment Services.
4. In the Windows Deployment Services console, select Servers.
5. Right click on the server to open the contextual menu.
6. Select All Tasks and Start.
You must then add images manually as described in the next section.
14. If you want to modify any of the settings on the server, right-click the server in the Windows
Deployment MMC Snap-in, and click Properties.
WDS requirements 73
First time configuration
The WDS Management console snap-in uses a configuration wizard to step you through the initial
configuration including the option for boot and installation images.
NOTE: Do not use the images from the default Windows media when deploying Windows to
HP ProLiant Moonshot Servers, they are referenced here as a normal step for configuring WDS on
the assumption that not only ProLiant Moonshot servers will be deployed from this WDS server.
Adding default boot images from the product media to the WDS store is one of the first configuration
steps. The boot image consists of the Windows Preinstallation Environment (WinPE) and Windows
setup. A minimum of one boot image is required for each architecture type, i.e x86, x64, and so
on.
NOTE: HP ProLiant Moonshot Server Cartridges are based on x64 processors and run the 64-bit
versions of Windows Operating Systems. However, the HP ProLiant m700 server cartridge supports
both the 32-bit and 64-bit versions of Windows 7 Enterprise and Professional Editions with SP1.
Use the custom images that correspond to the appropriate architecture.
1. Insert the Windows media into the DVD drive on the WDS server. Alternatively, you can copy
boot.wim from the \sources folder to a file system accessible from the WDS server.
2. In the WDS management console, right-click the Boot Images container and click Add Boot
Image, when prompted to locate an image, point to the folder containing the boot.wim file.
3. When complete, click the Boot Images container to verify that the image was added.
Adding Windows media images to the WDS store

This step adds the actual Windows image to the WDS store. There are four different Windows
SKUs included on the Windows Server 2012 or 2012 R2 media and one SKU for each processor
architecture of Windows 7 Enterprise or Professional with SP1. They are located in the
install.wim file.
Installation images can be stored in the WDS server in groups or containers; HP recommends that
you create groups based on Windows versions and/or customizations.
1. Insert the Windows media in the DVD drive on the WDS server. Alternatively, copy
install.wim from the /sources folder on the media to a file system accessible from the
WDS server.
2. In the WDS management console, right-click the Install Images container and click Add Image
group. For example, HP ProLiant Moonshot Servers.
3. Right-click the newly created container and select Add Install image.
4. On the next screen, click Browse and locate the install.wim file and continue through the
remaining screens.
5. Repeat steps 1 to 4 for each Microsoft Windows Operating system deployed using WDS.
74 Microsoft Windows Deployment Services installation

6. By default, four images are installed in this process in the case of Windows Server 2012 or
Windows Server 2012 R2 and one each for the 32-bit and 64-bit versions of Windows 7
with SP1. You can change the name and include a description of each image. The image
name appears in the management applet image group and is displayed to the user during
the PXE installation process.
Figure 23 WDS management console
In “WDS management console” (page 75), the install image group is HP ProLiant Moonshot
Servers.
The Pre-staged Devices container is used to store devices that are pre-staged for WDS. In
stand-alone mode these devices are stored on the local WDS server. Pre-staging devices allows
you to manage or customize settings at the device level without impacting other server types.
In our example, we pre-stage devices and associate client unattend files to each device in
order to automate Windows deployment. The Drivers container contains driver packages that
have been added to the WDS store.
WDS requirements 75
C Sample WDScapture.inf file entries
NOTE: This sample is intended for Windows 7. To modify it for another OS, everything that
corresponds to Windows 7 must be changed.
[Capture]
Unattended=Yes
VolumeToCapture=D:
SystemRoot=windows
ImageName="MoonshotWin7Capture"
ImageDescription="Moonshot Win7 Ent SP1 & WinUpdate, AMD"
DestinationFile=D:\MoonshotWin7Capture.wim
Overwrite=Yes
[ExclusionList]
$ntfs.log
hiberfil.sys
pagefile.sys
"System Volume Information"
RECYCLER
winpepge.sys
%SYSTEMROOT%\CSC
[WDS]
UploadToWDSServer=Yes
WDSServerName=hp-wds01
WDSImageGroup="Moonshot Win7 Enterprise SP1"
Username=ris
Domain=hpaddev.com
Password=Abcdef12
DeleteLocalWimOnSuccess=No
76 Sample WDScapture.inf file entries

D Enabling EMS in the Windows Recovery Environment
(WinRE)
Windows Recovery Environment (Windows RE) is an extensible recovery platform based on WinPE.
When the computer fails to start, Windows automatically fails over into this environment, and the
Startup Repair tool in WinRE automates the diagnosis and repair to the Windows system. If
Windows is running on a ProLiant Moonshot server were to fail over to the WinRE environment,
the administrator may not be aware that this has occurred because EMS is not enabled in the
WinRE environment by default. The following describes two methods for enabling EMS in the
WinRE environment. The first outlines the steps to enable EMS after the Operating System is installed,
and the second describes a way of enabling EMS in WinRE during Windows deployment.
There are a few different ways of enabling EMS in the Windows BCD store. One way is to take
advantage of BCD inheritance in which EMS is enabled in the bootloader settings identifier,
which in turns applies to all entries in the bootloader. A second approach is to only enable
EMS on the particular bootloader entry. Since ProLiant Moonshot servers are headless, we
suggest enabling EMS globally so EMS will be enabled by default on all bootloader entries.
Enabling EMS in the WinRE bootloader from a running operating system

1. Open an elevated CMD shell and enter:
bcdedit.exe /enum {bootloadersettings}
2. If EMS appears in the settings list with a value of “on” then no further configuration is required.
A value of “on” indicates that EMS is enabled for all bootloader entries through BCD
inheritance, unless specifically disabled on a particular bootloader entry.
3. If EMS does not appear in the {bootloadersettings} output, then enable EMS by entering:
bcdedit.exe /set {bootloadersettings} ems on
4. To verify the operation, enter:
With this change, if an error occurs resulting in Windows booting into WinRE, EMS will load with
SAC support allowing the system administrator to triage the system.
Programmatically enabling EMS in the WinRE bootloader during

Windows installation
1. Edit the image unattend file to add the following setting:
<FirstLogonCommands>
<SynchronousCommand wcm:action=”add”>
<CommandLine>cmd.exe /c bcdedit.exe /set {bootloadersettings} ems on </CommandLine>
<Description>EnableEMSglobally in the BootloaderSettings</Description>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
2. After the operating system is installed, verify that EMS is enabled:

Detecting WinRE environment at SAC on boot

At the SAC prompt, open a command prompt with cmd.exe, and switch to the newly created
channel.
1. At the SAC> prompt, enter cmd.
2. Press Esc+Tab to switch to the new channel.
Enabling EMS in the WinRE bootloader from a running operating system 77

3. Enter the following command:
reg query "HKLM\Software\Microsoft\Windows_NT\CurrentVersion" /v
InstallationType
The value returned or this key is one of the following:
• Client (for Windows 7 Enterprise with SP1)
• Server (for Windows Server 2012 or 2012 R2)
• WindowsPE (for Windows Recovery Environment)
NOTE: Note InstallationType is WindowsPE, indicating that the node was booted from
standard Windows 7 Enterprise with SP1.
Figure 24 Reg query on a ProLiant m700 server cartridge node
Note InstallationType is Client, which indicates the node was booted from a standard Windows
Recovery Environment (WinRE).
78 Enabling EMS in the Windows Recovery Environment (WinRE)

E Preseed template for non-ARM based server cartridges
Copy and paste the following lines into /var/www/html/answers/ubuntu-14.04.cfg and
customize as needed for your environment.
d-i debian-installer/locale string en_US
d-i console-setup/ask_detect boolean false
d-i keyboard-configuration/layoutcode string us
d-i netcfg/choose_interface select auto
d-i netcfg/dhcp_timeout string 60
d-i netcfg/get_hostname string unassigned-hostname
d-i netcfg/get_domain string unassigned-domain
d-i netcfg/get_gateway none
d-i mirror/country string manual
d-i mirror/http/hostname string 192.168.1.1
d-i live-installer/net-image string http://192.168.1.1/os/ubuntu-14.04/install/filesystem.squashfs
d-i mirror/http/directory string /os/ubuntu-14.04
d-i clock-setup/utc boolean true
d-i time/zone string US/Central
d-i clock-setup/ntp boolean false
d-i partman-auto/disk string /dev/sda
d-i partman-auto/method string regular
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-md/device_remove_md boolean true
d-i partman-lvm/confirm boolean true
d-i partman-auto/choose_recipe select atomic
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true
d-i partman-md/confirm boolean true
d-i base-installer/kernel/image string linux-generic
d-i passwd/user-fullname string Moonshot
d-i passwd/username string moonshot
d-i passwd/user-password password moonshot
d-i passwd/user-password-again password moonshot
d-i user-setup/allow-password-weak boolean true
d-i user-setup/encrypt-home boolean false
tasksel tasksel/force-tasks string server
#tasksel tasksel/first multiselect standard, ubuntu-server
d-i pkgsel/include string openssh-server build-essential
d-i grub-installer/only_debian boolean true
d-i grub-installer/with_other_os boolean true
d-i finish-install/reboot_in_progress note
d-i debian-installer/exit/halt boolean true
d-i debian-installer/exit/poweroff boolean true
xserver-xorg xserver-xorg/autodetect_monitor boolean true
xserver-xorg xserver-xorg/config/monitor/selection-method \
select medium
xserver-xorg xserver-xorg/config/monitor/mode-list \
select 1024x768 @ 60 Hz
79
F Preseed template for ARM based server cartridges
Copy and paste the following lines into /var/www/html/answers/m800/
ubuntu-14.04.1.cfg and customize as needed for your environment.
#### Contents of the preconfiguration file
### Localization
# Preseeding only locale sets language, country and locale.
d-i debian-installer/locale string en_US
# Keyboard selection.
# Disable automatic (interactive) keymap detection.
d-i console-setup/ask_detect boolean false
#d-i keyboard-configuration/modelcode string pc105
d-i keyboard-configuration/layoutcode string us
### Network configuration
# skip displaying a list if there is more than one interface.
d-i netcfg/choose_interface select auto
# If you have a slow dhcp server and the installer times out waiting for
# it, this might be useful.
d-i netcfg/dhcp_timeout string 60
# Any hostname and domain names assigned from dhcp take precedence over
# values set here. However, setting the values still prevents the questions
# from being shown, even if values come from dhcp.
d-i netcfg/get_hostname string unassigned-hostname
d-i netcfg/get_domain string unassigned-domain
### Mirror settings
# If you select ftp, the mirror/country string does not need to be set.
#d-i mirror/protocol string ftp
d-i mirror/country string United States
d-i mirror/http/hostname string ports.ubuntu.com
d-i mirror/http/directory string /ubuntu
#d-i mirror/http/proxy string http://proxy.ubuntu.com:8080/
### Clock and time zone setup
# Controls whether or not the hardware clock is set to UTC.
d-i clock-setup/utc boolean true
# You may set this to any valid setting for $TZ; see the contents of
# /usr/share/zoneinfo/ for valid values.
d-i time/zone string US/Central
# Controls whether to use NTP to set the clock during the install
d-i clock-setup/ntp boolean true
# NTP server to use. The default is almost always fine here.
d-i clock-setup/ntp-server string ntp.ubuntu.com
### Partitioning
# The installer will default to using the single disk available.
# Specify the partition method to use.
# The presently available methods are:
# - regular: use the usual partition types for your architecture
# - lvm: use LVM to partition the disk
d-i partman-auto/method string lvm
#d-i partman-auto/method string regular
# If one of the disks that are going to be automatically partitioned
# contains an old LVM configuration, the user will normally receive a
# warning. This can be preseeded away...
d-i partman-lvm/device_remove_lvm boolean true
# The same applies to pre-existing software RAID array:
d-i partman-md/device_remove_md boolean true
# And the same goes for the confirmation to write the lvm partitions.
d-i partman-lvm/confirm boolean true
# Choose a predefined partitioning recipe:
# - multi: separate /home, /usr, /var, and /tmp partitions
# — atomic: all files in one partition
d-i partman-auto/choose_recipe select atomic
# This makes partman automatically partition without confirmation, provided
# that you told it what to do using one of the methods above.
# This makes partman automatically partition without confirmation.
d-i partman-md/confirm boolean true
### Account setup
# To create a normal user account.
#d-i passwd/user-fullname string Ubuntu User
d-i passwd/username string ubuntu
# Normal user's password, in clear text
d-i passwd/user-password password ubuntu
d-i passwd/user-password-again password ubuntu
# Override the weak password warning.
d-i user-setup/allow-password-weak boolean true
# Set to true if you want to encrypt the first user's home directory.
d-i user-setup/encrypt-home boolean false
# Individual additional packages to install
d-i pkgsel/include string openssh-server
# Avoid that last message about the install being complete.
d-i finish-install/reboot_in_progress note
80 Preseed template for ARM based server cartridges

G SLES configuration file
<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
<add-on>
<add_on_products config:type="list">
<listentry>
<media_url><![CDATA[http://192.168.1.1/os/m300-kiso-1.0]]></media_url>
<product>HP_PROLIANT_M300</product>
<product_dir>/</product_dir>
</listentry>
</add_on_products>
</add-on>
<bootloader>
<device_map config:type="list">
<device_map_entry>
<firmware>hd0</firmware>
<linux>/dev/sda</linux>
</device_map_entry>
</device_map>
<global>
<activate>true</activate>
<default>SUSE Linux Enterprise Server 11 SP3 - 3.0.76-0.11</default>
<generic_mbr>true</generic_mbr>
<lines_cache_id>3</lines_cache_id>
<timeout config:type="integer">8</timeout>
</global>
<initrd_modules config:type="list">
<initrd_module>
<module>ahci</module>
</initrd_module>
</initrd_modules>
<loader_type>grub</loader_type>
<sections config:type="list">
<section>
<append>console=ttyS0,9600n8 textaddon=http://192.168.1.1/os/m300-kiso-1.0/ resume=/dev/sda2 splash=silent
crashkernel=256M-:128M showopts</append>
<image>(hd0,2)/boot/vmlinuz-3.0.76-0.11-default</image>
<initial>1</initial>
<initrd>(hd0,2)/boot/initrd-3.0.76-0.11-default</initrd>
<name>SUSE Linux Enterprise Server 11 SP3 - 3.0.76-0.11</name>
<original_name>linux</original_name>
<root>/dev/sda3</root>
<type>image</type>
</section>
<section>
<append>showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off
processor.max_cstate=1 nomodeset x11failsafe</append>
<image>(hd0,2)/boot/vmlinuz-3.0.76-0.11-default</image>
<initrd>(hd0,2)/boot/initrd-3.0.76-0.11-default</initrd>
<name>Failsafe -- SUSE Linux Enterprise Server 11 SP3 - 3.0.76-0.11</name>
<original_name>failsafe</original_name>
<root>/dev/sda3</root>
<type>image</type>
</section>
</sections>
</bootloader>
<deploy_image>
<image_installation config:type="boolean">false</image_installation>
</deploy_image>
<firewall>
<enable_firewall config:type="boolean">false</enable_firewall>
<start_firewall config:type="boolean">false</start_firewall>
</firewall>
<general>
<ask-list config:type="list"/>
<mode>
<confirm config:type="boolean">false</confirm>
<halt config:type="boolean">true</halt>
<final_reboot config:type="boolean">false</final_reboot>
<final_halt config:type="boolean">true</final_halt>
</mode>
</general>
<keyboard>
<keymap>english-us</keymap>
</keyboard>
<language>
<language>en_US</language>
<languages></languages>
</language>
<networking>
<interfaces config:type="list">
<interface>
<bootproto>dhcp4</bootproto>
<device>eth0</device>
<name>Intel Ethernet controller</name>
81
<startmode>auto</startmode>
</interface>
<interface>
<bootproto>dhcp4</bootproto>
<device>eth1</device>
<name>Intel Ethernet controller</name>
<startmode>auto</startmode>
</interface>
</interfaces>
<managed config:type="boolean">false</managed>
</networking>
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
<create config:type="boolean">true</create>
<crypt_fs config:type="boolean">false</crypt_fs>
<filesystem config:type="symbol">ext4</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mountby config:type="symbol">device</mountby>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">1</partition_nr>
<resize config:type="boolean">false</resize>
<size>500M</size>
</partition>
<partition>
<filesystem config:type="symbol">swap</filesystem>
<fstopt>defaults</fstopt>
<mount>swap</mount>
<mountby config:type="symbol">id</mountby>
<resize config:type="boolean">false</resize>
<size>8G</size>
</partition>
<partition>
<filesystem config:type="symbol">ext3</filesystem>
<fstopt>acl,user_xattr</fstopt>
<mount>/</mount>
<mountby config:type="symbol">id</mountby>
<resize config:type="boolean">true</resize>
<size>max</size>
</partition>
</partitions>
<pesize></pesize>
<type config:type="symbol">CT_DISK</type>
<use>all</use>
</drive>
</partitioning>
<runlevel>
<default>3</default>
</runlevel>
<software>
<packages config:type="list">
<package>hp_proliant_m300-sle11sp3-x86_64-release</package>
<package>hp_proliant_m300-sle11sp3-x86_64-release-cd</package>
<package>intel-igb</package>
<package>intel-igb-kmp-default</package>
</packages>
<patterns config:type="list">
<pattern>Minimal</pattern>
<pattern>base</pattern>
</patterns>
</software>
<timezone>
<hwclock>UTC</hwclock>
<timezone>America/Chicago</timezone>
</timezone>
<users config:type="list">
<user>
<encrypted config:type="boolean">false</encrypted>
<fullname>moonshot</fullname>
<gid>100</gid>
<home>/home/moonshot</home>
<password_settings>
<expire></expire>
<flag></flag>
<inact></inact>
<max>99999</max>
<min>0</min>
82 SLES configuration file

<warn>7</warn>
</password_settings>
<shell>/bin/bash</shell>
<uid>1000</uid>
<user_password>moonshot</user_password>
<username>moonshot</username>
</user>
<user>
<encrypted config:type="boolean">false</encrypted>
<fullname>root</fullname>
<gid>0</gid>
<home>/root</home>
<password_settings>
<expire></expire>
<flag></flag>
<inact></inact>
<max></max>
<min></min>
<warn></warn>
</password_settings>
<shell>/bin/bash</shell>
<uid>0</uid>
<user_password>moonshot</user_password>
<username>root</username>
</user>
</users>
</profile>
NOTE: The automated installation of SLES11SP3 onto an HP ProLiant m710 server cartridge
does not require the <addon> section (shaded) in the example above. Do not include the <addon>
section when installing SLES11SP3 onto an HP ProLiant m710.
83
Glossary
AD Active Directory
ADK Windows Assessment and Deployment Kit
DHCP Dynamic Host Configuration Protocol.
DISM Deployment Imaging Servicing and Management
DNS Domain Name System.
EMS Emergency Management Services.
failover Disconnecting a failed unit or path and replacing it with an alternative unit or path to continue
functioning.
GUI Graphical user interface.
Headless Without access to a graphics layer; incapable of GUI output.
HP MWDP HP Moonshot Windows Deployment Pack
iLO Integrated Lights-Out.
ISO International Organization for Standardization.
MAC address Media access control address. A unique identifier attached to most forms of networking equipment,
which is part of the Ethernet specification.
PuTTY A terminal emulator that can act as a client for the SSH, Telnet, rlogin, and raw TCP protocols
and as a serial console client.
PXE Pre-boot eXecution Environment
SAC System Administration Channel
Unattend A file that enables installation of a Windows image with minimal user intervention. Used here
interchangeably with answer file.
WDS Windows Deployment Service
84 Glossary
Index
A E
active directory, 18 EMS, 9, 12, 77
architecture, 9 real-time monitor, 12
audience, 6 EMS console, 36
automated installation
configuration files F
Linux, 58 F12, 33
RHEL, 58 fail over, 77
SLES, 60 Fedora
Ubuntu, 59 installation files, 50
Linux, 58 firmware, 9
B G
base configuration graphics driver, 9
Linux, 46
BCD, 77 H
boot phase, 12 headless, 14
bootloader, 77 headless access, 9
bootloadersettings, 77 HTTP server
bundle, 14 Linux installation, 49
C I
cartridge node image
managing, 57 boot, 74
network boot, 57 custom, 74
power state, 57 default, 74
cartridge type imageprep, 16
m300, 9 inheritance, 77
m700, 9 install
CentOS image, 24
installation files, 50 installation
chassis, 6 components, 9
co-existence environment, 9
moonshot and traditional network installation, 62 Microsoft Windows, 6
commands networking, 9
channel-management, 70 installation components
EMS, 69 Linux, 48
SAC, 69 installation files
configuration, 74 CentOS, 50
configure, 73 Fedora, 50
pre-staged, 27 kISO, 50
WDS, 73 OS, 49
console RHEL, 50
EMS, 36 Scientific Linux, 50
VSP, 37 SLES, 50
WDS, 24 Ubuntu, 50
installation requirements
D Linux, 46
deployment, 14 interactive installation
Linux, 46 Linux, 56
deployment server, 9 ISO image, 16
DHCP service configuration
Linux, 48 J
download, 9 join domain, 29
85
K PXE
kISO boot, 33
installation files, 50 configuration, 60
PXE boot files, 52 server-specific, 61
Linux deployment, 46
L PXE boot, 6, 9
Linux PXE boot files
automated installation, 58 kISO, 52
configuration files, 58 Linux, 51
base configuration, 46 RHEL, 51
deployment, 46 SLES, 52
DHCP service configuration, 48 Ubuntu, 51
installation components, 48 PXE configuration files
installation requirements, 46 Linux, 52
interactive installation, 56
post deployment, 62 R
preparation, 46 reboot loop, 35
PXE boot files, 51 redirection, 12
PXE configuration files, 52 RHEL
TFTP server configuration, 49 automated installation
Linux deployment configuration files, 58
using PXE, 46 installation files, 50
Linux installation PXE boot files, 51
HTTP server, 49
Linux server S
network installation, 46 SAC, 12
setting up, 46 channel, 35
login, 37 Scientific Linux
installation files, 50
M scripts, 14
m300, 16, 17, 26 session
m700, 16 duplicate, 32
MAC address, 32 set up
Microsoft Windows Linux server, 46
installation, 6 SLES
monitoring, 12 automated installation
MWDP, 9, 14 configuration files, 60
N PXE boot files, 52
network boot software bundles, 14
cartridge node, 57 stand-alone, 73
network installation
Linux server, 46 T
technician computer, 16
O TFTP server configuration
operating system Linux, 49
Microsoft Windows, 6 traditional network
OS moonshot co-existence with, 62
U
P Ubuntu
power state automated installation
cartridge node, 57 configuration files, 59
pre-staged device, 27 installation files, 50
preparation PXE boot files, 51
Linux, 46 unattend, 14, 27, 29
prerequisites, 11 client, 27
infrastructure, 11 image, 27
software, 11
86 Index
V
VLAN, 9
VSP, 9
VSP console, 37
W
WDS, 18
installation, 72
network components, 71
requirements, 71
role, 72
stand-alone, 72
volume, 71
Windows Server 2012, 18
Windows ADK, 12
Windows Deployment Pack, 11
Windows media, 74
Windows Server 2012 R2, 17, 26
Windows SKU, 18
WinPE, 74
WinRE, 77
87

Bigdata - Moonshot m400

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bigdata - Moonshot m400

Uploaded by

Copyright:

Available Formats

Operating System Deployment on HP

ProLiant Moonshot Server Cartridges

HP Part Number: 742543-003b

UNIX® is a registered trademark of The Open Group.

UBUNTU®, CANONICAL®, and JUJU® are registered trademarks of Canonical Ltd.

◦ “Microsoft Windows Deployment Services installation” (page 71)

◦ “Sample WDScapture.inf file entries” (page 76)

◦ “Enabling EMS in the Windows Recovery Environment (WinRE)” (page 77)

Related documentation and videos

HP Moonshot Information Library http://www.hp.com/go/moonshot/docs

Video: Updating Firmware on HP Moonshot (ProLiant m300 http://h20324.www2.hp.com/SDP/Content/

Video :Deploying Microsoft Windows on HP Moonshot http://h20324.www2.hp.com/SDP/Content/

Video: Deploying Linux on HP Moonshot (ProLiant m300 http://h20324.www2.hp.com/SDP/Content/

Operating System Deployment on HP ProLiant Moonshot http://www.hp.com/support/moonshot_os_deployment_en

Windows Deployment Services Getting Started Guide for http://technet.microsoft.com/en-us/library/jj648426.aspx

Windows Assessment and Deployment Kit (Windows ADK) http://www.microsoft.com/en-us/download/details.aspx?

Windows Assessment and Deployment Kit (Windows ADK) http://www.microsoft.com/en-us/download/details.aspx?

Unattend Windows Setup Reference http://technet.microsoft.com/en-us/library/ff699026.aspx

DISM How-to Topics (Deployment Image Servicing and http://technet.microsoft.com/en-us/library/

PuTTY Download Page http://www.chiark.greenend.org.uk/~sgtatham/putty/

BCDedit command (Windows Dev Center) http://msdn.microsoft.com/en-us/windows/

Microsoft EMS and SAC reference technet.microsoft.com/en-us/library/

Using Windows PowerShell http://technet.microsoft.com/en-us/library/

Common Management Tasks and Navigation in Windows http://technet.microsoft.com/en-us/library/

Windows Recovery Environment (Windows RE) http://technet.microsoft.com/en-us/library/

Windows RE technical reference for Windows Server 2012 http://technet.microsoft.com/en-us/library/

Related documentation and videos 7

HP ProLiant Intel Atom N/A • Red Hat Enterprise Linux

HP ProLiant AMD Opteron • Microsoft Windows 7 • Microsoft N/A

HP ProLiant TI Keystone 32-bit N/A N/A Ubuntu 14.04.1

HP ProLiant APM 64-bit ARM N/A N/A

Customizing a Windows image for Moonshot

2. Modify Windows boot entries to enable headless access.

Customizing a Windows image for Moonshot 9

Windows Deployment Server The deployment server must:

Server cartridges (PXE clients) Cartridge types:

10 Microsoft Windows preparation and deployment

◦ Networks must be configured to allow a Windows network based installation (PXE

Customizing a Windows image for Moonshot 11

◦ A user account authorized to perform deployment.

Enabling Windows Emergency Management Services (EMS)

12 Microsoft Windows preparation and deployment

Modifying BCD files to enable EMS

Customizing a Windows image for Moonshot 13

About the HP Moonshot Windows Deployment Pack (HP MWDP)

14 Microsoft Windows preparation and deployment

HP Moonshot Windows Deployment Pack for HP ProLiant m700 Server Cartridge

Customizing a Windows image for Moonshot 15

HP Moonshot Windows Deployment Pack for HP ProLiant m710 Server Cartridge

16 Microsoft Windows preparation and deployment

Customizing a Windows image for Moonshot 17

HP ProLiant m300 and m350 server cartridge notes:

HP ProLiant m700 server cartridge notes:

Example deployment using Microsoft Windows Deployment Services (WDS)

18 Microsoft Windows preparation and deployment

Deploying the Windows image

Adding boot images for ProLiant Moonshot server cartridges

3. Click Open, and then click Next.

Example deployment using Microsoft Windows Deployment Services (WDS) 19

Figure 4 Customize image name and image description

20 Microsoft Windows preparation and deployment

Example deployment using Microsoft Windows Deployment Services (WDS) 21

Figure 6 Boot image name

Enabling EMS in Boot Configuration Data files