Version Control Installation Guide

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:
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
Migrating Version Control with ProLiant Support Pack 7.1 and earlier 13