HP OpenView Smart Plug-in for Microsoft Windows OS

for HP OpenView Operations for Windows

Release Notes

Software version: 08.90 / June 2006

This document provides an overview of the changes made to the Smart Plug-in for Microsoft Windows OS (Windows OS SPI) 08.90 for the HP OpenView Operations for Windows (OVO) 7.5. It contains important information not included in the manuals or in online help.

In This Version
Installation Notes
Known Problems, Limitations, and Workarounds
Verified Environments
Local Language Support
Integration with Other OpenView Solutions
Support
Legal Notices

In This Version

This release of the the Windows OS SPI supports only HP OpenView Operations for Windows (OVO) 7.5. Earlier versions of OVO are not supported.

The new features added in this release are as follows:

• Improved management of IIS version 6.0
  Windows OS SPI provides improved management of IIS version 6.0. New tools and policies are included to enhance the management of IIS version 6.0.
• Support for Microsoft Windows 2003 on x64 computers
  Windows OS SPI now integrates with Microsoft Windows 2003 on x64 computers.
• Removal of HP Systems Insight Manager (HPSIM) and Insight Manager (IM) features.
  The HPSIM and IM features along with the associated policies and tools are removed from Windows OS SPI. These features are now available in the HP SIM integration kit that is included with the current version of the OVO SPI CD.

New Policies

The policies added to enhance IIS version 6.0 management are as follows:

• WINOSSPI-IIS60_WWWFileCacheHitspct
• WINOSSPI-IIS60_ApplicationPool
• WINOSSPI-IIS60_WWWCurrentConnections
• WINOSSPI-IIS60_WWWBytesTotalSec
• WINOSSPI-IIS60_WWWRequestsSec
• WINOSSPI-IIS60_WWWFilesTotalSec
• WINOSSPI-IIS60_SmtpDeliveredSec
• WINOSSPI-IIS60_SmtpOutbConnectionsCurrent
• WINOSSPI-IIS60_SmtpMessagesSentSec
• WINOSSPI-IIS60_SmtpInbConnectionCurrent
• WINOSSPI-IIS60_SmtpMessagesReceivedSec
• WINOSSPI-IIS60_NntpArticlesPostedSec
• WINOSSPI-IIS60_NntpArticlesReceivedSec
• WINOSSPI-IIS60_NntpArticlesSentSec
• WINOSSPI-IIS60_FtpCurrentNonAnonymousUsers
• WINOSSPI-IIS60_FtpBytesTotalSec
• WINOSSPI-IIS60_FtpCurrentConnections
• WINOSSPI-IIS60_FtpCurrentAnonymousUsers
• WINOSSPI-IIS60_ASPNETWorkerProcessesRunning
• WINOSSPI-IIS60_ASPNETRequestsQueued
• WINOSSPI-IIS60_ASPNETRequestWaitTime
• WINOSSPI-IIS60_ASPNETRequestsRejected
• WINOSSPI-IIS60_ASPNETApplicationRestarts
• WINOSSPI-IIS60_AspPreprocessorErrors
• WINOSSPI-IIS60_AspErrorsSec
• WINOSSPI-IIS60_AspRequestsFailedTotal
• WINOSSPI-IIS60_AspRequestWaitTime
• WINOSSPI-IIS60_AspScriptCompilerErrors
• WINOSSPI-IIS60_AspRequestsExecuting
• WINOSSPI-IIS60_AspRequestsSec
• WINOSSPI-IIS60_AspRequestsQueued
• WINOSSPI-IIS60_AspScriptErrors
• WINOSSPI-IIS60_AspRequestExecutionTime
• WINOSSPI-IIS60_AspRequestsRejected
• WINOSSPI-IIS60_SrvProcMon_NNTPSVC
• WINOSSPI-IIS60_SrvProcMon_MSFTPSVC
• WINOSSPI-IIS60_SrvProcMon_SMTPSVC
• WINOSSPI-IIS60_SrvProcMon_IISADMIN
• WINOSSPI-IIS60_SrvProcMon_W3SVC
• WINOSSPI-IIS60_InetinfoWorkingSet
• WINOSSPI-IIS60_Server_BytesTransmittedSec
• WINOSSPI-IIS60_Process_PctProcessorTime_inetinfo
• WINOSSPI-IIS60_SiteAvailability
• WINOSSPI-IIS60_IISGbl_FileCacheHitsPc

Refer to the Smart Plug-in for Microsoft Windows OS Online Help for additional information about the new policies.

New Policy Group

A new policy group named MS Internet Information Server 6.0 is added under Microsoft Windows > Web Servers > Manual Deploy

New Tool Group

The MS IIS 6.0 tool group is added to enhance IIS version 6.0 management.

Obsolescence Announcements for Windows OS SPI Release with OVO 8.0

The following applications might not be supported with the release of Windows OS SPI with OVO 8.0:

• Microsoft Windows NT 4.0
• Index Server
• Internet Information Server 4.x
• MSMQ 1.0
• Proxy Server 2.0
• Transaction Server 2.0
• Site Server 3.0
• SNA Server 4.0
• System Management Server 2.0
• Antivirus
• Citrix 1.8
• Veritas Backup

The following features might be removed from Windows OS SPI released with OVO 8.0:

• Active Directory
• Microsoft Enterprise Server
  • BizTalk Server 2000 and BizTalk Server 2002
  • Commerce Server 2000 and Commerce Server 2002
  • Internet Security and Acceleration Server 2004
  • Mobile Information Server 2000
• Microsoft Exchange Server
  The Active Directory, Microsoft Enterprise Server, and Microsoft Exchange Server management features removed from Windows OS SPI are available with the respective smart plug-ins (SPIs) for these applications.
• Novell Netware
  The Novell Netware management features might be available as a separate SPI with the OVO 8.0 release.

Installation Notes

Installation requirements, as well as instructions for installing the Windows OS SPI are documented in the following guides provided in Adobe Acrobat (.pdf) format:

• HP OpenView Operations for Windows Installation Guide
• HP OpenView Operations for Windows Upgrade Guide
• Smart Plug-ins CD for OpenView Operations Installation/Upgrade Guide

WINOSSPI Reporter on a Microsoft Cluster with OpenView Reporter 3.6 and no OVO installation

You must install the WINOSSPI-Reporter.msi only on the cluster node where the OV 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 OV Reporter 3.6 resource group is active on the cluster node during uninstallation.

Upgrade information

The following Windows OS SPI versions can be upgraded or migrated:

• B.08.75
• B.08.33
• B.08.30

Policies affected during side-by-side migration or in-place upgrade

During a side-by-side migration or an in-place upgrade:

• It is recommended to remove the policies listed below from the managed nodes and the management server prior to upgrade or migration because these policies have incorrect Policy IDs or Version IDs. You may not remove these policies if you are upgrading Windows OS SPI from version 08.75 that is included in the OVO 7.5 SPI CD released in 2005:
  • WINOSSPI-Ex60 Exchange Application Warnings
  • WINOSSPI-Ex60 Exchange Application Errors
  • WINOSSPI-Ex60 Exchange Application Information
  • WINOSSPI-NET_HostIntegrationServerFwdApplicationError
  • WINOSSPI-NET_HostIntegrationServerFwdAllInformation
  • WINOSSPI-Ex55 IS Private Send Queue Length
  • WINOSSPI-Ex55 IS Public Send Queue Length
  • WINOSSPI-Ex55 IS Public Receive Queue Length***
  • WINOSSPI-Ex55 IS Public Send Queue Length***

  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. The WINOSSPI-Ex60 Exchange Application Information and WINOSSPI-NET_HostIntegrationServerFwdAllInformation policies retain the incorrect IDs because these policies were made obsolete in the Windows OS SPI release B.08.33.

• The policy assignments in the management server are updated
• During an upgrade process, Windows OS SPI removes the HPSIM and IM policies from all the deployed nodes, but might not remove the policies from the management server. You must manually remove the policies prefixed with WINOSSPI-HPSIM and WINOSSPI-InsightManager from the management server. You must perform this step even if you are upgrading Windows OS SPI from version 08.75 included with OVO 7.5 SPI CD released in 2005.

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.

Services updated after Side-by-Side Migration or In-place Upgrade

The Active Directory service instances discovered by the Windows OS SPI are 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 to all Windows nodes. New instances will be created once service discovery runs on the Windows domain controller nodes based on the new Active Directory service model.

If autodeployment is disabled on the management server, you must deploy the following on all Windows nodes after the migration or upgrade is complete:

1. Microsoft Windows instrumentation
2. Microsoft Windows >Auto-Discovery >Auto-Deploy policy group

To enable or disable autodeployment, set the following registry value to 0 or 1 respectively.
HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\AutoDeployment\Disable

Novell Setup Requirements

Note: The Windows OS SPI can be used with Netware 6.5 from version B.08.33 onwards. The MX60.NLM supports Netware 6.0 and 6.5.

The Windows OS SPI uses a proxy configuration to obtain information from the Novell systems that are managed. A Windows NT or Windows 2000-managed node must be selected to serve as a proxy for several Novell nodes. This proxy node is configured using the WINOSSPI-NW Proxy Node Config policy. The Novell proxy instrumentation (executables, scripts, etc.) is distributed to the Novell proxy when the Novell policies are deployed. The proxy then queries the configured Novell Nodes (using SNMP) to obtain performance data. If a threshold is passed, the information is forwarded to the management server and a message is displayed in the active message browser.

Setup Requirements: The management server must have Novell Client installed. After the Novell Client software is installed, respond to the prompt to reboot - Yes/No (dialog).

Managed Node: A Novell proxy node can be a Windows NT or a Windows 2000 node, but not a Novell Node. If a Windows NT node is elected to be a Novell proxy node, the following additional requirements must be satisfied:

• SNMP Service must be installed. Check if the SNMP Service is running by entering net start at the command prompt on the managed node and checking for SNMP in the returned list of services. If SNMP Service is not installed, you can locate it on the Windows NT 4.0 installation disk.
  
  Add the SNMP Service by doing the following:
  1. Place the Windows NT installation disk in the CD drive.
  2. Right-click on Network Neighborhood.
  3. Click Properties.
  4. Click the Service tab.
  5. Click the Add button.
  6. Select the SNMP Service entry.
  7. Click the OK button.
  8. Answer the prompt to reboot the server - Yes/No (dialog).
• After you add the SNMP Service, reapply any service packs and reboot the server.

Known Problems, Limitations, and Workarounds

The known problems, limitations, and workarounds for Windows OS SPI 08.90 are listed below.

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 the WINOSSPI-IISLogFileCollector policy is configured to collect data for. This also must be done on all the Windows 2003 64-bit managed nodes where the policy is deployed. The steps to modify the default log file path are as follows:

1. Go to the Administrative Tools menu and launch the Internet Information Services (IIS) Manager.
2. Right-click on Web Sites. The Properties page opens.
3. From the Web Site tab pane, click Properties in the Enable logging frame.
4. In the Logging Properties dialog box, change the Log file directory to any location that is not under %systemRoot%\system32.
5. Click OK.
WINOSSPI-IIScollector on NT4 needs MDAC 2.5 or later

By default, this policy is scheduled to run every hour. It aggregates web server event log records into 5-minute intervals and stores the records for historical reports.

This policy requires MDAC version 2.5 or later. If you want to use the WINOSSPI-IISCollector policy on Windows NT 4.0 systems, you must ensure that MDAC 2.5 or later is installed. Windows 2000 systems install MDAC with the operating system; therefore, WINOSSPI-IISCollector requires no additional software on Windows 2000 systems. If the policy is deployed to a system without MDAC 2.5, a critical message is sent to the display console indicating that MDAC is not present.

Stand-alone WINOSSPI Reporter installation requires custom install

When you install the WINOSSPI Reporter integration outside the OVO Installer (by running the .msi file directly), the SPI files are placed in the following directory: C:\Program Files\HP OpenView. If you had specified a different installation directory during the OV 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:
1. Double-click on the WINOSSPI-Reporter.msi file.
2. Select Custom and ensure that the WINOSSPI Reporter package is installed in the same directory as the stand-alone Reporter installation.
3. Click Next to start the installation of WINOSSPI Reporter.
4. Click Finish to complete the installation of WINOSSPI Reporter.

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 on 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 is displayed 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.

Policies names changed with Windows OS SPI B.08.20

Old Policy Name	New Policy Name
WINOSSPI-Dell4.3_FwdEventLogEntries	WINOSSPI-DellServer_FwdEventLogEntries
WINOSSPI-Dell_FwdEventLogEntries	WINOSSPI-DellServerAgent_FwdEventLogEntries

Policies names changed with Windows OS SPI B.08.33

Old Policy Name	New Policy Name
WINOSSPI-ADS_GlobalCatalogReads	WINOSSPI-ADS_DSReads
WINOSSPI-ADS_GlobalCatalogSearches	WINOSSPI-ADS_DSSearches
WINOSSPI-ADS_GlobalCatalogWrites	WINOSSPI-ADS_DSWrites
WINOSSPI-SysMon_Server_WorkItemStorages	WINOSSPI-SysMon_Server_WorkItemShortages

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 path names are disabled. The Microsoft Windows > Self Healing Services > Self Healing Info tool, can be run on the nodes to gather diagnostic data.

OpenView Performance Manager (OVPM) on a cluster node with no OVO installation

If you have installed the WINOSSPI-Reporter.msi on a Microsoft cluster with no OVO installation, the Windows OS SPI graphs will be accessible only from the cluster node where you have installed the WINOSSPI Reporter. To access the graphs provided by Windows OS SPI, on other cluster nodes with OVPM, you must make sure that the files listed in the following table are copied to the target directories.

OVPM Version	Files to be Copied	Target Directory
OVPM 4	VPI_Graphs_WINOSSPI_THIN.txt VPI_GraphsCODA.txt	<OvInstallDir>\newconfig
	VPI_Graph.txt VPI_GraphJava.txt VPI_Table.txt	<OvInstallDir>\newconfig\VPI_SkinMMC
OVPM5	VPI_Graphs_WINOSSPI_THIN.txt VPI_GraphsCODA.txt	<OvInstallDir>\newconfig\OVPM
	VPI_Graph.txt VPI_GraphJava.txt VPI_Table.txt	<OvInstallDir>\newconfig\OVPM\VPI_SkinMMC

Note: <OvInstallDir> is the directory in which you have installed OpenView products.

Verified Environments

The verified environments are as follows

OVO Management Server

This release of Windows OS SPI supports only OVO 7.5.

Supported Operating System Platforms

The supported managed node operating system platforms are as follows:

• Microsoft Windows NT 4.0 (Workstation, Server, Enterprise Edition)
• Microsoft Windows 2000 (Professional, Server, Advanced Server, Datacenter Server)
• Microsoft Windows XP Professional
• Microsoft Windows 2003 (All editions)

Managed Applications

Windows OS SPI manages the following applications.

Application	Version(s)
Microsoft SMS	Microsoft SMS 2.0, 2003
Microsoft Active Directory Services	Microsoft Windows 2000, 2003
Microsoft Exchange Server	Microsoft Exchange Server 5.5, 2000, and 2003
Microsoft IIS	Microsoft IIS 4.0, 5.0, and 6.0
Microsoft Terminal Service	Microsoft Windows NT, 2000, XP Professional Edition, and 2003.
Microsoft Proxy Server	Microsoft Proxy Server 2.0
Microsoft Certificate Server	Microsoft Certificate Server 1.0
Microsoft Cluster Server	Microsoft Windows 2000, 2003 (32 bit and 64 bit)
Microsoft Index Server	Microsoft Index Server 2.0
Message Queue Server	All versions on the supported operating system platforms are managed.
Microsoft Operations Manager	MOM 2000, 2005
Microsoft System Network Architecture (SNA) Server	Microsoft SNA 4.0
Microsoft Transaction Server	All versions on the supported operating system platforms are managed.
Microsoft Application Center Server	Microsoft Application Center Server 2000
Microsoft BIZ Talk Server	Microsoft BIZ Talk Server 2000, 2002
Microsoft Commerce Server	Microsoft Commerce Server 2000, 2002
Microsoft Host Integration Server	Microsoft Host Integration Server 2000 Standard Edition
Microsoft Internet Security and Acceleration	Microsoft Internet Security and Acceleration 2000, 2004
Microsoft Mobile Information Server	Microsoft Mobile Information Server 2000
Microsoft Site Server	Microsoft Site Server 3.0
Novell Netware	Novell Netware 5.x (5.0, 5.10) Novell Netware 6.x (6.0, 6.5) Windows OS SPI manages the supported versions of Novell Netware Server only if the IPX/SPX protocol is enabled on them. From this release of Windows OS SPI, management of Novell Netware Server 4.x is not provided.
Norton Antivirus	All versions on the supported operating system platforms are managed.
Network Associates McAfee	All versions on the supported operating system platforms are managed.
Citrix Metaframe	Citrix Metaframe 1.8

Local Language Support

This release of the Windows OS SPI will be available in the following languages:

• Japanese
• Simplified Chinese
• Korean

Integration with Other OpenView Solutions

Windows OS SPI integrates with the following versions of OpenView Reporter:

• 3.5
• 3.6

Support

Please visit the HP OpenView support web site at:

http://www.hp.com/managementsoftware/support

This web site provides contact information and details about the products, services, and support that HP OpenView offers.

HP OpenView 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 valuable support customer, you can benefit by being able to:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Submit enhancement requests online
• Download software patches
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

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://www.hp.com/managementsoftware/access_level

To register for an HP Passport ID, go to the following URL:

http://www.managementsoftware.hp.com/passport-registration.html

Legal Notices

©Copyright 1999-2006 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.

NetBSD C Library Source

Copyright © 1996-2002 Internet Software Consortium.

Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

$Id: COPYRIGHT,v 1.6.2.2 2002/02/12 06:05:48 marka Exp $

Portions Copyright © 1996-2001 Nominum, Inc.

Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND NOMINUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL NOMINUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.