HP Version Control Installation Guide

HP Part Number: 381382-005

Published: April 2007
Edition: 12
© Copyright 2004-2007 Hewlett-Packard
Legal Notices
The information in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability
and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental,
or consequential damages in connection with the furnishing, performance, or use of this material.
Warranty
A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales
and Service Office.
U.S. Government License
Proprietary 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.
Copyright Notices

©Copyright 1983-2007 Hewlett-Packard Development Company, L.P. All rights reserved. Reproduction, adaptation, or translation of this
document without prior written permission is prohibited, except as allowed under copyright laws.
Trademark Notices

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open
Group UNIX 95 branded products.

Intel® and Itanium® are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux® is a U.S. registered trademark of Linux Torvalds.

Java™ is a US trademark of Sun Microsystems, Inc.

Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.

SUSE® is a registered trademark of SUSE Linux AG.

Publication History
The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The
manual part number will change when extensive changes are made.

To ensure that you receive the latest edition, you should subscribe to the appropriate product support service. See your HP sales representative
for details.

Please direct comments regarding this guide to:

Hewlett-Packard Company
HP-UX Learning Products
3404 East Harmony Road
Fort Collins, Colorado 80528-9599

Or, use this web form to send us feedback:

http://docs.hp.com/assistance/feedback.html

Typographic Conventions
We use the following typographical conventions.

Book Title Title of a book. On the web and on the Instant Information DVD, it can be a hot link to the book itself.
Command Command name or qualified command phrase.
ComputerOut Text displayed by the computer.
Emphasis Text that is emphasized.
Emphasis Text that is strongly emphasized.
KeyCap Name of a keyboard key. Note that Return and Enter both refer to the same key.
Term Defined use of an important word or phrase.
UserInput Commands and other text that you type.
Variable Name of a variable that you can replace in a command or function or information in a display that represents several possible
values.
[] Contents are optional in formats and command descriptions. If the contents are a list separated by |, you must choose one
of the items.
{} Contents are required in formats and command descriptions. If the contents are a list separated by |, you must choose one
of the items.
... Preceding element can be repeated an arbitrary number of times.
| Separates items in a list of choices.
Table of Contents
1 Product overview.............................................................................................................7
VCRM.....................................................................................................................................................7
VCA........................................................................................................................................................7
HP SIM integration.................................................................................................................................7
Basic functions of VCRM and VCA........................................................................................................8
VCRM................................................................................................................................................8
VCA...................................................................................................................................................9
HP SIM....................................................................................................................................................9
Security considerations...........................................................................................................................9

2 Migrating Version Control to the System Management Homepage.......................11

Migrating Version Control with ProLiant Support Pack 7.1 and earlier..............................................11
Migrating Version Control with ProLiant Support Pack 7.2 and later.................................................11
Migrating the VCA and the VCRM from Management HTTP Server to SMH to use operating
system authentication......................................................................................................................11

3 Obtaining the software...............................................................................................15

Obtaining HP SIM, VCA, and VCRM ..................................................................................................15
VCA.................................................................................................................................................15
VCRM..............................................................................................................................................15
HP SIM.............................................................................................................................................15

4 Installing the VCA remotely using the HP Remote Deployment Utility....................17

Pre-configuring the VCA for Windows using the HP Remote Deployment Utility............................17

5 Installing the VCA on Windows operating systems.................................................19

VCA for Windows requirements..........................................................................................................19
System requirements.......................................................................................................................19
Supported hardware and software............................................................................................19
Client requirements.........................................................................................................................20
Hardware and software .............................................................................................................20
Installation overview............................................................................................................................20
Installing the VCA for Windows.....................................................................................................20
Configuring the VCA.................................................................................................................21
Installing the VCA for Windows silently.............................................................................................21
Installing silently using the CLI......................................................................................................21

6 Installing the VCA using the Linux Deployment Utility..............................................23

Pre-configuring the VCA component...................................................................................................23
Installing the VCA as a single component............................................................................................23
Installing the VCA without pre-configuration.....................................................................................24

7 Installing the VCA on Linux operating systems.........................................................25

VCA for Linux requirements................................................................................................................25
System requirements.......................................................................................................................25
Supported hardware and software............................................................................................25

Table of Contents 5
 Client requirements.........................................................................................................................26
Hardware and software .............................................................................................................26
Installing the VCA for Linux................................................................................................................26
Verifying the VCA service is running.............................................................................................27
Installing the VCA for Linux silently....................................................................................................28
Installing silently using the CLI......................................................................................................28

8 Installing the VCRM on Windows..............................................................................29

VCRM requirements for Windows.......................................................................................................29
System requirements.......................................................................................................................29
Supported hardware and software ...........................................................................................29
Client requirements.........................................................................................................................30
Hardware and software requirements.......................................................................................30
Configuring Internet Explorer settings for SMH pre-configuration...............................................30
Installing the VCRM.............................................................................................................................31
VCRM Setup - Repository Directory...............................................................................................31
Repository Population - Initial Installation.....................................................................................32
Configuring Automatic Update......................................................................................................32
Installing the VCRM for Windows silently..........................................................................................33
Installing silently using the CLI......................................................................................................33

9 Updating a repository.................................................................................................35
Updating the repository from the HP SmartStart CD..........................................................................35
Updating the repository manually from the HP SmartStart CD..........................................................35
Updating the repository manually from the HP SmartSetup CD........................................................36

10 Uninstalling the VCA on Windows operating systems...........................................37

11 Uninstalling the VCA on Linux operating systems...................................................39

12 Uninstalling the VCRM on Windows operating systems........................................41

Glossary............................................................................................................................43

Index.................................................................................................................................45

6 Table of Contents
1 Product overview
Today’s distributed enterprise networks are some of the most complex ever constructed. As
companies deploy more business-critical applications, these networks continue to rapidly expand,
becoming more sophisticated and requiring servers that support the latest technological
innovations. In this fast-changing environment, any loss of availability translates into a loss of
time and money, and manageability has become the leading success criterion for today’s highly
competitive businesses.
HP systems provide maximum uptime with minimal maintenance. HP has developed advanced
server management technologies, such as the HP Version Control Repository Manager (VCRM),
HP Version Control Agent (VCA), and HP Systems Insight Manager (HP SIM). The tight integration
of these advanced technologies reduces server management efforts, enabling administrators to
work issues, resolve problems, and install server software from remote locations by means of a
standard web browser.

VCRM
The VCRM is a repository that stores the software and firmware components used to support
ProLiant servers on Windows and Linux platforms. By default, the VCRM is installed on the HP
SIM central management server, however you can specify a custom directory or server location.
You can use the VCRM as a central point to define software baselines and to automate the
installation and change management of HP software and firmware updates to production systems.
The VCRM catalogs system software and firmware that is stored where the VCRM is installed.
The software and firmware can be manually downloaded from http://www.hp.com/servers/
swdrivers directly to the file system, or you can use the VCRM to automatically download
software or manually upload software from any web client. Software is organized into groups
by function and operating system. You can view detailed information about each piece of software
by clicking the software component name. The VCRM also enables you to create customized
groupings of software, which can then serve as a system software baseline for the entire managed
environment or a subset of your environment.

VCA
The VCA is an Insight Management Agent that is installed on a server to enable you to view the
HP software and firmware that is installed on that server. The VCA can be configured to point
to a repository being managed by the VCRM, enabling easy version comparison and software
update from the repository to the server on which the VCA is installed.
The VCA provides version control and system update capabilities for a single HP system. The
VCA determines server software status by comparing each component installed on the local
system with the set of individual components or a specified ProLiant or Integrity Support Pack
listed in the VCRM. You can also update individual components or entire ProLiant or Integrity
Support Packs by clicking the install icon located next to the system software status icon.
The installation of single software components on an individual system can be initiated from
the VCA, which retrieves the software from the VCRM. To install multiple components or custom
baselines to one or more systems, you can use the installation options in HP SIM to install the
software from the VCRM.

HP SIM integration
For software versioning and updating, HP SIM relies on the VCRM and the VCA. By using these
applications, HP SIM provides a single view of the software status for all managed ProLiant or
Integrity servers, plus the capability to update software and firmware on those servers through
its powerful query and task features. Updates can be scheduled and applied to specific sets of

VCRM 7
 servers based on predetermined criteria, including applying updates only to those systems that
require an update.
To take full advantage of the software update capabilities of HP SIM, ensure that:
• Every managed target server on the network has the VCA installed and is configured to use
a repository managed by the VCRM
• Every repository that is to be used has the VCRM installed
• You use the automatic update feature of the VCRM to update all repositories with the latest
software from HP automatically
The following diagram illustrates the interaction of HP SIM with the VCRM and the VCA to
perform software updates.

Basic functions of VCRM and VCA

The VCRM and the VCA are integrated with the System Management Homepage (SMH), which
is the standard single-system management tool in the ProLiant Essentials Foundation Pack. HP
SIM, also part of the ProLiant Essentials Foundation Pack, uses the VCRM and the VCA to
facilitate software versioning, updates, and related tasks.

VCRM
The VCRM is designed to manage a repository containing ProLiant and Integrity Support Packs
as well as individual server software and firmware components.
The repository can be kept current by using the automatic update feature of the VCRM or by
copying software directly to the repository from the HP SmartStart CD, HP SmartSetup CD,
another repository, or the HP website.

8 Product overview
VCA
The VCA is available for Windows and Linux operating systems. The VCA is an integrated part
of the SMH that is designed to display the available software inventory of the server on which
it is installed. The VCA also enables the installation, comparison, and update of server software
from a repository that is managed by the VCRM.
Users with administrator or operator privileges can access the VCA to maintain the software
inventory of the server manually. Users with user privileges can access the VCA but cannot
perform installation and configuration activities. The installation of components and configuration
activities are saved to a log file at the server. The VCA logs activities, such as software installations,
which are saved in this log. However, installations performed outside the VCA do not appear
in this log.

HP SIM
HP SIM is a Web-based server management application that leverages the power of the Internet
to provide Web-based systems management. When integrated with the VCA and the VCRM,
HP SIM provides a proactive, easy-to-use, automated, and cost-effective solution for managing
distributed systems and updating software on the managed systems remotely.
HP SIM transforms management of standards-based, distributed computing environments. By
enabling browser access to its components, HP SIM provides efficient management of HP and
third-party devices and groups of systems using Simple Network Management Protocol (SNMP),
Desktop Management Interface (DMI), and Hypertext Transfer Protocol (HTTP), automatically
consolidating and integrating the management data and displaying the information on demand.
With HP SIM, you can monitor and manage groups of servers, clients, clusters, and networking
products anywhere, at any time, from a standard web browser.

Security considerations
Three distinct types of secure connections are employed in the version control architecture. The
following diagram illustrates the connections.

HP SIM 9
 All connections and data are transferred using Secure Sockets Layer (SSL) communications over
HTTP. Interactive users connect using a web browser (client) application. The specific security
depends on which web application they are browsing.
HP SIM uses operating systems authentication, based on the server where it is installed. Single
sign-on enables a user that browses to the HP SIM system to follow links from that system to
other managed systems without being prompted to login again.
When the same user browses directly to a managed server, they must authenticate through the
SMH, using an account and password that is valid on that system.
HP SIM communicates with web applications, such as the VCA and the VCRM, using Secure
Task Execution, which is enabled by configuring the SMH to trust that central management
server (CMS). Refer to the System Management Homepage Installation Guide for information regarding
configuring the SMH.
Finally, when the VCA communicates with a VCRM, it acts as a client application, and requires
the same kind of authentication information, such as an account and password, that an interactive
user needs to login to the SMH on which the VCRM is installed. The SMH requires a valid
operating system account and password. Refer to the VCA online help for more information
regarding configuring these settings for the VCA.
For more information regarding the SMH, refer to the System Management Homepage Installation
Guide. For more information regarding HP SIM, refer to the HP SIM User Guide.

10 Product overview
2 Migrating Version Control to the System Management
Homepage
Migrating Version Control with ProLiant Support Pack 7.1 and earlier
Legacy VCA continues to report accurately after upgrading Management HTTP Server to SMH
since SMH detects installed Web Agents and migrates the administrator credentials.
Legacy VCA uses legacy SMH account names including administrator, operator, and user.

Migrating Version Control with ProLiant Support Pack 7.2 and later
IMPORTANT: This section is specific to the VCA (starting with the ProLiant Support Pack 7.2
and later).
The VCA and VCRM login to the management web server by way of the SMH. The SMH is
security software that must be configured to allow the VCA to connect to the VCRM using
operating system authentication.
Previous versions of the SMH, known as Management HTTP Server, provided three levels of
account access, including administrator, operator and user. Access was granted using the
Management HTTP Server’s built-in, local accounts, administrator, operator and user, with a
password configured at the Management HTTP Server.
When the SMH is installed, the login changes to use operating system accounts that are
authenticated at the system where the SMH is installed. The concept of an administrator or
operator level still exists and is accomplished by associating, in the SMH security settings, an
operating system user group with that privilege level, and adding the user accounts to the groups
that provide the level or privilege desired.
Note: There are no specific operating privilege requirements, other than login, that must be
granted to the operating system groups or user accounts. Privilege is granted solely by configuring
the group in the SMH settings.
Note: After the SMH is installed, the Management HTTP Server’s built-in account and password
pairs are no longer valid for interactive login on that system, though existing Management HTTP
Server credentials can be used by a VCA to connect to a VCRM. For example, this scenario can
occur when an existing VCRM system is upgraded from Management HTTP Server to SMH.
Note: If you are using HP SIM or HP Insight Manager 7, the Software Status column on the
Home page displays Unknown for any VCA that cannot connect.
Operating system accounts that are in user groups that have been assigned the SMH administrator
or operator-level privileges, have full access to all VCA or VCRM features. Operating system
accounts that are in user groups that have been assigned anonymous or user access have read-only
access to page data.

Migrating the VCA and the VCRM from Management HTTP Server to SMH to use
operating system authentication
Although Version Control will continue to report accurately after upgrading Management HTTP
Server to SMH, HP recommends that you configure SMH to use operating system authentication
for VCA access, and re-configure the systems running VCA to point to the new account for added
security.
Use the following steps as a guideline to reconfigure version control to use operating system
authentication:

Migrating Version Control with ProLiant Support Pack 7.1 and earlier 11
 1. Identify the versions of the VCAs that are installed that are being reconfigured to use
operating system authentication.
2. Determine whether you intend to update all of the systems with VCAs installed with ProLiant
Support Pack 7.20 or Integrity Support Pack 3.20.
3. From the system where the VCRM is installed, create a local user account and user group
specifically for version control use. If the installed VCAs are 2.0.7.10 or later, any account
name can be used, for example, vcadmin. If earlier versions of the VCA are installed and
you are not planning to upgrade the VCA, you must use an account name that matches one
of the non-administrator accounts the earlier versions of the SMH defined, for example,
operator or user.
By default, the VCA is unable to login with an account named administrator using operating
system authentication, to prevent an accidental lockout of the local administrator account.
To add operating system accounts:
1. Select Start→Settings→Control Panel.
2. Double-click Users and Passwords. The Users and Passwords dialog box appears.
3. From the Users tab, click Add. The Add New User dialog box appears.
4. In the User name field, enter a user name for this account.
5. In the Full name field, enter a full name for this account.
6. In the Description field, enter a brief description of this account.
7. Click Next. The Add New User dialog box appears.
8. In the Password field, enter a password for this account.
9. In the Confirm Password field, re-enter the password exactly as you entered it in the
Password field.
10. Click Next. The Add New User dialog box appears asking you to indicate what level
of access you want to grant this user.
11. Select the appropriate access level for this user:
• Standard User Users can modify the computer and install programs, but cannot
read files that belong to other users.
• Restricted User Users can operate the computer and save documents, but cannot
install programs or make potentially damaging changes to the system files and
settings.
• Other This option enables you to specify a custom level.
— Administrators Administrators have complete and unrestricted access to the
computer/domain. This level is required to connect from the VCA to the VCRM.
— Backup Operators Backup Operators can override security restrictions for
the sole purpose of backing up or restoring files.
— Guests Guests have the same access as members of the Users group by
default, except for the Guest account which is further restricted.
— Power Users Power Users possess most administrative powers with some
restrictions.
— Users Users are prevented from making accidental or intentional
system-wide changes.

12. Click Finish. The account is created and appears in the Users for this computer list.
13. Click OK to close the Users and Passwords dialog box.
4. Create a user group that includes the SMH's Administrator or Operator list, for example,
VCOperators. Add the account that you created to that group.

12 Migrating Version Control to the System Management Homepage

5. If you used one of the legacy account names, and you have not upgraded to SMH yet, change
the existing operator or user account's password to match the identically named operating
system account.
6. If you intend to upgrade, add the created user group to the Administrator or Operator
group list in the SMH Operating System Groups page during installation. If you have
already upgraded to SMH, add the created user group to SMH through the SMH Settings
page. For more information regarding assigning accounts in SMH, refer to the SMH online
help.
The user group must be added to the Administrator or Operator lists in the SMH for the
VCA to have the ability to download and install software using the VCRM on this system.
Login to the SMH using the newly created account and password to verify that it logs in
successfully.
7. Change the configuration of the VCAs that are already installed. There are several ways to
change the configuration, including:
a. HP SIM users should use Replicate Agent Settings to configure one VCA to the account
and password previously created in step 3, and then deploy that configuration to all
installed VCAs.
Note: This is the lowest impact solution, and it does not cause a reboot or restart of the
affected systems.
b. Pre-configure a VCA component using the VCRM, and use HP SIM or HP Insight
Manager 7 to create a software deployment task to deploy this component.
If you choose to deploy the VCA from the 7.20 ProLiant Support Pack, you must deploy
the SMH component before the VCA can install.
Note: This method causes a reboot of the Windows systems where the VCA is upgraded,
since it is being used to upgrade itself.
c. Use the HP Remote Deployment Utility to pre-configure a VCA for Windows
component. If you choose the VCA from the 7.20 ProLiant Support Pack or Integrity
Support Pack 3.20, you must deploy the SMH component before the VCA can install.
8. Verify that the settings are correct and functioning by browsing to one of the systems where
an updated VCA is installed, and confirming the software status is accurate. If you are an
HP SIM or HP Insight Manager 7 user, run the Software Status Polling task to display
updated status.

Migrating Version Control with ProLiant Support Pack 7.2 and later 13
14
3 Obtaining the software
This chapter provides information regarding obtaining the VCRM and VCA.

Obtaining HP SIM, VCA, and VCRM

VCA
The VCA is available from the following sources:
• ProLiant Support Pack or Integrity Support Pack. To download the latest version of the
ProLiant Support Pack, go to http://www.hp.com/servers/swdrivers or to download the
latest Integrity Support Pack, go to http://www.hp.com/support/itaniumservers. The ProLiant
Support Pack is also available on the HP SmartStart CD and the HP Software Update CD.
The Integrity Support Pack is available on the HP SmartSetup CD.
• HP SmartStart CD. For more information regarding the HP SmartStart CD, refer to the
documentation included on the HP SmartStart CD or go to http://www.hp.com/servers/
manage.
• HP Software Update CD. The HP Software Update CD provides software maintenance
functionality. For more information regarding the HP Software Update CD, refer to the
documentation included on the HP Software Update CD or go to http://www.hp.com/servers/
manage.
• HP SmartSetup CD. For more information about the HP SmartSetup CD, refer to the
documentation included on the HP SmartStart CD or go to http://www.hp.com/servers/
manage.

VCRM
The VCRM is available from the following sources:
• HP website. Go to http://www.hp.com/servers/swdrivers.
• HP Management CD. When web access is not available or download speeds are too slow,
the VCRM can be obtained from the HP Management CD 7.20 or later. For more information
about the HP Management CD, refer to the documentation included on the HP Management
CD or go to http://www.hp.com/servers/manage.
• HP Insight Control Management DVD The VCRM can be obtained from the HP Insight
Control Management DVD. For more information about the HP Insight Control Management
DVD, refer to the documentation included on the HP Insight Control Management DVD,
or go to http://www.hp.com/servers/manage.

HP SIM.
HP SIM is available from the following sources:
• HP website. Go to http://www.hp.com/servers/manage.
• HP Management CD. When Web access is not available or download speeds are too slow,
HP SIM can be obtained from the HP Management CD 7.20 or later. For more information
about the HP Management CD, refer to the documentation included on the HP Management
CD or go to http://www.hp.com/servers/manage.
• HP Insight Control Management DVD HP SIM can be obtained from the HP Insight Control
Management DVD. For more information about the HP Insight Control Management DVD,
refer to the documentation included on the HP Insight Control Management DVD, or go to
http://www.hp.com/servers/manage.

Obtaining HP SIM, VCA, and VCRM 15

16
4 Installing the VCA remotely using the HP Remote
Deployment Utility
The HP Remote Deployment Utility for Windows is a graphical application that provides enhanced
ProLiant and Integrity Support Pack deployment capabilities. Using a point-and-click interface,
the utility enables you to deploy and maintain ProLiant and Integrity Support Packs and Smart
Components on a local server or remote server accessible over a network connection.
To run the HP Remote Deployment Utility, invoke the Setup.exe which is present as part of the
ProLiant or Integrity Support Pack corresponding to each operating system. The ProLiant and
Integrity Support Pack is identified based on the operating system installed on the server. The
components that are supported for installation are listed in the right side of the frame. The VCA
can be installed as a part of the complete ProLiant or Integrity Support Pack, or you can install
the VCA component individually. The VCA component also provides support for
pre-configuration, which allows the configurations of the component to be configured and saved
as part of the component itself before installing on target machines. This facilitates the installation
of the pre-configured component without any user intervention, and the installed component
has the configurations, which are saved during pre-configuration.
All configurable components are listed at the top of the left frame under All configurable
components.

Pre-configuring the VCA for Windows using the HP Remote Deployment

Utility
To pre-configure the VCA component:
1. Under All configurable components, right-click the VCA for Windows component and
select Configure. The VCA Setup page appears.
The VCA must be configured to connect to a VCRM to determine software status of installed
software, availability of updates, and to download software for installation. The VCA Setup
page enables you to specify a system that has the VCRM installed.
2. In the Computer Name field, enter the name of the system that has the VCRM installed.
3. In the Login Account field, enter the login account for the SMH of that system. If you have
created an account specifically for version control, use that account name.
4. In the Login Password field, enter the password for the login account on the VCRM system
specified.
5. Enable or disable Overwrite corresponding settings of an already installed VCA when
this version is installed as an upgrade or re-installed. If not checked, the values saved
here will apply only on the initial installation of this copy of VCA software. Enable this
option if you are upgrading or reinstalling and you want to overwrite the existing VCA
settings.
Note: This option is enabled by default. If you do not want to overwrite existing VCA settings,
you must deselect this option.
6. Click Save to save your settings for the VCA component. Click Cancel to discard the settings
and close the VCA Setup page.
You can install this pre-configured component to target systems without the need for you to
configure settings in the VCA after installation. For more information regarding using the HP
Remote Deployment Utility, refer to chapter 2 of the HP ProLiant Support Pack and Deployment
Utilities User Guide on the HP SmartStart CD.
Note: HP recommends that you install the SMH component, which is required to use the VCA,
along with the VCA component.

Pre-configuring the VCA for Windows using the HP Remote Deployment Utility 17
18
5 Installing the VCA on Windows operating systems
VCA for Windows requirements
The VCA can be used in conjunction with HP SIM and the VCRM. The options must be configured
for full functionality. The installation of the VCA requires that you specify a certified login with
a VCRM. When specified, VCAs can determine the versions of HP software and firmware installed
on each individual system and compare the version with the latest software or firmware and
baseline definitions available in the VCRM. The following diagram illustrates a logical order for
the initial VCA installation process on a Windows operating system.

System requirements
To install the VCA on a Windows system, the system must meet the following minimum
requirements.

Supported hardware and software

• Supported operating systems
— Windows Server 2003 with Service Pack 2
— Windows Server 2003 R2
— Windows Server 2003, Service Pack 1
— Windows Server 2003 ES for 64-bit Extended Systems (starting with the ProLiant Support
Pack 7.2 and later)
— Windows Server 2003 64-bit Enterprise Edition
• Server software
— TCP/IP installed
— SMH installed (starting with the ProLiant Support Pack 7.2 and later)
• Hardware
— ProLiant Server
— Integrity Server (rx1620, rx2600, rx2620, rx4640, rx5670, rx7620, rx8620, Superdome)

VCA for Windows requirements 19

 • Disk space
— 11 MB on the Windows SystemDrive
Note: The VCA installer can require up to 12 MB of additional free space on your
Windows SystemDrive to complete the installation.
• System memory
— 256 MB of RAM for Windows Server 2003
— 256 MB of RAM for Windows 2003 Server ES for 64-bit Extended Systems (starting with
the ProLiant Support Pack 7.2 and later)
— 256 MB of RAM for Windows 2003 Server 64-bit Edition (starting with the ProLiant
Support Pack 7.2 and later)

Client requirements
Requirements for client access to the VCA are outlined.

Hardware and software

• Operating system
— Windows Server 2003 with Service Pack 2
— Windows XP
• Browser
— Internet Explorer 7.0
— Internet Explorer 6.0 with Service Pack 1 or later
— Mozilla 1.6 or later
— Firefox 1.0 or later
• System memory
— 256 MB of RAM for Windows XP or Windows Server 2003

Installation overview
1. Verifies the presence of a previously installed version of the VCA or performs new installation
on systems with no previous installation or upgrades current installation on systems with
existing installation
Note: You do not need to initiate the upgrade process because the installation of the VCA
does it for you.
2. Copies the necessary files to the correct location
3. Registers VCA
4. Initiates the operation of the VCA
The VCA installation executable is located in the following locations:
• http://www.hp.com/servers/manage
• HP SmartStart CD
• HP SmartSetup CD
• Software Update CD
• A repository managed by the VCRM that contains the latest Windows ProLiant and Integrity
Support Pack.

Installing the VCA for Windows

The VCA installation wizard launches in interactive mode when the installation executable is
run from the command line or launched from Windows Explorer.
After the wizard initiates, the HP Setup dialog box appears.

20 Installing the VCA on Windows operating systems

 If a previous version of the VCA is installed, the VCA upgrade is initiated. The HP Setup dialog
box appears and indicates the software is installed but not current. Click Install to upgrade.
If a current version of the VCA is installed, the VCA reinstall is initiated. The HP Setup dialog
box appears and indicates the software is installed and current. Click Install to reinstall over the
currently installed software.
If you have a newer version of the VCA installed, and you want to downgrade, uninstall the
current VCA, reboot the machine, and run the new installation.
Click Install. If this is the initial installation, the VCA Configuration dialog box appears.

Configuring the VCA

The VCA Configuration wizard appears during the initial installation of the VCA, and enables
you to configure the VCRM, which provides a reference point for available HP software.
Caution: Enter the account and provide the appropriate password for the VCA to download
software from the VCRM. Enter at least a user-level account and provide the appropriate password
for the VCA to provide software status by comparing the inventory with what is available at the
VCRM. However, user-level account access does not allow the VCA to download and install
software.
To configure the VCA's settings to use a VCRM to obtain software status and software downloads:
1. In the Repository Manager Device field, enter the name of the system that hosts the VCRM.
You can enter an IP address or system name.
2. In the Login Account field, enter a login that has the appropriate security level for the SMH
on the specified system. The type of account, account name and password depend on whether
the SMH or Management HTTP Server is installed at the system specified in the previous
step. This account must have Operator or Administrator level at the VCRM system, so it
is recommended that you use a browser to verify the login account and password before
entering it.
Note: This account is at the VCRM system, not the VCA system.
Note: To avoid any potential administrator lockouts from the SMH, the account named
Administrator cannot be used to connect to the VCRM from the VCA. Do not use that
account if the VCRM system has the SMH installed. For more information regarding
migrating version control to SMH, refer to Migrating Version Control to the System
Management Homepage.
3. In the Password field, enter the password for the login account.
4. In the Password Confirm field, re-enter the password exactly as you entered it in the
Password field.
5. Click Finish. The HP Setup dialog box appears and the installation begins. When it
completes, the results of the installation are displayed.
6. Click Close. The installation is complete.

Installing the VCA for Windows silently

The VCA installation for Windows enables you to silently install the VCA.

Installing silently using the CLI

To install silently using the CLI:
From a command prompt, enter the following command:
component name /silent
For example, you might enter c:\>cp005693.exe /silent.
or

Installing the VCA for Windows silently 21

 c:\>cp005693.exe /s
Note: Be sure to configure the VCA component using the HP Remote Deployment Utility before
installing it to remote systems. If the component is not configured, the VCA displays an unknown
status.

22 Installing the VCA on Windows operating systems

6 Installing the VCA using the Linux Deployment Utility
The Linux Deployment Utility provides an easy and efficient method to upgrade and manage
system software. The utility enables you to deploy and maintain ProLiant and Integrity Support
Pack software on local servers through use of the terminal window and on remote servers through
use of the secure shell (ssh) utility. The Linux Deployment Utility is shipped with the Linux
ProLiant and Integrity Support Pack, which is available on the HP SmartStart CD. The Linux
Deployment Utility enables you to install components or ProLiant and Integrity Support Packs
in-place, but not remotely.
The Linux Deployment Utility parses the .XML files associated with each component and verifies
whether the installation of those components is supported on the specific environment. The
components that are supported for installation are listed with a status icon indicating whether
the component should be installed, and whether it should be configured. Configuring or
pre-configuring the VCA component is optional.

Pre-configuring the VCA component

Note: All pre-configuration settings are saved in the component XML file.
To pre-configure the VCA component:
1. Run the installxxx.sh script. The HP ProLiant LDU page appears.
2. Select VCA for Linux
3. Right-click and select Configure Component. The Configuration Options page appears.
a. In the Server Name field, enter the VCRM system name.
b. In the Login Name field, enter the login name for the VCRM system.
c. In the Password field, enter the password associated with the VCRM specified.
d. Click Save. The Save Configuration Parameters? page appears.
e. Enter the absolute path name or click OK to accept the default path name for storing
the configuration settings.
f. Click OK to complete the VCRM configuration. The Config? column displays
Completed.
4. After pre-configuration is complete, installation can be initiated through the Linux
Deployment Utility as part of the complete ProLiant and Integrity Support Pack or the single
component can be installed independently.

Installing the VCA as a single component

You can install the VCA independently of other components included in the ProLiant and Integrity
Support Pack.
To install the VCA as a single component:
1. Run the installxxx.sh script. The HP ProLiant Linux Deployment Utility page appears.
2. Select all components except the VCA component.
3. Right-click all other components and select Do Not Install component.
Note: The VCA component can also be installed by invoking the following command from
the shell prompt:
./install720######.sh –c hpvca-2.1.x-x.*linux.rpm
4. This process installs the component with the configurations that are provided through the
Linux Deployment Utility.
For more information regarding use of the Linux Deployment Utility, refer to the HP ProLiant
Support Pack and Deployment Utilities User Guide.

Pre-configuring the VCA component 23

Installing the VCA without pre-configuration
You can install the VCA component interactively without any configurations. After installation,
you can configure the VCA settings at any time by browsing to VCA with SMH's Administrator
or Operator privileges.

24 Installing the VCA using the Linux Deployment Utility

7 Installing the VCA on Linux operating systems
VCA for Linux requirements
The VCA can be used in conjunction with HP SIM and the VCRM. The options must be configured
for full functionality. The following diagram illustrates a logical order to the VCA installation
process on a Linux operating system.

System requirements
To install the VCA on a Linux system, the system must meet the following requirements.

Supported hardware and software

• Operating systems
— Novell Open Enterprise Server (OES) with Service Pack 1 or later
— Red Hat Enterprise Linux 5 for x86
— Red Hat Enterprise Linux 5 for AMD64 and Intel EM64T
— Red Hat Enterprise Linux 5 for AMD64 and x86
— Red Hat Enterprise Linux 4 for x86, Update 2
— Red Hat Enterprise Linux 4 for AMD64 and Intel EM64T, Update 2
— Red Hat Enterprise Linux 3 Update 3 for x86, Update 6
— Red Hat Enterprise Linux 3 Update 3 for AMD64 and Intel EM64T (starting with the
ProLiant Support Pack 7.2 and later), Update 6
— SUSE Linux Enterprise Server 10 for x86
— SUSE Linux Enterprise Server 10 for AMD64 and Intel EM64T
— SUSE Linux Enterprise Server 9 for x86, Service Pack 2
— SUSE Linux Enterprise Server 9 with Service Pack 2 for AMD64 and Intel EM64T (starting
with the ProLiant Support Pack 7.2 and later)
— SUSE Linux Enterprise Server 8 for AMD64 (starting with the ProLiant Support Pack
7.2 and later), Service Pack 4
— UnitedLinux 1.0, Service Pack 4 or later
• Server software
— SMH (hpsmh RPM) installed
— HP Server Management Application and Agents (hpasm RPM) 7.00 or later required
for software inventory and status features to be functional

VCA for Linux requirements 25

 • Hardware
— ProLiant Server
• Disk space
— 36 MB
• System memory
— 256 MB of RAM
• HP Server Management Drivers and Agents
— hpasm RPM 7.0 or later
Note: The SNMP services must be active with at least one community string defined
to allow read access, must be configured for software inventory and status features to
be functional.

Client requirements
Requirements for client access to the VCA from Linux operating systems are outlined.

Hardware and software

• Supported Operating Systems
— Red Hat Enterprise Linux 5 for x86
— Red Hat Enterprise Linux 5 for AMD64 and Intel EM64T
— Red Hat Enterprise Linux 5 for AMD64 and x86
— Red Hat Enterprise Linux 4 for x86, Update 2
— Red Hat Enterprise Linux 4 for AMD64 and Intel EM64T, Update 2
— Red Hat Enterprise Linux 3 Update 3 for x86, Update 6
— Red Hat Enterprise Linux 3 Update 3 for AMD64 and Intel EM64T (starting with the
ProLiant Support Pack 7.2 and later), Update 6
— Red Hat Enterprise Linux 2.1 Update 5
— SUSE Linux Enterprise Server 9 for x86, Service Pack 2
— SUSE Linux Enterprise Server 9 for AMD64 and Intel EM64T (starting with the ProLiant
Support Pack 7.2 and later), Service Pack 2
— SUSE Linux Enterprise Server 8 for AMD64 (starting with the ProLiant Support Pack
7.2 and later), Service Pack 4
— UnitedLinux 1.0, Service Pack 4
• Browsers
— Mozilla 1.7 (local or remote access) or later
— Firefox 1.0 or later
• System memory
— 128 MB of RAM
Note: You can browse to a Linux server from a Windows system using Internet Explorer 6.0 or
higher.

Installing the VCA for Linux

The VCA installation process installs the necessary files and starts the services, which are
registered for automatic execution on the next system initialization. A reboot is not necessary
after the installation process.
The VCA for Linux requires the VCRM 2.0.1.30 or later.
To install the VCA on a Linux system:

26 Installing the VCA on Linux operating systems

 Note: You must be logged in as root to perform the initial install, reinstall, or upgrade of the
VCA.
1. For an initial install or upgrade, enter the following command:

rpm –ivh hvca-2*.linux.rpm

Starting with ProLiant Support Pack 7.2, VCA for Linux can be installed or upgraded as
part of the ProLiant or Integrity Support Pack installation.
2. If the SMH has not been configured, then it must be configured. For more information
regarding configuration of the SMH, refer to the SMH Online Help System.
3. The initial installation of the VCA enables you to configure the VCRM. The VCRM host
address, login name, and password can be specified. For example:
Please, set the required fields for version control agent
configuration
Repository............: <enter the name or IP of the system where the repository is
installed>
Login.....................: <enter a login name with administrator privileges. For
example, vcadmin. >
Password.............: <enter the password associated with the login name above>
Confirm Password: <reenter the password exactly as you entered it previously>
Confirm data? Y/N: <enter Y or N>
vcagent configuration complete
press any key to continue...
Note: If you do not specify a VCRM, a message displays asking you if you want to specify
the VCRM. If you select No, a warning message appears indicating a repository has not been
configured.
4. The VCA configuration is complete. A reboot is not necessary.

Verifying the VCA service is running

To verify the VCA service is running on the system, enter the following:
1. For UnitedLinux and SUSE Linux:

/etc/init.d/hpvca status

The output that appears is similar to:

Checking for process hpvca: running

2. For Red Hat Linux:

Installing the VCA for Linux 27

 # service hpvca status

The output that appears is similar to:

vcagentd (pid 698 697 696 695 694 657) is running…

Installing the VCA for Linux silently

The VCA installation for Linux enables you to silently install the VCA.

Installing silently using the CLI

To install silently using the CLI:
1. Copy the Linux Support Pack contents from the HP SmartStart CD.
2. Using the Linux Deployment Utility, run the following script:
./installxxx.sh -s -c component name

28 Installing the VCA on Linux operating systems

8 Installing the VCRM on Windows
VCRM requirements for Windows
The following diagram illustrates a logical order to the VCRM installation process.

System requirements
To install the VCRM, the computer must meet the minimum requirements listed.

Supported hardware and software

• Operating system
— Microsoft Windows Server 2003
— Windows Server 2003 ES for 64-bit Extended Systems
— Windows Server 2003 64-bit Enterprise Edition
— Windows XP Professional with Service Pack 2 for x86
• Browser
— Firefox 1.0 or later
— Internet Explorer 6.0 with Service Pack 1 or later
• Server software
— TCP/IP installed
— SMH installed
• Hardware
— ProLiant Server
— HP Business Desktops
— Integrity Server (rx1620, rx2600, rx2620, rx4640, rx5670, rx7620, rx8620, Superdome)

VCRM requirements for Windows 29

 • Disk space
— 14-15 MB (Installation files only)
— 200 MB in the VCRM installation drive for temporary ProLiant or Integrity Support
Pack extraction
— 2 GB for the repository. This must be on a local, writeable drive.
• System memory
— 256 MB for Windows XP and Windows Server 2003

IMPORTANT: The disk space requirements previously mentioned are specific to the installation
of the VCRM. The size of the repository depends on the files contained in the repository directory.
Each ProLiant or Integrity Support Pack executable, which is downloaded automatically if the
Auto Update feature is enabled, is approximately 100 MB in size and extracts to approximately
200 MB in size. If you are downloading multiple ProLiant or Integrity Support Packs, then you
can multiply this size by the number of ProLiant or Integrity Support Packs you are downloading
in your repository to determine how much disk space is required.

Client requirements
Minimum requirements for client access to the VCRM are outlined.

Hardware and software requirements

• Operating system
— Windows Server 2003
— Windows XP
• Browser
— Internet Explorer 6.0 with Service Pack 1 or later
— Mozilla 1.6 or later
Note: Uploading software by way of the Mozilla browser interface is not supported.
• System memory
— 256 MB of RAM for Windows XP or Windows Server 2003

Configuring Internet Explorer settings for SMH pre-configuration

Some features of the VCRM's browser interface depend on browser settings at the client system
from which the VCRM is being accessed. The security settings in Microsoft Internet Explorer
must be set to initialize the VCRM Upload process.
To configure the Microsoft Internet Explorer security settings:
1. From the Microsoft Internet Explorer toolbar, click Tools and select Internet Options. The
Internet Options dialog box appears.
2. Click Custom Level. The Security Settings dialog box appears.
3. Under ActiveX controls and plug-ins, Download signed ActiveX controls, select Enable.
4. Under Run ActiveX controls and plug-ins, select Enable.
5. Under Script ActiveX controls marked safe for scripting, select Enable.
The advanced settings in Microsoft Internet Explorer must be set to ensure that saving a copy of
the VCRM log functions when the log is cleared.
To configure the Microsoft Internet Explorer advanced settings:
1. From the Microsoft Internet Explorer toolbar, click Tools and select Internet Options. The
Internet Options dialog box appears.
2. Click the Advanced tab.

30 Installing the VCRM on Windows

 3. Scroll down to the Security section, and disable Do not save encrypted pages to disk.
4. Click OK to save your changes and close the Internet Options dialog box.

Installing the VCRM

The VCRM can be installed during the HP SIM installation or you can install it independently.
Although the VCRM can be obtained from multiple sources (see Chapter 3: “Obtaining the
software” (page 15)), the following example shows the steps for obtaining the software from the
HP Insight Control Management DVD and installing it independently of HP SIM.
To install VCRM from the HP Insight Control Management DVD:
1. Insert the HP Insight Control Management DVD in the DVD drive. The HP Insight Control
Management window appears.
2. Click Agree to accept the license agreement. You can click Disagree to cancel and close the
window.
3. Click the Products tab.
4. From the left pane, click the Version Control Repository Manager link. The VCRM options
appear in the right pane.
5. The VCRM installation wizard initiates the HP Insight Management Agent configuration
settings in interactive mode when the installation executable is run from the command line
or launched from Windows Explorer. After the wizard initiates, the HP Setup - VCRM
dialog box appears.
If you have a previous version of the VCRM installed on a machine, the installation wizard
detects it and initiates the upgrade with the current version displayed in the dialog box.
If you have the current version of the VCRM installed on a machine, the installation wizard
detects it and initiates the reinstallation. The HP Setup - VCRM dialog box indicates that
the software is installed and current and that you can reinstall it.
Note: If you have a newer version of the VCRM installed and you want to downgrade,
uninstall the current VCRM, reboot the machine, and run the new installation.
6. Click Install. The VCRM Setup - Repository Directory dialog box appears.
Note: You can click View Documentation to view the documentation.
7. Click Cancel to exit the setup and abort the installation.

VCRM Setup - Repository Directory

The VCRM Setup - Repository Directory dialog box enables you to specify the directory where
HP software is located so the VCRM can monitor it. The default repository directory path is
%SystemDrive%\repository. In addition, you can select to have the repository initially
populated if you are installing the VCRM for the first time.
Note: If you are upgrading or reinstalling the VCRM, the Perform an initial repository
population option is unavailable.
To change the repository directory:
1. Click Browse.
2. Select the directory where the HP software is to be stored. The path to the directory appears
in the Repository Directory field.

Installing the VCRM 31

 3. Select Perform an initial repository population if you want to have the repository updated
with ProLiant and Integrity Support Packs. (If Perform an initial repository population is
deselected, or the option is not displayed, the Automatic Update wizard page appears next.
4. Click Next to accept the selected directory. If you selected Perform an initial repository
population on the previous dialog box, the VCRM Setup - Initial Repository Configuration
dialog box appears.
The Automatic Update dialog box enables you to schedule automatic updates for your
repository from the HP website.
Note: If you do not want to use the automatic update feature, refer to Updating a repository
to update the repository manually.

Repository Population - Initial Installation

1. Click Add to select a directory that contains a ProLiant and Integrity Support Pack. The
Browse for Folder dialog box appears.
2. Navigate to the directory that contains a ProLiant and Integrity Support Pack, and click OK
or Cancel to abort the selection.
All Support Packs found in the selected directory are added to the list shown in the Initial
Repository Configuration dialog box. You can choose as many directories as you want,
and then delete any Support Packs from the list you do not want to be copied.
3. Click Next. The VCRM Setup - Automatic Update dialog box appears.

Configuring Automatic Update

The Automatic Update dialog box enables you to schedule automatic updates for your repository
from the HP website.
Note: If you do not want to use the automatic update feature, refer to Updating a repository to
update the repository manually.
To configure an automatic update:
1. Select Enable Automatic Update to automatically download ProLiant and Integrity Support
Packs and components at a specific time.
2. In the Interval between updates field, select an interval from the dropdown menu.
3. In the Day of Week field, select a day of the week to update the repository from the
dropdown menu to update the repository.
4. In the Time of Day field, select a time for the update to occur from the dropdown menu for
the update to occur.
5. Use the Set Proxy option to configure a proxy server for VCRM.
To set the proxy server:
a. Click Set Proxy. The Proxy Server Settings dialog box displays.
b. In the Server Name field, enter the name of the proxy server. Clearing this field removes
all proxy server settings, and the automatic update is performed without connecting
through a proxy server.
c. In the Port field, enter the proxy server port. For example, enter 8080. If the Server
Name field is blank, this value is ignored.
d. In the Server Login field, enter a valid login for the proxy server. Leave this field blank
if a server login is not required.
e. In the Password field, enter a valid password for the login on the proxy server. If the
Server Login field is blank, this field is ignored.
f. Click OK to save your settings or Cancel to discard the settings.

32 Installing the VCRM on Windows

 6. Click Finish to save the VCRM settings.
If Automatic Update is enabled and a proxy server is configured, the connection with the
proxy server is verified before continuing. If the proxy server cannot be reached, a message
appears indicating there was an error testing the download of the auto-update catalog. Click
Yes to save your settings or click No to re-enter the proxy server information.
7. The HP Setup wizard page appears, and the installation begins. When it completes, the
result of the installation appears.
8. Click Close. The installation is complete.
Note: You can install the VCRM during the HP SIM installation. Refer to the HP SIM User
Guide for more details.

Installing the VCRM for Windows silently

The VCRM installation for Windows enables you to silently install the VCRM.

Installing silently using the CLI

To install silently using the CLI:
From a command prompt, enter the following command:
component name /silent
or
component name /s
For example, you might enter c:\>cp005693.exe /silent.
Note: Installing the VCRM using /silent uses %SystemDrive%\repository as the repository
store directory, so you must configure the VCRM Automatic Update Settings manually.

Installing the VCRM for Windows silently 33

34
9 Updating a repository
The Auto Update feature of the HP Version Control Repository Manager is the preferred solution
for updating repositories automatically. The Auto Update feature of the VCRM keeps servers
connected to HP for proactive delivery of the latest ProLiant and Integrity Support Packs and
components directly to a specified repository. You can configure the automatic population of
the repository during the VCRM installation, or in the event you cannot use the Auto Update
feature, you can populate the repository from the HP SmartStart CD as indicated in the Updating
the repository from the HP SmartStart CD section. If you must update the repository manually,
for example, because you deleted a Support Pack from the repository and you later needed it,
refer to the Updating the repository manually from the HP SmartStart CD section.

Updating the repository from the HP SmartStart CD

To populate the repository with ProLiant Support Packs from the HP SmartStart CD 6.0 or later:
1. Insert the HP SmartStart CD in the CD-ROM drive. The SmartStart welcome screen
appears.
2. Click Populate a version control repository with the ProLiant Support Pack available
on this HP SmartStart CD. A screen appears asking you to enter a machine name.
3. In the Machine Name field, enter the name of the machine that has the repository installed.
4. Click Populate. Click Clear to clear the Machine Name field or Back to return to the previous
screen. The SMH appears.
5. In the User field, select the appropriate login from the dropdown menu.
6. In the Password field, enter the password associated with the login that you selected.
7. Click OK. The Upload Support Pack(s) page appears.
8. To upload a ProLiant Support Pack, refer to the Updating the repository manually from the
HP SmartStart CD.

Updating the repository manually from the HP SmartStart CD

To populate the repository manually with ProLiant Support Packs from the HP SmartStart CD
version 6.0 or later:
1. Insert the HP SmartStart CD in the CD-ROM drive.
2. From Windows Explorer, double-click the CD-ROM drive to open the HP SmartStart CD.
3. Click Compaq to open the directory.
4. From within the Compaq directory, click CSP to open the directory.
5. The CSP directory contains a NW directory that contains the Netware-related Support Packs,
a Linux directory for Linux-related Support Packs, and a Windows NT® directory that
contains all of the components and support packs and an XML file for each supported
Microsoft operating system. Click Linux or NT depending on the type of Support Packs with
which you want to populate your repository.
6. After you have opened one of the directories, select all of the Support Pack files, click Edit
from the Windows Explorer toolbar, and select Copy.
7. From Windows Explorer, navigate to the repository directory, for example, c:\repository.
Click the repository directory.
8. From the Microsoft Windows Explorer toolbar, click Edit and select Paste. The Support
Packs are copied into the c:\repository directory. The repository is now populated.
9. From the c:\repository directory, select a component. Right-click the component and
select Properties. Note that the file is read-only. For the VCRM to allow component
configuration, a component cannot be read-only. Deselect the read-only attribute and click
OK.

Updating the repository from the HP SmartStart CD 35

Updating the repository manually from the HP SmartSetup CD
To populate the repository with Integrity Support Packs from the HP SmartSetup CD 3.2 or later:
1. Insert the HP SmartSetup CD in the CD-ROM drive.
2. From Windows Explorer, double-click the CD-ROM drive to open the HP SmartSetup CD.
3. Click Contents to open the directory.
4. From within the Contents directory, click supportpack to open the directory.
5. The contents directory contains a supportpack directory that contains all Integrity
Support Packs.
6. After you have opened the directory, select all of the Integrity Support Pack files, click Edit
from the Windows Explorer toolbar, and select Copy.
7. From Windows Explorer, navigate to the repository directory, for example, c:\repository.
Select the repository directory.
8. From the Windows Explorer toolbar, click Edit and select Paste. The Integrity Support
Packs are copied into the c:\repository directory. The repository is populated.
9. From the c:\repository directory, select a component. Right-click the component and
select Properties. Note that the file is read-only. For the VCRM to allow component
configuration, a component cannot be read-only. Deselect the read-only attribute and click
OK.

36 Updating a repository
10 Uninstalling the VCA on Windows operating systems
To uninstall the VCA:
1. Select Start→Settings→Control Panel.
2. Click Add/Remove Programs. The Add/Remove Programs Properties dialog box appears
with a listing of installed software.
3. Select VCA.
4. Click Change/Remove. The Remove dialog box appears asking you to confirm your
intention to remove the VCA.
5. Click Yes. The VCA Remove dialog box appears again indicating whether the VCA has
been successfully removed.
6. Click OK. A dialog box appears asking you to reboot the system.
Note: Reboot the system before reinstalling the VCA.
7. Click OK to reboot the system.

37
38
11 Uninstalling the VCA on Linux operating systems
To uninstall the VCA for Linux:
To uninstall the HP Version Control Agent, log in as root, and execute the following command:

# rpm –e hpvca

The VCA is uninstalled.

Note: After the VCA has been removed, the configuration options and logs are deleted.

39
40
12 Uninstalling the VCRM on Windows operating systems
To uninstall VCRM:
1. Select Start→Settings→Control Panel.
2. Click Add/Remove Programs. The Add/Remove Programs dialog box appears with a
listing of installed software.
3. Select VCRM.
4. Click Change/Remove. The Remove dialog box appears asking you to confirm your
intention to remove the VCRM.
5. Click Yes. If you decide you do not want to uninstall the VCRM, click No to cancel. The
Reboot Required dialog box appears indicating that a reboot is required to remove files
that are currently in use by Windows.
6. Click OK. A dialog box appears asking you to reboot the system.
Note: After an uninstall, reboot the system before reinstalling the VCRM.
Note: The designated repository directory is not deleted during uninstallation. The directory
must be manually deleted.
7. Click OK to reboot the system.

41
42
Glossary
available A listing of the software components available in the repository that the VCA has been
software configured to point to. When browsing directly into a VCA, these additional components can
be selected for installation.
component A component is a single, self-describing, installable (interactive or silent) binary file containing
a single piece of software, such as firmware image, driver, agent, or utility, that is supported
by the management and update tools.
Custom Software A set of HP software components that have been bundled together as a baseline by the customer.
Baseline Modifying the contents of an existing Support Pack provides customers with the flexibility to
define their own baselines for their environment.
graphical user A program interface that takes advantage of the computer's graphics capabilities to make the
interface (GUI) program easier to use. HP SIM's GUI is Web-enabled and displays in a web browser.
HP Insight A program that regularly gathers information or performs some other service without the user's
Management immediate presence.
Agent
HP ProLiant and An HP ProLiant and Integrity Support Pack, or Custom Software Baseline is a set of HP software
Integrity Support components that have been bundled together by HP, and verified to work with a particular
Pack operating system. A ProLiant and Integrity Support Pack contains driver components, agent
components, and application and utility components. All of these are verified to install together.
HP Systems System management software that is capable of managing a wide variety of systems, including
Insight Manager HP systems, clusters, desktops, workstations, and portables.
HP SIM combines the strengths of HP Insight Manager 7, HP Toptools, and HP Servicecontrol
Manager to deliver a single tool for managing HP ProLiant, Integrity, and HP 9000 systems
running Windows, Linux, and HP-UX. The core HP SIM software delivers the essential
capabilities required to manage all HP server platforms. HP SIM can also be extended to deliver
unparalleled breadth of system management with plug-ins for HP storage, power, client, and
printer products. Plug-ins for rapid deployment, performance management, and workload
management enable systems administrators to pick the value added software required to deliver
complete lifecycle management of their hardware assets.
HP Version An Insight Management Agent that is installed on a server to enable the customer to see the
Control Agent HP software that is installed on that server. The VCA can be configured to point to a repository
being managed by the VCRM, enabling easy version comparison and software deployment
from the repository to the server that the VCA is installed upon.
HP Version An Insight Management Agent that enables a customer to manage software from HP that is
Control stored in a directory/repository known as the Version Control Repository.
Repository
Manager
HP Web-enabled Software that manages HP Web-enabled products.
System
Management
Software
installed version A particular HP software component that is installed on the server on which the VCA is installed.
latest version The latest version of a particular HP software component that is contained in the repository.
overall software This section indicates whether the software on the server on which the VCA is installed has
status any updates available within the repository in which it has been configured to monitor.
Red Hat Package The Red Hat Package Manager is a powerful package manager that can be used to build, install,
Manager (RPM) query, verify, update, and uninstall individual software packages. A package consists of an
archive of files and package information, including name, version, and description.
Reference A baseline bundle of HP software components that the VCA can be configured to point to in
Support Pack the repository. This setting enables users to indicate that they want to keep all of their software
up to a certain Support Pack level.

43
Replicate Agent A tool that can be used to copy Web-based agent settings to a group of systems.
Settings
repository A directory containing ProLiant and Integrity Support Packs and Smart Components.
Secure Task Secure execution of a task from a managed system. This feature of HP SIM ensures that the
Execution (STE) user requesting the task has the appropriate rights to perform the task, and encrypts the request
to protect data from snooping.
Simple Network One of the management protocols supported by HP SIM. Traditional management protocol
Management used extensively by networking systems and most servers. MIB-2 is the standard information
Protocol (SNMP) available consistently across all vendors.
single login Permission granted to an authenticated user browsing to HP SIM to browse to any of the
managed systems from within HP SIM without re-authenticating to the managed system. HP
SIM is the initial point of authentication and browsing to another managed system must be
from within HP SIM.
software A listing of the HP software installed on the system where the VCA is installed.
inventory
support pack A field that displays the version of a particular HP software component that is contained in the
version Reference Support Pack that the VCA has been configured to use as a baseline. There might be
a later version than this available in the repository, but this is the latest version of this particular
component in the Reference Support Pack.
System An integrated piece of software used by the HP suite of HP Web-enabled System Management
Management Software to communicate over HTTP and HTTPS. It provides a uniform set of functionality
Homepage and security to HP Web-enabled System Management Software.
VCA log A listing of all the software maintenance tasks completed by the VCA and reports resulting
from those tasks.
version control Referred to as the VCRM installed on a Windows system for Windows and Linux ProLiant
systems, and Software Distributor on HP-UX operating systems. Provides an overview of the
software status for all managed ProLiant or Integrity systems and can update system software
and firmware on those systems programmatically using predetermined criteria. Version control
identifies systems that are running out-of-date system software, indicates if an upgrade is
available, and provides reasons for upgrading. For HP-UX systems, Software Distributor can
be launched from an HP SIM CMS against one or more installed HP-UX systems.

44 Glossary
Index
Linux install, 25, 26
C Linux system requirements, 25
conventions, typographic, 2 Linux uninstall, 39
obtaining software, 15
F overview, 7
features, 7 requirements for Windows, 19
Windows client requirements, 20
H Windows installation, 19
HP SIM Windows system requirements, 19
integration, 7 Windows uninstall, 37
VCRM
I client requirements, 30
installation installation, 29
HP Remote Deployment Utility, 17 obtaining software, 15
VCA, 25 overview, 7
VCA for Windows, 19 system requirements, 29
VCRM, 29 uninstall, 41
update, 35
L
Linux W
Linux Deployment Utility, 23 Windows install
Linux Deployment Utility Installation HP Remote Deployment Utility, 17
Linux, 23

O
obtaining software
VCA, 15
VCRM, 15
overview, 7
SMH, 11
VCA, 7
VCRM, 7

R
Repository
update, 35

S
security considerations, 9
SMH
integration, 11
migration, 11

T
typographic conventions, 2

U
uninstall
VCA for Windows, 37
VCA Linux, 39
VCRM, 41
update software, 7

V
VCA
Linux client requirements, 26

45