HP Smart Update Manager 6.4.1 Release Notes

HP SUM does not present some RPMs for deployment even if they apply to the node
Suggested Action: Some RPMs do not contain the appropriate data for HP SUM to present them for
deployment. You can deploy these RPMS outside of HP SUM. The required data will be updated in a
future version of the RPM.
Advanced filters do not work as expected when you create a custom baseline
Suggested Action: No action. This will be resolved in a future version.
HP SUM does not build source RPMs
Suggested Action: Build the source RPM outside of HP SUM and then add the RPM to a baseline. After
HP SUM performs inventory on the baseline, it can deploy the RPM. This is how HP SUM designed to
work.
HP SUM unexpectedly stops running when you disconnect an ISO that contains a baseline that has
been added to HP SUM
Suggested Action: Do not disconnect from an ISO that contains a baseline that has been added to HP
SUM while HP SUM is running.
HP SUM adds an empty Additional Package to a baseline if the directory includes a .zip file
Suggested Action: Do one of the following:
• Do not assign the empty Additional Package to nodes.
• Move the .zip file to a directory mapped to a baseline.
HP SUM does not create a custom baseline if there is not enough free space, but HP SUM displays a
message that the baseline was created
Suggested Action: Make sure there is enough free space before creating a custom baseline.
HP SUM does not save a custom baseline if there are Japanese characters in the directory path
Suggested Action: No action. This will be resolved in a future version.
HP SUM does not display an Additional Package for a node on the Nodes Overview screen
Suggested Action: No action. This will be resolved in a future version.
HP SUM does not display the UNC option on Linux hosts
Suggested Action: No action. HP SUM does not support UNC paths on Linux hosts.
HP SUM displays components ready for deployment after deploying the components
If you run HP SUM after deploying updates to a node, HP SUM displays some components are ready
for deployment. These components have more than one driver in them, and HP SUM is only comparing
one update to the node.
Suggested Action: No action. This will be resolved in a future version.
A custom bootable ISO includes more than one source ISO
Suggested Action: When you create a custom baseline, make sure that the source ISO directory includes
only one ISO file.
HP SUM continues to download a file from the web after you click Abort
Suggested Action: HP SUM finishes downloading the current component after you click Abort.
Issues and suggested actions 25