SMS HP Tools Release Notes
Table Of Contents
- Release Notes for SMS Inventory Tool for HP ProLiant and Integrity Update (version: 1.2)
- Additional Online Resources for SMS
- Using the SMS Inventory Tool for HP ProLiant and Integrity Update
- Upgrading the SMS Inventory Tool for HP ProLiant and Integrity Update to a newer version
- Known Issues with the current release
- Microsoft Windows Vista is not supported
- HP Insight Inventory Collector does not support new version of Insight Management Agents
- Advertisement status in SMS SP2 for HP update installation does not reflect actual reboot requirement
- The previous version of the scan tool is executed after uninstalling and reinstalling the SMS Inventory Tool for HP ProLiant and Integrity Update
- Unsupported HP servers
- Specifying an Authentication Account for the Synchronization Task to Use
- Enabling access privilege for the Synchronization Task when obtaining manifest catalog from local share
- Knowledge Base (KB) Article Issues
- Additional Components are downloaded from the Internet
- For Integrity Servers, SMS Inventory Tool for HP ProLiant and Integrity update will not recognize HP software prior to version 3.4
- For Integrity Servers, SMS Inventory Tool for HP ProLiant and Integrity falsely reports default drivers as compliant
- Smart Component information is not available without a direct internet connection
- IA-64 and x64 platforms need to be selected manually when creating a custom package using the DSUW
- Software Update status for components does not reflect newly installed hardware
- Complaint status for Support Paq might not reflect actual system status
- Log files in 64-bit managed system contains incorrect path information
- Errors and inconsistencies for compliance and requested status in Reports and DSUW
Software Update status for components does not reflect newly
installed hardware
ISSUE: The Scan tool can only detect component status if the component is installed and
therefore will not be able to report status for hardware without HP software installed.
WORKAROUND: Always install whole Support Paq to ensure required software is
installed for all supported devices.
Complaint status for Support Paq might not reflect actual
system status
ISSUE: Due to the limitation that the Scan tool can only detect status for components
that are currently installed and therefore, the Complaint status for Support Paq might not
reflect the actual system status. The Scan tool report Complaint status for the Support Paq
if all installed and detected component statuses are complaint.
WORKAROUND: Always install whole Support Paq to ensure required software is
installed for all supported devices.
Log files in 64-bit managed system contains incorrect path
information
ISSUE: Log files generated by the Scan tool contain incorrect path information when
running on 64-bit operating system. 64-bit Windows operating system enable Directory
Redirection by default for several system directories and therefore causing the Scan tool
to report incorrect information for some paths.
WORKAROUND: None
Errors and inconsistencies for compliance and requested status
in Reports and DSUW
ISSUE: Compliant and Requested status in HP Reports show incorrect information due
to NULL SMS database entries. The incorrect status also reports in DSUW. When a HP
compliance report is ran, a list of software components is displayed with columns
"Requested" and "Compliant" indicating the number of non-compliant and compliant
clients respectively for a particular software. When an entry in the first column is clicked
to drill down for details, the next page will reveal an inconsistent count of non-compliant
and compliant clients when compared to the previous page. This is also true for other
reports.