HP Integrity rx1620 Software Manual
Proliant essentials rapid deployment pack
Hide thumbs
Also See for Integrity rx1620:
- Operation manual (136 pages) ,
- Deployment manual (105 pages) ,
- Software manual (96 pages)
Related Manuals for HP Integrity rx1620
Summary of Contents for HP Integrity rx1620
-
Page 1: Hp Proliant Essentials Rapid Deployment Pack
HP ProLiant Essentials Rapid Deployment Pack Installation Guide Part number 352869-402 Eleventh edition August 2007 Product version: 3.70... - Page 2 Legal notices © Copyright 2001, 2007 Hewlett-Packard Development Company, L.P. 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.
-
Page 3: Table Of Contents
Contents Licensing ............................. 4 Licensing options ............................. 4 Obtaining licenses ........................... 4 Evaluation licenses ..........................4 Purchased licenses ..........................5 Applying a license file ..........................5 Applying license files during a first-time installation.................. 5 Applying license files during an upgrade installation ................5 Adding licenses to an existing installation .................... -
Page 4: Licensing
Licensing A license enables a server, either a physical server or a virtual machine, to be deployed and managed by the Altiris Deployment Server. One license is required for each server being managed. After a license is applied to a specific server, the license cannot be removed or transferred to another server. -
Page 5: Purchased Licenses
Purchased licenses Use your unique product registration number to obtain a license file. A 16-character alpha or 20-character alphanumeric registration number is located on a label on the outside back panel of a purchased software packaging box. The registration number is in the format: xxxx-xxxx-xxxx-xxxx or xxxxx-xxxxx-xxxxx-xxxxx IMPORTANT: Keep your product registration number for future reference. -
Page 6: Replacing Licenses In An Existing Installation
Replacing licenses in an existing installation If you have previously purchased, returned, or transferred licenses and have obtained a new license file to replace your existing license file: Shut down all connections to the Deployment Server Console and Deployment Server Web Console. -
Page 7: Prerequisites
Prerequisites Network infrastructure requirements If PXE will be used to perform remote deployment of servers, then DHCP must be installed and accessible on the network prior to the installation. Deployment Server requirements Hardware ○ 2+ processors in ProLiant G3 or G4 server with 2 GB RAM or an equivalent virtual machine ○... -
Page 8: Installing
Installing Getting started The Rapid Deployment Pack cannot be installed through a Terminal Services, remote shell, or network share connection. Obtain a license file (either purchased or evaluation). Collect the applicable Windows, VMware ESX, or Linux distribution files. Get the applicable Windows product keys. Before you upgrade The Rapid Deployment Pack upgrade must be completed using the Rapid Deployment Pack autorun utility. - Page 9 Verify that the appropriate components are selected for installation, and click Install. If Microsoft .NET Framework and Microsoft SQL Server are not installed on the server, these components are automatically selected. If you plan to use an existing database, clear the Microsoft SQL Server 2005 Express option.
- Page 10 Select the appropriate licensing option, and click Next. For more information about licensing, see the “Licensing” section in this guide. ○ If installing for the first-time, select Free 7 day license, or select License file, and enter the license file path and name. ○...
- Page 11 Enter the service credentials for the Deployment Server, and click Next. NOTE: Do not install the Deployment Server component to a remote server because it causes the Integration Module installations to fail. Installing 11...
- Page 12 Select the name of the server instance where you want to install the database, and click Next. If the database is located on a remote server, you might be prompted for credentials. Enter a username and password with administrative rights. Enter the appropriate database authentication method, and click Next.
- Page 13 If upgrading, click Yes when prompted to retain the data in the existing database. On the Pre-boot Operating Systems screen, click Next. NOTE: Linux and Windows PE are the only automation environments supported with the Rapid Deployment Pack 3.00 or later. The MS-DOS preboot environment is no longer supported. Installing 13...
- Page 14 Specify the location where PXE Server is to be installed, and click Next. If you choose not use PXE, then see “Appendix D Creating and using automation boot media.” If DHCP is installed on a separate server, click OK when prompted that DHCP services are required.
- Page 15 Specify how clients connect to the Deployment Server, and click Next. Installing 15...
- Page 16 Specify the location where the Deployment Server Console is to be installed, and click Next. Installing 16...
- Page 17 Specify if and where the Deployment Server Web Console is to be installed, and click Next. Installing 17...
- Page 18 On the Installation Information screen, click Install. If upgrading, click Yes when prompted to replace the eXpress share. When the installation is complete, click Finish. If ProLiant Integration Module software was selected for installation, on the Prerequisites screen, click Verify. If ProLiant Integration Module software was not selected, proceed to step 34. When the verification process is complete, click Next.
- Page 19 Select the operating systems that are to be deployed to target servers, and click Next. Installing 19...
- Page 20 Specify the appropriate configuration options, and click Next. If you are not using an IIS FTP server for VMware ESX or Linux installations, clear the Create IIS FTP virtual directory “DSLIB” option. For more information, see “Appendix B Manually modifying configuration settings.” On the Installation and Configuration screen, click Install If upgrading, click OK when prompted to back up and overwrite existing configuration files and reimport existing jobs.
- Page 21 For each operating system that was selected and that is not present, specify the root directory of the distribution files, and click Copy. If you choose to skip copying any distribution, see “Appendix A Manually installing distribution files.” If you are prompted to reinsert the Rapid Deployment Pack media, reinsert it, and click OK. If you skipped any distributions, click OK when the warning message appears.
- Page 22 If the Integrity Integration Module software was selected for installation, on the Prerequisites screen, click Verify. If Integrity Integration Module software was not selected, proceed to step When the verification process is complete, click Next. Select the operating systems that are to be deployed to target servers, and click Next. Installing 22...
- Page 23 Specify the appropriate configuration options, and click Next. If you are not using an IIS FTP service for Linux installations, clear the Create IIS FTP virtual directory “DSLIB” option. For more information, see “Appendix B Manually modifying configuration settings.” On the Installation and Configuration screen, click Install. If upgrading, click OK when prompted to back up and overwrite existing configuration files and reimport existing jobs.
- Page 24 On the autorun utility, click Next. Review the post-installation step, and click Finish. Select Yes when prompted to reboot the server. The installation is complete. For configuration instructions, see chapter 1 of the HP ProLiant Essentials Rapid Deployment Pack User Guide.
-
Page 25: Hp Support And Contact Information
HP support and contact information Related documents HP recommends reviewing the following documentation: HP ProLiant Essentials Rapid Deployment Pack Planning Guide HP ProLiant Essentials Rapid Deployment Pack User Guide HP ProLiant Essentials Rapid Deployment Pack Knowledge Base at http://www.hp.com/servers/rdp/kb which includes the latest Deployment Support article. All PDF documents can be found at http://www.hp.com/servers/rdp and at \docs on the product... -
Page 26: Hp Contact Information
HP contact information For the name of the nearest HP authorized reseller: In the United States, see the HP U.S. service locator webpage at http://www.hp.com/service_locator. In other locations, see the Contact HP worldwide webpage at http://welcome.hp.com/country/us/en/wwcontact.html. For HP technical support: In the United States, for contact options see the Contact HP United States webpage at http://welcome.hp.com/country/us/en/contact_us.html. -
Page 27: Hp Software Technical Support And Update Service
HP Software Technical Support and Update Service HP ProLiant Essentials Rapid Deployment Pack now includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP technical resources for help in resolving software implementation or operations problems. The service also provides access to software updates and reference manuals either in electronic form or on physical media, as they are made available from HP. -
Page 28: Appendix A Manually Installing Distribution Files
Appendix A Manually installing distribution files If you did not copy the Windows, VMware, or Linux distribution files during the installation, you must manually copy the files for the scripted install jobs to function properly. Manually copying the distribution files produces the same results as copying the files during the installation. To manually copy the distribution files, copy the entire contents of each distribution CD or DVD to the appropriate .\lib\osdist\yyyy directory, where yyyy indicates the operating system shortcut name. -
Page 29: Appendix B Manually Modifying Configuration Settings
Appendix B Manually modifying configuration settings Synchronize display names with computer names option The Deployment Server can use a console display name that is different from the actual computer name. However, you can select to have the console always reflect the same name as the computer name. -
Page 30: Primary Lookup Key Option
Primary lookup key option The Deployment Server uses the primary lookup key to determine if a server is already in the database. HP recommends setting the primary lookup key as the server serial number. Setting the primary lookup key as the server serial number has two benefits: It enables servers to be imported by their serial number, rather than keys that are more difficult to determine, such as the MAC address. -
Page 31: Pxe Initial Deploy Boot Timeout Option
PXE initial deploy boot timeout option By default, when a new computer (a computer not listed in the Deployment Server database) performs a PXE boot, the PXE server sends the computer the PXE menu and waits for manual selection of the Initial Deployment option. -
Page 32: Client/Server File Transfer Port Option
Client/server file transfer port option For adlagent to properly transfer files under VMware ESX 3.x, the client/server file transfer port must be set to match the value in the supplied ESX kickstart files. To manually set the client/server file transfer port to 4300: In the Deployment Server Console, select Tools>Program Options. -
Page 33: Creating An Iis Ftp Virtual Directory Option
Creating an IIS FTP virtual directory option For VMware ESX and Linux scripted installation deployments, a virtual directory must be configured on an FTP server, such as IIS. If you use an FTP server other than IIS, use the same entry settings. To manually configure IIS FTP: Launch the Internet Information Services (IIS) Manager. -
Page 34: Windows Product Keys
Windows product keys For Windows scripted installation deployments, a Windows product key must be provided. To manually configure or reconfigure the Windows product keys: In the Deployment Server Console, select Tools>Integration Module>User Tokens Editor. Add or edit the appropriate entry. Click Save. -
Page 35: Appendix C Installing An Iis Ftp Server
Appendix C Installing an IIS FTP server To install an IIS FTP server: Log in to the Deployment Server as a user with administrator rights. Click Start>Control Panel>Add/Remove Programs. Click Add/Remove Windows Components. Select Application Server, and click Details. Select Internet Information Services (IIS), and click Details. Select File Transfer Protocol (FTP) Server, and click OK. -
Page 36: Appendix D Creating And Using Automation Boot Media
Appendix D Creating and using automation boot media If you choose not to use PXE in your deployment infrastructure, you must create automation boot media for each automation environment that you will be using. The boot media boots a target server to automation without leaving any files on the server, and can be installed to DVDs, CDs, or USB keys. -
Page 37: Index
Index adding licenses, 5 evaluation licenses, 4 Altiris Boot Disk Creator, 29 FTP service installing, 9 installing, 39, 40 Product Licensing Utility, 5 requirements, 7 applying licenses, 5 Applying a license file, 5 Getting started, 11 boot diskette, creating, 29 hardware, requirements, 7 HP authorized reseller, 30 client connection, 9... - Page 38 evaluation, 4 purchased licenses, 5 obtaining, 4 PXE. See Preboot eXecution Environment options, 4, 9 purchased, 5 related documents, 29 replacing, 6 replacing licenses, 6 Licensing, 4 requirements Deployment Server, 7 Microsoft .NET Framework, installing, 9 installing, 9 Microsoft Internet Information Services network, 7 creating an FTP virtual directory, 37 ProLiant Integration Module, 10...