The HP Blade Workstation SolutionA new paradigm in workstation computing featuring the HP ProLiant xw460c Blade Workstation
Executive overview.... 2 HP Blade Workstation Solution overview... 2 Details of the HP Blade Workstation Solution... 4 HP Session Allocation Manager... 8 Management capabilities.... 10 Additional HP RGS capabilities.... 11 A real-life example: Deployment of HP blade workstations in the finance industry.. 12 Benefits of the HP Blade Workstation Solution.... 12 Conclusion..... 13 For more information.... 14

Executive overview

The HP Blade Workstation Solution represents a new paradigm in workstation computing. Rather than placing the workstation's computing power at the user's desk, the computing power, in the form of blade workstations, is moved to the data center where the workstations can be more easily, securely, and inexpensively managed. Centralizing an organization's workstations in the data center provides many benefits, including:
1. Improved uptime and business continuityThe next-generation remote management capabilities
of the HP Blade Workstation Solution, along with its fault tolerant design and re-provisioning capabilities, deliver outstanding uptime. To maximize business continuity and interagency coordination, multi-site blade workstation installations can be created.
2. Enhanced data securityThe HP Blade Workstation Solution ensures that your business-critical
data remains in the data center.
3. Reduced IT costsBy centralizing your organization's workstations into the data center and by
taking advantage of HP's robust set of remote management tools, your IT costs can be significantly reduced. This paper describes the industry-leading HP Blade Workstation Solution and how this solution delivers the above benefits as well as many other important benefits. An overview of the solution is presented first followed by a more detailed description.
HP Blade Workstation Solution overview
The HP Blade Workstation Solution consists of three primary components, as shown in Figure 1: The rack-mounted HP ProLiant xw460c Blade Workstation The client computer (the HP Compaq t5730 Thin Client is shown) HP Remote Graphics Software (HP RGS)
Figure 1. The HP Blade Workstation Solution featuring the HP ProLiant xw460c Blade Workstation.
This symbol denotes the HP RGS product. The stylistic R stands for Remote while the Greek gamma symbol stands for Graphics.
The users applications run on the blade workstation
Interactive desktop image

TCP/IP network

HP ProLiant xw460c Blade Workstation
Keyboard & mouse inputs
HP Compaq t5730 Thin Client
The blade workstation, which executes the user's applications, is designed for maximum performance and can be configured with one or two high-speed Intel Xeon Dual-Core or QuadCore processors. 1 The blade workstation also includes up to 64 GB of high-speed ECC memory and a dedicated graphics card that computes and renders the interactive desktop image. Using HP RGS, the desktop image is transmitted over the network to the user's client computer, which displays the desktop image locally. HP RGS is designed to provide extremely fast capture, compression, and transmission of the desktop image over standard TCP/IP networks. HP RGS is also used to capture the user's keyboard and mouse inputs and send them to the blade workstation for processing by the operating system (OS) and the applications running on the blade workstation. For more information on HP RGS, visit www.hp.com/go/rgs. The client computer can range from a thin client to a multi-display desktop computer. The HP dc73 Blade Workstation Client, shown in Figure 2, supports up to four displays, providing the performance and screen real estate for demanding, data-intensive applications. To minimize cost and maintenance, the OS of the HP dc73 Blade Workstation Client is installed on a solid-state disk. To improve data security, there are no floppy or optical drives.

Figure 2. The HP dc73 Blade Workstation Client supports up to four displays.
Because of the performance and features of HP RGS, client computers can be located anywhere, from near the data center to remote locations, while still providing a highly-interactive experience for the user. Additionally, HP RGS supports remote collaboration by permitting the desktop image from a single blade workstation to be sent to multiple client computers.
Details of the HP Blade Workstation Solution
At the heart of the HP Blade Workstation Solution is the HP ProLiant xw460c Blade Workstation Figure 3 shows the blade workstation with and without the optional HP Graphics Expansion Blade attached.
Figure 3. HP ProLiant xw460c Blade Workstation with and without the optional HP Graphics Expansion Blade.
PCI Express NVIDIA Graphics Adapter HP Graphics Expansion Blade DVI connectors HP ProLiant xw460c Blade Workstation
The HP Graphics Expansion Blade mounts on top of the blade workstation, and supports a fulllength PCI Express graphics adapter. The HP ProLiant xw460c Blade Workstation can be ordered with or without the expansion blade. Without the expansion blade, small form-factor graphics adapters are installed internally in the blade workstation. With the expansion blade, full size PCI Express graphics adapters are installed in the expansion blade.
Figure 4 shows the block diagram of the blade workstation and the expansion blade. Following the block diagram is a summary of the key features of the system. To display additional information, click any rounded rectangle on the block diagram.
Figure 4. Block diagram of the HP ProLiant xw460c Blade Workstation and the HP Graphics Expansion Blade.
HP Graphics Expansion Blade (optional)
Click any rounded rectangle to display additional information

DVI DVI

PCI Express NVIDIA Quadro FX graphics adapter
Serial Attached SCSI (SAS) hard drive(s)
Intel Xeon Dual-Core or Quad-Core processor(s)
NVIDIA Quadro FX graphics adapter(s)
Click here to display the Key Features below

Serial USB x 2 Video

Operating System
Up to 64 GB of error-correcting memory
Dual Broadcom 5708s Ethernet controllers iLO 2 management processor

NIC 1 NIC 2

1 Gb/s Browser window

Local I/O Connector

ATI RN50 video controller
iLO 2 network port 10/100 Mb/s
Key Features: PCI Express NVIDIA Quadro FX graphics adapters: The following PCI Express NVIDIA Quadro FX graphics adapters Operating in the Windows Vista Business Blade PC card only): can be installedsystem:HP Graphics Expansion Blade (single Edition with 1 RDL (Remote Desktop License) 32-bit with downgrade to Windows XP Professional 32-bit SP2 custom installed can be ordered.2 The following operating 1. systems are also supported, and can be acquired Express graphics the customer: graphics NVIDIA Quadro FX 3700 graphics adapter --PCI and installed by adapter for 3D applications. Windows XP Professional x64 Edition Red Hat Enterprise Linux 4.5 (and later), 64-bit 2. NVIDIA Quadro FX 5600 graphics adapter --PCI Express graphics adapter for ultra high-end Red Hat Enterprise Linux 5.2 (and later), 64-bit 3D graphicsapplications. Processors: One or two Intel Xeon Dual-Core or Quad-Core processors running at speeds up to 3.33 GHz can These graphics adapters are the same models used with the xw series of HP Personal Workstations. be installed.

Memory: Up to 64 GB of ECC, Double Data Rate 2 (DDR2)3 memory running at 667 MHz can be installed. When the HP Graphics NVIDIA Quadro FX graphics adapters: The NVIDIA can be installed internally and dual), FX Internally-installed Expansion Blade is installed, no graphics adapters Quadro FX 560M (single in the blade workstationgraphics adapters can only be installed in the expansion blade. 770M (single and dual), FX 1600M (single only), and FX 3600M (single only) graphics adapters can be installed internally in the blade workstation (if the HP Graphics Expansion Blade is not attachedsee next bullet). HP Graphics Expansion Blade (optional): The graphics expansion blade attaches to the top of the blade workstation, allowing the installation of high performance PCI Express NVIDIA graphics adapters. Expansion Blade PCI Express graphics adapters: The NVIDIA Quadro FX 3700 and FX 5600 PCI Express graphics adapters can be installed in the expansion blade. Attachment of the HP Graphics Expansion Blade to the blade workstation precludes graphics adapters being installed internal to the blade workstation. ATI RN50 video controller: The ATI video controller generates the boot console, which can be viewed using the video output of the Local I/O Connector or through the Integrated Lights-Out version 2 (iLO 2) network port. Hard drives: The blade workstation supports one or two Serial Attached SCSI (SAS) hard drives, either 72 GB or 146 GB per drive. The storage controller can be ordered with 64 MB of cache or 128 MB of battery-backed write cache. Ethernet: Two Ethernet ports are provided, each operating at a fixed speed of 1 Gb/s. iLO 2 management processor: The iLO 2 management processor provides an independent means to monitor and control the blade workstation.
Figure 5 shows the internal view of the blade workstation and its high-density packaging. For optimum space utilization, the Intel Xeon processors are installed beneath the SAS drive bays.
Figure 5. Internal view of the HP ProLiant xw460c Blade Workstation.

Slots underneath drive bays for one or two Dual-Core or Quad-Core Intel Xeon processors
Two hot-plug SAS drive bays for 72 GB or 146 GB drives
128 MB of batterybacked write cache for the Smart Array storage controller
One or two NVIDIA Quadro FX graphics adapters
Windows XP Pro SP2 can be ordered factory-installed
Smart Array storage controller integrated on drive backplane
8 fully buffered DIMM slots DDR 2, 667Mhz, up to 64 GB of memory
The small form factor of the HP ProLiant xw460c Blade Workstation allows installation of up to 64 blade workstations in a single 42U rack, as shown in Figure 6.
Figure 6. Up to 64 HP ProLiant xw460c Blade Workstations can be installed in a single 42U rack.
16 blade workstations per enclosure
4 enclosures per 42U rack
HP BladeSystem c7000 Enclosure
The innovative HP BladeSystem c7000 Enclosure, which accommodates 16 blade workstations, contains everything needed to support the blade workstationshot-swappable power supplies, high-efficiency ducted cooling fans, and a next-generation blade management infrastructure. For usages such as remote offices that require fewer blades, HP offers the HP BladeSystem c3000 Enclosure. The c3000 enclosure supports eight blade workstations, and is available in both a rack mounted model and a tower model, as shown in Figure 7.
Figure 7. The c3000 enclosure is available in a rack mounted model and a tower model.
HP BladeSystem c3000 Enclosures

Rack model Tower model

Once the blade workstations are installed, they can be allocated to local or remote users. A single data center can support users at multiple sites, as shown in Figure 8, providing a high degree of flexibility and ensuring optimal use of blade workstation resources.
Figure 8. The blade workstations in the data center can be allocated to users at multiple sites.
HP ProLiant xw460c Blade Workstations

(need correct picture)

Site #1

Data Center

HP RGS is used over standard TCP/IP networking to connect client computers to blade workstations in the data center

Site #2

HP Session Allocation Manager
HP Session Allocation Manager (SAM) can be used to optimize your HP Blade Workstation Solution deployment by automatically provisioning the blade workstation resources to your users. HP SAM provides the following capabilities with the blade workstation solution: Static and dynamic resource assignmentsHP SAM supports two types of resource assignments: Static resourcesWith static resources, a user and the users client computer are connected to a pre-defined set of remote computing resources, even when the user changes location. Dynamic resourcesWith dynamic resources, users are assigned remote computing resources from a pool of available computing resources. These two types of resource assignments provide significant flexibility in meeting the needs of your users. Single log inHP SAM simplifies the user experience by allowing the user to log in just once, even if the user is connecting to multiple blade workstations. Furthermore, with a multi-monitor client computer, HP SAM will automatically position the users windows on the monitors connected to the client computer based on pre-configured information. The net result is that logging into the blade workstation solution is as simple as logging into a single workstation. Follow-me roamingThis feature enables users to move to a different location, and automatically reconnect to the computing resources they used previously. In doing so, HP SAM automatically adapts to different monitor configurations. For example, lets assume that a user has four monitors in the office, each displaying the frame buffer from a different blade workstation. If the user relocates to home, where there is only one monitor, HP SAM will reconnect to the live sessions on

the same four blade workstations as before, but will stack the four frame buffer windows onto the single monitor for viewing. HP RGS can then be used to cycle between each of the four windows. Automatic failoverHP SAM can be configured so that if a blade workstation fails, another blade workstation will be automatically assigned to the task performed by the failed unit. This feature works for both static and dynamic connections, maximizing the uptime of the blade workstation solution and the users productivity. Automatic client aggregationThe blade workstation solution allows multiple client computers to be aggregated together to form a single virtual client device, operated by a single keyboard and mouse. HP SAM can be configured to perform client aggregation automatically, while ensuring that each client computer connects to its pre-configured set of blade workstations. Ease of administrationHP SAM provides a web interface that allows all parameters of HP SAM operation to be easily monitored and changed from a central location. This is much more efficient than configuring the blade workstation solution by separately logging into each solution component. For more information on HP SAM, visit www.hp.com/go/sam.

Management capabilities

The HP Blade Workstation Solution contains extensive built-in management capabilities, most of which are accessible over the network. For example, as shown in Figure 4, the blade workstation contains the iLO 2 management processor, which provides an independent means of monitoring and controlling each blade. Furthermore, the blade enclosure contains the HP BladeSystem Onboard Administrator, which allows IT personnel to collectively monitor and manage all of the blades in an enclosure, such as viewing the operating status of each blade. Figure 9 shows two sample management screens for the blade workstation solution.
Figure 9. HP's blade workstations provide industry-leading remote management capabilities.
The HP BladeSystem Onboard Administrator allows remote viewing and management of all blade workstations
The System Management Homepage allows remote viewing of the detailed status of each blade workstation
The blade workstation remote management capabilities are critical to providing superior uptime and reducing IT costs by allowing support personnel to quickly detect, diagnose, and resolve problems. For example, if a user experiences a blade failure, IT personnel can quickly and remotely assign a new blade workstation to the user from a spare pool, reducing the user's total downtime to minutes.
Additional HP RGS capabilities
HP RGS is more than just a mechanism for sending the blade workstation's desktop image to the client access deviceit is a full-function, real-time collaboration tool. In Figure 10, the desktop image is shared with three remote users, all of whom can interact with the same application running on the blade workstation.

Figure 10. HP RGS can be used in a collaborative environment to share the desktop with remote users, all of whom can view and interact with the same application running on the blade workstation.

Remote user 1

Network

Remote user 2

Remote user 3
The HP Blade Workstation Solution ensures that your application data never leaves the data centeronly the desktop image is exported to the users via HP RGS. Furthermore, the pixels in the desktop image are encrypted for added security. The interactivity and security provided by HP RGS make it ideal for uses such as: Financial tradingstream video, market data, and financial trading applications from multiple workstations to a multi-display trading desk, remote office, or disaster recovery site. Natural resource explorationvisualize large datasets from remote access points. Classified research and defenseenable highly-secure, high-performance access to sensitive data and applications. Command and control centersenable a highly-secure, continuous-operation environment by providing multi-location access to blade workstation resources located in redundant data centers. Mobile professionalsenable professionals to efficiently work locally or remotely so they can live where they choose and work conveniently through an Internet connection. Scientific research and visualizationinteract with high-performance compute and visualization simulations from an office and collaborate with colleagues in real-time. Supportprovide application support to end users by connecting to existing user sessions with system administrator rights to troubleshoot and resolve issues. Classroom trainingshare live training sessions with one or many students at local or remote campuses.
A real-life example: Deployment of HP blade workstations in the finance industry
HP blade workstations have been deployed at a number of firms in the finance industry, specifically for use on the trading floor. In a detailed follow-up study, the measured benefits included: Trader productivity was increased by 68%. IT productivity was increased by 32%. Disaster recovery and contingency planning were significantly simplified. Deployment and installation of blade workstations was simpler and more trouble-free than installing individual workstations. The trading floor work environment was markedly improvedless noise, heat, and clutter. Traders were more easily able to work remotely. For a copy of this study, Blade Workstations in the Securities IndustryAn ROI Study, see h71028.www7.hp.com/ERC/downloads/c00834884.pdf.
Benefits of the HP Blade Workstation Solution
Summarized below are the benefits of the HP Blade Workstation Solution, and how these benefits are provided.

1. Benefit: Improved uptime and business continuity.
How provided: The HP Blade Workstation Solution maximizes uptime by providing a number of fault-tolerant features such as redundant network switches, RAID, error correcting memory, and hot-swappable power supplies. Furthermore, HP's advanced management features enable quick detection and correction of hardware problems. In the event of a blade workstation failure, another blade workstation can be rapidly provisioned to the end user. Business continuity can be further optimized by employing a distributed data center strategy, and routing activity to a fallback data center if the primary data center experiences problems.
2. Benefit: Enhanced data security for your company-critical data.
How provided: With the HP Blade Workstation Solution, your sensitive data is locked in the data centeronly the encrypted desktop image is exported to the users via HP RGS. In addition, HP's blade workstation client contains no removable storage media, further protecting your data.
3. Benefit: Reduced IT costs.
How provided: HP's innovative blade workstation solution reduces IT costs in a number of ways, including: By centralizing your workstation resources, support personnel will be able to more easily manage and support your workstations. HP's leading-edge blade workstation management tools enable support personnel to quickly detect, diagnose, and resolve problems. If a blade workstation goes down, IT can quickly provision another blade workstation to the user without needing to physically visit the user.
4. Benefit: Reduced noise, heat, and clutter.
How provided: Moving your workstations into the data center will eliminate the noise, heat, and clutter associated with having workstations distributed about in an office environment, providing your users with a much friendlier work environment.
5. Benefit: Simplified load balancing of the workstation demands within your organization.
How provided: The flexibility to quickly re-assign workstation resources is often necessary, ranging from a situation where a single user's workstation goes down to a situation where many workstations need to be re-allocated to handle computationally-intensive task such as a computer simulation. With the HP Blade Workstation Solution, reassigning workstation resources can be done remotely and without needing to physically move any equipment or wires. Incorporation of HP Session Allocation Manager provides additional capabilities to load-balance your workstations and respond quickly to new requirements.
6. Benefit: Support for users working locally or remotely.
How provided: Because of the performance provided by HP RGS, users are able to work locally or remotely with comparable efficiency.
7. Benefit: The ability for teams to securely collaborate from remote locations while allowing the

owner of the data to retain complete control of it. How provided: With HP RGS, the desktop image from the blade workstation can be sent to multiple users, allowing them to view and interact with the same applications. In doing this, the application data remains securely on the blade workstation.

Conclusion

The HP Blade Workstation Solution is an industry-leading workstation infrastructure that delivers many important benefits compared to distributed workstations, including improved uptime/business continuity, enhanced data security, and reduced IT costs. The solution also provides improved user comfort, better resource utilization, ease of working remotely, and real-time, remote collaboration between individuals and teams. The HP Blade Workstation Solution, 5+ years in the making, is the only solution of its kind, and has successfully proven itself in very demanding environments, including on the financial trading floor.

For more information

For more information on the HP Blade Workstation Solution, visit the blade workstation solution home page at www.hp.com/go/bladeworkstation. A number of papers on the blade workstation solution are located under the Learn more tab. For further information on the following products, visit the websites listed: HP ProLiant xw460c Blade Workstation: www.hp.com/support/xw460c_manuals HP dc73 Blade Workstation Client: www.hp.com/support/dc73_manuals HP Remote Graphics Software: www.hp.com/support/rgs_manuals
Certain Windows Vista product features require advanced or additional hardware. See www.microsoft.com/windowsvista/getready/hardwarereqs.mspx and www.microsoft.com/windowsvista/getready/capable.mspx for details. Windows Vista Upgrade Advisor can help you determine which features of Windows Vista will run on your computer. To download the tool, visit www.windowsvista.com/upgradeadvisor. Windows Vista Business disk also included for future upgrade if desired. 64-bit computing on Intel architecture requires a computer system with a processor, chipset, BIOS, operating system, device drivers and applications enabled for Intel 64 architecture. Processors will not operate (including 32-bit operation) without an Intel 64 architecture-enabled BIOS. Performance will vary depending on your hardware and software. Quad-Core and Dual Core are new technologies designed to improve performance of multithreaded software products and hardware-aware multitasking operating systems and may require appropriate operating system software for full benefits. Not all customers or software applications will necessarily benefit from use of these technologies. 2 To qualify for this downgrade an end user must be a business (including governmental or educational institutions) and is expected to order at least 25 customer systems with the same custom image. 3 Dual Channel is only supported when the system is configured with DDR2 symmetric memory (i.e. 2 x 256).

2008 Hewlett-Packard Development Company, L.P. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Vista is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. Intel and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the U.S. and other countries. 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. October 2008

HP Blade Workstation Client series
Embedded OS Version 10.xx
Part number: 495825-001 First edition: 6/2008
Legal notices Copyright 2008 Hewlett-Packard Development Company, L.P. 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. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
Part number: 495825-001 Second edition: 6/2008

Contents

1 HP Blade Workstation Client seriesIntroduction5
1-1 1-2 Embedded OS Version 10.xx.... 1 Document organization.... 6 Documentation on the HP Blade Workstation Client series.. 7 1-2-1 HP Blade Workstation Client documentation... 7 1-2-2 HP dc72 Blade Workstation Client documentation... 7 1-2-3 HP dc73 Blade Workstation Client documentation... 7 1-3 Thin client documentation.... 7 1-4 HP ProLiant xw460c Blade Workstation documentation... 7 1-5 HP Remote Graphics Software documentation... 8 1-6 Altiris Deployment Solution documentation... 9 1-7 Session Allocation Manager documentation... 9 1-8 Obtaining HP technical support... 9 2-1 2-2 2-3 3-1 Features of the client computer... 10 Embedded OS..... 11 Webmin..... 11
2 Blade workstation solution overview10
3 Turning on the client computer12
Hardware setup..... 12 3-1-1 Turn-on sequence.... 13 3-2 Local and remote access to Webmin.... 14 3-3 Using Webmin.... 14 3-4 Desktop menu.... 15 3-5 Viewing version information.... 16 3-6 Rebooting the client computer.... 17 3-7 Unlocking the client computer case.... 17 3-8 Supported keyboards.... 18 4-1 4-2 4-3 Changing the administrator password.... 19 Setting the system time parameters.... 19 Network configuration.... 20 4-3-1 Assigning a hostname when DHCP provides the IP address... 21 4-3-2 Configuring static networking.... 21 4-3-3 Specifying domain suffixes... 21 4-3-4 Setting the network speed.... 22 4-3-5 Altiris Deployment Server parameters... 22 4-3-6 Setting host addresses.... 22 4-3-7 Adding the client computer to Active Directory... 23 4-4 Keyboard language selection.... 23 4-5 Downloading and using PSCP (Putty Secure Copy)... 23 4-5-1 Downloading PSCP... 23 4-5-2 Using PSCP to copy a file to the client computer... 24 4-6 Modifiable files..... 24 4-7 Settings files..... 24 4-7-1 Groups of settings files.... 24 4-7-2 Modifying the settings files... 25 4-8 Specifying a new background image... 25
4 Configuring the client computer19
5 Monitor layout and client aggregation26

5-1 5-2 6-1

Monitor layout..... 26 Client aggregation.... 28
6 Connecting to a blade workstation31
Blade connection settings for Embedded OS 10.50... 31 6-1-1 Editing the SAM configuration file... 32 6-2 Selecting the RGS mode.... 33 6-3 Setting additional RGS parameters.... 33 6-4 Establishing an RGS connection.... 33 6-5 Remote USB..... 34 6-6 Blade workstation remote power button... 35 7-1 7-2 Downloading Embedded OS 10.xx from HP... 37 Example installation from the USB key.... 42
7 Installing Embedded OS 10.xx37
8 Known client computer limitationsRegulatory information47
9-1 Federal Communications Commission notice... 47 9-1-1 Modifications.... 47 9-1-2 Cables.... 47 9-1-3 Canadian notice (Avis Canadien)... 47 9-2 European Union regulatory notice... 47
Appendix A: 9.40 enhancements48 Appendix B: 9.45 enhancements49 Appendix C: 9.61 enhancements50 Appendix D: 10.50 enhancements51 Appendix E: Sample settings_25_local_custom.txt file52 Appendix F: Sample settings_30_local_root.txt file53 Appendix G: Sample settings_35_local_custom.txt file56 Appendix H: Sample settings_40_local_user.txt file57 Appendix I: Sample settings_20_site.txt file58 Appendix J: Sample rgreceiverconfig file61

1 Introduction

HP supports five client computers for use with the HP ProLiant xw460c Blade Workstation, as shown in Table 1-1. Table 1-1 lists the base platform upon which these client computers are based, and also shows the OS executed by the client computers. This document describes operation of the first three client computers listed in Table 1-1 these computers all run the Embedded OS. Table 1-1 Client computers, their base platforms, and their OS
Client computer Base platform Supported operating systems Embedded OS versions 8.xx, 9.xx, and 10.xx Embedded OS versions 8.xx, 9.xx, and 10.xx Embedded OS versions 9.xx and 10.xx Windows XP Embedded SP2
HP Compaq Business PC dc7600 HP Blade Workstation Client (formerly referred to as the HP Compaq Blade Workstation Client) HP dc72 Blade Workstation Client HP dc73 Blade Workstation Client HP Compaq t5720 Thin Client, HP Compaq t5730 Thin Client HP Compaq dc7700 Business PC HP Compaq dc7800 Business PC Same No customization of these platforms is performed.

NOTE: The HP Compaq t5720 Thin Client and HP Compaq t5730 Thin Client, which both run Microsoft Windows XP Embedded SP2, are not covered in this document. To find documentation on these client computers, see Section 1-3, Thin client documentation. NOTE: The first release of Embedded OS 10.xx is version 10.50, which is described in this document. This OS is available by download onlyblade workstation clients shipping from the factory currently have Embedded OS 9.61 installed. For information on earlier Embedded OS releases, refer to these manuals: HP Blade Workstation Client series Embedded OS Version 8.xx HP Blade Workstation Client series Embedded OS Version 9.xx
If your Embedded OS version is 8.xx or 9.xx, HP recommends that you update to Embedded OS 10.50 (after validating the OS in your production environment). See Section 3-5, Viewing version information, to determine the version of your client computer Embedded OS. Table 1-2 lists the recent Embedded OS versions, and provides a link to the enhancements available with each Embedded OS. Table 1-2 Recent embedded OS versions and enhancements
Embedded OS version 9.40 9.45 9.61 10.50 (described in this document) Enhancements Appendix A: 9.40 enhancements Appendix B: 9.45 enhancements Appendix C: 9.61 enhancements Appendix D: 10.50 enhancements
IMPORTANT: For a version of this document that may be newer than this version, see the HP website for your client computer: HP Blade Workstation Client: http://www.hp.com/support/bwclient_manuals HP dc72 Blade Workstation Client: http://www.hp.com/support/dc72_manuals HP dc73 Blade Workstation Client: http://www.hp.com/support/dc73_manuals
IMPORTANT: The configuration of the graphics cards installed in the back of the HP dc73 Blade Workstation Client is different than the graphics card configuration of the HP dc72 Blade Workstation Client. See Section 31, Hardware setup, for a description of the graphics card configuration of the HP dc73 Blade Workstation Client.
1-1 Document organization
This document is organized as follows: Chapter 1Introduction This chapter describes the documentation that is available for the client computers as well as the blade workstation solution in general. This chapter also describes how to obtain HP technical support. Chapter 2Blade workstation solution overview This chapter provides an overview of the blade workstation solution. Chapter 3Turning on the client computer This chapter describes how to turn on the client computer, including setting up the hardware, logging into Webmin, accessing Webmin locally and remotely, and using the desktop menu. Chapter 4Configuring the client computer Configuring of the client computer is described in this chapter, including changing the administrator password, setting the system time parameters, configuring the network, selecting a keyboard language, and modifying the settings files. Chapter 5Monitor layout and client aggregation The monitor layout tool and the client aggregation tool are described in this chapter. The monitor layout tool specifies the relationship between monitors on each client, while the client aggregation tool allows multiple clients to be controlled by a single keyboard and mouse. Chapter 6Connecting to a blade workstation This chapter describes how to configure RGS to establish a connection between the client computer and a blade workstation. Chapter 7Installing Embedded OS 10.xx This chapter describes how to download the latest Embedded OS 10.xx from HP, and install it on the client computer. Chapter 8Known client computer limitations This chapter lists the known limitation on the client computers. Chapter 9Regulatory information This chapter provides regulatory information on the client computers. Appendices The appendices list the enhancements available with each version of Embedded OS 9.xx and Embedded OS 10.50. Also, a number of sample client files are provided.

1-2 Documentation on the HP Blade Workstation Client series
The following three sections describe where documentation can be found for the HP Blade Workstation Client, the HP dc72 Blade Workstation Client, and the HP dc73 Blade Workstation Client.
1-2-1 HP Blade Workstation Client documentation
Documentation on this product is available in the following locations: On the Documentation and Diagnostics CD that ships with this product On the HP website http://www.hp.com/support/bwclient_manuals
In both locations, youll find the following documents, which provide information on setting up and using the HP Blade Workstation Client. Business PC Quick Setup poster Getting Started guide for Business PCs HP Compaq Business PC dc7600 Hardware Reference Guide
1-2-2 HP dc72 Blade Workstation Client documentation
Documentation on this product is available in the following locations: On the Documentation and Diagnostics CD that ships with this product On the HP website http://www.hp.com/support/dc72_manuals
In both locations, youll find the following documents, which provide information on setting up and using the HP dc72 Blade Workstation Client. Quick Setup and Getting Started guide for Business PCs HP Compaq Business PC dc7700 Hardware Reference Guide
1-2-3 HP dc73 Blade Workstation Client documentation
Documentation on this product is available in the following locations: On the Documentation and Diagnostics CD that ships with this product On the HP website http://www.hp.com/support/dc73_manuals
In both locations, youll find the following documents, which provide information on setting up and using the HP dc73 Blade Workstation Client. Quick Setup and Getting Started guide for Business PCs HP Compaq Business PC dc7800 Hardware Reference Guide
1-3 Thin client documentation
As noted previously, the HP Compaq t5720 Thin Client and the HP Compaq t5730 Thin Client are not covered in this document. Documentation for these products can be found by starting at http://www.hp.com, and then searching on t5720 and t5730.
1-4 HP ProLiant xw460c Blade Workstation documentation
The HP ProLiant xw460c Blade Workstation design is based on the HP ProLiant BL460c Server Blade design, and many of the features are common between the two products. Documentation on the blade workstation plus documentation on the features and infrastructure that are common between the blade workstation and the server blade, are available in the following locations: On the Documentation and Diagnostics CD that ships with the blade workstation On the HP website http://www.hp.com/support/xw460c_manuals

1-5 HP Remote Graphics Software documentation
HP Remote Graphics Software (RGS) provides the link between the blade workstation and the client computer. Using RGS, the blade workstation desktop image is transmitted over the network to the client computer, which displays the desktop image locally. RGS is designed to provide fast capture, compression and transmission of the desktop image over standard TCP/IP networks. RGS also captures keyboard and mouse inputs from the client computer, and sends them to the blade workstation for processing by the OS and the applications running on the blade workstation. RGS is pre-installed on the three client computers described in this document. RGS documentation, including the RGS User Guide, is available in the following locations: On the Documentation and Diagnostics CD that ships with your client computer On the HP website http://www.hp.com/support/rgs_manuals
The above website also contains a list of USB devices which can be connected to the client computer, and then remotely attached to the blade workstationsee Section 6-5, Remote USB, for details. NOTE: The documentation on the HP websites listed above is often more current and more comprehensive than the documentation included on the Documentation and Diagnostics CDs.
1-6 Altiris Deployment Solution documentation
Altiris Deployment Solution is used to download, capture, and deploy the operating system on the client computers described in this document. The Altiris Deployment Solution Guide for Blade Workstation Clients using Embedded OS 9.xx and 10.xx can be found in the following locations: HP Blade Workstation Client: http://www.hp.com/support/bwclient_manuals HP dc72 Blade Workstation Client: http://www.hp.com/support/dc72_manuals HP dc73 Blade Workstation Client: http://www.hp.com/support/dc73_manuals
1-7 Session Allocation Manager documentation
Session Allocation Manager (SAM) can be used to set up and manage RGS connections between blade workstations and client computers. For information and documentation on SAM, see http://www.hp.com/go/sam.
1-8 Obtaining HP technical support
If you encounter an issue that requires technical support, please do the following prior to contacting HP for assistance: Be near your client computer Have available your client computer serial number, product number, and model name Note the following: Error messages The status of the front panel LEDs Applications you were using when you encountered the issue

Be prepared to spend the time necessary to troubleshoot the problem with the service technician
To find the local call center for your region, go to http://welcome.hp.com/country/us/en/wwcontact_us.html. Select your region, and click Technical support after you buy under the Call HP heading to obtain the support center telephone number for your region. In North America, call 800-HP Invent (800-474-6836).
2 Blade workstation solution overview
The blade workstation solution represents a new paradigm in high performance workstations. Rather than placing the workstation computing power at the users desk, the computing power is moved to the data center where the rack-mounted workstations can be more easily, securely, and inexpensively managed. Users can remotely view and interact with the blade workstations using inexpensive client computers. This reduces the heat, clutter, and noise inherent in multi-workstation desktop configurations. For information on the HP Blade Workstation Solution, visit http://www.hp.com/go/bladeworkstation. The data center can be nearby or, for business continuity reasons, more distant. Standard networking technology connects the blade workstation to the client computer. The client computer is a customized dc7600, dc7700, or dc7800 PC. It is not a standalone PC, but rather an appliance designed to display the desktop of one or more blade workstations. The client computer has two graphics cards, supporting up to four monitors (see Figure 2-1). Figure 2-1 HP Blade Workstation Solution
User applications run on the blade workstation
interactive desktop image
This symbol denotes the HP RGS product. The stylistic R stands for Remote while the Greek gamma symbol stands for Graphics.

Client computer network

keyboard & mouse inputs
Up to 4 monitors can be connected to the client computer
HP ProLiant xw460c Blade Workstation
2-1 Features of the client computer
The client computer is optimized for its role within the blade workstation solution. This small form-factor device uses a Disk on Module (DOM), a small solid-state hard drive with no moving parts. To enhance data security, no removable media drives (such as diskette or CD-ROM drives) are provided. The USB ports are disabled to provide further data security. In addition, the Embedded OS contains only those components required to support the blade workstation solution. This design provides: A small form factor with minimal heat dissipation and noise. Security Stability Reliability Fast reboots Ease of use Easy of administration and maintenance

2-2 Embedded OS

The client computer Embedded OS is not customizable, and is not based on a standard OS stream. The Embedded OS is stored on the flashable DOM, and contains the necessary drivers, software, and tools to perform its primary taskdisplay the video output of the blade workstations on the client monitors.

2-3 Webmin

Webmin is preinstalled on the client computer, and is the primary administration tool. Webmin is a widely-used open source tool based on secure sockets. HP has added a number of modules to Webmin to simplify client configuration. Webmin can be accessed locally from a monitor, keyboard, and mouse connected to the client computer, or can be accessed remotely through a web browser.
3 Turning on the client computer
This chapter describes how to turn on your client computer, including: Setting up the hardware Logging into Webmin Local and remote access to Webmin Capabilities provided from the desktop menu Rebooting the client

3-1 Hardware setup

Set up the client computer as described in the documentation for your computersee Section 1-2, Documentation on the HP Blade Workstation Client series. The primary hardware setup steps are listed below for a single-monitor system: 1. 2. Connect power to the computer and to the monitor. Connector the video cable from the computer to the monitor. On the computer, the video cable should be connected to the circled connector (A1) shown in Figure 3-1, depending on which client computer you have.
Figure 3-1 Connect a single monitor to the circled video card and cable (video card A, connector A1)
HP Blade Workstation Client, HP dc72 Blade Workstation Client
HP dc73 Blade Workstation Client
NOTE: Most video cables are marked with 1 or 2 on the free endsthe end marked with 1 is the A1 connector circled in Figure 3-1. Alternatively, the A1 cable can be identified because it is the lower of the two cables that join at the connector housing which plugs into the video card. 3. 4. Connect the USB cables from the keyboard and mouse to USB ports on the client computer. For a list of supported keyboards, see Section 3-8, Supported keyboards. Connect the computer to your network.

3-1-1 Turn-on sequence

This section describes the steps to turn-on and log into the client computer. 1. 2. 3. Turn on the monitor. Press the computer power button. The computer will automatically detect the monitor plugged into the first connector of the first graphics card (see Figure 3-1), and will start in single-screen mode. After booting is complete, the Webmin login prompt is automatically displayed (see Figure 3-2).

4-3 Network configuration
To customize client network settings from Webmin, first select the Network Configuration icon, and then select the Network Parameters icon to display the network parameters dialog (partially shown in Figure 4-2). Figure 4-2 Partial network parameters dialog
The Interface Status section displays several network parameters, such as the client IP address and the network speed. The Interface Parameters section enables you to select whether DHCP will be used or whether static networking will be used. If DHCP is selected, you can specify whether the DHCP server will supply the hostname to the client or the client will supply the hostname to the DHCP server. Note the default setting abovethe DHCP server will supply the hostname to the client.
4-3-1 Assigning a hostname when DHCP provides the IP address
Assigning a hostname is optional. If your DNS server automatically assigns a hostname, no additional configuration is required. However, if your DNS server provides an IP address but does not assign a hostname, a hostname can be assigned as follows: 1. Select DHCP, client supplies hostname to DHCP server (see Figure 4-3).
Figure 4-3 Select this DHCP option to allow the client to provide a hostname
Enter the hostname in the Hostname for DHCP dialog box. Click Save and Apply.
A new feature in Embedded OS 9.40 is the ability to specify a DHCP Timeout (see also Figure 4-3). Upon expiration of the timeout, an error message indicates that the computer was unable to connect to a DHCP server.
4-3-2 Configuring static networking
To configure static networking, click the Static Networking radio button, and set the parameters shown in Figure 4-4. Figure 4-4 Static network parameters
When done, click Save and Apply. The network settings should take affect immediately. If the client computer is unable to connect to other computers, reboot the computer.
4-3-3 Specifying domain suffixes
The dialog in Figure 4-5 enables the user to specify the domains that the client computer will search, even in a DHCP environment. Figure 4-5 Domain search dialog
4-3-4 Setting the network speed
To set the network speed, HP recommends using Auto-Negotiate (which is the default settingsee Figure 4-6). This will allow the client network interface to be auto-configured for optimal performance. However, for troubleshooting purposes or on networks that dont auto-negotiate to optimal speeds, manual settings may be required. If necessary, select Manually set network options, and specify full-duplex or half-duplex operation, as well as the network speed. Figure 4-6 Setting the client network speed
IMPORTANT: The client computer network settings should be adjusted to the same settings as the network switch the client computer is connected to. This will prevent problems such as an auto-negotiating network switch having difficulty connecting to a manually-set client computer.

Sample files for the above four settings files are provided in Appendices DG. 2. Site settings fileThe site settings file is typically supplied by the administrator, and is common to many clients. This file might include site-wide settings such as a common encrypted administrator password or the IP address of DNS servers. The site settings file is: settings_20_site.txt A sample file for the above settings file is provided in Appendix H. 3. System default fileSupplied by HP, the system default settings in this read-only file can change from one release of the Embedded OS to the next. For example, the default mouse acceleration level would be stored in this file. The system default file is: settings_10_default.txt Each time the client reboots, it uses the settings files to generate a full set of relevant system configuration files from the primitives in the settings files. Manual modifications in the configuration files are discarded.
4-7-2 Modifying the settings files
The settings files can be modified using any of the following methods: When installing from a USB key, installation dialogs can be used to set both site and local settingssee Section 7-2, Example installation from the USB key. Site settings are preserved on the USB key, and are applied to every client system installed subsequently from that USB key. Use Webmin to change values in the local or site settings files. Use the PSCP program to copy a customized settings file to the /settings directory of the client. Upgrade Embedded OS 10.xx on a client with customized settings. Site and local settings will be preserved. The software can also extract an initial set of local settings from a client running older software.
IMPORTANT: If the settings files are modified directly (for example, by using PSCP), the new settings will not take affect until after the client computer is rebooted.
4-8 Specifying a new background image
The steps to specify a new background image on the monitor are as follows: 1. From another computer on the network, use PSCP to copy the new background image to the client /root/user/backgrounds directory. For example: pscp 2. 3. C:\pics\waterlilies.jpg user@client1.myco.com:/root/user/backgrounds Right click on the client desktop. Select Background Image, and then select the tiling method for stretching the image across the monitor.
The first image (alphabetically) found in the /root/user/backgrounds directory is used to set the background image. To minimize wasted space, unused background images should be deleted.
5 Monitor layout and client aggregation
The client computer provides a high degree of flexibility in laying out monitors. For example, if your client computer has four monitors, you can arrange them in a 2x2 matrix, a 1x4 column, or a 4x1 row. The client computers also support a feature called client aggregation, which allows up to four client computers to be combined together, and controlled by a single keyboard and mouse. Because each client computer supports up to four monitors, this allows programs displaying on up to 16 monitors to be controlled by a single keyboard and mouse.

6 Connecting to a blade workstation
This chapter describes how to configure RGS to establish a connection between the client computer and a blade workstation. Remotely controlling blade power is also described in this chapter.
6-1 Blade connection settings for Embedded OS 10.50
Select the Webmin Blade Connection Settings icon to configure RGS. Figure 6-1 shows the upper portion of the Blade Connection Settings screen (the lower portion of the screen is described in Section 6-3). Figure 6-1 Upper portion of the Blade Connection Settings screen for Embedded OS 10.50
IMPORTANT: RGS provides interoperability between versions of RGS Senders and Receivers that have the same major version number. For example, RGS Sender version 5.0 and Receiver version 5.1.5 will interoperate together. However, Sender version 4.2 is not guaranteed to interoperate with Receiver version 5.1.2. Connection between a Receiver and a Sender should only be attempted when their major version numbers are the same. Selecting RGS 5.1.5 will cause the Receiver Control Panel to be displayed on the client computer monitor, allowing you to connect to one or more blade workstation using RGS. For information on RGS, see Section 1-5, HP Remote Graphics Software documentation. Alternatively, if youve deployed SAM 2.2 or later in your facility, you can check SAM Connection Client 2.2.1.2. Instead of displaying the RGS Receiver Control Panel, the SAM Session Allocation Client is displayed on the client computer monitor. The Session Allocation Client can be used to connect the client to one or more blade workstations (depending on how SAM is configured).
IMPORTANT: If SAM Connection Client 2.2.1.2 is selected, SAM will use RGS 5.1.5 to connect to the blade workstations. If you select SAM Connection Client 2.2.1.2, ensure that your blade workstations are also running RGS 5.xx. Note also that the SAM Session Allocation Client interface on the client computer is not localizedit is English only. For information on SAM, see Section 1-7, Session Allocation Manager documentation.
6-1-1 Editing the SAM configuration file
The ability to edit the SAM configuration was added with Embedded OS 9.61. To edit this file, click Edit SAM Config in Figure 6-1. This brings up the edit screen in Figure 6-2. Figure 6-2 SAM configuration file edit screen
IMPORTANT: During normal operation, SAM parameters should be changed using the SAM Session Allocation Client. Editing of the SAM configuration file should only be performed if youre unable to change a parameter using the Session Allocation Client, and youre knowledgeable of how SAM works.
6-2 Selecting the RGS mode
As shown in Figure 6-1, RGS supports three modes to connect to blade workstations from the client computer: Normal Mode (default)Referred to previously as Manual Mode, the blade workstation hostname or IP address is entered into the RGS Receiver Control Panel to establish a connection. Directory ModeThe blade workstation IP addresses are stored in a file on the client computer. These addresses are used to auto-start the connections to each blade workstation. Enterprise ModeQueries the enterprise server IP address or hostname for blade workstation available for connection. Multiple enterprise servers can be used. If the first server IP address is not found, the second one is tried, and so on.

NOTE: All remote power interactions are done through the blade workstation iLO port, not the blade workstation Ethernet ports. If the iLO login is successful, a power button is presented on the client desktop (see Figure 6-5). For this particular blade workstation (with an iLO address of 10.10.42.66), the power is on. Figure 6-5 Power button
A short press of the power button will cause the blade workstation to perform a soft shutdown, allowing the blade workstation to shut down gracefully, and save system data (see Figure 6-6). Figure 6-6 Power buttons during a soft shutdown
Clicking on the power button again will turn power on. To perform a hard shutdown, click on the button for five secondsthis will remove power to the blade workstation immediately.
7 Installing Embedded OS 10.xx
Embedded OS 10.xx cannot be customizedto update or install the Embedded OS, youll need to flash the entire IDE DOM drive. There are two ways to do this: Download the Embedded OS from http://www.hp.com, store it on a USB key, and install the client image from the USB key. This process is described in detail in the next two sections. Download the Embedded OS from http://www.hp.com, and use Altiris Deployment Solution to deploy the image to one or more client computers. See Section 1-6, Altiris Deployment Solution documentation, for documentation on this tool.
IMPORTANT: Performing an update to change the software revision backwards from 10.xx to 9.xx is not supported. To determine the current Embedded OS version, click the Webmin Custom Commands icon, and then click Query Version. If you need to revert from Embedded OS 10.xx to 9.xx, the entire DOM needs to be cleared first. This can be performed using the following steps: 1. 2. 3. Insert your 9.xx USB key drive and boot to this drive. When youre given the choice, choose run from USB-disk rather than install or update. After the system is up, log into webmin and bring up a terminal window via Custom CommandsStart Xterm. In the xterm window, type the following: dd if=/dev/zero of=/dev/hda bs=512 count=1 This writes zeros into the Master Boot Record of the DOM drive. 4. Then reboot from the 9.xx USB key drive and install normally.
CAUTION: All contents of the client computer DOM will be deleted during the process of installing the Embedded OS.
7-1 Downloading Embedded OS 10.xx from HP
Perform the following steps on a Windows computer to download Embedded OS 10.xx, and store the image on a USB key. Embedded OS 10.50 is used as an example. 1. Based on your client computer, go to one of the following websites: 2. 3. HP Blade Workstation Client: http://www.hp.com/support/bwclient HP dc72 Blade Workstation Client: http://www.hp.com/support/dc72 HP dc73 Blade Workstation Client: http://www.hp.com/support/dc73

Figure 7-7 Keyboard language selection
Next youll be prompted to select either Upgrade, Install, or Run (see Figure 7-8). Upgrade allows the OS to be installed while preserving client settings saved in the /settings directory. Install does a complete installation of the operating system, overwriting previous settings. Run allows the operating system to run directly from the USB key, and is primarily for troubleshooting. For this example, select Install Cleanly, and press Enter.
Figure 7-8 Select Install Cleanly
The next screen will give you the option to set site-wide default settings that will be used on every client installed from this USB key (see Figure 7-9). If you select Yes, the settings that you set on this client will be written to the USB key for use on subsequent installations. For this example, use the arrow keys to select No, and press Enter.
Figure 7-9 Select No for site-wide default settings
The next screen will give you the option of setting local, system-specific settings for this particular client (see Figure 7-10). For illustration purposes and because Network Settings often need to be set, use the arrow keys to select Yes, and press Enter.
Figure 7-10 Select Yes to set local, system-specific settings
NOTE: Independent of whether or not you set local settings on the client at this time, youll have the option of modifying the local settings subsequently using Webmin. 6. The Local Settings screen is displayed next (see Figure 7-11). Use the up and down arrow keys to select Network Settings, and press Enter.
Figure 7-11 Local Settings screen
The next screen enables you to select the networking protocol (see Figure 7-12). If you have a DHCP server, select one of the two DHCP options. If you dont have a DHCP server, select Static networking. When done, press Enter.
Figure 7-12 Selection of networking protocol
The Local Client Network Parameters screen is shown next (see Figure 7-13). Use the up and down arrow keys to select the parameter to change, and then enter the new parameter. For example, if youll be using Altiris Deployment Solution in the future to install new Embedded OS images, enter the IP address of the Altiris server. In Figure 7-13, the Altiris Server Address has been changed from its default value of 127.0.0.1 to 15.2.76.101. When done, press the Tab key to highlight either OK or Skip (if no changes need to be made), and press Enter.

Appendix F: Sample settings_30_local_root.txt file
### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### The first line of this file contains a character at the beginning to let Windows-style editors know the file is in UTF-8 encoding with DOS-stype CR-LF sequences at the end of lines. This file contains machine-specific settings for various configurable parameters on a client system. It can be overridden by settings in files in the /settings directory with higher numbers, e.g. settings_30_local_root can be overridden by settings in settings_40_local_user, though local_user is only allowed to change certain settings. This file's syntax allows it to be directly sourced by shell scripts or parsed by perl scripts. All entries are of the form parameter=value Do not artificially surround the parameters with quotes. Comments are started with the '#' character. are ignored during parsing. Comments and blank lines
This file uses UTF-8 character encoding. If you're using a UTF-8 capable editor, the following string should read as: currency sign, euro sign, latin small letter a with acute, latin small letter w with acute, black spade suit:
#################### PASSWORDS #################### ### The parsing scripts will delete any plaintext passwords found and ### replace them with hashed versions, as a security measure. #root_password=<disabled> #user_password=<disabled> #webmin_password=a fixed value ### Encrypted passwords #hashed_root_password=* #hashed_user_password=* #hashed_webmin_password=$1$XXXXXXXX$YdmGlRibUPSH3cowtgTnQ.
#################### NETWORK SETTINGS #################### hostname=unassigned #ip_address=192.168.3.4 #broadcast_address=192.168.3.255 #hostdomain=test.hp.com ### Set pass_hostname_to_dhcp to true if the hostname on the client is ### passed to the DHCP server, rather than the server passing the hostname ### to the client. This is ignored if the boot protocol is static. #pass_hostname_to_dhcp=[true,false] #nameservers=10.10.1.1 10.10.1.2 #search_domains=test.hp.com hp.com #boot_protocol=[dhcp,static] #netmask=255.255.255.0 #network_autonegotiate=[true,false] #network_duplex=[half,full] #network_speed=[10,100,1000] #default_gateway=192.168.0.1 #host_table=192.6.234.18:hp.com,hp 199.232.41.10:gnu.org #################### ACTIVE DIRECTORY SETTINGS #################### #network_ad_user=Administrator
#network_ad_domain= #network_ad_ou=Computers/Clients/Blade #network_ad_update_ddns=[true,false] #################### ALTIRIS SETTINGS #################### ### Deployment Solution server IP Address ### To use static IP, disable multicasting. ### Disable ADLagent connection agent daemon if Altiris DS ### will not be used. #ds_enable=[true,false] #ds_mcast=[true,false] #ds_address=127.0.0.1 #################### KEYBOARD AND LANGUAGE #################### ### A=US English; B=Intl English; C=Canadian; D=German; E=Spanish; F=French; ### N=Norwegian; P=Swiss-German; Q=Swiss-French; S=Swedish; U=UK English; ### V=UK English-Extended; X=Finnish; Y=Danish; Z=Italian #keyboard_type=A

#################### MONITORS #################### ### Times are in minutes #monitor_blank_time=40 #monitor_dpms=off #monitor_standby_time=60 #monitor_suspend_time=60 #monitor_off_time=90 #monitor_hsync=32.0-68.0 #monitor_vrefresh=56-71 ### monitor_resolution=[bestCommon or WidthxHeight list] ### bestCommon = use the highest resolution supported by all monitors on ### the system. ### If a single resolution is specified, e.g. "monitor_resolution=1024x768", ### it will be used on all monitors. ### If a list is specified, each monitor in order will use the resolution ### specified, e.g. ### monitor_resolution=1600x1200,1600x1200,1280x1024,1280x1024 ### Supported resolutions include the following list, which will be trimmed ### to those supported by the graphics card + monitor combination. ### 800x600,1024x768,1152x864,1280x1024,1400x1050,1440x900,1600x1024, ### 1600x1200,1600x1280,1680x1050,1920x1200 #monitor_resolution=bestCommon ### monitor_layout=[1x1,2x1,3x1,4x1,2x2,3x1L,1x2,1x3,1x4,2x1P,3x1P,4x1P, ### 1x2P,1x3P,1x4P,2x2P or a layout specification] ### A layout specification has digits 0-3 for the monitors, colons between ### rows and dashes for empty space. For example: -2:01 #monitor_layout=0 ### monitor_orientation is 'L' = landscape, or 'C' = rotate clockwise, ### or 'A' = rotate anticlockwise. This can be a set of orientations ### separated by commas, one for each monitor. #monitor_orientation=L ### monitor_type=[autodetect,analog,digital] ### Usually you would only change this if using converters in the cabling. ### We haven't seen any cases where you would need to force "digital". #monitor_type=autodetect
#################### RGS #################### ### Can run 4.X or 5.X RGS. Set rgs_version=[4,5] #rgs_version=5 ### rgs_mode=[manual,enterprise,directory] #rgs_mode=manual #rgs_enterprise_servers= #rgs_enterprise_settings_on_system=true #rgs_directory_servers=
### Timeouts in milliseconds #rgs_warning_timeout=2000 #rgs_error_timeout=30000 #rgs_global_image_updates=false
#################### TIME #################### ### Timezone syntax: 1. Recognized location such as Europe/Vienna or just Vienna ### 2. Recognized description e.g. Tasmania or "Eastern Time" ### 3. Country name for single-zone countries ### 4. +-LAT+-LONG in DDMM|DDDMM|DDMMSS|DDDMMSS ### e.g. +404250-0740022 is near New York City ### 5. Recognized timezone filename, e.g. MST7MDT ### See /usr/share/zoneinfo/zone.tab #timezone=America/New_York #timeservers=ip-addresses or hostnames #timeservers_from_dhcp_used=[true,false]
#################### MOUSE ACCELERATION #################### ### mouse_acceleration=[slow,medium,fast,veryfast] #mouse_acceleration=medium
#################### CLIENT AGGREGATION #################### ### Synergy is the software client aggregation solution. ### synergy_mode=[disabled,primary,secondary] #synergy_mode=disabled #synergy_primary= #synergy_secondaries= ### Synergy layout has the same syntax as monitor_layout, above. #synergy_layout=