HP OpenView Smart Plug-in for Microsoft Windows OS

Release Notes

April 2005

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

In This Version
Installation Notes
Enhancements and Fixes
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:

Windows OS SPI on a clustered OVO Management Server
Windows OS SPI can be used with OVO 7.5 running on a Microsoft Cluster Server.
Microsoft Systems Management Server (SMS) 2003 management
This release of Windows OS SPI manages SMS 2003 in addition to SMS 2.0 and provides features as follows:
- Autodiscovery of SMS 2003 server
- Autodeployment of the Microsoft Windows > Microsoft BackOffice Applications > Auto Deployment > MS Systems Management Server (SMS) 2003 policy group
- New reports and graphs as listed in the New reports and graphs section
Microsoft Operations Manager 2005 (MOM 2005) integration
With this release, Windows OS SPI provides integration with MOM 2005 in addition to MOM 2000 and provides the following features:
- Autodiscovery of MOM 2005
- Forwarding of MOM 2005 alerts to the OVO Management Server
Enhanced integration with HP System Insight Manager (HPSIM) versions 4.0, 4.1, and 4.2
Windows OS SPI now provides integration with HPSIM versions 4.1 and 4.2 in addition to HPSIM version 4.0. The other features include:
- Single step tool integration to retrieve the status of a tool execution
- Option to launch the HPSIM page in a context-sensitive manner
Insight Manager Agent integration
The Simple Network Management Protocol (SNMP) trap policies are updated for this release of Windows OS SPI to provide additional or new traps for the Insight Manager Agent 7.20 Management Information Bases (MIBs) shown in the link below.
Click here for a list of the Insight Manager Agent 7.20 MIBs.
- CPQFCA
- HS_Agent
- CPQTHRSH
- CPQSTSYS
- CPQSM2
- CPQRPM
- CPQSWCC
- CPQSCSI
- CPQSTDEQ
- CPQIDA
- CPQSINFO
- CPQRACK
- CPQCR
- CIMTRAPS
- CPQHOST
- CPQNIC
- CPQIDE
- CPQHLTH
- CPQCLUS
- CPQICA
- CPQCMC
Data collection using the Self-healing services in the event of a problem on the managed node
Microsoft Cluster Server Management on Itanium 64-bit system running Microsoft Windows 2003 operating system
Novell Netware Server 4.x management feature is discontinued from this release

NOTE: The Microsoft SQL Server management feature is removed from this release. You can use the HP OpenView Smart Plug-in for Microsoft SQL Server to manage SQL server environments.

New policy groups

The following policy groups are added in this release:

Microsoft Windows > Microsoft BackOffice Applications > Auto-Deploy > MS Systems Management Server (SMS) 2003
Microsoft Windows > Microsoft BackOffice Applications > Manual-Deploy > MS Systems Management Server (SMS) 2003 > Diagnostic
Microsoft Windows > Microsoft Windows Core > Manual-Deploy > MS Terminal Server > MS Windows 2000, XP and 2003 > Additional

Policy group names changed

The policy group names that have changed are as follows:

The MS Operation Manager 2000 policy group is renamed to MS Operations Manager.
This change is implemented because Windows OS SPI now integrates with MOM 2005 in addition to MOM 2000.
The MS System Management Server (SMS) 2.0 policy group is renamed to MS Systems Management Server (SMS) 2.0
The Commerce Server 2000 policy group is renamed to Commerce Server 2000 and 2002
This change is implemented because Windows OS SPI now manages MIcrosoft Commerce Server 2002 in addition to Microsoft Commerce Server 2000.
The MS Biztalk Server 2000 policy group is renamed to MS Biztalk Server 2000 and 2002
This change is implemented because Windows OS SPI now manages Microsoft BIZ Talk Server 2002 in addition to Microsoft BIZ Talk Server 2000.
The MS Windows 2000 policy groups listed below have been renamed to MS Windows 2000, XP and 2003:
- Microsoft Windows > Microsoft BackOffice Applications > Manual-Deploy > MS Index Server > MS Windows 2000
- Microsoft Windows > Microsoft Windows Core > Auto-Deploy > MS Terminal Server > MS Windows 2000
- Microsoft Windows > Microsoft Windows Core > Manual-Deploy > MS Terminal Server > MS Windows 2000
- Microsoft Windows > Microsoft Windows Core > Auto-Deploy > Network Infrastructure > RAS > MS Windows 2000
- Microsoft Windows > Microsoft Windows Core > Manual-Deploy > Network Infrastructure > RAS > MS Windows 2000
- Microsoft Windows > Microsoft Windows Core > Auto-Deploy > Operating System > MS Windows 2000
- Microsoft Windows > Microsoft Windows Core > Manual-Deploy > Operating System > MS Windows 2000
The policies are renamed because the policies in the MS Windows 2000 policy groups can be used with Microsoft Windows XP and Microsoft Windows 2003 platforms in addition to the Microsoft Windows 2000 platform. Windows OS SPI policies that contain Win2k in the policy name will work on Microsoft Windows XP and 2003.

Removed policy group

The Microsoft Windows > Self-Deployment policy group is removed from this release. With the earlier versions of the Windows OS SPI, the policies in the Self-Deployment policy group were deployed to the Management Server. The policies in this policy group were used to autodeploy the appropriate policies based on the operating system version on the managed nodes:

WINOSSPI-RAS_DeployPolicyWhenServiceDiscovered
WINOSSPI-WTS_DeployPolicyWhenServiceDiscovered
WINOSSPI-OS_DeployPolicyWhenServiceDiscovered

The policies listed above are removed from the Management Server agent node during an in-place upgrade or a side-by-side migration. If the agent on the Management Server is not running during the upgrade or migration, you must manually undeploy these policies once the agent is running. You must remove these policies from the Management Server.

With this release, Windows OS SPI uses attribute-based autodeployment to deploy the required policies on the managed nodes.

New Policies

The policies that have been added in this release are as follows:

WINOSSPI-InsightManager_FwdCIMTraps
WINOSSPI-InsightManager_FwdRPMTraps
WINOSSPI-InsightManager_FwdOneMsgPerTrap
WINOSSPI-SMS2003_SMS_SITE_COMPONENT
WINOSSPI-SMS2003_SMS_CLIENT_SERVICE
WINOSSPI-SMS2003_SMS_EXECUTIVE
WINOSSPI-SMS2003_SMS_SQL_MONITOR
WINOSSPI-SMS2003_FwdClientWarnError
WINOSSPI-SMS2003_FwdGenericWarnError
WINOSSPI-SMS2003_FwdServerWarnError
WINOSSPI-SMS2003_Logging

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

Policies changed

The policies changed in this release are grouped as follows:

Internet Information Services (IIS) policies

WINOSSPI-IIS40_ActiveServerPages_MemoryAllocated
WINOSSPI-IIS40_ActiveServerPages_RequestsQueued
WINOSSPI-IIS40_InternetInformationServicesGbl_CachedFileHandl
WINOSSPI-IIS40_InternetInformationServicesGbl_CacheHitsPct
WINOSSPI-IIS40_InternetInformationServicesGbl_DirectoryList
WINOSSPI-IIS40_InternetInformationServicesGbl_FileCacheHitsPc
WINOSSPI-IIS40_InternetInformationServicesGbl_Objects
WINOSSPI-IIS40_MSMQQueue_MessagesInQueue
WINOSSPI-IIS40_Process_PageFaultsSec_inetinfo
WINOSSPI-IIS40_Process_PctProcessorTime_inetinfo
WINOSSPI-IIS40_Process_PrivateBytes_inetinfo
WINOSSPI-IIS40_Process_ThreadCount_inetinfo
WINOSSPI-IIS40_Process_WorkingSet_inetinfo
WINOSSPI-IIS40_Server_BytesTransmittedSec
WINOSSPI-IIS40_WebServices_CurrentAnonymousUsers
WINOSSPI-IIS50_ActiveServerPages_RequestsQueued
WINOSSPI-IIS50_IndexingService_FilesToBeIndexed
WINOSSPI-IIS50_IndexingService_NoDocumentsIndexed
WINOSSPI-IIS50_IndexingService_RunningQueries
WINOSSPI-IIS50_InternetInformationServicesGbl_FileCacheHitsPc
WINOSSPI-IIS50_MSMQQueue_MessagesInQueue
WINOSSPI-IIS50_Process_PageFaultsSec_inetinfo
WINOSSPI-IIS50_Process_PctProcessorTime_inetinfo
WINOSSPI-IIS50_Process_PrivateBytes_inetinfo
WINOSSPI-IIS50_Process_ThreadCount_inetinfo
WINOSSPI-IIS50_Process_WorkingSet_inetinfo
WINOSSPI-IIS50_Server_BytesTransmittedSec
WINOSSPI-IIS50_WorkingSet_AvailableBytes

Insight Manager policies

WINOSSPI-InsightManager_FwdChannelArrayTraps
WINOSSPI-InsightManager_FwdClusterTraps
WINOSSPI-InsightManager_FwdCMCTraps
WINOSSPI-InsightManager_FwdDriveArrayTraps
WINOSSPI-InsightManager_FwdHostOSTraps
WINOSSPI-InsightManager_FwdICATraps
WINOSSPI-InsightManager_FwdIDEDriveTraps
WINOSSPI-InsightManager_FwdNICTraps
WINOSSPI-InsightManager_FwdPCConfigTraps
WINOSSPI-InsightManager_FwdRackTraps
WINOSSPI-InsightManager_FwdRaidControllerTraps
WINOSSPI-InsightManager_FwdRIBTraps
WINOSSPI-InsightManager_FwdSCSIDevicesTraps
WINOSSPI-InsightManager_FwdSTEAMTraps
WINOSSPI-InsightManager_FwdStorageSysTraps
WINOSSPI-InsightManager_FwdSvrHealthTraps
WINOSSPI-InsightManager_FwdSWCCTraps
WINOSSPI-InsightManager_FwdSysInfoTraps
WINOSSPI-InsightManager_FwdThresholdMgmtTraps

The listed Insight Manager policies are enhanced to forward new SNMP traps from the Insight Manager Agent version 7.20 to OVO.

Autodiscovery policies

WINOSSPI-MSWINApp_AutoDiscovery

WINOSSPI-MSWINSys_AutoDiscovery

WINOSSPI-HPSIM_AutoDiscovery

System monitor policies

WINOSSPI-SysMon_DiskBusyCheck

WINOSSPI-SysMon_DiskFullCheck

Commerce server policy

WINOSSPI-NET_CommerceServerServices

This policy is enhanced to monitor services of Commerce Server 2002 in addition to Commerce Server 2000.

Microsoft Windows Terminal Server policy

WINOSSPI-WTS_TermService

This policy is enhanced to monitor the terminal service process on Windows XP and Windows 2003.

Microsoft Message Queue Server policies

WINOSSPI-MSMQ_journalQueue
WINOSSPI-MSMQ_QueueSize

These policies are enhanced to handle multiple instances and to display the instances that have exceeded the threshold limit in the message browser.

Active Directory services policy

WINOSSPI-ADS_KDCFailureGrantTicket

This policy is enhanced to include verification for event 672, which indicates a failure to grant authentication tickets.

NOTE: Policies with version 12.0 indicate new policies or improvements to the previous version of the policies.

Obsolete policies

The following sections list the policies that have been discontinued with each release (obsolete policies) of the Windows OS SPI. An in-place upgrade or a side-by-side migration does not remove the obsolete policies from the Management Server.

Policies made obsolete with Windows OS SPI release B.08.75

WINOSSPI-OS_DeployPolicyWhenServiceDiscovered
WINOSSPI-RAS_DeployPolicyWhenServiceDiscovered
WINOSSPI-WTS_DeployPolicyWhenServiceDiscovered
WINOSSPI-MSWINSvc_ServiceDeletionMsg
WINOSSPI-MSS-SrvProcMon-SQLExecutive
WINOSSPI-MSS-EventLog-Errors
WINOSSPI-MSS-EventLog-Warnings
WINOSSPI-MSS-SrvProcMon-MSSQLServer
WINOSSPI-MSS-SrvProcMon-SQLServerAgent

Policies made obsolete with Windows OS SPI release B.08.33

WINOSSPI-ADS_DNSServ_FwdAllInformation
WINOSSPI-ADS_FwdAllInformationDS
WINOSSPI-ADS_FwdAllInformationFRS
WINOSSPI-Ex55 Exchange Application Information
WINOSSPI-Ex60 Exchange Application Information
WINOSSPI-HPOmniBackII_FwdAllInformation
WINOSSPI-HPOmniBackII_FwdAllWarnError
WINOSSPI-IIS40_FtpServerFwdAllSystemInformation
WINOSSPI-IIS40_FwdAllApplicationInformation
WINOSSPI-IIS40_FwdAllSystemInformation
WINOSSPI-IIS40_IndexServerFwdAllApplicationInformation
WINOSSPI-IIS40_NntpServerFwdAllSystemInformation
WINOSSPI-IIS40_SmtpServerFwdAllSystemInformation
WINOSSPI-IIS50_FtpServerFwdAllSystemInformation
WINOSSPI-IIS50_FwdAllApplicationInformation
WINOSSPI-IIS50_FwdAllSystemInformation
WINOSSPI-IIS50_IndexServerFwdAllApplicationInformation
WINOSSPI-IIS50_NntpServerFwdAllSystemInformation
WINOSSPI-IIS50_SmtpServerFwdAllSystemInformation
WINOSSPI-McAfee_FwdAllInformation
WINOSSPI-MF_FwdAllSysInformation
WINOSSPI-MSCertSv_FwdAllInformation
WINOSSPI-MSIndexServer_FwdAllInformation
WINOSSPI-MSMQ_FwdAllInfo
WINOSSPI-MSPS20_FwdAllInformation
WINOSSPI-MSS-EventLog-Information
WINOSSPI-MTS20_FwdAllApplInfo
WINOSSPI-NAV_FwdAllApplInfo
WINOSSPI-NAV_FwdAllSysInfo
WINOSSPI-NET_ACFwdApplicationInformation
WINOSSPI-NET_BizTalkServerFwdApplicationInformation
WINOSSPI-NET_CommerceServerFwdApplicationInformation
WINOSSPI-NET_HostIntegrationServerFwdAllInformation
WINOSSPI-NET_ISAServerFwdApplicationInformation
WINOSSPI-NET_MobileInformationServerFwdApplicationServerFwdApplicationInformation
WINOSSPI-SNA40_FwdAllInformation
WINOSSPI-SMS20_FwdAllInformation
WINOSSPI-SS30_AcmServerFwdAllApplicationInformation
WINOSSPI-SS30_AuthServerFwdAllApplicationInformation
WINOSSPI-SS30_CommerceServerFwdAllApplicationInformation
WINOSSPI-SS30_CrsServerFwdAllApplicationInformation
WINOSSPI-SS30_GathererServerFwdAllApplicationInformation
WINOSSPI-SS30_LdapServerFwdAllSystemInformation
WINOSSPI-SS30_ListBldrServerFwdAllApplicationInformation
WINOSSPI-SS30_MsgBldrServerFwdAllApplicationInformation
WINOSSPI-SS30_SearchServerFwdAllApplicationInformation
WINOSSPI-SS30_SiteServerFwdAllApplicationInformation
WINOSSPI-VeritasBackupExec_FwdAllInformation
WINOSSPI-WTS_FwdAllSysInformation

Policies made obsolete with Windows OS SPI release B.08.30

WINOSSPI-ADS_PrivilegedAccounts
WINOSSPI-ADS_SecDirectoryServiceAccess
WINOSSPI-ADS_SecErrAccessPermissions_userbased
WINOSSPI-ADS_SecErrGrantedAccess_userbased
WINOSSPI-MSCS_FwdCritLogEntries
WINOSSPI-TopTools_FwdAllAppInformation
WINOSSPI-TopTools_FwdAllApplWarnError

Policies made obsolete with Windows OS SPI release B.08.20

WINOSSPI-ADS_DirComputerModif
WINOSSPI-ADS_SAMServPropChange
WINOSSPI-SysMon_Cache_DataMapsSec
WINOSSPI-SysMon_Cache_MDLReadsSec
WINOSSPI-SysMon_Cache_PinReadHitsPct
WINOSSPI-SysMon_Cache_ReadAheadsSec
WINOSSPI-SysMon_CacheFaultsSec
WINOSSPI-SysMon_Memory_PagesInputSec
WINOSSPI-SysMon_Memory_PagesSec
WINOSSPI-SysMon_PageFaultsSec

Policies made obsolete with Windows OS SPI release B.08.00

Refer the Guide for Upgrading to OpenView Operations for Windows Version 7.10 for policies made obsolete with Windows OS SPI release B.08.00.

Tool group names changed

The tool group names that have changed are as follows:

The MS Operation Manager 2000 tool group is renamed to MS Operations Manager
The tool group was renamed because Windows OS SPI now integrates with MOM 2000 and MOM 2005.
The MS SMS 2.0 tool group is renamed to MS Systems Management Server
The tool group was renamed because Windows OS SPI now provides SMS 2.0 and SMS 2003 management features.
The MS Terminal Server (NT 4.0) tool group is renamed to MS Terminal Server
The tool group was renamed because Windows OS SPI can be used with all versions of the Terminal Server or Service on the managed agent platforms.

New tool

The Self Healing Info tool has been added in this release to support collection of diagnostic data on specified nodes.

New reports and graphs

The new reports and graphs added for this release are as follows:

The g_SMS-SWMSummary.rpt report has been added in this release to show the statistics of SMS 2003 software metering.
The new graphs for SMS 2.0 and 2003 in this release are as follows:
- SMS Site Component Memory
- SMS Site Component CPU
- SMS Executive Memory
- SMS Executive CPU
- SMS Client Service Monitor CPU
- SMS Client Service Monitor Memory
- SMS SQL Monitor Memory
- SMS SQL Monitor CPU

Reports modified

All the reports have been modified to work with HP OpenView Reporter 3.6

Reports removed

The reports that have been removed in this release are as follows:

g_WINOSSPI_MSSQLServerCPU.rpt
g_WINOSSPI_MSSQLServerMemory.rpt

Graphs removed

The graphs that have been removed in this release are as follows:

Microsoft SQL Server CPU
Microsoft SQL Server Agent CPU
Microsoft SQL Server Agent Memory
Microsoft SQL Server Memory

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 (released before the OVO 7.5 release) can be upgraded or migrated:

B.08.33
B.08.30
B.08.20
B.08.00

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

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

The policies listed in the obsolete policies section are removed from the managed nodes
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:
- 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 will remove these policies from the managed nodes, but not 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

If a managed node is not accessible from the Management Server during an upgrade or migration, you can remove the obsolete 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:

Microsoft Windows instrumentation
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.

Enhancements and Fixes

The following items (identified by error tracking number) are fixed in the current software release. To display details about each software fix, click the error tracking number. To hide details, click again.

QXCR1000198767: X-axis of report not readable.

	PROBLEM:	In WinOSSPI reports, contents on the X-axis are not clearly displayed.
	CAUSE:	This is a problem with the CPU Overall Status report shipped with the earlier versions of Windows OS SPI. The report shows a mingled chart for the CPU Detail report when data is collected for a long period of time.
	FIX:	This problem is addressed by providing four reports for the different time ranges (Yesterday, Last Week, Last Month, All), which implement different granularities and summarizations in the charts and calculations.

QXCR1000113889: WINOSSPI-SysMon_DiskFullCheck policy shows incorrect error.

	PROBLEM:	The WINOSSPI-SysMon_DiskFullCheck policy displays incorrect information about the disk space available on systems.
	CAUSE	This problem was caused by using perfmon instead of Embedded Performance Component (EPC). EPC does not check for diagnostics and system partitions. The system partitions can include diagnostic or hardware configuration programs, programs to start operating systems, or other manufacturer-supplied programs.
	FIX:	The policy WINOSSPI-SysMon_DiskFullCheck now uses EPC to check the logical disk usage.

QXCR1000223796: policy WINOSSPI-MSMQ_JournalQueue failed.

	PROBLEM:	Monitoring of Microsoft Message Queue fails.
	CAUSE	The WINOSSPI-MSMQ_JournalQueue and the WINOSSPI-MSMQ_QueueSize policies fail to handle multiple instances of queues in the embedded scripts.
	FIX:	The embedded scripts in the policies have been enhanced to handle multiple instances of queues.

QXCR1000223308: No OPCMON value received for WINOSSPI-MSCS_ClusterUpdate policy.

	PROBLEM:	The monitor agent sends error messages to the message browser indicating that the script invoked by WINOSSPI-MSCS_ClusterUpdate policy does not return the state of the monitored object.
	CAUSE	This problem was caused by faulty instrumentation. The RegNodeCheck.js script was the cause for the faulty instrumentation.
	FIX:	The RegNodeCheck.js script has been modified to return the state of the monitored object on all return paths.

Known Problems, Limitations, and Workarounds

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

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:

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

WINOSSPI-IIScollector on NT4 needs MDAC 2.5 or greater

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:

Double-click on the WINOSSPI-Reporter.msi file.
Select Custom and ensure that the WINOSSPI Reporter package is installed in the same directory as the stand-alone Reporter installation.
Click Next to start the installation of WINOSSPI Reporter.
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
OVPM 4	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
OVPM5	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.
HP (Compaq) Insight Manager	HP Insight Manager 7.0, 7.2
HP Systems Insight Manager	HP Systems Insight Manager 4.0, 4.1, and 4.2
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:

Support

Please visit the HP OpenView web site at: http://www.managementsoftware.hp.com/

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

You can also go directly to the support web site at:

http://support.openview.hp.com/

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
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 log in. Many also require an active support contract. To find more information about support access levels, go to the following URL:

http://support.openview.hp.com/access_level.jsp

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

https://passport.hp.com/hpp2/newuser.do

To view release notes and other documentation:

Click using hp software--> product manuals.

The product manuals search window opens. It is located at:
http://ovweb.external.hp.com/lpe/doc_serv/
In the select product list, click Smart Plug-ins for Microsoft Windows.
In the select version list, click b.08.75.
In the OS list, click Windows.
To start the search, click Open or Download.

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 URL:

http://www.adobe.com

Legal Notices

The information contained herein is subject to change without notice.

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.

NetBSD C Library Source

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.

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.