This document provides an overview of the changes made to HP Operations Manager for Windows (HPOM for Windows) with patch OMW_00090 and higher. It contains important information not included in the manuals or in online help provided with the patch.
Patch Description
Important Installation Notes
Virtual Nodes in Cluster Environments
Remote Console Interoperability
Remote Console Software
License Report Changes
Installation Patch
Backup and Restore
SQL Server Log Shipping
Signature Verification
As user Option in Policies
Known Problems, Limitations, and Workarounds
Local Language Support
Support
Legal Notices
Patch OMW_00090 can be applied to the following versions of HPOM for Windows:
The patch updates HPOM 8.1x for Windows installations to the same level of features that is available with HPOM 9.00 (64-bit) for Windows. New features include support for HP Event Correlation Services and virtual nodes, as well as changes to the MMC and web console. For more details, see the HPOM 9.00 for Windows release notes.
Patches released after patch OMW_00090 require OMW_00090 as an installation prerequisite.
Patch OMW_00090 can be installed on the management server and on remote consoles. However, in contrast to other HPOM patches, patch OMW_00090 cannot be uninstalled because the patch installation modifies the database. You are therefore required to perform a full system backup of all management server systems, including a full database backup of any remote database systems before installing patch OMW_00090. You can then use the backup data to restore the previous system state, if necessary.
The installation of patch OMW_00090 takes considerably longer than average HPOM for Windows patch installations.
Starting with patch OMW_00097, all HPOM server patches for version 8.1x (32-bit) have a dependency on patch OMW_00090 (or OMW_00096, Korean only). To get to the latest server patch level, you must perform the following high-level steps:
Patch OMW_00090 introduces the concept of virtual nodes to represent cluster resource groups. In contrast to HPOM 9.00 (64-bit) for Windows, this patch does not automatically add a virtual node for the HPOM management server. You must do this manually as described in the online help section Monitoring cluster-aware applications.
Important Note: When you set up a virtual node, make sure that the OS properties of the virtual node (see the System tab of the node properties dialog box) are the same as the OS properties of the physical nodes that you plan to add. The Associate Node with Node dialog box filters on these properties and shows only nodes that match. For example, if you select Windows Server 2008, you will only be able to associate Windows Server 2008 systems with the virtual node.
For more information about deploying instrumentation to virtual nodes, see the online help.
Patch OMW_00090 supports remote console interoperability between HPOM 8.1x and 9.00 for Windows if patch OMW_00090 is installed on the HPOM 8.1x management server and on all remote consoles installed from the 8.10 or 8.16 installation media. It is not supported to connect an HPOM 8.1x management server with patch OMW_00090 installed to an HPOM 8.1x remote console that does not have patch OMW_00090 installed.
The following table gives an overview of the supported combinations:
| Remote Console | Management Server | Interoperability |
|---|---|---|
| 8.16 or 8.16 with OMW_00070 (32-bit) | OMW_00090 or higher (32-bit) | no |
| OMW_00090 or higher (32-bit) | OMW_00090 or higher (32-bit) | yes |
| OMW_00090 or higher (32-bit) | 8.16 or 8.16 with OMW_00070 (32-bit) | no |
| 8.16 or 8.16 with OMW_00070 (32-bit) | 9.00 (64-bit) | no |
| OMW_00090 or higher (32-bit) | 9.00 (64-bit) | yes |
| 9.00 (64-bit) | OMW_00090 or higher (32-bit) | yes |
| 9.00 (32-bit)a | OMW_00090 (32-bit) | yes |
| 9.00 (32-bit)a | 8.16 or 8.16 with OMW_00070 (32-bit) | no |
aTo patch 32-bit remote consoles installed from the 9.00 (64-bit) installation media, install patch OMW_00097 or higher (the latest currently available patch is OMW_00117). Do not use patch OMW_00098 (or OMW_00118); they apply to 64-bit installations only. Patch OMW_00090 is not a prerequisite for 32-bit remote consoles; you can directly install patch OMW_00097 or higher.
Patch OMW_00090 installs two additional packages on all remote consoles:
Patch OMW_00090 includes several fixes that allow OS instance licenses to be reported correctly and enable correct license reporting. The patch introduces the new product structure for license reporting.
A special installation patch is required in the following scenarios:
The most recent, currently available installation patch is patch OMW_00091. For more information about the availability of installation patches, visit the HP Software Support web site at:
http://www.hp.com/go/hpsoftwaresupport
HPOM provides a tool that enables you to back up the management server online. The tool downloads backup data to a folder that you specify. This backup data includes the HPOM database and also HPOM configuration data from the registry, from other configuration files, and from the file system (for example, instrumentation). The management server backup also includes all the management server's certificates.
The backup data does not include the operating system, group membership, exported messages, custom console definitions, or licenses. If you want to back up these items, you must back them up separately.
To restore a management server from this type of backup, you must first restore the operating system independently. You can then restore the management server using a combination of the backup data and the HPOM installation media.
Depending on the HPOM version and patch level, an installation patch may be required:
| HPOM Version | Patch Level |
|---|---|
| 8.10 (without patch OMW_00090) | Installation patch OMW_00059 or higher required |
| 8.16 (without patch OMW_00090) 9.00 |
No installation patch required |
| 8.10 or 8.16 with patch OMW_00090 or higher | Installation patch OMW_00091 or higher required |
Starting with patch OMW_00090, the log shipping solution is supported with SQL Server databases only. (SQL Server Express databases are no longer supported for log shipping.) This is because with patch OMW_00090, HPOM switches to using SQL Server Agent Log Shipping jobs instead of sqldmo, which is used in previous versions.
For more information about log shipping, see the HPOM white paper:
%OvInstallDir%\paperdocs\en\HPOM_HA_with_SQL_Log_Shipping.pdf
Starting with patch OMW_00090, the HPOM Web Services binary files are signed for security. Every time the web server on the HPOM management server starts an HPOM Web Service, it attempts to verify the signatures. The web server needs Internet access to verify the signatures. If the web server has no Internet access, the web service may not start for several minutes. To avoid delays, you can disable verification of signatures. For more information, see the online help topic Web Server Configuration.
Note: Other components of HPOM, for example VBScript scripts, might also be affected if the management server has no Internet access.
Patch OMW_00090 adds the As user option to automatic and operator-initiated command dialog boxes. This option is designed for use with HP Operations Agent version 11.00 or higher. It enables you to specify a user account under which the action will run.
Note: It is not possible to deploy policies with the As user option selected to nodes that have HP Operations Agent version 8.60 or lower.
Stop HPOM services and processes. The patch installation process stops all running HPOM services and processes. Stopping some HPOM services might take several minutes. This has been observed mainly for the "HP OpenView Ctrl Service (OvCtrl)". If this service shows in the patch progress bar as being stopped, wait patiently.
Stop MMC consoles and services. To avoid reboots, stop the MMC console (mmc.exe) before starting the patch installation. (Rebooting may be necessary if HPOM files are loaded or locked during the patch installation.) The patch installation process detects instances of mmc.exe and prompts the user to stop them.
It is also necessary to stop all non-HPOM services that depend on the Windows Management Instrumentation (WMI) service before the patch installation. These services must be restarted manually after the patch installation has finished.
Close Windows Event Viewer. Close the Windows Event Viewer before starting the patch installation.
DEBUG mode. Patch OMW_00090 does not support installation in DEBUG mode. Do not use this installation mode as it might have an adverse effect on the HPOM instance you are patching.
"Feature transfer error". You may occasionally encounter the following problem during the patch installation:
Problem: After all HPOM services have been stopped and the data transfer from the patch media to the system has been initiated, an error dialog with the title "Feature transfer error" is shown. After you confirm this dialog the patch installation terminates.
Workaround: Retry the patch installation.
Registry key errors. After installing patch OMW_00090 for the first time (and no superseding patch already applied), the following two critical messages may be seen in the message browser:
"EventID: 0x00000400 (1024) - (MS922) RegCreateKeyEx(...) failed for Registry key "HKLM\Software\Hewlett-Packard\OpenView\OvOWRmtAgt": 5: Access is denied."
"EventID: 0x00000400 (1024) - (MS923) RegOpenKeyEx(...) failed for Registry key "HKLM\Software\Hewlett-Packard\OpenView\OvOWRmtAgt": 2: The system cannot find the file specified."
Workaround: You can safely ignore these errors. They do not have any impact on the product functionality.
License report problems (QCCR1A107095). After installing SPIs from the SPI DVD, there might be problems to open the license reports.
Workaround:
%OvInstallDir%\misc\EL\pd_files.dotnetspi.xml.<pdfile>dotnetspi_pdf.txt</pdfile><pdfile>F36WVpEA65mUPyw.txt</pdfile>.Failed license type registrations. If the user who installs patch OMW_00090 is not a member of the HP-OVE-ADMINS group, the patch fails to register the new license types.
Workaround: Run the following file as a member of the HP-OVE-ADMINS group to enable license reporting:
%OvInstallDir%Patches\OMW_00090\reglic.cmd
Undefined config item messages in Windows Event Log. During the patch installation, several messages similar to the ones below are added to the Windows Application Event Log:
"Error | 'HPOV-MS' | 03.11.2010 | 11:37:44 | (MS910) ConfigItem "ovow.MsgActSrv..." is NOT defined."
Workaround: You can safely ignore these messages.
Exception when uninstalling on Japanese systems. On Japanese systems, an exception is thrown during the product uninstallation:
"Exception thrown (check log file for details):
System.Management.ManagementException:
System.Management.ManagementException.
ThrowWithExtendedInfo(ManagementStatus errorCode)
System.Management.ManagementObject.InvokeMethod(
String methodName,
ManagementBaseObject inParameters,
InvokeMethodOptions options)
InstallApp.Setup.Components.SPIshare.Remove()"
Workaround: You can safely ignore these messages.
Installation in failover clusters. On each cluster node, at the end of the patch installation, you will be advised to restart the system. Do not do this before the patch is installed on all cluster nodes.
Patch OMW_00090 installation stops on cluster nodes. The patch installation on a cluster node may stop at the very beginning with the following popup message:
Unable to switch over to current node. Patch OMW_00090 cannot be installed.
Workaround: Retry the patch installation on that cluster node. The cluster environment could have the status:
The group is unable to accept the request since it is moving to another node.
Check patch.log for more information about the error.
Patch OMW_00090 updates CLUSTER_LOCAL_NODENAME with virtual cluster name (QCCR1A117895). The patch installation changes the value of CLUSTER_LOCAL_NODENAME from the cluster node name to the virtual cluster name.
Workaround: Manually change the value back to the cluster node name, for example:
ovconfchg -ns conf.cluster -set CLUSTER_LOCAL_NODENAME clustnode.example.com
Customized console files (.msc) cannot be used with patch OMW_00090. Because of design changes to the HPOM MMC console, customized console files (.msc) can no longer be used with patch OMW_00090. The patch replaces the default console file with a new console file with default settings.
Workaround: If you have created customized console files, complete the following steps to create new ones:
Open a command prompt and type mmc.exe.
Click File > Add/Remove Snap-In and select HP Operations Manager, then click Add.
In the Add or Remove Snap-ins dialog, click OK. The HPOM console loads in the MMC snap-in console.
Change the HPOM console layout to suit your needs and then click File > Save As to save your changes to a .msc file.
Patch OMW_00090 removes some agent platforms (QCCR1A119896). Several obsolete agent platforms have been removed and are missing in the HPOM console after installation of patch OMW_00090.
Workaround: A hotfix is available through HP Support, which re-enables the obsolete platforms.
Installation of UNIX or Linux agents fail when deployed from the console. Patch OMW_00090 replaces the files %OvInstallDir%\contrib\OVOW\PuTTY\runplink.cmd and %OvInstallDir%\contrib\OVOW\PuTTY\runpscp.cmd with newer versions with changed syntax. The patch installation also changes the EXEC and COPY definitions in the namespace depl.mechanisms.ssh to match the new syntax:
Syntax of OMW_00070 and lower:
depl.mechanisms.ssh COPY=pscp -q -batch -pw <passwd> <sourcefile> <user>@<host>:<targetfile> EXEC=runplink.cmd <passwd> <user> <host> <command>
Syntax of OMW_00090 and higher:
depl.mechanisms.ssh COPY=runpscp.cmd <host> <sourcefile> <targetfile> <user> <passwd> EXEC=runplink.cmd <host> <command> <user> <passwd>
If you have copied pre-OMW_00090 versions of runplink.cmd and runpscp.cmd to another folder on the management server, these copied versions do not work with the updated definitions of OMW_00090.
Workaround: Copy the OMW_00090 versions of runplink.cmd and runpscp.cmd from %OvInstallDir%\contrib\OVOW\PuTTY to the folder that holds the previous copies.
For more information, see the online help topic Configure HTTPS agent deployment to UNIX and Linux nodes.
Patch OMW_00090 disables previously deployed server policies (QCCR1A119483). Patch OMW_00090 disables all previously deployed server policies: Remote Action Security policies, Server-based Flexible Management policies, and Server-based MSI policies. Server policies that are deployed after the patch installation are not affected.
Workaround: Complete one of the following workarounds. If you read these release notes before installing patch OMW_00090, complete Workaround 1. If you read these release notes after installing patch OMW_00090, complete Workaround 2.
Workaround 1: Before installing patch OMW_00090
Uninstall all server policies that are deployed to the management server.
Install patch OMW_00090.
Redeploy the server policies to the management server.
Workaround 2: After installing patch OMW_00090
Correct the database migration corruption by executing the following SQL statement for the openview database:
update ov_pm_PolicyOnNode set forServer=1 where PolicyVersionId In ( select PolicyVersionId from ov_pm_PolicyVersion where PolicyId In ( select PolicyId from ov_pm_Policy where PolicyTypeId like N'%70128090-4CB5-43CB-804D-7596CCCC01E' OR PolicyTypeId like N'%CE46FF27-A51C-4E94-A103-AB6973067289' OR PolicyTypeId like N'%CE46FF27-A51C-4E94-A103- AB6973067280'))
The above SQL statement sets the column forServer to the value 1 for all deployed server policies.
This value has been incorrectly set to value 0 during the database migration. Consequently the deployed server policies were incorrectly interpreted as agent policies (instead of server policies).
List all server policies, type:
ovpolicy -list -level 4 -targetovrg server
The command output lists all policies that are deployed on the management server.
For each server policy, type the following command to remove it:
ovpolicy -remove -polid <policy ID>
NOTE: Make sure to not delete any agent policies.
Restart the management server, type:
vpstat -3 -r
Start the HPOM console and check the policy inventory. The server policies should be shown correctly.
Uninstall all server policies that are deployed to the management server.
Redeploy the server policies to the management server.
Patch OMW_00090 triggers automatic deployment of self-management policies. The patch installation uploads new versions of self-management policies to the management server. The management server then automatically deploys these policies during the patch installation. (Self-management policies monitor the availability and performance of the management server and agents on managed nodes.)
If you have customized the self-management policies on the management server and deployed them to one or more managed nodes, the customized policies are replaced on the management server by the patch installation and on all managed nodes by automatic deployment.
Workaround: Before installing patch OMW_00090, disable automatic deployment of self-management policies:
In the console tree, right-click Operations Manager, and then click Configure > Server.... The Server Configuration dialog box opens.
Click Namespaces, and then click Self Management. A list of values appears.
Set the value of Auto Deploy Policies to False.
After the patch installation, adapt the new policies to your needs and then re-enable automatic deployment of self-management policies.
ovpolicy -list no longer lists server policies. Starting with patch OMW_00090, server policies are stored in a different folder from the agent policies. This has the side effect that ovpolicy -list no longer lists server policies.
Workaround: To list server policies, use ovpolicy -l -targetovrg server.
Database backup uses up disk space on the management server (QCCR1A126571) Patch OMW_00090 introduces a new script (backup_openview.vbs) for backing up the HPOM database. This script appends backup data to the file openview_dat.bak rather than overwriting the existing data. The backup data therefore consumes more and more disk space on the HPOM management server.
Workaround: A hotfix is available from HP Support.
OMW_00090 includes localized versions for the Japanese and Simplified Chinese languages.
NOTE: Patch OMW_00090 does not support the Korean language. Install patch OMW_00096 to obtain Korean language support. Patch OMW_00096 is the Korean language equivalent of patch OMW_00090 and should only be installed on Korean HPOM 8.1x management servers.
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
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.
For information about third-party and/or open source license agreements, see the \Open Source Licenses directory on the product installation media.
To view open source code, see the \x64\Redist and \x86\Redist directories on the product installation media.
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.
© Copyright 1999-2011 Hewlett-Packard Development Company, L.P.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java is a registered trademark of Oracle and/or its affiliates.
Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
This product includes software developed by the JDOM Project (http://www.jdom.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.