Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators

RDP ”Windows Edition Architecture

There are two editions of the RDP:

• RDP ”Windows Edition : Windows-hosted deployment for heterogeneous Windows and Linux environments.

• RDP ”Linux Edition : Linux-hosted deployment for Linux environments. For details on the Linux edition see the HP Web site.

note

To deploy and manage Linux servers from the RDP ”Windows Edition requires a Linux server that is running the Network File System (NFS) Server with the ProLiant Integration Module for NFS Server installed. This Linux NFS server hosts the Linux installation files.

The architecture of the RDP ”Windows Edition is a client-server design in which an agent runs on the client (the target or managed server) that enables the server (the Deployment Server) to gather inventory information and perform actions such as running scripts, changing the configuration, and rebooting.

The Deployment Server is a Windows-based server. The target servers can either be new servers, Windows-based servers, or Linux-based servers.

Server Components

The RDP ”Windows Edition is a combination of the Altiris Deployment Solution and the HP ProLiant Integration Module. The Altiris Deployment Solution provides the foundation for deploying and managing supported servers. The HP ProLiant Integration Module provides ready-to-use ProLiant server deployment support.

The following server components must be installed on one or more Windows-based servers:

Deployment Server (Windows)

• Altiris Deployment Solution, which includes the following components:

  • Deployment Server

  • Deployment Server database

  • Deployment Server Console

  • Client Access Point

  • PXE server

• ProLiant Integration Module for Deployment Server

note

The DHCP server component is required, but is not supplied by the RDP. Typically, an existing Windows DHCP server is used or DHCP can be installed on the Deployment Server.

To support Linux scripted installs , the following server components must be installed on a Linux-based server that is running an NFS

NFS Server (Linux)

ProLiant Integration Module for NFS server

Deployment Server

The Deployment Server controls the flow of the work and information between the managed servers and the other server components. The managed servers connect and communicate with the Deployment Server to register their information. This information is stored in the Deployment Server database.

Deployment Server Database

The Deployment Server database maintains all the information about the managed servers, including hardware information, serial numbers , computer names , MAC and TCP/IP (Transmission Control Protocol/Internet Protocol) addresses, deployment history, and device information.

Deployment Server Console

The Deployment Server Console is a drag-and-drop GUI application that provides the main point of control. It enables you to

• View newly discovered and managed servers

• Create and edit "jobs," sequences of tasks such as running scripts, changing configuration, and rebooting

• Execute jobs on selected servers

Client Access Point

The Client Access Point is a file share where the images, scripts, configuration files, tools, and software packages are stored. The space available on the Client Access Point must be large enough to accommodate all of the disk images and files.

PXE Server

The PXE server provides PXE clients with a boot image. The boot images use a Windows 9x DOS environment created from customer-supplied media. There are two boot images:

• The New Computer image is downloaded to a PXE client that is not listed in the database. This image runs the Deployment Agent for DOS program, which discovers information about the client, and places that information into the database. The client is displayed in the New Computers group of the Deployment Server Console and, by default, waits for an operator to initiate deployment from the console.

• The Managed Computer image is downloaded to a PXE client that is listed in the database and has been assigned a task to perform, or has a pending operation that requires booting to DOS.

The PXE server assigns the correct image to the client without user intervention.

DHCP Server

The DHCP server provides clients with an IP address. The Altiris PXE server is designed to work with most DHCP servers, located either on the same server or on a different server. The Altiris PXE server has been optimized for use with the Microsoft DHCP server.

ProLiant Integration Module for Deployment Server

The ProLiant Integration Module for Deployment Server adds jobs, scripts, configuration files, the latest version of the ProLiant Support Packs (PSPs) for Windows, and the latest version of the SSSTK to the Altiris Deployment Solution.

The provided deployment jobs deploy ProLiant servers by configuring the hardware and array controllers, installing the OS either by scripting or imaging, and then installing the latest version of the PSP.

ProLiant Integration Module for NFS Server

The ProLiant Integration Module for NFS server adds scripts, configuration files, and the latest version of the PSPs for Linux to an existing Linux-based NFS server. These files are required for the Linux scripted install jobs, which use an NFS-based installation mechanism.

Client Components

The Altiris Deployment Solution has three client programs:

• Deployment Agent for Windows (formerly known as AClient)

• Deployment Agent for Linux

• Deployment Agent for DOS (formerly known as BootWorks)

Deployment Agents for Windows and Linux

The Deployment Agents for Windows and Linux are installed on the production OS.

The agents enable the Deployment Server to

• Gather inventory and configuration data

• Execute OS scripts or programs

• Change the OS configuration

• Reboot, shut down, or wake up

Deployment Agent for DOS

The Deployment Agent for DOS is not installed on the production OS; instead, it's part of a specific DOS-based environment. This environment enables the Deployment Server to manage servers that do not have a production OS installed or must be disconnected from the production OS.

The agent enables the Deployment Server to

• Gather inventory data

• Execute scripts

• Capture and deploy images

• Reboot

Server Component Installation Options

warning

Before installing the Altiris PXE server component, a DHCP server must be installed, running, and accessible on the network.

note

When the Altiris PXE server is installed on the same server with Microsoft DHCP server, Altiris automatically configures the Option 60 setting in the DHCP options. If the DHCP server is not Microsoft, Option 60 must be manually configured with the value of PXECLIENT.

There are two common installation options:

• Option 1 : Installing all the server components onto an existing DHCP server (see Figure 9.9).

  Figure 9.9. Install Option 1.

• Option 2 : Installing some of the server components and using an existing, separate DHCP server and/or database (see Figure 9.10).

  Figure 9.10. Install Option 2.

For complete installation requirements and directions, refer to the HP ProLiant Essentials RDP ”Windows Edition User Guide at http://www.hp.com/servers/rdp .

Client Component Installation Options

There are two client component installation options, one for existing servers and one for new or unconfigured servers.

Existing Servers

For Windows-based servers, you can install the Deployment Agent for Windows using either of the following methods :

• In the Deployment Server Console, use the Remote Agent Installer to push the agent to the target server.

• On the target server, manually install the agent from the Client Access Point.

For Linux-based servers, the Deployment Agent for Linux can be installed by manually installing the RPM on the target server.

For complete directions, refer to the Altiris Deployment Solution Product Guide at http://www.altiris.com.

New or Unconfigured Servers

The Deployment Agent for DOS is not installed, but the agent and DOS-based environment can be executed by any of the following methods:

• Performing a PXE boot and receiving a boot image from the Altiris PXE server

• Booting an Altiris boot floppy disk in the physical floppy disk drive

• Booting an image of an Altiris boot floppy disk through the virtual floppy feature of the Remote Insight Lights-Out Edition (RILOE) board or integrated Lights-Out (iLO)