Altiris® HP Client Manager 6.2 Release Notes
|Article:DOC1193|||||Created: 2006-08-22|||||Updated: 2008-06-24|||||Article URL http://www.symantec.com/docs/DOC1193|
What do I need to know about Altiris® HP Client Manager 6.2?
Altiris® HP Client Manager™ 6.2
HP Client Manager 6.2 is a Web-based application specifically designed for HP computers to leverage HP's manageability technology. HPCM offers greater capabilities and enhanced features , such as client inventory, driver and utility updating, remote BIOS management, remote Embedded Security management, hardware monitoring, diagnostics, and problem resolution to efficiently manage HP and Compaq desktops, workstations, and notebook computers. For a complete list of supported computers, see Supported HP Computers.
HP Client Manager now supports computers using Intel* vPro Technology (Intel* AMT). HP Client Manager 6.2 includes Altiris Out of Band Management Solution that you can use to perform discovery, hardware inventory, power management, alerting, and other configuration tasks on HP computers vPro systems, all independently of system power and OS state. HPCM 6.2 includes full reporting of AMT capabilities for HP systems.
For additional support of Intel* vPro Technology, you can purchase Altiris Real-Time System Manager. This solution allows administrators and help desk technicians to manage remote computers real-time using Intel* Active Management Technology (Intel* AMT), Alert Standard Format (ASF), and Windows Management Instrumentation (WMI) technologies through a Web browser. It provides detailed real-time information about the health and status of a remote computer, and allows those with appropriate permissions to perform administrative tasks such as BIOS configuration, remote diagnostics and repair using Serial over Lan (SOL) and IDE-Re-direct, rebooting the computer, resetting a password, running a traceroute, performing a port check, event logging, and more.Supported Operating Systems.
|Desktops||Supports Embedded Security|
|Compaq Evo D330||Yes|
|Compaq Evo D530||Yes|
|Compaq Evo D320||No|
|Compaq Business Desktop D325 Slim Tower||No|
|Compaq Business Desktop D325 Microtower||No|
|HP Compaq Business Desktop dx6050 Microtower||No|
|Compaq D530 Ultra-slim Desktop||Yes|
|HP Compaq dc5000||No|
|HP Compaq dc5100 Microtower PC||No|
|HP Compaq dc5100 Small Form Factor PC||No|
|HP Compaq dc5700 Small Form Factor PC||No|
|HP Compaq dc5700 Microtower PC||No|
|HP dc5750 Small Form Factor PC||Yes|
|HP dc5750 Microtower PC||Yes|
|HP Compaq dc7100 Ultra-slim Desktop||Yes|
|HP Compaq dc7100 Convertible Minitower||Yes|
|HP Compaq dc7100 Small Form Factor||Yes|
|HP Compaq dx6100 Slim Tower||Yes|
|HP Compaq dc7600 Ultra-slim Desktop||Yes|
|HP Compaq dc7600 Small Form Factor||Yes|
|HP Compaq dc7600 Convertible Minitower||Yes|
|HP Compaq dc7608 Small Form Factor||Yes|
|HP Compaq dx7200 Slim Tower Business PC||Yes|
|HP Compaq dx7200 Microtower Business PC||No|
|HP Compaq dx7208 Slim Tower PC||Yes|
|HP Compaq dx7208 Microtower Business PC||No|
|HP Compaq dx7300 Microtower PC||No|
|HP Compaq dx7300 Slim Tower PC||Yes|
|HP Compaq dc7608 Convertible Minitower||Yes|
|HP Compaq dc7700 Convertible Minitower PC||Yes|
|HP Compaq dc7700 Small Form Factor PC||Yes|
|HP Compaq dc7700 Ultra-slim Desktop PC||Yes|
|HP Compaq dx5150 Microtower PC/Slim Tower/Small Form Factor
Note: This computer has limited management capabilities.
|HP Compaq dx6100 Microtower||No|
|HP Compaq dx6120 Microtower||No|
|HP Compaq dx6120 Slim Tower||No|
|HP Compaq rp5000||No|
|HP Compaq dx7200 Micro Tower Business PC||No|
|Workstations||Supports Embedded Security|
|HP Workstation xw3100||Yes|
|HP Workstation xw4100||No|
|HP Workstation xw4200||Yes|
|HP Workstation xw4300||Yes|
|HP Workstation xw4400||No|
|HP Workstation xw6000||No|
|HP Workstation xw6200||No|
|HP Workstation xw6400||No|
|HP Workstation xw8000||No|
|HP Workstation xw8200||No|
|HP Workstation xw8400||No|
|HP Workstation xw9300||No|
|HP Workstation xw9400||Yes|
|HP Compaq Workstation w6000||No|
|Notebooks and Tablet Computers||Supports Embedded Security|
|Compaq Evo N610c||No|
|Compaq Evo N620c||No|
|Compaq Evo N800v/N800c||No|
|Compaq Evo N1000||No|
|HP Compaq Business Notebook nc4000/nc4010||Yes|
|HP Compaq nc4200 Notebook PC||Yes|
|HP Compaq tc4200 Tablet PC||Yes|
|HP Compaq Business Notebook nx5000||No|
|HP Compaq Business Notebook nc6000||Yes|
|HP Compaq nc6220 Notebook PC||Yes|
|HP Compaq nc6230 Notebook PC||Yes|
|HP Compaq Business Notebook nc8000||Yes|
|HP Compaq nc8220 Notebook PC/HP Compaq nc8230 Notebook PC||No|
|HP Compaq nx8220/nw8240 Notebook PC||Yes|
|HP Compaq nc6120 Notebook PC||No|
|HP Compaq nx6120/nc6140/nc6110 Notebook PC||No|
|HP Compaq Mobile Workstation nw8000||Yes|
|HP Compaq Mobile Workstation nw8240||Yes|
|Compaq Tablet PC tc1000||No|
|Compaq Tablet PC tc1100||No|
|HP Compaq nx9420/nw9440 Notebook PC||Yes|
|HP Compaq nc8430/nw8440/n8420 Notebook PC||Yes|
|HP Compaq nc6320/nx6320/nx6310 Notebook PC||Yes|
|HP Compaq nc6400 Notebook PC||Yes|
|HP Compaq nc4400 Notebook PC||Yes|
|HP Compaq tc4400 Tablet PC||Yes|
|HP Compaq nc2400 Notebook PC||Yes|
|HP Compaq nx6315/nx6325 Notebook PC||No|
- Windows 2000 Professional, SP3, SP4
- Windows XP Tablet Edition
- Windows XP Embedded
- Windows XP Professional, SP2
- Windows XP Professional x64 Edition
- Vista Business x32 and x64
- Vista Enterprise x32 and x64
|Compaq Deskpro EN Series (Manufactured prior to 2001)|
|Compaq iPAQ Desktop (Manufactured prior to 2001)|
|Compaq D300 Small Form Factor|
|Compaq D500 Small Form Factor|
|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 D500 Ultra-slim Desktop|
|Compaq Evo D500 Small Form Factor|
|Compaq Evo D510 Ultra-slim Desktop|
|Compaq Evo D510 Small Form Factor|
|Compaq Evo D510 e-PC|
|Deskpro Workstation AP250|
|Deskpro Workstation AP300|
|Professional Workstation AP200|
|Professional Workstation AP400|
|Professional Workstation AP550|
|Professional Workstation SP700|
|Professional Workstation SP750|
|Evo Workstation W4000|
|HP Workstation xw5000|
|Evo Workstation W6000|
|Evo Workstation W8000|
|HP Workstation x1000|
|HP Workstation x1100|
|HP Workstation x2000|
|HP Workstation x2100|
|HP Workstation x4000|
|HP Workstation xw4000|
|Notebooks and Tablet Computers|
|Compaq Evo N800w|
|Compaq Evo N1005|
|Compaq Evo N1020|
|Compaq Armada M300 Family|
|Compaq Armada M700 Family|
|HP Omnibook 6100|
|HP Omnibook XE4000|
|HP Omnibook XE-GF|
System RequirementsThe following information provides the system requirements for installing Notification Server and HP Client Manager on a server and setting up the Altiris Agent on managed client computers.
Operating System: Windows Server 2003, or Windows 2000 Server, Windows 2000 Advanced Server with SP2 or later
Processor: Pentium III 800 MHz or faster
RAM: 512 MB, 1 GB recommended for increased speed in large environments
Hard Drive: 20 GB (recommended), 105 MB for Notification Server and components (disk space), 1 GB for SQL Server database
File System: NTFS partition
Client Requirements The following information provides the client requirements for the client computer running the Altiris Agent.
- Operating System: Windows 2000 or later
- Disk space on client: 5 MB disk space for Altiris Agent, and the space to install required software
- RAM: 64 MB
- Browser: Microsoft Internet Explorer 4 or later
Note: Unblock ports 80 and 445 if the operating system is Windows XP SP2 with firewall enabled. These ports can be blocked after installation. You can also create an exception for the Altiris Agent in the Windows Firewall dialog. If the Altiris Agent is installed successfully on the client computer, HPCM functions properly.
Installation and Upgrade
Complete installation instructions are contained in the HP Client Manager Product Guide.
Note: If HP Client Manager 6.1 SP1 is currently installed, we recommend upgrading to HP Client Manager 6.2 rather than uninstalling HP Client Manager 6.1 SP1 and then installing HP Client Manager 6.2.
Caution: If HP Client Manager 6.1 SP1 is uninstalled, the existing data and custom packages, collections, and so on, are lost.
To upgrade from HP Client Manager 6.1 SP1 to 6.2
Tip: While upgrading to HP Client Manager 6.2:
- Verify that any HP Client Manager 6.1 SP1 tasks are not running or are not scheduled to run.
- Disable all events that are scheduled to run immediately or during the next hour or so until the upgrade completes.
Note: If the HP Client Manager 6.1 SP1 server or client computers are in the process of executing a task, the upgrade to HP Client Manager 6.2 may not complete successfully.
|1. Notification Policies|
During an upgrade from HP Client Manager 6.1 or 6.1 SP1 to HP Client Manager 6.2, any modified Notification Policy actions that are a 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 the health of client computers, custom notification policies that were created in HP Client Manager 6.1 may not be applicable in HP Client Manager 6.2. You must re-create these policies in HP Client Manager 6.2.
During an upgrade from HP Client Manager 6.1 or 6.1 SP1 to HP Client Manager 6.2, any collection that uses NT 4.0 or Windows 98 is not valid in 6.2 because NT 4.0 and Windows 98 are not supported in HP Client Manager 6.2. Apart from this, all collections are retained during the upgrade.
HP Client Manager installations that upgrade to HP Client Manager 6.2 retain the Windows 2000 Servers collection. Do not use this collection in HPCM 6.2 for client systems because it is not a client operating system. Windows 2000 Server is a supported operating system for the Notification Server.
|3. Custom Reports|
During an upgrade from HP Client Manager 6.1 or 6.1 SP1 to HP Client Manager 6.2, custom reports may not be retained. 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 do not contain updated historical data.
|4. Softpaq and BIOS Administration Policies and Packages|
Existing SoftPaq policies and packages and BIOS administration policies and packages created in HP Client Manager 6.1 are retained in HP Client Manager 6.2. However, both the policies and the packages are listed under the respective Tasks folder. For example, a SoftPaq policy and package created in HPCM 6.1 is retained in HPCM 6.2, but it is listed under HP SoftPaq Delivery\HP SoftPaq Delivery Tasks folder. In HP Client Manager 6.2 all new SoftPaq and BIOS changes have their respective policies and tasks displayed in separate folders.
|5. Health Monitoring Settings|
During an upgrade from HP Client Manager 6. 1 or 6.1 SP1 to HP Client Manager 6.2, health monitoring settings retain only the global enable and disable setting. Individual selections of enable and disable for specific hardware items are not retained due to changes in health monitoring in 6.2.
6. Non-default HP Softpaq Filestore Path must be reconfigured
A custom path to the Filestore is not supported. For information on how to configure the HP SoftPaq Filestore path, see the HPCM Product Guide at InstallPath\Altiris\Notification Server\NSCap\Help.
7. Clicking on the HP Backup and Recovery QuickStart link launches the Altiris 6.0 console
On the HP Client Manager 6.2 QuickStart page, you can click the HP Backup and Recovery link to launch the Altiris Notification Server console and view the newly-created Backup and Recovery policy. This link will only open the Altiris 6.0 Console and not the 6.5 Console, even if it is installed.
8. The Altiris Notification Server 6.5 console must be installed to use Out of Band Management Solution
To use the Out of Band Management Solution (OOB) in HP Client Manager 6.2, you must use the Altiris Notification Server 6.5 console. The Out of Band Management Solution does not work with the Notification Server 6.0 console. The 6.5 Console is installed with Out of Band Management Solution. For more information, see the Out of Band Management Solution documentation.
Improvements for this release include the following new features:
|1. Latest version of SSM is available on the Altiris Web site
The latest version of SSM (2.0 D 10) is provided with the latest build of HP Client Manager and is also available on the Altiris Web site. The HPToolUpdate wizard downloads the current version of SSM from the Altiris Web site.
|2. Execution of Policies works on some 64-bit computers
The execution of the HP Instant Support Diagnostics and HP Instant Support System Health Scan policies now works on 64-bit computers. The default collections of the policies are no longer changed.
|3. HPCM supports Embedded Security (TPM) on Vista 64-based systems
HPCM now supports Embedded Security (TPM) on Vista 64-based systems.
|4. SoftPaqs do not disappear from the "Softpaqs pending download list"
While downloading Softpaqs through the "HP Instant Support System Health Scan Softpaq Downloads" option, even if the Softpaq fails to download, it no longer disappears from the "Softpaqs pending download list." This results in a complete success of the download process and no error during the Update Filestore process. Try downloading the Softpaq again.
|1. Hot-swapping devices on client computers are not detected until restart|
To configure the Health monitor on the Altiris Console, click the Configuration tab and, in the left pane, select 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 HP Client Manager probes 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 occur only "Once at boot."
|2. 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 the batteries are equal, a device change cannot be determined, and an event is not sent.
|3. 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.
|4. 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
When HP client computers are updated with the new Altiris Agent settings, they are correctly configured to recognize and respond to Wake on LAN packets.
|5. Certain BIOS settings do not take effect until a restart is enabled|
HP recommends restarting the client computer after making a BIOS change. For example, on HP computers manufactured after 2002, the enabling or disabling Wake on LAN or the Hood Lock does not engage until the client computer is restarted. Therefore, to ensure that BIOS changes have been implemented, restart the client computer after the BIOS package has been installed.
|6. 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.
|7. Computers that do not support BIOS modifications|
The following HP legacy computers were designed in such a way that BIOS changes cannot be made using HP Client Manager.
|8. Battery Level Threshold reporting below -1 percent|
The following alert notifies that the battery is reporting odd or irregular data: HP Client Manager has detected that your battery level threshold is below -1 percent.
9. Making changes in the Softpaq Delivery Wizard
|10. Managed HP Computers by Type (Count) report displays incorrect data|
The Managed Computers by Type (Count) report may show a different number of computers in the bar graph and the drilldown on the graph. This usually happens when computers are discovered multiple times. If you drill down, the correct number is displayed. For example, the bar graph may display 500 desktops, but the drilldown displays 250, which is correct.
|11. Battery Serial Number|
Due to a limitation of the manufacturing process, HPCM 6.2 returns the battery tracking number and not the serial number. These numbers are not unique among batteries.
|12. Initiating Embedded Security|
In some cases, SSM.exe, which is used by the HPCM agent to enable Embedded Security, does not work properly with some systems. Therefore, the HPCM agent may not be able to enable the Embedded Security in BIOS. Due to this, the "Initialization of Embedded Security" task does not function properly.
It is for the same reason that the "Allow user to reject initialization" task does not function properly. In some ROM BIOS, the "Allow user to reject initialization" property is not supported. Hence, the user is not prompted to reject the initialization.
|13. WMI service|
Computer inventory and Embedded Security related inventory may not work properly if there is a problem with the WMI service of the operating system. Try restarting the client computer.
|14. HPCM Inventory|
HPCM inventory will not gather TPM inventory if the TPM chipset is set to "hidden" in the BIOS.
|15. HPCM QuickStart|
You can access the HPCM QuickStart page in one of the following ways:
Immediately after the installation of HPCM, please allow up to 1 minute for HPCM settings to take effect prior to using the HPCM QuickStart page.
|16. Phantom 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 occur due to an improper serial number gathered for the monitor.
17. Limitation while downloading Softpaq through "HP Instant Support System Health Scan Softpaq Downloads"
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. We recommend that you do not manually place any SoftPaqs in this download directory.
|18. Limitation of Wake on LAN (WOL) option|
In some environments, due to limitations of the Notification Server, the WOL option of a schedule does not work as expected. Ensure that at least two client computers per subnet are present for WOL proxies to work.
|19. IE ActiveX update issue|
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 in a future update of the Notification Server.
|20. BIOS inventory|
On some systems, such as HP dc7200 Desktop and HP dc7600 Desktop, due to problems with the BIOS, garbage 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 may be released to address this issue.
The inventory of BIOS settings on a system running Windows XP64 requires the system to have native WMI support in the BIOS. BIOS Inventory items are not available on systems running WinXP64 without the native WMI support. Example: HP dx7100, xw9300, DX5150, nx6125, xw6200, and xw8200. Systems running Windows XP32 will be able to gather the inventory of BIOS settings with or without the native WMI support in the BIOS.
|21. Limitation of HP BIOS Report Wizard|
The HP BIOS Report Wizard does not work properly if you create a report that joins multiple selections using OR. Use AND to properly join multiple selections.
|22. Incorrect hard disk size reported by the resource manager|
In the resource manager, the reported disk size is not reported correctly through the WMI HPCMS_WMI_Win32_DiskDrive. The correct size for the hard disk is located in HPCMS_WMI_Win32_LogicalDisk.
|23. Incorrect description stated in the Health Alert Policy|
In the Health Alert Policy, “Disk Drive Threshold Alerts”, the description provided for “Send E-Mail” incorrectly states that the alert is for a memory module alert.
|24. Embedded Security features|
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
b) Manage security credentials and Settings: Archive and Restore
However, with the same version of TPM, these features are supported on notebooks, such as the nc6220.
Please refer to the computer’s reference manual to get information on Embedded Security support-related information.
|25. Case insensitivity of BIOS password when provided through the HP BIOS (Advanced) Administration Wizard|
HP Client Manager has limitations in that the BIOS password provided through the HP BIOS Administration Wizard and the HP BIOS Advanced Administration Wizard is always used in lowercase. If a case-sensitive password is already set outside of HPCM on a system, HPCM is not able to modify the BIOS setting. This happens even if the correct (case-sensitive) password is provided through any of the wizards.
|26. Blank alerts are seen when modifying BIOS settings on 2006 notebooks
When BIOS settings are modified using the BIOS Administration wizard, blank BIOS change alerts are displayed. The following 2006 notebooks produce blank/empty alerts:
|27. No local alerts are seen on certain computers with the Windows 2000 operating system when BIOS settings are changed
When BIOS settings are modified using the BIOS Administration wizard, the local alerts are not displayed on certain computers with the Windows 2000 operating system. These computers include the HP Compaq rp5000 and the HP Compaq dc7100 Ultra-slim Desktop/ Convertible Minitower/Small Form Factor.
|28. 64-bit Operating System Support
Most HP systems that support 64-bit operating systems also support BIOS modification using SSM because the support is built into the BIOS. However, the following systems with 64-bit operating system support do not support BIOS modification using SSM because their BIOS lacks the support:
As a result, inventory settings cannot be properly obtained for these systems with 64-bit operating systems.
|29. HP Backup and Recovery Support
HPCM support for systems with HP Backup and Recovery is limited to version 18.104.22.168 and later of the scheduler.exe file. If the version number of the scheduler.exe file is less than 22.214.171.124, the WMI provider is not installed on the client computer.
|30. 2006 notebook BIOS support under Windows 2000
All 2006 notebooks (with native WMI BIOS support) do not support BIOS modifications with SSM under Windows 2000.
|31. Updating the Supported Systems List
The operation of updating the Supported Systems List should be performed from the Notification Server itself and not using a remote computer.
|32. Proxy Configuration
In certain situations, the proxy information provided on the Proxy Configuration page does not let you perform an update to the HP Supported Systems list from the Internet. In such a situation, use this option: Update the HP Supported Systems list using an update file. A list of steps are provided to manually update the Supported Systems list.
|33. Garbage message displayed as output for Disk Drive Changes report
When you add a USB-based flash memory drive (USB disk on a key drive) to a system, garbage characters are displayed under the Message column in the Disk Drive Changes report. This does not occur when you add a hard disk drive to a system.
|34. Report may incorrectly list computers
The HP Computers not capable of upgrading to Windows Vista or Vista Premium report may list the computers that can be upgraded to Windows Vista. A computer can be upgraded to Windows Vista if it meets certain hardware requirements. Two of the hardware requirements are the amount of total graphics card memory and screen resolution for a system.
Some systems report an incorrect graphics card memory size. Some systems also do not report the correct screen resolution. These systems appear as if they are not capable of being upgraded to Windows Vista. For a complete list of hardware requirements, refer to the Windows Vista Enterprise Hardware Planning Guidance on the Microsoft Web site.
|35. The HP Instant Support Diagnostics task may display an error on an HP xw8000
The HP xw8000 computer displays an error when running the HP Instant Support Diagnostics task. The HPHwScan has encountered a problem and needs to close error message appears. On selecting Don't send, an HPDiags.exe runtime error appears. Therefore, HP Diagnostics does not run successfully.
To resolve this issue, perform the following steps on the HPxw8000 computer:
Note: The HPHwScan.exe error is still displayed. However, the error with HPDiags.exe does not occur. HPDiags.exe runs the list of diagnostics and posts the results to the Notification Server. A newer version of HP Instant Support Diagnostics may resolve this issue in a future release.
Altiris product documentation is available in Microsoft* HTML Help (.CHM) and Adobe* Acrobat (.PDF) formats. To view Altiris product documentation in .PDF format, use Adobe Acrobat Reader (available at: http://www.adobe.com/products/acrobat/readstep2.html).
Documentation files are installed in the following directory on the Notification Server computer: InstallPath\Altiris\Notification Server\NSCap\Help.
The following documentation is provided with HPCM 6.2:
You can access documentation from the Altiris Console by clicking the following icons in the upper-right corner of the console:
Access the contextual online help by clicking the online help icon.
Access an index of all installed help by clicking the index icon.
Altiris Information Resources
|Source||What Information it Includes||Where to Find it|
|Altiris Documentation||Information about new features, update instructions, and known issues for each release. Includes Altiris formal documentation such as Release Notes, Help, Reference Guides, Best Practice Articles, and Technical Reference Articles.||http://www.altiris.com/support/documentation|
|Altiris Knowledgebase||Comprehensive collection of articles, incidents, and issues for Altiris solutions.||http://kb.altiris.com/|
an online magazine for Altiris users
|Best Practices, tips and tricks, and articles for users of Altiris solutions.||http://www.altiris.com/juice|
|Online Forums||Forums for Altiris solutions and suites.||http://forums.altiris.com/|
|08/23/2006||Alpha release notes posted as Draft|
|11/22/2006||Beta release notes posted as Draft|
Article URL http://www.symantec.com/docs/DOC1193