This document provides an overview of the changes made to HP Operations Manager for Windows for the 8.00 release (HPOM for Windows). It contains important information not included in the manuals or in online help.
In This Version
Documentation Updates
Installation Notes
Obsolescence Announcements
Known Problems, Limitations, and Workarounds
Documentation Errata
Local Language Support
Support
Legal Notices
HPOM 8.00 for Windows manages your information technology environment by managing nodes and the services running on these managed nodes. It provides graphical user interfaces to configure policies, nodes, services, service types, tools, and user roles. These components work together to automate detection, evaluation, and responses to events and simplify the process of analyzing and resolving problems.
The HPOM 8.00 for Windows media kit contains a number of CDs and DVDs required to install the HPOM 8.00 for Windows foundation product, HP Operations Smart Plug-ins (SPIs), and add-on products. See the HP Operations Manager for Windows Installation Guide for details about the contents of your media kit and instructions for installing HPOM 8.00 for Windows. For HP Operations Smart Plug-ins, see the HP Operations Smart Plug-ins DVD Installation and Upgrade Guide and the HP Operations Smart Plug-ins DVD Release Notes for details about available SPIs and instructions for installing and configuring them.
HPOM 8.00 for Windows includes many documents in Adobe® Acrobat® PDF format. You must have Adobe Acrobat Reader to view and print these documents. Click here to download the Acrobat Reader from the Adobe web site.
The HP Operations Smart Plug-ins DVD contains an index list in the DVD Documentation directory that provides links to available documentation. See spi_docs_index.htm on the HP Operations Smart Plug-ins DVD.
HPOM 8.00 for Windows includes the following new features:
Before HPOM 8.00 for Windows, management servers and agents communicated using DCE/RPC. HPOM 8.00 for Windows introduces an agent that communicates using HTTPS. Although the DCE agent is currently still supported, you are encouraged to use the HTTPS agent for new nodes. If nodes already exist in your environment that have DCE agents, consider migrating to the HTTPS agent.
All communication between management servers, and between management servers and nodes is strongly encrypted.
Nodes and management servers accept all inbound communications to a single port, so it is simpler to configure firewalls and proxies.
Policies, messages, and actions all contain signatures, which management servers and nodes create and check using certificates. If a malicious user attempts to tamper with a signed policy, message, or action, the signature becomes invalid.
You can now change the status display mode in two ways: disable user-specific status calculation and enable operational status calculation. User-specific status calculation is enabled by default and means that the status of services in a user's map is calculated based on the user's subordinate services and messages. Another user with a different set of responsibilities may see a different status for the same services. Operational status calculation is disabled by default. When enabled, owned messages are considered acknowledged and do not affect the severity status of a service.
HPOM 8.00 for Windows distinguishes unplanned and scheduled outages. The outage state can be applied to nodes and node groups, and to services and service hierarchies, either by using the console (for unplanned outages only) or by applying command-line tools (for both unplanned and scheduled outages).
You can now add Windows groups to the HP-OVE-OPERATORS group and assign the Windows group to an operator user role. Windows users who are members of that group automatically receive the permissions associated with that user role. In addition, you can set permissions to view reports and graphs, to change the unplanned outage state, to create message filters, and to perform administrative tasks on policies.
External nodes handle messages from nodes without the need to configure them as nodes. For example, by setting up an external node, you can immediately receive messages from new systems in a certain IP subnet, and then decide later whether it is necessary to set up the systems as managed nodes. Or you can receive messages from systems without an HP Operations agent installed (SNMP devices, for example) for agentless monitoring. When you set up an external node, you define a pattern that must be matched by the node's fully qualified domain name, IP address, or node name.
The server configuration dialog contains a generic server configuration tab, which enables you to configure many different aspects of a management server's configuration. This eliminates the need to manually configure values on a management server using registry editors or commands.
You can now use a wizard to create new nodes. The wizard guides you through the node setup and helps you to enter the required information. In addition, heartbeat polling and autodeployment can be set for each node individually. A node's properties now also include settings for the agent communication type and binary format.
Custom message attributes represent additional, user-defined properties that can be attached to a message, for example owner, location, or emergency phone number. The administrator defines custom message attributes for outgoing messages. The operator can see custom message attributes in the message browser, can add, modify, and delete them, and can filter messages based on them.
In addition to custom message attributes, HPOM 8.00 for Windows introduces the following new message attributes: Time Created, Sender, and Origin.
Message-related tools can be launched on multiple, selected messages.
Owned messages in the message browser will now use a different color. When a new message arrives, the following system tray notifications are available: icon or popup or both, and sound notification.
Messages can now be saved to a .txt or .csv file.
HPOM 8.00 for Windows introduces a new policy type for management server policies. Server policies configure the behavior of the management server and do not require an agent or software other than the management server itself. They can be deployed to the local management server only and are listed under a new folder Server policies grouped by type.
The following server policy types are available:
The new ovowserviceutil command-line tool complements the already existing ovownodeutil, ovowtoolutil, and ovowmsgutil range of command-line tools.
The server-based MSI enables you to read messages from the internal message stream on the management server, to modify them as required, and to write them back.
Service logging is configured using the new ServiceLogger Service GUI tool, which is available in the Service Logging tool group of the HP Operations Manager Tools group. Use the service logger configuration dialog to select or clear the services to be logged. The status of selected service is logged every five minutes. When at least 24 hours of data exist, the data can be used to produce reports. Logging is available for autodiscovered and for self-defined services.
HP Performance Agent Software, version 4.70 can be integrated with HPOM 8.00 for Windows. You can deploy HP Performance Agent Software from the HPOM 8.00 for Windows console. You can also centrally control and configure HP Performance Agent Software from HPOM 8.00 for Windows. For more information, refer to the HP Performance Agent Software Deployables Installation Guide and the topic HP Performance Agent Software from the HPOM 8.00 for Windows console online help.
HP Reporter and HP Performance Manager are now part of the HPOM 8.00 for Windows product. You can install HP Reporter locally on the management server or remotely. HP Performance Manager can only be installed on the management server system. For more information about what's new in HP Reporter 3.80 and HP Performance Manager 8.00, see the release notes for each product.
The first page of this release notes document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition,
go to the following web site:
http://h20230.www2.hp.com/selfsolve/manuals
NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following web site:
http://www.adobe.com
Installation requirements, as well as instructions for installing HPOM 8.00 for Windows, are documented in the Installation Guide for HPOM 8.00 for Windows provided in Adobe Acrobat (.pdf) format. The document file is included on the product's installation media as:
\Documentation\HPOM Guides\HPOM_Installation_Guide.pdf
After installation the document can be found at:
%OvInstallDir%\HP\paperdocs\en\
For SPI installations, see the HP Operations Smart Plug-ins DVD Installation and Upgrade Guide and HP Operations Smart Plug-ins DVD Release Notes for more information.
Software and hardware requirements can be found in the HP Operations Manager 8.00 for Windows Installation Guide.
Supported platforms are specified in detail in the support matrix available at this location:
http://h20230.www2.hp.com/sc/support_matrices.jsp
NOTE: If you are upgrading from previous versions of HP Operations Manager for Windows, be sure to read the upgrade guide, available in .htm format on the product media. You must take certain steps before installing the current release.
Symptom: The in-place or side-by-side migration of an HPOM 7.5 installation can lead to missing data if the policy database references policy bodies that do not exist in the file system. This causes an undetermined number of policies to be missing in the export data. To determine whether your 7.5 system is affected, execute the following query in a command window, and compare the resulting number of policies in the database with the number of files in the policies directory.
osql.exe -S <server> -d <database name>
-U <user> -P <password> -q "SELECT Count(*)
FROM OV_PM_LogPolicy"
<server>
<system>\<instance> (for example, "ovmsql\ovops"
or ".\ovops"). Found in the ODBC Database
Source Administrator.
<database name>
"HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\DBAccess\Source".
<user>
<password>
Example:
osql.exe -S ovmsql\ovops -d openview -U ovms_admin
-P ovms -q "SELECT Count(*)
FROM OV_PM_LogPolicy"
Solution: Currently none. We are investigating the root cause of this issue, and will provide a fix for this problem as soon as possible.
Symptom: The download of the reporter data from the source system fails because of an error in the data download logic. This causes the loss of old reports after migration of the Reporter.
Solution: You must perform the download of the reporter data from the source system manually. To do this, follow these steps:
Remove the wrongly created "<MigrationDir> \ReporterDB -p -d" directory.
From the command line, switch to <DVDdrive>.
Enter cd <DVDdrive>\InstallApp\Migration\Binn.
Enter the following:
regsvr32 sqldmo.dll
When a dialog window appears, press OK.
Enter the following:
cd ..
Enter the following:
cscript ovr_dnl_conf_db.vbs "<MigrationDir> \ReporterDB" -p –d
Enter the following:
regsvr32 /u sqldmo.dll
When a dialog window appears, press OK.
NOTE: You must replace <DVDdrive> and <MigrationDir>
with the appropriate values in your environment.
Symptom: The following HPOM services fail to start during the installation:
You are using a Remote Desktop Connection to the system where you are installing HPOM but you are not connected to the server console session (session 0).
Solution:
To install HPOM successfully via a Remote Desktop Connection, use mstsc /console when starting the Remote Desktop Connection. This command connects you to the server console session.
Symptom: Although the installation of the management server finishes without errors, not all components are installed properly. The agent binaries are missing and so it is not possible to deploy the HP Operations agent to a remote managed node.
Solution:
Do not use a name for the management server that is longer than 14 characters.
With Operations Manager 8.10, the maximum length of a netBIOS computer name (which is 15 characters) will be supported.
Symptom: After the installation of the HPOM for Windows management server, many entries appear in Add/Remove Programs that are related to the HP Operations agent on the management server.
Solution:
To uninstall the management server, do not remove individual entries for the HP Operations agent in Add/Remove Programs. Selecting HP Operations Manager 8.0 for Windows also removes the HP Operations agent.
Symptom: After the installation of the HPOM for Windows management server, a failed "Change Agent" job is listed in the Deployment jobs section of the console.
Solution:
To remove the failed "Change Agent" job, right-click the job and select Cancel Job.
Also review the support matrix available at: http://h20230.www2.hp.com/sc/support_matrices.jsp
HP discontinues support of the following agent platforms with the release of HP Operations Manager 8.00 for Windows.
NOTE: If vendors obsolete further operating systems during the lifetime of HP Operations Manager 8.00 for Windows, support of the agent on the respective platform will be discontinued at the same time as the operating system itself ends support. Service Packs become obsolete as per vendor lifecycle policy. Review the product support matrix regularly for early announcements of platform support obsolescence plans.
HP will end certification of new platforms for the DCE agent by the end of June 2008. After this date, new operating system versions and cluster or virtualization solutions released by the respective vendors are no longer tested and supported by the DCE agent.
DCE agent support for HP Operations Manager 8.00 for Windows will be discontinued at the same time as HP Operations Manager 7.50 for Windows will reach end of support. Visit the HP Software Support web page for announcements.
HPOM 8.00 for Windows will not support the following management server platforms. Service Packs will become obsolete as per Microsoft lifecycle policy.
The following console platforms are not supported with HPOM 8.00 for Windows. Service Packs will become obsolete as per Microsoft lifecycle policy.
The following web console platforms are not supported with HPOM 8.00 for Windows:
The following high availability solutions are not supported with HPOM 8.00 for Windows:
HP discontinues support of the following databases:
HPOM 8.00 for Windows does not support the following integrations:
HP plans to obsolete the following platforms with the next major release of HP Operations Manager for Windows after version 8.00.
HP appreciates your feedback. Contact your HP sales or support representative if you would like HP to continue supporting the managed node platforms listed in this section with the next major release.
| New policies and policy groups | Changed policies | Obsolete policies and policy groups | |
|---|---|---|---|
| Self Management Module
All new or changed policies of the HPOM 8.00 for Windows Self Management module have the version 7.0. The name of the self management policy group has changed from OV Operations Self Manager to HPOM Self Management. |
|
|
|
| Sample Policies
All new or changed policies of the HPOM 8.00 for Windows Samples module have the version 7.0. |
|
||
| Service Logging Module |
|
|
NOTE: Some of the change request (CR) numbers listed below are used internally by HP and cannot be found on the HP Software Support web site.
Occasionally the previous HP OpenView Operations product name or its OVO abbreviation may appear as an application name in a message browser message, in error messages, or in a policy name. This is not a cause for concern.
Symptom: In a server-based flexible management scenario, messages cannot be forwarded because the maximum buffer size has been reached.
Solution:
Restart the OvEpMessageActionServer service; this is the service that has reached the maximum buffer size.
Symptom: In a server-based flexible management scenario, messages cannot be forwarded because the message and action server crashes. This happens when a large number of messages must be forwarded.
Solution:
%OVShareDir%\server\datafiles\bbc\snf\OvEpMessageActionServer
Symptom: Over time, the message and action server consumes more and more memory.
Solution:
There is currently no workaround available other than restarting the OvEpMessageActionServer service.
Symptom: Cluster support does not work with software package names containing non-ASCII characters.
Solution:
Rename the packages.
Symptom: After installing the Performance Agent on a node where the HTTPS agent is running, the HTTPS agent no longer functions properly.
Solution:
Restart the HTTPS agent with the commands:ovc -kill ovc -start.Avoid this problem by stopping the HTTPS agent before installing the Performance Agent.
Symptom: Policy and package deployment to a Tru64 node fails because of an unknown node platform. The HP Operations agent for Tru64 sends the wrong OS version string (5.1) to the management server, so the node is not correctly set up in the managed environment (Agent Comm. Type and Agent Binary Format are set to n/a ).
Solution:
Use the System tab of the Managed Nodes Properties dialog box to set the OS version to "5.1B". Afterwards, the agent comm type and agent binary format should also be set up correctly.
This issue will be fixed with Operations Manager 8.10.
Symptom: The remote deployment of the HP Operations agent fails with a WMI error (PMD 1089). Subsequently, the policy deployment jobs fail with a "Platform is not supported" error. Root cause is the agent tool ASSD, which discovers the Tru64 5.1B node's OS version as 5.1 instead of 5.1B.
Solution:
A hotfix is available through HP Support.
Symptom: HTTPS agents only. The following information applies to 32-bit Windows custom applications that read the following registry values:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP OpenView\InstallDirHKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP OpenView\DataDirSolution:
The Windows HTTPS agent supports Windows x64 operating systems natively. It provides 32-bit libraries for 32-bit applications to communicate with the 64-bit runtime of the agent. 32-bit applications that use the registry to get the paths of the agent installation directory and the data directory should change their applications to read the 64-bit registry view as specified by the following article by Microsoft:
http://msdn2.microsoft.com/en-us/library/aa384129.aspx
Symptom: HTTPS agents only. To remotely install or deinstall an HTTPS agent on a Windows node with a username/password the user must have permission to log on as a service. If the user does not have this permission, the agent deployment job fails, even if you subsequently assign this permission to the user account on the target node and restart the job.
Solution:
Open a command prompt on the node, and then type sc delete OvDeplSvc.
Symptom: HTTPS agents only. Expected behavior: when the buffer-file size reaches the maximum limit, only messages with a severity equal to or higher than the one set with OPC_BUFLIMIT_SEVERITY should be added to the buffer file. In addition, messages in the buffer file with a severity lower than the one set with OPC_BUFLIMIT_SEVERITY should be deleted from the buffer file to make room for high severity messages.
This expected behaviour is currently not seen; there are inconsistencies observed.
Solution:
There is currently no workaround available.
Symptom: HTTPS agents only. After a system restart, the message agent continues to buffer messages instead of sending them to the management server.
Solution:
Restart the agent processes after a system restart:
ovc -killovc -startSymptom: HTTPS agents only. When you monitor an agentless node through measurement threshold policies using WMI, the messages from the agentless node arrive at the proxy node's message browser instead of the message browser of the agentless node.
Solution:
There is currently no workaround available.
Symptom: HTTPS agents only. On Windows Vista and Linux x86, 64-bit nodes, automatic and operator-initiated commands fail because the variable $MSG_NODE_NAME resolves to an incorrect IP address.
Solution:
ovconfchg -ns eaagt -set OPC_IP_ADDRESS <IP_ADDRESS>
Where <IP_ADDRESS> is the IP address of the node represented in dot notation.
ovc -restart opcmsga
This step is not necessary on Windows Vista x86 platforms.
Symptom: HTTPS agents only. The following error appears in the file opc_inst.log during a manual HP Operations agent installation on a Windows Vista node:
opc_inst Error: Failed to set Auto-start flag for ovcd service.
Solution:
Use ovconfchg to set the autostart flag on the Windows Vista node. Open a command prompt on the node, and then type:
ovconfchg -ns ctrl -set START_ON_BOOT true
Symptom: HTTPS agents only. The following commands fail to disable scheduled task and WMI policies on a managed node:
opctemplate -d -all
opctemplate -d -all_schedule
opctemplate -d -all_wbem
The following error message appears:
WARNING: (conf-556) No policies found on host 'localhost' for which the
policy operation can be applied.
Solution:
Run opctemplate for each policy individually (for example, opctemplate -d VP_SM_DB_Backup).
Symptom: HTTPS agents only. Some HP Operations agent processes fail to start after the deployment of an HTTPS AIX agent.
Solution:
On the AIX managed node:
ovc -startSymptom: HTTPS agents only. A remote reinstallation of HTTPS agents on HP-UX nodes ends with the error (ctrl-7) Error in the target component. The agent processes are not automatically started.
Solution:
Manually start the agent processes on the HP-UX node after the reinstallation.
Symptom: HTTPS agents only. After the uninstallation of HTTPS HP-UX agents, the following directory is still present on the node: /opt/OV/lbin/eaagt
The embedded performance component and HP Performance Agent Software check this directory to determine whether an agent is installed. Even after the uninstallation of the agent, the output of perfstat reports an installed agent.
Solution:
Manually remove /opt/OV/lbin/eaagt from the HP-UX node after the uninstallation.
Symptom: HTTPS agents only. The HTTPS discovery agent cannot switch user to execute a discovery policy. This means that if the discovery policy is configured to run as any other user than $AGENT_USER the discovery will fail for all platforms.
Solution:
Run the discovery policy as the $AGENT_USER.
Symptom: HTTPS agents only. The logfile encapsulator on Windows nodes stops sending messages when the variable OPC_LE_SAVE_STATE is set to TRUE.
Solution:
There is currently no workaround available.
Symptom: HTTPS agents only. When you install an HP Operations HTTPS agent on a system with HP Service Desk installed, several settings that were made by the HP Service Desk server are overwritten (for example, CORE_ID, CERTIFICATE_SERVER, and so on).
Solution:
After the installation of HP Service Desk and before installing the HP Operations agent, take a backup of all the configuration settings and certificates. After the agent has been installed, restore the settings from backup.
Symptom: HTTPS agents only. When an ECS policy is installed on an HTTPS agent running as non root, the opceca process aborts.
Solution:
There is currently no workaround available.
Symptom: HTTPS agents only. The logfile encapsulator sends duplicate messages to the message browser, even when duplicate message suppression is configured in the Message correlation tab of the Outgoing message defaults dialog box.
Solution:
Message correlation for logfile messages cannot be set globally. Configure duplicate message suppression for each rule individually in the Message correlation tab of the Outgoing Message dialog box.
Symptom: HTTPS agents only. When using a non-root Windows HTTPS agent, ovconfd.exe changes the permissions for <datadir>\datafiles\policies (by setting a DACL and removing the HP Operations agent ACE).
Solution:
There is currently no workaround available.
Symptom: HTTPS agents only. In some cases, you are not able to run applications from any location and the installation of the HP Operations agent fails. This is because the Windows PATH variable may already be filled up before the HP Operations agent installation and the installation is not able to update it. There is no warning in the installation log.
Solution:
Make sure the PATH variable is not filled up before the HP Operations agent installation. Or update it manually after the installation.
Symptom: HTTPS agents only. In rare cases, the monitor agent coredumps when all policies are removed from an HTTPS node.
Solution:
There is currently no workaround available.
Symptom: HTTPS agents only. bbcutil -ping may return the following error on Linux nodes:
***glibc detected *** double free or corruption (!prev): 0x09c25208 ***
Solution:
There is currently no workaround available.
Symptom: HTTPS agents only. The deployment of HP Performance Agent Software to RHEL 4.0 64-bit nodes with an HP Operations agent already installed fails with the following error messages:
The Perf Agent alarm generator is being started.
/opt/perf/bin/perfalarm: error while loading shared libraries: libOvCoda.so: cannot open shared object file: No such file or directory
ERROR: The alarm generator /opt/perf/bin/perfalarm failed to execute
Solution:
The problem occurs only with 64-bit HP Operations agents being installed on RHEL 4.0 systems, which is not supported. To solve the problem, uninstall the 64-bit HP Operations agent from the node and install the 32-bit version instead.
Symptom: The deployment of HP Performance Agent Software to HP-UX, Solaris, and Windows nodes fails with Self-patch bundle could not be installed error (depl-412).
The deployment of HP Performance Agent Software completes successfully in spite of the error.
Solution:
Update the package inventory on the management server:
Symptom: In an outbound-only communication setup, if you run ovbbccb -status, the connections will show only the proxy rather than the actual nodes that are using the proxy.
Solution:
There is currently no workaround available.
Symptom: When an external tool uses the WMI interface to query for OV_Message instances, the OvEpMessageActionServer service crashes if the query contains time comparisons (for example, SELECT * FROM OV_Message WHERE TIMECREATED>'20071102').
This problem does not affect the core functionality of HPOM for Windows.
Solution:
Do not use time comparisons in queries of OV_Message until this problem has been solved by HP.
Symptom: When you launch a graph but close the graph window before it loads completely, and then later close the console, the console crashes before it closes completely.
Solution:
Do not close graph windows before they load completely.
Symptom: After the uninstallation of HP Performance Manager, HP Reporter disappears from the console.
Solution:
Do not uninstall HP Performance Manager when HP Reporter is also installed.
Symptom:
Solution:
Before installing the HP NNM Adapter, make sure the following additional prerequisites are met:
After the installation of the HP NNM Adapter, restore the original values in the Server Configuration dialog box.
You must have a Windows account for running HP NNM Adapter components. The account must have administrative rights on the HP NNM server. You may use the same account that was used for the HPOM installation.
Symptom: After a reboot of the HPOM 8.00 for Windows management server with the HP BAC Adapter installed, the HPOM 8.00 for Windows services may take a long time to start or may fail to start.
Solution:
Open the Start menu and select Run. Then type regedit and click OK.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HPOvOpc2Bac
DependsOnService to modify it, add the following string at the end of the list (in a new line), then click OK:
OvEpMessageActionServer
Generic Service in the HPOM 8.00 for Windows resource group, then click Next.HPOvOpc2Bac in the Generic Service Parameters page, then click Next.For more information about certificate management and problems related to certificate handling, see the Certificate Management in Environments with Multiple HP BTO Software Products white paper. This document is located on the product media, in the Documentation\Whitepapers directory.
Symptom: 100% CPU is used if you enable stack trace for all process and components during tracing. Processes become extremely slow.
Solution:
Use stack trace only for absolutely necessary trace areas. Do not switch on stack traces for all areas.
Symptom: The dialog boxes in the trace GUI are not completely visible. Happens only on Simplified Chinese windows.
Solution:
Switch to higher resolution, for example 1024x768.
Symptom: If you use non-existent directories as trace file destinations, HPOM components may hang.
Solution:
Use only existing directories as trace file destinations.
The following items are listed incorrectly in the documentation. To display details about each documentation error, click the error summary. To hide details, click again.
| LOCATION: | Topic in online help, "Implementing HP SiteScope Adapter alerts." |
| ERROR: | Between steps 5 and 6, an additional step is missing. |
| CORRECTION: | Insert the following step between steps 5 and 6: In Main Settings, Template drop-down box, make sure Default is selected as template for this SiteScope Adapter script alert. |
| LOCATION: | Upgrade guide, "7.50 to 8.00 in-place cluster to cluster upgrade." |
| ERROR: | Additional steps are missing. |
| CORRECTION: |
Use the procedure below to perform a "7.50 to 8.00 in-place cluster to cluster upgrade."
|
HPOM 8.00 for Windows is currently only available in the English language. Localized versions for the Japanese, Korean, and Simplified Chinese languages will be available with HPOM version 8.10.
You can visit the HP Software Support web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP offers.
HP Software online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to do the following:
NOTE: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to the following URL:
http://h20230.www2.hp.com/new_access_levels.jsp
To register for an HP Passport ID, go to the following URL:
http://h20229.www2.hp.com/passport-registration.html
©Copyright 2007 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Adobe®, Acrobat®, and PostScript® are trademarks of Adobe Systems Incorporated.
AMD is a trademark of Advanced Micro Devices, Inc.
Intel®, Itanium®, and Pentium® are trademarks of Intel Corporation in the U.S. and other countries.
Java™ is a US trademark of Sun Microsystems, Inc.
Microsoft®, Windows®, Windows NT®, and Windows® XP are U.S. registered trademarks of Microsoft Corporation.
Windows Vista™ is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.
Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.
UNIX® is a registered trademark of The Open Group.