Automating Software Maintenance in an HP Environment

(CMS). Refer to the System Management Homepage Installation Guide for information regarding
configuring the System Management Homepage.
Finally, when the Version Control Agent communicates with a Version Control Repository Manager, 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 System Management Homepage
on which the Version Control Repository Manager is installed. The System Management Homepage
requires a valid operating system account and password. Refer to the Version Control Agent online
help for more information regarding configuring these settings for the Version Control Agent.
For more information regarding the System Management Homepage, refer to the System
Management Homepage Installation Guide. For more information regarding HP Systems Insight
Manager, refer to the HP Systems Insight Manager User Guide.
Setting up Software Maintenance in the HP Environment
If you are setting up your HP network initially, use the following flow diagram and steps as a
guideline to ensure the network is set up correctly to manage as efficiently and effortlessly as possible.
1. Create the User Group and User account to use for Version Control. This is an account on the
Version Control Repository Manager system that is used by Version Control Agents when
communicating with the Version Control Repository Manager. This account must be configured in
the System Management Homepage’s security settings on the Version Control Repository Manager
system. There are no special privileges required for the group or account except login. If you are
using legacy installations of the Version Control Agent, you must create an account called
operator or user so those agents can be configured. Otherwise, create an account such as
vcoperator and add it to the group you have created. When the System Management
5