HP Version Control Agent 7.2 Release Notes

3 Issues and workarounds
HP VCA undergoes rigorous testing before releasing any given version of the product. From HP
test activities to date, the following items have been uncovered that you should keep in mind.
HP VCA
• Issue: A system running HP Insight Management Agents on a named Windows 2003 account,
the HP VCA upgrade does not finish successfully.
Description: The HP VCA is designed to be installed and running on the local system account
on Windows for performing installation tasks.
• Issue: HP VCA does not accept HP SIM software update tasks if a previous software update
task was terminated because of the HP VCA service stopping before completion.
Description: This is because of HP SIM task reporting In Progress from the HP VCA.
Workaround: HP recommends:
1. Restart the HP VCA.
2. Stop the HP SIM task that is reporting In Progress.
3. Restart the HP SIM task. The task initiates and completes successfully.
• Issue: When a Windows Foundation Agent service or Linux Host agent (cmahostd) is stopped,
the HP VCA status and Overall System Status are displayed as green indicating Normal, even
if the real status indicates a Warning.
• Issue: When the SMH where the HP VCRM is installed allows Anonymous access, a HP VCA
that is configured to use that HP VCRM can be configured on the Change Settings page.
Description: If the login information is incorrect for the HP VCRM system, it enables the settings
to be saved, and inventory data at the HP VCA appears correct. However, software installations
at that HP VCA fail because the secure login at the HP VCRM is rejected because of the
incorrect settings.
• Issue: The memory utilization of the HP VCA increases as a result of installing software. Memory
is released when the service restarts, for example, following installation of a complete ProLiant
or Integrity Support Pack upgrade or Service Pack for ProLiant upgrade.
6 Issues and workarounds