This document provides an overview of the changes made to the Smart Plug-in for Microsoft Windows Operating System (Windows OS SPI) 9.11 for HP Operations Manager for Windows, versions 7.50 and 8.10. This document contains important information not included in the manuals or in online help.
In
This Version
Documentation Updates
Installation Notes
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Documentation Errata
Verified Environments
Local Language Support
Integration with Other HP Software Solutions
Support
Legal Notices
HP OpenView Operations is now HP Operations Manager, OVO for Windows is HPOM for Windows, and HP OpenView Smart Plug-ins are now HP Operations Smart Plug-ins.
NOTE: Due to these product name changes there may be situations where the product name in the documentation temporarily differs from the name you see on the software, or where the latest Smart Plug-in online help product names conflict with the earlier OVO for Windows product name.
Multilingual User Interface allows the user interface language of the operating system to be changed to one of the supported languages, according to the preferences of individual users.
The OS SPI instrumentation files support the HTTPS agent on the managed nodes for HP Operations Manager for Windows.
HP Network Node Manager (NNM) detects events like the state of the link and raises trap events for issues found. NNM Adapter intercepts these trap events and sends messages to the HP Operations message browser. The Windows OS SPI maps the severity of these messages to the service map.
| Original Name | New Name |
| WINOSSPI-IIS50_InternetInformationServicesGbl_FileCacheHitsPc | WINOSSPI-IIS50_IISGbl_FileCacheHitsPc. |
| WINOSSPI-WTS_TerminalServiceSession_PctProcessorTime-Win2k | WINOSSPI-WTS_TerminalServiceSession_PctProcTime-Win2k |
Version Verify – Helps track the different versions of instrumentation files, that are modified due to various hot fixes and patches applied on the managed node. The Version Verify tool helps to check which configuration files are missing on a managed node.
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:
HP Product
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:
Adobe
Installation requirements, as well as instructions for installing the Windows OS SPI are documented in the following guides:
You must install the WINOSSPI-Reporter.msi only on the cluster node where the HP Reporter 3.6 resource group is active.
To uninstall WINOSSPI Reporter, you must make sure that you uninstall WINOSSPI Reporter from the same cluster node on which you installed it. In addition, you must make sure that the HP Reporter 3.6 resource group is active on the cluster node during uninstallation.
The following Windows OS SPI versions can be upgraded or migrated:
During a side-by-side migration or an in-place upgrade:
If you did not remove the policies, the Windows OS SPI installation process removes these policies from the managed nodes, but does not remove the policies from the management server. The Policy IDs and Version IDs are corrected for the policies with this release.
If you did not remove the policies, the Windows OS SPI installation process removes these policies from the managed nodes, but does not remove the policies from the management server. The Policy IDs and Version IDs are corrected for the policies with this release.
If a managed node is not accessible from the management server during an upgrade or migration, you can remove the obsolete policies and the removed policies from the managed node after the managed node becomes accessible. This stops reception of messages from obsolete policies.
To check for the list of policies removed in this version, see removed policies.
Following are the service instances discovered by the Windows OS SPI and removed from the management server during a side-by-side migration or an in-place upgrade:
The Windows OS SPI installation process automatically deploys the new versions of the service discovery policies and the Microsoft Windows instrumentation on all Windows nodes.
If autodeployment is disabled on the management server, you must deploy the following on all Windows nodes after the migration or upgrade is complete:
To enable or disable autodeployment, set the following registry value to 0 or 1 respectively:
HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\AutoDeployment\Disable.
NOTE: In HPOM version 8.10, you can also set this registry value by: Configure> Server, Policy Management and Deployment> Disable autodeployment.
To display details about each software enhancement or fix, click the reference number link to go to the HP Online Software Support web site. The first time you click a link, you must enter your HP passport information. To set up your passport profile, go to:
http://www.hp.com/go/hpsoftwaresupport
The following policies are not supported on Windows 2008 server operating system
When trying to run any of these policies, a warning message will appear in the message browser stating an error occurrence while processing the policy.
Unknown Severity Messages for x64 Managed Nodes
When the stopped services and processes are restarted on an x64 managed node, the measurement threshold policies (Windows OS SPI service and process monitoring policies) generate messages with unknown severity in place of the normal acknowledgement messages on the active message browser.
WINOSSPI-IISCollector fails on Windows 2003 64-bit
The workaround is to change the default location of the IIS Log files to another directory outside the <systemroot> \system32 folder. This must be done on all the web sites where the WINOSSPI-IISLogFileCollector policy collects data. This also must be done on all the Windows 2003 64-bit managed nodes where the policy is deployed. To modify the default log file path:
Stand-alone WINOSSPI Reporter installation requires custom install
When you install the WINOSSPI Reporter integration outside the HP Operations Installer (by running the .msi file directly), the SPI files are placed in the following directory: <Installation directory>\HP\HP BTO Software\Install\WINOSSPI. If you specified a different installation directory during the HP Reporter installation, select Custom when prompted for Setup Type by the WINOSSPI Reporter installation.
In the Custom Setup dialog, change the Install to: directory to match the installation directory you specified when installing Reporter. To install WINOSSPI Reporter on a stand-alone Reporter System:
Changed policy names are not displayed for messages from nodes that have earlier versions of the policy
Though a policy name might have changed, the node that has an earlier version of the policy displays messages in the message browser with the unchanged policy name in the General tab. This occurs in spite of the server Policy Management and Deployment (PMAD) database displaying the changed policy name. The changed policy name displays in the General tab only after the new version of the policy is deployed on the node.
This is not a problem and does not affect any functionality including duplicate message suppression.
Integration with Self-Healing Services client software fails on some systems
The integration with Self-Healing Services client software fails on managed nodes where Microsoft Windows short paths are disabled. The Microsoft Windows > Self Healing Services > Self Healing Info tool, can be run on the nodes to gather diagnostic data.
In case of fresh installation, the Windows OS SPI Reporter Package gives the following error messages in the reporter trace file:
<Date> <Time>: RepLoad Begin removing template file <Installation directory>\HP\HP BTO Software\newconfig\Packages\repload_WINOSSPI_FULL.SRP
<Date> <Time>: ERROR: RepLoad Unable to open file "<Installation directory>\HP\HP BTO Software\newconfig\Packages\repload_WINOSSPI_FULL.SRP"
<Date> <Time>: ERROR: RepLoad Unable to remove template information from database
<Date> <Time>: RepLoad Begin removing template file <Installation directory>\HP\HP BTO Software\newconfig\Packages\repload_WINOSSPI_AD.SRP
<Date> <Time>: ERROR: RepLoad Unable to open file "<Installation directory>\HP\HP BTO Software\newconfig\Packages\repload_WINOSSPI_AD.SRP"
<Date> <Time>: ERROR: RepLoad Unable to remove template information from database
<Date> <Time>: RepLoad Begin removing template file <Installation directory>:\Program Files\HP\HP BTO Software\newconfig\Packages\repload_WINOSSPI_IIS.SRP
<Date> <Time>: ERROR: RepLoad Unable to open file "<Installation directory>:\Program Files\HP\HP BTO Software\newconfig\Packages\repload_WINOSSPI_IIS.SRP"
<Date> <Time>: ERROR: RepLoad Unable to remove template information from database
These messages do not have any impact on the functionality of the product.
On uninstallation of Windows OS SPI Reporter Package, the configuration for reports provided by Windows OS SPI is not removed from the Reporter database.
Hence there may be messages in the Reporter trace file that it has failed to generate reports (for all the reports that are shipped with Windows OS SPI).
There are no errors in the Windows OS SPI documentation currently.
| Application | Version(s) |
| Microsoft SMS | Microsoft SMS 2003 |
| Microsoft IIS | Microsoft IIS 5.0, 6.0, and 7.0 |
| Microsoft Terminal Service | Microsoft Windows 2000, XP Professional Edition, 2003, and 2008 |
| Microsoft Certificate Server | Microsoft Certificate Server 1.0 |
| Microsoft Cluster Server | Microsoft Windows 2000, 2003 (32 bit and 64 bit) |
| Microsoft Index Server | Microsoft Indexing Service |
| Message Queue Server | Versions 2.0 and 3.0 are managed on the supported operating system platforms. |
| Microsoft Operations Manager | MOM 2005 SP1 |
| Microsoft Distributed Transaction Co-ordinator | 2.0 version on the supported operating system platforms are managed |
| Dell open Manage Server | Dell open Manage Server 4.5 |
This release of the Windows OS SPI will be available in the following languages:
Windows OS SPI integrates with the following versions of HP Reporter:
You can visit the HP Software Support web site:
Support
This web site provides contact information and details about the products, services, and support that HP offers.
HP Software online support provides an efficient way to access interactive technical support tools. 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 and HP Passport, go to the
following URL:
HP Passport Access Levels
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.