HP Rapid Deployment Pack User Guide HP Part Number: 352869-406 Published: March 2009, Fifteenth Edition
© Copyright 2003, 2009 Hewlett-Packard Development Company, L.P. Legal Notices 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. The information contained herein is subject to change without notice.
Table of Contents 1 Licensing...................................................................................................7 License types..........................................................................................................................................7 Applying a license file.............................................................................................................................7 Applying a license file during an first-time installation or upgrade...........
Index.........................................................................................................
List of Tables 5-1 5-2 5-3 5-4 5-5 5-6 5-7 A-1 B-1 B-2 Job folders.....................................................................................................................................27 Hardware configuration default settings.............................................................................................27 Windows default settings.................................................................................................................28 VMware default settings...........
1 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 you apply a license to a server, you cannot remove or transfer the license to another server. A license file contains licenses for a predetermined number of servers. Purchased license files are not specific to Rapid Deployment Pack versions.
2 Prerequisites Network infrastructure requirements If you use Preboot eXecution Environment (PXE) to remotely deploy servers, then Dynamic Host Configuration Protocol (DHCP) must be installed and accessible on the network. Deployment Server requirements • • Hardware: • For a new installation, a HP ProLiant server with at least a 2.
3 Installing Getting started • Log in to the local console. You cannot install Rapid Deployment Pack through Terminal Services, remote shell, or from a network share. • 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 • Turn off console security. • Back up modified jobs or batch files. • Shut down all Deployment Server Consoles and Web Consoles.
5. 12 Installing Verify that the appropriate components are selected for installation, and click Install. If you plan to use an existing database, clear the Microsoft SQL Server 2005 Express option.
6. If selected, the Microsoft .NET Frameworks and Microsoft SQL Server are installed silently. You must download and install the Microsoft WAIK 1.1, also known as the “Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008”. It is available at http://www.microsoft.com/ downloads/details.aspx?familyid=94bb6e34-d890-4932-81a5-5b50c657de08&displaylang=en&tm. After completing the WAIK install, reinsert the Rapid Deployment Pack media and click Continue. 7.
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 the Integration Module installations fail. 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.
13. Enter the appropriate database authentication method, and click Next. NOTE: If you choose SQL Server Authentication, some Integration Module Configuration tasks fail. 14. If upgrading, click Yes when prompted to retain the data in the existing database.
15. On the Pre-boot Operating Systems screen, click Next. NOTE: 16 Installing Even though the WinPE options are not selected, WinPE is installed.
16. Specify the location where you want to install PXE Server, and click Next. If DHCP is installed on a separate server, click OK when prompted that DHCP services are required. If you choose not to use PXE, then see the Knowledge Base article Creating and Using Automated Boot Media (Article 196). NOTE: When upgrading, you must select Yes, I want to upgrade PXE Server(s) on this computer or on a remote computer.
17. Specify how clients connect to the Deployment Server, and click Next.
18. Specify the location where you want to install the Deployment Server Console, and click Next. NOTE: Do not install the initial Deployment Console component to a remote server because the Integration Module installations fail. 19. Specify where you want to install the Deployment Server Web Console, and click Next.
. On the Installation Information screen, click Install. 21. 22. 23. 24. 25. 26. 27. 20 Installing If upgrading, click Yes when prompted to replace the eXpress share. When the installation is complete, click Finish. If you did not select the Altiris Deployment Server Hotfix, proceed to Step 25 Wait while the Altiris Deployment Server Hotfix is applied. If you did not select ProLiant Integration Module software, proceed to Step 36. On the Prerequisites screen, click Verify.
28. Specify the appropriate configuration options, and click Next. For more information, see Appendix B Manually modifying configuration settings. NOTE: The MAC Address lookup value is required for Integrity and new ProLiant servers. 29. Specify the appropriate Windows product keys, and click Next. 30. On the Installation and Configuration screen, click Install. 31. If upgrading, click OK when prompted to back up and overwrite existing configuration files, and reimport existing jobs. 32.
37. On the Prerequisites screen, click Verify. When the verification process is complete, click Next. 38. Select the operating systems that you want to deploy to target servers, and click Next. 39. Specify the appropriate configuration options, and click Next. For more information, see Appendix B Manually modifying configuration settings. NOTE: The MAC Address lookup value is required for Integrity and new ProLiant servers. 40. Specify the appropriate Windows product keys, and click Next. 41.
46. 47. 48. 49. On the Installation and Configuration screen, click Finish. On the Installation screen, click Next. On the Post-Installation screen, click Finish. Click Yes when prompted to reboot the server. The installation is complete. Regularly updated troubleshooting information, frequently asked questions, and specific how-to procedures are available at the HP Rapid Deployment Pack Knowledge Base at http://www.hp.com/servers/rdp/kb.
4 Using the Rapid Deployment Pack To get started with the Rapid Deployment Pack, double-click the Deployment Console icon on the desktop. This will bring up the console from which you can manage computers and execute jobs. Deployment Console basics Computers Pane—This pane shows managed computers. The New Computers group shows computers that have connected to the Deployment Server for the first time. Click View→Show Physical Devices to add the Physical Devices group.
Deploying the first server blade 1. In the Jobs pane, in the Server Deployment folder, select a Windows scripted installation job. Drag the job to the server blade in the Computers pane. 2. 3. Select Run this job immediately, and click OK. To view the progress of the job, double-click the computer in the job’s computer history. Reconfiguring the server blade By default the Windows scripted installation job configures the computer name as the console display name and configures the network as DHCP.
5 Understanding the Deployment Server Rapid Deployment Pack populates the Deployment Server Console with jobs and the Deployment Server directory with tools, scripts, configuration files, software drivers, and documentation files. This section explains these provided jobs and files, and the directory structure. Design philosophy The provided jobs, perhaps with a few tweaks, are sufficient for generic operating system deployment.
Table 5-3 Windows default settings Component Default setting Windows administrator password The administrator password is password. This password is stored as clear text in the unattend answer file. HP recommends changing the default administrator password. Drive configuration A single partition is created automatically that expands to the full drive size. Computer name The Windows computer name uses the 15 right-most characters of the console display name. Firewall Firewall settings are disabled.
Linux imaging notes: • The reference and target servers must have an identical storage controllers. • The capture image file will be .\lib\images\yyyy-linux.img where yyyy is the computer model name, for example ProLiant DL360 G4. • Subsequent captures on the same model will overwrite any existing image file. • Some applications do not image properly.
Job—Directory relationship The provided jobs follow a common design consisting of a sequence of Run Script, image capture or deploy, and reboot tasks. The embedded scripts in the Run Script tasks, reference files or directories using environment variables and pass those variables to external wrapper scripts. The wrapper scripts perform one well-defined function, for example, calling a single utility like conrep. Using external scripts enables detailed error reporting to the Deployment Server.
copy f:\lib\osoem\altiris\altiris-aclient*.exe c:\$oem$\aclient\aclient.exe Run Script Copy Unattend.txt {WinPE Managed (64-bit)} rem replacetokens .\lib\osconfig\w52e.64\default.txt .\lib\osoem\w52e.64\%ID%.txt set unattendfile=w52e.64\%ID%.txt call f:\lib\bin64\winpe\osconfig1.cmd copy f:\lib\osoem\w52e.64\%ID%.txt c:\unattend.txt Run Script Copy Distribution Files {WinPE Managed (64-bit)} set dist=w52e.64 call f:\lib\bin64\winpe\osdist1.cmd copy f:\lib\osdist\w52e.64\i386\*.
Automation environments An automation environment is an operating system in which scripts can be run on the target independent of the target’s production operating system or the Deployment Server’s operating system. The target can boot the automation environment from a CD-ROM, USB key or through PXE. Each automation environment consists of the necessary base files, additional HP drivers, and the appropriate Altiris Deployment Agent.
6 HP support and contact information Online resources • For more information about HP Rapid Deployment Pack and to obtain the latest updates, see the HP Rapid Deployment Pack website at http://www.hp.com/servers/rdp. • For more information about specific how-to procedures, regularly updated troubleshooting information, and frequently asked questions, see the HP Rapid Deployment Pack Knowledge Base at http://www.hp.com/servers/rdp/kb.
support. Using your SAID, you can also go to the Software Update Manager (SUM) web page to view your contract online and elect electronic delivery for product updates. Warranty – HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Control Management, HP Systems Insight Manager, and ProLiant Essentials products.
A Manually installing distribution files If you did not copy the Windows, ESX, or Linux distribution files during the installation, you must manually copy the files for the scripted installation 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 .
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, the console can always reflect the same name as the computer name. To manually enable synchronization of the display and computer names: 1. In the Deployment Server Console, click Tools>Options. 2. Click the Global tab. 3. Select the Synchronize display names with computer names. 4. Click OK.
4. Complete the Virtual Directory wizard by entering the following information when prompted. Table B-1 Virtual directory information Field Entry Virtual Directory Alias DSLIB FTP Site Content Directory \lib Virtual Directory Access Permissions Read 5. 6. 7. 8. Right-click the FTP site, and click Properties. Click the Security Accounts tab. Select Allow Anonymous Connections, and click OK.
Index A O Altiris Product Licensing Utility, 7 automation environment, 32 obtaining licenses, 7 online resources, 33 options, configuring, 37 C configuring HP BladeSystem servers, 25 options, 37 Preboot eXecution Environment, 37 creating FTP virtual directory, 37 image, 26 reference server, 26 D P Preboot eXecution Environment booting, 25 configuring, 37 PXE Configuration Utility , 37 reference, 25 prerequisites, installing, 9 primary lookup key, setting, 37 product keys, 38 Deployment Server configu
