HP Integrity Support Pack and Deployment Utilities User Guide May 2004 (First Edition) Part Number 371826-001
© Copyright 2004 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. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About This Guide Audience Assumptions..................................................................................................................................v Where to Go for Additional Help..................................................................................................................v Reference Documentation.......................................................................................................................v Operating System Information..............
Contents Installing Single Components ..................................................................................................................2-21 Command Line Syntax ......................................................................................................................2-22 Command Line Arguments ...............................................................................................................2-22 Command Line Examples ..................................................
About This Guide This user guide is designed as a reference for implementing and using the Integrity Support Pack (ISP) deployment utilities for Microsoft® Windows Server 2003 64-bit server environments. Audience Assumptions Because of the potential risk of data loss, the ISP deployment utilities should be used only by individuals who are experienced and knowledgeable in the use of such utilities.
About This Guide For HP technical support: vi • In the United States and Canada, call 1-800-652-6672. • Outside the United States and Canada, refer to: http://www.hp.com.
1 Introduction Each ISP consists of a deployment utility and setup and software maintenance tools designed to provide an efficient way to manage routine software maintenance tasks. These tools include ISP deployment utilities for Microsoft Windows Server 2003 64-bit server environments.
Introduction Benefits of the ISP Deployment Utilities The improved software features of the ISP deployment utilities make software maintenance easier by: • Increasing server manageability • Enabling administrators to update systems remotely • Reducing server maintenance costs • Saving time The ISP deployment utilities provide the following software maintenance benefits to system administrators: • Self-installable components with easy-to-understand software update descriptions • Components that c
Introduction Obtaining the ISP Deployment Utilities You can obtain the ISP deployment utilities from the HP website or HP CD media. HP Website The latest ISP deployment utilities, ISPs, and individual components for supported Microsoft Windows operating systems are available at: http://www.hp.com/support/files.
Introduction Creating a Centralized, Network-Based Software Repository The practice of deploying ISPs and individual components from a centralized, networkbased software repository saves time and standardizes software maintenance and deployment procedures. For maximum flexibility across operating system platforms, the software repository must be on a Windows shared network drive. The repository can be updated in any of the ways shown in Figure 1-1.
2 Deploying Integrity Support Packs in Microsoft Windows This chapter discusses how to use ISPs for Microsoft Windows. HP provides the following tools for configuring components and deploying ISPs for Windows: • Remote Deployment Utility for Microsoft Windows • Remote Deployment Console Utility for Microsoft Windows Several usage scenarios are provided as examples at the end of this chapter. Overview ISPs are operating system-specific bundles of HP server support software.
Deploying Integrity Support Packs in Microsoft Windows 4. Deploy the ISP, using a deployment tool such as the Remote Deployment Utility for Windows or the Remote Deployment Console Utility for Windows. NOTE: Smart Components can also be installed individually. For more information, refer to the “Installing Single Components” section in this chapter.
Deploying Integrity Support Packs in Microsoft Windows Remote Deployment Utility for Microsoft Windows HP has developed the Remote Deployment Utility (RDU) for Windows as a graphical application that provides enhanced ISP deployment capabilities. Using a point-and-click interface, the utility enables you to deploy and maintain ISPs and Smart Components on a local server or remote server accessible over a network connection.
Deploying Integrity Support Packs in Microsoft Windows Main Window When the RDU is launched, a main control window similar to Figure 2-1 appears. Repository View Tree Target Computer List Figure 2-1: Remote Deployment Utility main control window After startup, the RDU automatically selects the latest applicable Support Pack for the operating system of the target computer if one exists in the repository.
Deploying Integrity Support Packs in Microsoft Windows The main window consists of the following elements: • Menu bar • Repository toolbar • Target Machine toolbar • Support Pack Selected for Installation toolbar • Repository view tree • Target computer list The following sections describe each element of the main window in more detail. Menu Bar The menu bar consists of the following menu items: • The File menu item enables you to exit the RDU.
Deploying Integrity Support Packs in Microsoft Windows Target Machine Toolbar The Target Machine toolbar contains the Target Machine field, which enables you to enter the path to the target server on which the ISP and other Smart Components will be deployed. The Target Machine field defaults to the name of the server that launches the RDU. If you are deploying to a remote server, change the Target Machine field to the remote server name. The toolbar also contains the following buttons.
Deploying Integrity Support Packs in Microsoft Windows Repository View Tree The repository view tree is the pane on the left side of the main RDU window, as shown in Figure 2-1. The repository view tree displays a categorized view of all Support Packs and Smart Components contained in the selected software repository. The Support Packs and components are sorted, with the most recent version listed first.
Deploying Integrity Support Packs in Microsoft Windows Target Computer List The target computer list is the pane on the right side of the main RDU window, as shown in Figure 2-1. The target computer list contains all components that have been selected for installation on the target computer. This panel has three columns: • The Description of Software to be Installed column lists the names of components selected for installation.
Deploying Integrity Support Packs in Microsoft Windows Revision History and Properties The Revision History and Properties options enable you to view additional information about a component or ISP in the repository view tree. To view the revision history for a component, right-click the component and select View Revision History, or click the revision history icon ( ) on the Repository toolbar. A sample revision history is shown in Figure 2-2.
Deploying Integrity Support Packs in Microsoft Windows To view the properties of a component, right-click the component and select Properties, or click the properties icon ( ) on the Repository toolbar. The Properties window displays the properties of the component or ISP, including file name, version number, and operating system information. A sample Properties window is shown in Figure 2-3.
Deploying Integrity Support Packs in Microsoft Windows Icons next to each component in the repository view tree indicate whether the component must be configured. Refer to Table 2-3 for descriptions of each of the icons.
Deploying Integrity Support Packs in Microsoft Windows To configure a Smart Component: 1. Select a component in the repository view tree. 2. Select Repository>Configure from the menu bar, or right-click the component and select Configure. The configuration information screen for the selected component appears. An example is shown in Figure 2-5. Figure 2-5: Sample component configuration settings 3. From the component configuration screen, set the configuration features that you want and click Save.
Deploying Integrity Support Packs in Microsoft Windows Deploying Components or ISPs The RDU allows local and remote non-scripted deployments only. To deploy Smart Components or ISPs: 1. Select the components to be installed by dragging them from the repository view tree into the target computer list or by selecting an ISP from the Support Pack Selected for Installation dropdown list. 2. Click Install on the Target Machine toolbar. The following screen appears.
Deploying Integrity Support Packs in Microsoft Windows Installation Results After deploying the ISP on the target server, the RDU displays an installation confirmation screen. Click Finish to exit.
Deploying Integrity Support Packs in Microsoft Windows If one or more components are not installed successfully, a screen similar to the following appears. Figure 2-8: Installation failure Each component writes an installation activity report (including errors) to a common installation log file called CPQSETUP.LOG on every target server. To view the installation log file, select Target from the menu bar and select View Installation Log, or click View target installation log on the Target toolbar.
Deploying Integrity Support Packs in Microsoft Windows Information regarding installation activity is appended to the same log file, providing a chronological history of all component installation activity on the target server. NOTE: The installation log file CPQSETUP.LOG is always located in the C:\CPQSYSTEM\LOG subdirectory on the boot partition of the target system.
Deploying Integrity Support Packs in Microsoft Windows Remote Deployment Console Utility for Microsoft Windows The Remote Deployment Console Utility for Microsoft Windows is a command line version of the RDU. The functionality of the command line-based Remote Deployment Console Utility is identical to the graphical RDU but enables unattended scripted deployment. The Remote Deployment Console Utility allows both local and single or multiple remote scripted deployments.
Deploying Integrity Support Packs in Microsoft Windows Command Line Arguments The following table lists the arguments recognized by the Remote Deployment Console Utility. Table 2-4: Command Line Arguments Command Line Argument Description /help Displays command line Help information. /? Is identical to the /help argument. /use-latest Instructs SETUPC to automatically install the latest available Support Pack for the target operating system.
Deploying Integrity Support Packs in Microsoft Windows Table 2-4: Command Line Arguments continued Command Line Argument Description /use-location:fileshare Instructs SETUPC to look in the specified directory or file share for the Support Pack and components. If this parameter is not specified, the directory containing SETUPC.EXE is used by default. The current logged-in account must already have access to this location.
Deploying Integrity Support Packs in Microsoft Windows Command Line Examples The following table lists examples of command line input for the Remote Deployment Console Utility. NOTE: Although lowercase letters are used in these examples, the Remote Deployment Console Utility is not case sensitive, and either uppercase or lowercase letters can be used. However, the operating system environment variable is case sensitive. For example, %I is not the same as %i.
Deploying Integrity Support Packs in Microsoft Windows Installing Single Components In some instances, you might want to install a single component manually, rather than install an entire Support Pack. To install a single component on your local system: 1. Double-click the component to be installed (cpxxxxxx.EXE). A screen similar to the following appears. Figure 2-10: Component installation 2. Click the Install button. A screen similar to the following appears.
Deploying Integrity Support Packs in Microsoft Windows Command Line Syntax The general command line syntax for single-component installation is: cpxxxxxx [/h[elp]] [/?] [/s[ilent]] [/f[orce]] [/r[eboot]] CPxxxxxx is the file name of the Smart Component; the Xs represent the component number. NOTE: All arguments and information enclosed in brackets are optional. Refer to the “Command Line Arguments” section for a full description of the arguments the Smart Components accept.
Deploying Integrity Support Packs in Microsoft Windows Command Line Examples The following table lists examples of command line input for single-component installation. NOTE: Although lowercase letters are used in these examples, either uppercase or lowercase letters can be used. Table 2-7: Examples of Single-Component Installations Command Line Input Result cp002575 Starts installation of the CP002575.EXE component. cp002575 /s Installs the CP002575.
Deploying Integrity Support Packs in Microsoft Windows Deployment Utilities Usage Scenarios for Windows-Based Systems This section discusses deployment scenarios for ISPs and components stored in a centralized, network-based software repository. All of the ISP deployment examples described in this guide assume a centralized, network-based software repository.
Deploying Integrity Support Packs in Microsoft Windows Table 2-9 summarizes the deployment scenarios on Windows-based systems and the utilities to use in each scenario. Table 2-9: Deployment Scenarios on Windows-Based Systems Scenario 1 2 3 4 Type of Deployment Deployment Utility Used • User is not familiar with operating system command line tools or does not need to deploy from a command line. Remote Deployment Utility (SETUP.EXE) • User must deploy on a single local or remote target system.
Deploying Integrity Support Packs in Microsoft Windows Scenario 1: Graphical Deployment on a Single-Target System Using the RDU IMPORTANT: Be sure that all components that require configuration are configured before deploying them. Both the RDU and the Remote Deployment Console Utility can be used to maintain and deploy ISPs and individual components on a local or remote target system. However, the graphical RDU is the easiest utility to use when deploying on a single-target system.
Deploying Integrity Support Packs in Microsoft Windows Deploying an ISP To deploy an ISP stored in a centralized, network-based software repository using the graphical RDU: 1. Be sure that all requirements are fulfilled as listed in the section “Minimum Requirements for Windows Servers.” 2. Be sure that the centralized, network-based software repository can be accessed by the administrative system. 3. Launch the RDU on the administrative system.
Deploying Integrity Support Packs in Microsoft Windows 6. Select components to be installed: — To install all components in the applicable Support Pack, select a Support Pack from the Support Pack Selected for Installation toolbar. All the components in the Support Pack appear in the target computer list, as shown in Figure 2-15. IMPORTANT: To install an ISP, all files that comprise the ISP must be present in the same directory.
Deploying Integrity Support Packs in Microsoft Windows If error text appears under a Support Pack in the repository view tree (refer to Figure 2-16 for an example), a component referenced in the Support Pack is not available in the software repository. To correct the situation, obtain the missing component from the HP website, Smart Setup CD, or Software Maintenance CD and copy it to the software repository. Figure 2-16: Component missing from the ISP 7. Select the target machine.
Deploying Integrity Support Packs in Microsoft Windows 8. Deploy all components displayed in the target computer list by clicking Install after the RDU identifies the target system. A progress window tracks the progress of the deployment. 9. Click Cancel at any time to stop deployment. There might be a slight delay before the installation is canceled while the RDU finishes the last initiated task.
Deploying Integrity Support Packs in Microsoft Windows 11. If necessary, reboot the target server to complete the installation by clicking Reboot and confirming when prompted by the system. The deployment is complete. NOTE: If the target system is the local administrative system, clicking Reboot causes the system to reboot, and the RDU must be restarted to deploy components or ISPs on another target system. 12. Close the Installation Results window to deploy components or ISPs on another target server.
Deploying Integrity Support Packs in Microsoft Windows Deploying an ISP To deploy an ISP stored in a centralized, network-based software repository from a command line prompt on a single-target system: 1. Be sure that all requirements are fulfilled as listed in the section “Minimum Requirements for Windows Servers.” 2. Be sure that the software repository can be accessed by the administrative system. 3. Map a drive letter to the network-based software repository that contains the ISP files. 4.
Deploying Integrity Support Packs in Microsoft Windows Scenario 3: Command Line Deployment on Multiple-Target Systems Using the Remote Deployment Console Utility IMPORTANT: Be sure that all components requiring configuration are configured before deploying them. Figure 2-19 illustrates the basic, multiple-target system deployment process with the Remote Deployment Console Utility.
Deploying Integrity Support Packs in Microsoft Windows To deploy an ISP stored in a centralized, network-based software repository from a command line prompt on multiple-target servers: 1. Follow steps 1 through 5 in the section “Scenario 2: Deploying Software on a SingleTarget System with the Remote Deployment Console Utility.” 2. Launch the Remote Deployment Console Utility, using command line parameters to specify each of the target systems.
Deploying Integrity Support Packs in Microsoft Windows Scenario 4: Command Line Deployment on Multiple-Target Systems Managed by HP Systems Insight Manager IMPORTANT: Be sure that all components that require configuration are configured before deploying them. For initial ISP deployment on multiple-target systems managed by HP Systems Insight Manager, use the Remote Deployment Console Utility.
Deploying Integrity Support Packs in Microsoft Windows Deploying an ISP For information on using HP Systems Insight Manager with the Version Control Repository Manager and the Version Control Agent, refer to the • The HP Systems Insight Manager Help Guide at: http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.
Index directory tree See repository view tree C command line arguments, Windows 2-18, 2-22 examples, Windows 2-20, 2-23 syntax, Windows 2-17, 2-22 components adding to target computer list 2-7 configuration icons 2-7 configuring in Windows 2-10 deploying individually 2-21 deploying with Remote Deployment Console Utility 2-17 deploying with Remote Deployment Utility 2-13 installing individually 2-21 installing with Remote Deployment Console Utility 2-17 installing with Remote Deployment Utility 2-13 missing
Index L log file installation 2-15 location 2-16 viewing 2-15 M menu bar, Remote Deployment Utility 2-5 Microsoft website v Microsoft Windows See Windows multiple-target deployment 2-33, 2-35 P properties, component example 2-10 viewing 2-10 R RDU See Remote Deployment Utility (RDU) Remote Deployment Console Utility 2-17 command line arguments 2-18 command line examples 2-20 command line syntax 2-17 Remote Deployment Utility (RDU) main window 2-4 menu bar 2-5 Repository toolbar 2-5 repository view tree
