Release Notes
HP Client Manager Software 6.0 Service Pack 1

October 7, 2004

Contents
SECTION 1 OVERVIEW.... 2 SECTION 2 WHATS NEW IN HPCMS 6.0 SERVICE PACK 1... 2 SECTION 3 WHATS NEW IN HPCMS 6.0.... 6 SECTION 4 KNOWN ISSUES.... 8

Notice

The content in this document represents the current view of Altiris as of the date of publication. Because Altiris responds continually to changing market conditions, this document should not be interpreted as a commitment on the part of Altiris. Altiris cannot guarantee the accuracy of any information presented after the date of publication. 2004 Altiris. All rights reserved. Altiris, the Altiris logo, BootWorks, Inventory Solution, LabExpert, PC Transplant, RapiDeploy, and RapidInstall are registered trademarks of Altiris, Inc. in the United States. Carbon Copy is a registered trademark licensed to Altiris, Inc. in the United States and a trademark of Altiris, Inc. in other countries. Altiris eXpress, Deployment Server, Deployment Solution, My IT Forum, Notification Server, Vision, Web Reports and other product names are trademarks of Altiris, Inc. in the United States and other countries. All other brand names are trademarks or registered trademarks of their respective companies. Information in this document is subject to change without notice. For the latest documentation, visit our Web site at www.altiris.com. RNT: D

Section 1 Overview

1.1 Document Purpose
This document provides the whats new and known issues information for HP Client Manager Software 6.0 Service Pack 1.

1.2 Background

The HP Client Manager Software 6.0 version is a completely re-engineered product from previous versions and is co-developed by HP and Altiris. This version works with Altiris Notification Server (NS) version 6.0 and has been rewritten on a.NET platform

1.3 Documentation

Product documentation is available in the HP Client Manager Software 6.0 Product Guide. To view Altiris product documentation in.PDF format, use Adobe Acrobat Reader (http://www.adobe.com/products/acrobat/readstep2.html).
1.4 Installation and Licensing
Installation and licensing information is provided in the Altiris Getting Started Guide available when the software is downloaded from the Altiris Web Site, the HP Client Manager Software Product Guide and the Altiris Notification Server Product Guide.
Section 2 Whats New in HPCMS 6.0 Service Pack 1
2.1 New HP System Support
The following systems have been added to the supported systems list for HP Client Manager Software. HP Desktop dc7100 USDT HP Desktop dc7100 CMT HP Desktop dc7100 SFF HP Desktop dx6100
Note: If there are newer HP systems not listed as a supported system in the table below, it is possible that support may be added in between releases. See the Update Supported HP Client Computer List section in the HP Client Manager Software Product Guide for more information on how to update and install newly supported systems. Some older systems that are no longer being supported by HP have had their support discontinued. The following is a complete list of systems supported by HPCMS 6.0 SP1:

RELEASE NOTES

HPCMS 6.0 SP1

PAGE 2 OF 10

HP computers supported Desktops Compaq Deskpro EN (manufactured after 2001) Compaq iPAQ Desktop (manufactured after 2001) Compaq Deskpro EX/EXS Compaq Evo D300/D310 Compaq D 315 Business PC Compaq Evo D320/D500/D510 HP Evo D510 e-PC HP Compaq Business Desktop d325/d330/d530/dc5000 HP Point of Sale system rp5000 HP e-PC HP Vectra VL400/VL410/VL420/VL800/VL8i HP Desktop dc7100 USDT HP Desktop dc7100 CMT HP Desktop dc7100 SFF HP Desktop dx6100 Notebooks/ Tablet PC Compaq Armada E500 Family Compaq Evo N400c/N410c Compaq Evo N600c/N610c/N620c/N800c/N1000c Compaq Tablet PC TC1000 HP Compaq Tablet PC tc1100 HP Compaq Business Notebook nc4000/nc6000/nc8000 HP Omnibook VT6200/510 Workstations
HP computers with support discontinued Compaq Desktop EN Series (manufactured prior to 2001) Compaq iPAQ Desktop (manufactured prior to 2001)
Compaq Evo N800w Compaq Evo N1005/N1020v Compaq Armada M300/M700 Families HP Omnibook 6100/XE4000/XE-GF
HP Workstation Compaq Deskpro Workstation 300 xw3100/xw4000/xw4100/xw4200 Compaq Professional Workstation xw5000/xw6000/xw8000/xw6200/xw8200 AP200/AP250/AP400/AP550 Compaq Professional Workstation SP700/SP750 Compaq Evo Workstation W4000/W6000/W8000 HP Workstation x1000/x1100/x2000/x2100/x4000

PAGE 3 OF 10

2.2 Select BIOS Settings Can Now be Made to HP Business Notebook Computers
HPCMS now provides the ability to change select BIOS settings on HP Notebook Computers. Supported BIOS settings vary by platform. Through the HPCMS BIOS Administrator Wizard you can change the following settings for HP Business Notebooks. Serial Port Parallel Port Boot Order BIOS Setup Password Wake on LAN
BIOS setting options in HPCMS that are not available to HP Notebooks include: USB Cover Removal Sensor Cover Lock UUID Advanced BIOS Settings BIOS setting options not available through the BIOS Administration Wizard in HPCMS may be changed using the RMSET.TXT file. Please reference the Advanced BIOS Settings section in the HPCMS Product Guide.
2.3 Multi-Language Support
You can now view HPCMS in German, French, and Japanese in the Altiris console after changing the language setting in your Browser. The HPCMS Product Guide and all help files will also appear in the selected language. Additional languages will be supported for the HPCMS client agent. Note: Although the HPCMS client agent is in English only, the diagnostics error and message return will be localized.
2.4 Fixes intermittent issue when flashing the BIOS on nc4000, nc6000, and nc8000 systems. 2.5 Now allows updated HP CVA files to replace older versions in the SoftPaq FileStore directory. 2.6 Upgrading from previous versions of HP Client Manager Software
HPCMS 6.0 Service Packs can now be installed on systems that have had previously installed versions of HPCMS 6.0.

PAGE 4 OF 10

2.6.1 Upgrading from HPCMS 5.6 SP1 to HPCMS 6.0 SP1
HPCMS can be installed onto systems that have had the Notification Server (NS) upgraded from previous versions to NS 6.0. There are specific steps that must be done in the correct sequence order for the upgrade to perform properly. Refer to the HP Client Manager Software 6.0 Product Guide for information on upgrading from a previous version of HPCMS 6.0.
2.7 Upgrading from HPCMS 6.0 to HPCMS 6.0 Service Pack 1
In addition to upgrading from a previous version of HPCMS 5.6, HPCMS 6.0 SP1 can be installed to any server with an existing HPCMS 6.0 installation. When upgrading from HPCMS 6.0, HPCMS 6.0 SP1 does not retain certain server policy settings you may have changed before the upgrade occurred. After upgrading, you can reset the server policy settings listed below back to their original values prior to the upgrade, and then re-apply all server policies. Note: It is recommended that you manually record the following server policy settings, which primarily consist of the schedule settings and collections to which these policies apply, before you attempt to upgrade to HPCMS 6.0 SP 1. The following policies are affected by the upgrade from HPCMS 6.0 to HPCMS 6.0 SP1: a. Configuration Tasks/Policies o HP Client Health Monitoring Settings b. HP Client Health Notification Policies o Battery Alerts o Chassis Intrusion Alerts o Chassis Thermal Alerts o CPU Error Alerts o Disk Drive Error Alerts o Memory Module Error Alerts Steps to upgrading to HPCMS 6.0 SP1 a. During the HPCMS installation, by default, the client agent is disabled so that console operators can control when agents are deployed to client computers. During Notification Server installations where the agent rollout has already occurred, the installation task on client computers is disabled. To re-enable the HP Client Manager Agent policy at client computers, go to the HPCMS console on the server, and click the Enable HP Client Manager Software link on the QuickStart page. b. From the Altiris Console, restore any server policy settings (user defined schedules and collections) that have been overwritten by the HPCMS installer during the upgrade. Use the server policy settings written down before the HPCMS upgrade for reference. c. Reset all policy schedules and collections that have been changed after the HPCMS upgrade.

PAGE 5 OF 10

Section 3 Whats New in HPCMS 6.0
3.1 Integration with HP Systems Insight Manager
Through the Altiris Connector for HP Systems Insight Manager (HP SIM), HP SIM users can perform HP Client Manager Software tasks from within the HP SIM console. The SoftPaq delivery and BIOS Administration wizards, inventory, diagnostic reports, and the HPCMS QuickStart console can be accessed from menus in the HP SIM console. Additionally, hardware events from HPCMS notification policies can be forwarded to HP SIM via the SNMP policy action.
3.2 Power management support for HP clients (Wake on LAN)
SoftPaq delivery, BIOS administration, Inventory and Diagnostics policies have an option to Power up the client computer on their configuration pages. If Notification Server is properly configured, this option will cause the power management module to send a Wake-On-LAN packet to applicable systems in the associated collection(s). After each machine wakes up, they will download and execute any pending policies, including the correlating SoftPaq or BIOS administration policy. Configuring Notification Server to enable power management on clients is done via the Altiris Console by editing the Altiris Agent Settings (Configuration > Altiris Agent > Altiris Agent Configuration > All Desktop Computers - Advanced Settings) and selecting the Enable Power Management on Altiris Agents check box. You can now also enable/disable Wake-On-LAN on client computers using the BIOS Administration Wizard.
3.3 Improved health monitoring
Client side system components are monitored at individual intervals defined on the server under Configuration | Solution Settings | Platform Administration | HP Client Management | HP Health Client Monitoring. The monitoring of each component may be turned on or off. Some probe intervals can be adjusted.
3.4 HP supported systems update process has improved
When HP releases new computers, Altiris goes through a series of tests on these systems for compliance and compatibility with HPCMS. Upon successful completion of these tests, the newly supported systems can be supported by HPCMS. The process that HPCMS goes though retrieves the system information correlating to these new systems from the Internet and updates the list of supported systems in HPCMS. This process now shows the list of supported systems and allows users to use downloaded files located on a network or local removable storage instead of only using the Internet to retrieve the updated list.

3.5 HP client auto-discovery
Upon installing HPCMS, the HP computer discovery task is enabled by default and will rollout and execute the HP discovery agent. By enabling the HP agent deployment via the QuickStart or the Altiris console, all HP components can be enabled and deployed. This step has been made simpler and more efficient.
3.6 Built on new Altiris 6.0 core infrastructure

PAGE 6 OF 10

HPCMS 6.0 is built on the new Altiris 6.0 core Notification Infrastructure that provides improved scalability, security, usability, globalization, supportability, and new integration with other Altiris solutions. A new task based user interface groups tasks by function. HPCMS tasks are now located under the Platform Administration folder. HPCMS benefits from a new Altiris Resource Manager (used to be called Resource Explorer) that provides additional functionality including Shortcuts. Shortcuts allow administrators to create their own links to specific Web console pages that are used most often.
3.7 HP Diagnostics installed as a separate package
In version 5.6 SP1, the client agent package included the HP diagnostics package and installed it when the agent was installed. In version 6.0, the diagnostics package is installed separately. This reduces the amount of time it takes to install the client agent making the package smaller and provides more control for installing different diagnostics packages in the future. There is a diagnostics installation task, which applies to a collection that specifies All HP computers without HP diagnostics installed. This will allow diagnostics to be executed on systems which already have HP diagnostics installed.
3.8 HP client agent can be uninstalled from the server
The HPCMS client agent can be uninstalled via a software delivery policy, which can be configured via the Altiris console; by default this task is disabled. When enabling this task, computers that apply to the specified collection will execute the agent uninstaller. This will remove the agent from the client computer and place it into the All Discovered HP Computers with no HP Client Manager Agent collection. This policy should be used to uninstall all agents before uninstalling the HPCMS solution from the server.
3.9 Improved QuickStart Console functionality
From the QuickStart Console, Discovery, Agent Rollout, Inventory, Diagnostics and Health monitoring can be enabled with a few clicks of the mouse. This feature even allows for basic scheduling. The QuickStart page can also be used to deploy SoftPaqs via the SoftPaq delivery wizard and update the BIOS via the BIOS Administration wizard. From the QuickStart page the user can also run Inventory, Diagnostic, Health, and Software Delivery reports. The QuickStart Console can be used to help you get installed and setup quickly, be used as your main access to HPCMS functions, and to help you quickly evaluate the product. The same functions available in the QuickStart can be accessed directly within the Altiris console.

3.10 The SoftPaq delivery wizard operates independently from the Filestore
Updating the Filestore is now done via the configuration section of the Altiris console. The SoftPaq delivery wizard will not create SoftPaq delivery tasks until after the Filestore has been updated.
3.11 The set of HP systems supported by HPCMS has been modified
The following new systems have been added to the supported system list: Notebooks o HP Compaq Business Notebook nc6000 o HP Compaq Business Notebook nc8000 Desktops o HP Compaq Business Desktop dc5000 o HP rp5000

PAGE 7 OF 10

Tablet PC o Compaq Tablet PC TC1100 Workstations o HP Workstation xw4200 o HP Workstation xw6200 o HP Workstation xw8200

Section 4 Known Issues

4.1 Upgrade from HPCMS 5.6 SP1 to 6.0
The NS 5.5 server and clients should be upgraded to NS 6.0 before HPCMS 6.0 is installed. To insure that HPCMS 6.0 performs properly, all NS clients should be upgraded to the Altiris NS 6.0 Agent prior to HPCMS 6.0 being installed. HPCMS 6.0 should not be installed on an NS 5.5 Server because HPCMS 6.0 is not supported under NS 5.5.
4.2 Hot-swapping devices on clients, will not be detected until reboot
On the NS Console, under the Configuration tab, in the tree Solution Settings | Platform Administration | HP Client Management | HP Health Client Monitoring the Health monitor may be configured. The Battery changed, Disk drive changed, and Monitor changed settings are associated with On device changed event. This setting means HPCMS will probe for a device change when it receives a Plug and Play notification from the system. Due to issues where PnP notification does not work properly, these probes only occur Once at boot.
4.3 Swapping batteries of the same capacity may not be detected
The serial numbers of some batteries on some machines cannot be determined. In these cases, the capacity of the batteries is used to differentiate battery changes. If the capacity of such batteries is equal, a device change cannot be determined, and an event will not be sent.
4.4 Swapping memory sticks of the same capacity may not be detected
As with batteries, the serial numbers of some memory sticks on some machines cannot be determined. In these cases, the capacity and speed of the memory is used for differentiation. If the capacity and speed of such memories is equal, a device change cannot be determined, and an event will not be sent.
4.5 Enabling Wake-on-LAN requires configuration of the Altiris Agent Settings

PAGE 8 OF 10

Enabling Wake-On-LAN for HP Client Manager Software SoftPaq delivery, BIOS Administration, Inventory, and Diagnostics requires the user to enable the power management feature on the client. Go to the Altiris Console and configure the Altiris Agent settings, as shown in the graphic below. When HP client computers are updated with the new Altiris Agent settings, they will be correctly configured to recognize and respond to Wake-On-LAN packets.

3.7 figure 1. This page can be accessed via the Configuration tab in the Altiris console by select the Altiris Agent, Altiris Agent Configuration, the by selecting the All Desktop Computers (excluding Package Servers).
4.6 Certain BIOS settings do not take affect until reboot enabling or disabling of Wake-on-LAN doesnt take affect until reboot
It is recommended by HP to reboot your client after you make a BIOS change. For example, on HP systems manufactured after 2002, the enabling or disabling Wake-On-LAN or the Hood Lock will not engage until the client system is rebooted. Therefore, to insure that BIOS changes have been implemented reboot the client after the BIOS package has been installed.
4.7 Multi-Language Support Report Data
For multinational support, the HP Client Manager Client Agent is English only. Information that is reported by the agent is recorded in the HPCMS database in English. Reports showing this information my have the proper language for report names and column headings, but the content (data) in the report will be in English where applicable.

PAGE 9 OF 10

4.8 Systems that do not support BIOS modifications with HP Client Manager Software
The following HP legacy systems were designed such that BIOS changes are not able to be made using HP Client Manager Software. HP Omnibook 510 HP Omnibook 6200 HP Vectra VL400 HP Vectra VL410 HP Vectra VL420 HP VL8i HP e-PC HP Workstations xw8000

PAGE 10 OF 10

Altiris HP Client Manager 6.1 SP1 Release Notes

May 4, 2006 NOTICE

The content in this document represents the current view of Altiris as of the date of publication. Because Altiris responds continually to changing market conditions, this document should not be interpreted as a commitment on the part of Altiris. Altiris cannot guarantee the accuracy of any information presented after the date of publication. 2006 Altiris, Inc. All rights reserved. Altiris, the Altiris logo, BootWorks, Inventory Solution, LabExpert, PC Transplant, RapiDeploy, and RapidInstall are registered trademarks of Altiris, Inc. in the United States. Carbon Copy is a registered trademark licensed to Altiris, Inc. in the United States and a trademark of Altiris, Inc. in other countries. Altiris eXpress, Deployment Server, Deployment Solution, My IT Forum, Notification Server, Vision, Web Reports and other product names are trademarks of Altiris, Inc. in the United States and other countries. All other brand names are trademarks or registered trademarks of their respective companies. Information in this document is subject to change without notice. For the latest documentation, visit our Web site at www.altiris.com.

Release Notes

Altiris HP Client Manager 6.1 SP1

Page 1 of 13

RNT: H

Contents

Overview.... 2 Supported Computers and Platforms.... 3 Installation and Licensing... 6 New Features in this Release... 7 Feature Enhancements in this Release... 9 Known Issues.... 10

1 Overview

1.1 Document Purpose
This document provides the whats new and known issues information for the 6.1 SP1 release of Altiris HP Client Manager.

Background

HP Client Manager (HPCM, formerly known as HP Client Manager Software - HPCMS) is a free hardware management tool for HP client computers. This tool provides in-depth client inventory, driver and utility updating, remote BIOS management, remote Embedded Security management, hardware monitoring, diagnostics, and problem resolution. HP Client Manager integrates with Altiris Client Management Suite, Altiris HP OpenView, Altiris HP Systems Insight Manager, and Microsoft Systems Management Server (SMS).

Documentation

Product documentation for version 6.1 SP1 is available in the HP Client Manager Product Guide (HPCM.pdf and HPCM.chm). To view Altiris product documentation in.PDF format, use Adobe Acrobat Reader (available at: http://www.adobe.com/products/acrobat/readstep2.html).

Page 2 of 13

HP Client Manager 6.1 SP1
2 Supported Computers and Platforms
2.1 Supported HP Computers
The following table lists the HP commercial computers that are tested and supported by HP Client Manager 6.1 SP1. Additionally, the computers must be running one of the supported operating systems. For more information, see Supported Operating Systems. Desktops Compaq Evo D330 Compaq Evo D530 Compaq Evo D300 Compaq Evo D500 Compaq Evo D300 Small Form Factor Compaq Evo D500 Slim Tower Compaq Evo D310 Small Form Factor Compaq Evo D510 Small Form Factor Compaq Evo D310v Compaq Business Desktop D315 Compaq Evo D320 Compaq Business Desktop D325 Slim Tower Compaq Business Desktop D325 Microtower HP Compaq Business Desktop dx6050 Microtower Compaq Evo D500 Ultra-slim Desktop Compaq Evo D500 Small Form Factor Compaq Evo D500 Ultra-slim Desktop Compaq Evo D510 Ultra-slim Desktop Compaq Evo D510 Small Form Factor Compaq Evo D510 e-pc Compaq D530 Ultra-slim Desktop HP Compaq dc5000 HP Compaq dc5100 Microtower PC HP Compaq dc5100 Small Form Factor PC HP Compaq dc7100 Ultra-slim Desktop HP Compaq dc7100 Convertable Minitower HP Compaq dc7100 Small Form Factor HP Compaq dx6100 Slim Tower HP Compaq dc7600 Ultra-slim Desktop Supports Embedded Security No Yes No No No No No No No No No No No No No No No No No No Yes No No No Yes Yes Yes No Yes

Page 3 of 13

HP Compaq dc7600 Small Form Factor HP Compaq dc7608 Small Form Factor HP Compaq dx7200 Slim Tower Business PC HP Compaq dx7208 Slim Tower PC HP Compaq dc7600 HP Compaq dc7608 Convertible Minitower HP Compaq dx5150 Microtower PC /Slim Tower/Small Form Factor HP Compaq dx6100 Microtower HP Compaq dx6120 Microtower HP Compaq dx6120 Slim Tower HP Compaq rp5000 HP e-PC HP Compaq dx7200/dx7208 Micro Tower Business PC Workstations HP workstation xw4000 HP Workstation xw4100 HP Workstation xw4200 HP Workstation xw4300 HP Workstation xw5000 HP Workstation xw6000 HP Workstation xw6200 HP workstation xw8000 HP Workstation xw8200 HP Workstation xw9300 HP Compaq Workstation w6000 Notebooks and Tablet PCs Compaq Evo N610c Compaq Evo N620c Compaq Evo N800v/N800c Compaq Evo N1000 HP Compaq Business Notebook nc4000/nc4010 HP Compaq nc4200 Notebook PC HP Compaq Business Notebook nx5000 HP Compaq Business Notebook nc6000 HP Compaq nc6220 Notebook PC HP Compaq nc6230 Notebook PC
Yes Yes Yes Yes Yes Yes No No No No No No Yes Supports Embedded Security No No Yes Yes No No No No No No No Supports Embedded Security No No No No Yes Yes No Yes Yes Yes

Page 4 of 13

HP Compaq Business Notebook nc8000 HP Compaq nc8220 Notebook PC/HP Compaq nc8230 Notebook PC HP Compaq nc6120 Notebook PC HP Compaq Nx6120/nc6140/nc6110 Notebook PC HP Compaq Mobile Workstation NW8000 HP Compaq Mobile Workstation nw8240 Compaq Tablet PC TC1000 Compaq Tablet PC TC1100
Yes No No No Yes Yes No No
Note: Newer models not listed are probably supported.
Supported Operating Systems
Windows XP Professional Windows 2000 Professional Windows XP Tablet Edition Windows XP Professional x64 Edition *
*x64 systems do not support Diagnostics, System Health Scan, and Management of Embedded Security.
Discontinued HP Computer Support
Desktops Compaq Deskpro EN, EX/EXS Series Compaq iPAQ Desktop Workstations Deskpro Workstation AP 250 Deskpro Workstation AP 300 Professional Workstation AP200 Professional Workstation AP400 Professional Workstation AP550 Professional Workstation SP700 Professional Workstation SP750 Evo Workstation W4000 Notebooks and Tablet PCs Compaq Evo N800w Compaq Evo N1005 Compaq Evo N1020 Compaq Evo n400c/410c Compaq Evo n600c Compaq Armada M300 Family Compaq Armada M700 Family HP Omnibook 6100 HP Omnibook XE4000 HP Omnibook XE-GF Evo Workstation W6000 Evo Workstation W8000 HP Workstation x1000 HP Workstation x1100 HP Workstation x2000 HP Workstation x2100 HP Workstation x4000

Page 5 of 13

Note: Systems supported in previous versions of HPCM and are not listed in current version of Supported HP system list are probably retired in the current version.
List of computers that require BIOS upgrade to become HPCM Embedded Security Manageable
The following models are currently not manageable by HPCM due to partial support for remote management of Embedded Security [TPM]: nw9440 nc8430 nw8440 nc6320 nc6400 nc4400 tc4400 nc2400
These notebook PCs require an upgrade to the system BIOS to fully support remote management of Embedded Security chip [TPM]. Until the BIOS upgrades are available, these systems will be unsupported by HP Client Manager. It is expected that the BIOS updates will be available for these systems in the summer of 2006. When available, the BIOS upgrades can be automatically deployed to these systems, thus enabling them to fully support remote management of Embedded Security.
3 Installation and Licensing
Installation and licensing information is provided in the HPCM documentation, the Readme Quick Install.PDF file (included in the solution.ZIP file downloaded from the Altiris Web site), the Altiris Getting Started Guide, and the Altiris Notification Server Reference Guide.
Upgrading to HPCM 6.1 SP1
If you currently have HPCM 6.1 installed, we recommend upgrading to HPCM 6.1 SP1 rather than uninstalling HPCM 6.1 and then installing HPCM 6.1 SP1. If you uninstall HPCM 6.1, your existing data and custom packages, collections, and so forth will be lost. To upgrade from HPCM 6.1 to HPCM 6.1 SP1, simply install HPCM 6.1 SP1 over the existing HPCM 6.1. Important: While upgrading to HPCM 6.1 SP1, you should not have any HPCM 6.1 tasks running or scheduled to run. Disable all events that are scheduled to run ASAP or during the next hour or so until the upgrade completes. If the HPCM 6.1 server or HPCM 6.1 clients are in the process of executing a task, the upgrade to HPCM 6.1 SP1 may not complete successfully.
3.1.1 Upgrade Recommendations
3.1.2 Notification Policies
During an upgrade from HPCM 6.0 or 6.1 to HPCM 6.1 SP1, any modified Notification Policy actions that are part of the standard set of installed Notification Policies and their settings are not upgraded. Any customer created Notification Policies are saved. However, due to changes in the way HPCM detects health of client computers, custom Notification Policies that were created in HPCM 6.0 or 6.1 may not be applicable in HPCM 6.1 SP1. You will have to re-create these policies in HPCM 6.1 SP1.

Page 6 of 13

3.1.3 Collections
All collections are retained during the upgrade from HPCM 6.0 or 6.1 to HPCM 6.1 SP1. However, during an upgrade from HPCM 6.1 to HPCM 6.1 SP1, any collection that uses NT 4.0 or Windows 98 is not valid in 6.1 SP1 because NT 4.0 and Windows 98 are not supported. HPCM installations that upgrade to HPCM 6.1 SP1 may retain the collection, Windows 2000 Servers. This collection should not be used in HPCM 6.1 SP1 for client systems because it is not a client OS. Windows 2000 Server is a supported OS for the Notification Server.

3.1.4 Custom Reports

During an upgrade from HPCM 6.0 to 6.1 SP1, or from HPCM 6.1 to 6.1 SP1, custom reports may not be retained. If you want to retain custom reports, we recommend exporting the reports to a safe location and then importing them after the upgrade. However, because the inventory and diagnostics tables change after the upgrade, the reports will not contain updated historical data.
3.1.5 SoftPaq and BIOS Administration Policies/Packages
Existing SoftPaq policies/packages and BIOS administration policies/packages created in HPCM 6.0 are retained in HPCM 6.1 SP1. However, both the policies and the packages are listed under the respective Tasks folder. For example, a SoftPaq policy/package created in HPCM 6.0 is retained in HPCM 6.1 SP1, but it is listed under HP SoftPaq Delivery\HP SoftPaq Delivery Tasks folder. In HPCM 6.1 SP1 all new SoftPaq and BIOS changes have their respective policies and tasks displayed in separate folders.
3.1.6 Health Monitoring Settings
During an upgrade from HPCM 6.0 or 6.1 to HPCM 6.1 SP1, health monitoring settings retain only the global enable/disable setting. Individual selections of enable/disable for specific hardware items are not retained due to changes in Health monitoring in 6.1 SP1.
3.1.7 Non-default HP SoftPaq Filestore Path must be reconfigured
The HP SoftPaq Filestore has the following default path: C:\Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\HPCMS\Filestore If you are using a non-default path, you must reconfigure your custom path after you perform the upgrade. For information on how to configure the HP SoftPaq Filestore path, refer to the HPCM Product Guide.
3.1.8 Issues when upgrading from HPCMS 5.6 SP1 to HPCM 6.1 SP1
Notification Server 5.5 should be upgraded to Notification Server 6.0 SP3 before you install HPCM 6.1 SP1. To ensure that HPCM 6.1 SP1 works properly, all Notification Server clients should be upgraded to the Notification Server 6.0 SP3 Altiris Agent prior to HPCM 6.0 being installed. HPCM 6.1 SP1 should not be installed on Notification Server 5.5 because HPCM is not supported on Notification Server 5.5.
4 New Features in this Release
4.1 Manage Embedded Security
HPCM 6.1 SP1 provides various features to manage Embedded Security on client computers. These include archiving the Embedded Security credentials and settings, and managing the state of Embedded Security. These features are provided with the help of HP Embedded Security Tasks and an Embedded Security Wizard.

Note: Before using the Embedded Security (TPM) features in HPCM, we recommend that you
read the HP ProtectTools Security Manager Guide to gain an understanding of how Embedded

Page 7 of 13

Security works. This guide can be found on the HP Web site for each model: http://www.hp.com/. The following tasks are provided with the Embedded Security feature:
4.1.1 Initialization of Embedded Security
HP Client Manager lets an administrator initialize Embedded Security for the client computer, which can further be managed with the help of the HP Client Manager Agent. This feature initializes the Embedded Security by enabling and taking ownership of the TPM (Trusted Platform Module) chipset. The TPM chipset is the device that enables the usage of Embedded Security features on client computers.
4.1.2 Modify Embedded Security Owner password
This feature helps an administrator modify an Embedded Security Owner password.
4.1.3 Create Password Reset Token file [Manage Security User passwords]
This feature lets an administrator create password reset token information, which is further used to generate a password reset secret code.
4.1.4 Reset Security User Password [Manage Security User passwords]
This feature lets an administrator generate a password reset secret code for a client computer. This code is used to reset the Embedded Security password of a user on the client computer.
4.1.5 Archive Embedded Security
This feature helps an administrator archive Embedded Security credentials and settings. In case of a disaster, the administrator can use this archive to restore the Embedded Security credentials and settings on the client computer.
4.1.6 Restore Embedded Security
This feature lets the administrator restore Embedded Security credentials and settings.
4.1.7 Embedded Security Wizard
This feature helps an administrator create Embedded Security related policies using the wizard.

Page 8 of 13

5 Feature Enhancements in this Release
5.1 Improved Serial and Parallel port data
HPCM now provides additional data about Serial and Parallel ports, which includes information on Interrupt, DMA channel, connector type, and port type.
Information related to PCI slots
HPCM provides information about PCI slots, which includes information on Slot Designation, Current Usage, and Maximum Data Width.

Information related to Memory slots
HPCM now provides information about Memory slots, which includes the total number of memory slots present and number of used memory slots.

Improved Disk Drive data

HPCM now provides additional data about disk drives, which includes the Serial number, Version, and Manufacturer of the disk drive.

Improved battery data

HPCM now provides detailed information related to columns already present in the battery information. The following descriptive information is provided: Availability, BatteryStatus, Chemistry, DesignCapacity, and DesignVoltage.

Improved monitor data

HPCM now provides additional data about monitors including the monitor serial number.

Page 9 of 13

6 Known Issues
6.1 Hot-swapping devices on clients are not detected until restart
You can configure the Health monitor on the Altiris Console by clicking the Configuration tab, and, in the left pane, selecting Solution Settings > Platform Administration > HP Client Management > HP Health Client Monitoring. The Battery changed, Disk drive changed, and Monitor changed settings are associated with On device changed event. This setting implies that HPCM will probe for a device change when it receives a Plug and Play (PnP) notification from the system. Due to issues where a Plug and Play notification does not work properly, these probes only occur Once at boot.
Swapping batteries of the same capacity may not be detected
The serial numbers of some batteries on some computers cannot be determined. In such cases, the capacity of the batteries differentiates between battery changes. If the capacities of such batteries are equal, a device change cannot be determined, and an event is not sent.
Swapping memory sticks of the same capacity may not be detected
The serial numbers of some memory sticks on some computers cannot be determined. In such cases, the capacity and speed of the memory sticks are used for differentiation. If the capacity and speed are equal, a device change cannot be determined, and an event will not be sent.

Enabling Wake on LAN requires configuration of the Altiris Agent Settings
To enable Wake on LAN for HP Client Manager SoftPaq delivery, BIOS Administration, Inventory, and Diagnostics, the user must enable the power management feature on the client computer. To enable power management,
1. 2. 3. 4. 5. 6. From the Altiris Console, click the Configuration tab. In the left pane, select Configuration > Altiris Agent > Altiris Agent Configuration. Click All Desktop Computers (excluding Package Servers). Click the Advanced Settings tab. Select the Enable power management on Altiris Agent checkbox. Click Apply.
When HP client computers are updated with the new Altiris Agent settings, they will be correctly configured to recognize and respond to Wake on LAN packets.
Certain BIOS settings do not take affect until a restart is enabled
HP recommends restarting your client computer after you make a BIOS change. For example, on HP computers manufactured after 2002, the enabling or disabling Wake on LAN or the Hood Lock will not engage until the client computer is restarted. Therefore, to ensure that BIOS changes have been implemented, restart the client after the BIOS package has been installed.

Page 10 of 13

Multi-Language Support Report Data
The HP Client Manager Agent does not support regional languages. Information reported by the agent is in English and it is saved in the same language in the HPCM database. Reports showing this information may have names and column headings in regional languages, but content (data) in the report is always displayed in English.
Computers that do not support BIOS modifications
The following HP legacy computers were designed such that BIOS changes cannot be made using HP Client Manager.
HP e-PC HP Workstations xw5000 HP Workstations xw8000 HP Compaq dx5150 (to a limited extent) Compaq Tablet PC tc1000 series Compaq Tablet PC tc1100 series
HP Instant support diagnostic tools limitations
HP Instant Support diagnostic tools do not currently support client computers running Windows XP Embedded or XP Professional x64.
Limited Support for Windows XP Professional x64
HPCM 6.1 SP1 includes SSM 2.0, which supports driver updates under Windows XP Professional x64 as well as BIOS flashing, BIOS changes, and driver installation.
6.10 Task Limitations for Windows XP64 computers
Windows XP64 bit computers do not support the following tasks: HP Instant Support Diagnostics and HP Instant Support System Health Scan. Presently, these tasks are only supported under Windows 32bit Operating Systems.

6.11 Inventory Limitations for Windows XP64 computers
The inventory of BIOS settings on a system running Windows XP64 requires the system to have HP Client Management Interface native in the BIOS. BIOS Inventory items are not available on systems running WinXP64 without the HP Client Management Interface native in the BIOS (for example, HP dx5150 desktop). Systems running Windows XP32 will be able to gather the inventory of BIOS settings with or with out the HP Client Manager Interface native in the ROM.
6.12 Embedded Security (TPM) and XP64 bit systems
Embedded Security (TPM) is not supported on Windows XP64 bit systems. Therefore, if any TPM related task is executed on Windows XP64 platform, it will fail. When TPM is supported on Windows XP64 bit systems in the future, the administrator will be able to remotely manage those systems since those systems will automatically become a TPM supported platform.
6.13 Battery Level Threshold reporting below -1 percent
The following alert means that the battery is reporting odd or irregular data: HP Client Manager has detected that your battery level threshold is below -1 percent.

Page 11 of 13

6.14 Reject Initialization
On certain notebooks (for example, nc6220), the Embedded Security option to allow users to reject initialization does not work. A future update to the ROM BIOS will correct this issue.
6.15 TPM Feature Limitations
On the HP d330 and HP dc7100 desktops with Embedded Security (TPM) version 1.1b, the following Embedded Security features are not supported: a) Manage security User passwords and b) Manage security credentials and Settings: Archive and Restore. However, with the same version of TPM, the above listed features are supported on notebooks such as the nc6220.

6.16 Inventory and WMI

Computer inventory along with Embedded Security related inventory may not work properly if there is problem in the WMI service of the operating system. Try rebooting the client.

Hidden TPM

HPCM inventory will not gather TPM inventory if the TPM chip is set to hidden in the BIOS.
6.18 HPCM QuickStart Availability
In some cases, the installed HPCM settings may take time to be reflected in the Notification Server. As a result, the HPCM QuickStart page may not automatically open properly immediately after installation for about one minute. For this reason, the HPCM QuickStart page can be accessed through the Start menu by clicking Start > Programs > Altiris > Quick Starts > HP Client Manager. There is also an HPCM QuickStart shortcut available on the Desktop.

6.19 Monitor Change Alerts
On some systems, due to unsynchronized information received from the operating system for a connected monitor, phantom monitor change alerts can be displayed. These alerts can also happen due to an improper serial number gathered for a monitor.
6.20 Failed SoftPaq Downloads
If System Health Scan encounters a problem downloading SoftPaqs from HP, it can cause HPCM to think that all SoftPaqs were downloaded successfully. This can cause empty SoftPaq packages to be created. If you encounter failed downloads via System Health Scan, download the desired SoftPaqs from www.hp.com/suppport and manually place them into the Filestore directory (not in a subdirectory within the Filestore.) Rebuild the Filestore and then use the SoftPaq wizard to deploy the SoftPaqs. Use the Notification Server error log to confirm if SoftPaqs were downloaded successfully. Then view the Notification Server (NS) error log using the following steps: a) click on the Configuration tab in the NS Console page b)Expand Server Settings \ Notification Server Settings c) click on Error Logging d) click on the View Status Messages button to view the NS error log.
6.21 SoftPaq File Locations
The SoftPaq Wizard cannot handle SoftPaqs that are located in subdirectories under the main Filestore directory. The download directory is used only by System Health Scan. It is recommended that you do not manually place any SoftPaqs into this download directory.

Page 12 of 13

6.22 Duplicate SoftPaqs
Before downloading a SoftPaq through a System Health Scan, confirm that you do not already have the SoftPaq in your Filestore. Duplicate SoftPaqs can cause a SQL error when updating the Filestore.

6.23 Mouse Response

Microsoft recently changed the operation of their ActiveX controls which may result in some HPCM pages requiring two mouse clicks before a pointer changes. This will be addressed by a future update of Notification Server.
6.24 Incorrectly Formatted Information
On some systems (i.e. HP dc7200 desktop and HP dc7600 desktop), due to problems with BIOS, incorrectly formatted information is gathered and reported to the Notification Server This can also affect the information displayed through the HP BIOS Advanced Administrator wizard, HP Tool Update Wizard and HP BIOS Report. A new ROM BIOS from HP as well as an Advanced BIOS Wizard cleaning utility will be released to address this issue.
6.25 Incorrect Reported Disk Size
In the resource manager, the reported disk size is not reported correctly through WMI (HPCMS_WMI_Win32_DiskDrive). The correct size for hard disk is located in HPCMS_WMI_Win32_LogicalDisk.
6.26 Disk Drive Threshold Alerts Description Error
In the Health Alert Policy, Disk Drive Threshold Alerts, the description provided for Send EMail incorrectly states the alert is for a memory module alert.

6.27 Windows 2000 Servers Collection Usage
HPCM installations that upgrade to HPCM 6.1 SP1 may retain the collection, Windows 2000 Servers. This collection should not be used in HPCM 6.1 SP1 for client systems because it is not a client OS. Windows 2000 Server is a supported OS for the Notification Server.
6.28 Wake-on-Lan Scheduling Limitations
In some environments, due to limitations of Notification Server, the WOL option of schedule is not working as expected. Ensure you have at least two clients per subnet for WOL proxies to work.
6.29 HP BIOS Report Wizard
The HP BIOS Report Wizard does not work properly if you create a report that joins multiple selections using OR. The use of AND to join works properly.
6.30 Anti-virus Agents and Java Scripts
HP Insight Manager System Health Scan executes java scripts. If you have virus detection software that is blocking java scripts from executing you will need to allow the following java scripts the ability to execute: defrag.js (executes to see if the client needs to be defragged) parasite.js (executes to see if spyware is loaded on the client).

Page 13 of 13