Smart Plug-in for Windows B.08.33
Release Notes
The Windows OS SPI contains functionality for monitoring, controlling, and reporting on the health of the complete Windows enterprise. It provides preconfigured policies, tools, and reports for managing the Windows XP, Windows 2003, Windows 2000, and Windows NT 4.0 operating systems; a broad range of Microsoft applications; and the most common Microsoft applications on the Windows server systems. It encompasses most of the functionality of the following HP products: Winmodule and Win+SPI from the VantagePoint for Windows 6.0 release, the Microsoft functionality of the HP OpenView VantagePoint Internet Services Passive Monitoring Component version A.03.50, and a number of policies to duplicate policy coverage found in ManageX.
ManageX customers should read the following manual for information on the conversion process: "HP OpenView Guide for Upgrading from ManageX/OV Express to OpenView Operations 7.0 for Windows" (ManageXUpgrade.pdf).
What's New in This Release
Migration and Upgrade Requirements and Procedure
Known Problems and Possible Workarounds
Fixed CRs in This Release
Changed functionality
- OvSpiModelCleaner.exe and OvSpiModelTool.dll have been enhanced to provide for deletion of subtrees in the service model.
- OvSpiModelCleaner.exe and OvSpiModelTool.dll are packaged with the Windows OS SPI and will be shipped for OpenView Operations for Windows 2004.2 SPI CD only. OpenView Operations for Windows 7.5 will ship this component with the enhanced functionality.
- The Windows OS SPI removes the AD service model during upgrade because the AD SPI has a new enhanced service model that can discover AD forests.
Policies numbered 11.0 incorporate improvements to the previous version. Unchanged policies are numbered 10.0, 9.0, 8.0, or 7.0.
Policies changed
Most of the following policies were modified to fix CR# ROSmm36446. The change involved resetting the threshold counter of the metric value below threshold value for a consecutive number of readings. The remainder were changed to fix defects.
- WINOSSPI-ADS_SecErrorsLogon
- WINOSSPI-CpuBottleneck_Win2k
- WINOSSPI-CpuBottleneck_NT4
- WINOSSPI-DiskBottleneck_Win2k
- WINOSSPI-DiskBottleneck_NT4
- WINOSSPI-IIS40_ActiveServerPages_MemoryAllocated
- WINOSSPI-IIS40_ActiveServerPages_RequestsQueued
- WINOSSPI-IIS40_InternetInformationServicesGbl_CachedFileHandl
- WINOSSPI-IIS40_InternetInformationServicesGbl_DirectoryList
- WINOSSPI-IIS40_InternetInformationServicesGbl_Objects
- WINOSSPI-IIS40_InternetInformationServicesGbl_CacheHitsPct
- WINOSSPI-IIS40_InternetInformationServicesGbl_FileCacheHitsPc
- 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
- WINOSSPI-McAfee_McShield
- WINOSSPI-McAfee_AVSyncMgr
- WINOSSPI-MemoryBottleneck_NT4
- WINOSSPI-MemoryBottleneck_Win2k
- WINOSSPI-MF_Process_PctProcessorTime_IBrowser
- WINOSSPI-MSIndexServer_ContentIndex_FilesToBeFiltered
- WINOSSPI-MSIndexServer_ContentIndex_NumDocumentsFiltered
- WINOSSPI-MSIndexServer_IndexingService_FilesToBeIndexed
- WINOSSPI-MSIndexServer_IndexingService_NumDocumentsIndexed
- WINOSSPI-MSPS20_FailingRequestsSec
- WINOSSPI-MSPS20_ThreadPoolFailures
- WINOSSPI-MSPS20_TotalDroppedFrames
- WINOSSPI-MSPS20_TotalFailedSocksSessions
- WINOSSPI-MSPS20_TotalFailingRequests
- WINOSSPI-Net_BytesTotalSec
- WINOSSPI-Net_CurrentCommands
- WINOSSPI-Net_NetworkErrorsSec
- WINOSSPI-Net_ReadsDeniedSec
- WINOSSPI-SS30_AvailableBytes
- WINOSSPI-SysMon_AvgDiskSecTransfer
- WINOSSPI-SysMon_CpuSpikeCheck-NT4
- WINOSSPI-SysMon_CpuSpikeCheck-Win2k
- WINOSSPI-SysMon_PageFileCheck
- WINOSSPI-SysMon_PageReadsSec
- WINOSSPI-SysMon_Redirector_WritesDeniedSec
- WINOSSPI-SysMon_Server_PoolNonpagedFailures
- WINOSSPI-SysMon_Server_PoolPagedFailures
- WINOSSPI-SysMon_Server_WorkItemShortages
- WINOSSPI-SysMon_System_ProcessorQueueLength
- WINOSSPI-SysMon_VirtualMemCheck
- WINOSSPI-WTS_System_PctProcessorTime-NT4
- WINOSSPI-WTS_System_TotalErrors-NT4
- WINOSSPI-WTS_System_TotalFrames-NT4
- WINOSSPI-WTS_TerminalServiceSession_PctProcessorTime-Win2k
- WINOSSPI-WTS_TerminalServiceSession_TotalErrors-Win2k
- WINOSSPI-WTS_TerminalServiceSession_TotalFrames-Win2k
- WINOSSPI-WTS_TerminalServices_ActiveSessions-Win2k
- WINOSSPI-WTS_User_PctProcessorTime-NT4
- WINOSSPI-SysMon_PhysicalMemCheck
- WINOSSPI-SysMon_DiskBusyCheck
- WINOSSPI-SysMon_DiskFullCheck
Policies removed
- WINOSSPI-ADS_DNSServ_FwdAllInformation
- WINOSSPI-ADS_FwdAllInformationDS
- WINOSSPI-ADS_FwdAllInformationFRS
- WINOSSPI-Ex55 Exchange Application Information
- WINOSSPI-Ex60 Exchange Application Information
- WINOSSPI-HPOmniBackIIc_FwdAllInformation
- WINOSSPI-HPOmniBackIIc_FwdAllWarnErro
- 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 with changed names
- WINOSSPI-ADS_GlobalCatalogReads to WINOSSPI-ADS_DSReads
- WINOSSPI-ADS_GlobalCatalogSearches to WINOSSPI-ADS_DSSearches
- WINOSSPI-ADS_GlobalCatalogWrites to WINOSSPI-ADS_DSWrites
- WINOSSPI-SysMon_Server_WorkItemStorages to WINOSSPI-SysMon_Server_WorkItemShortages
CAUTION: To avoid loss of collected data, review the detailed upgrading
information contained in the following two guides that are enclosed in the
OVO Version 7.21 CD package in the OVO Guides folder: HP OpenView
Operations/Performance for Windows Upgrade Guide Version 7.21
(OVOWUpgrade.pdf) and HP OpenView Guide for Upgrading from ManageX/OV
Express to OpenView Operations 7.0 for Windows (ManageXUpgrade.pdf)
.
Required patches for different versions of the OVO Management Server
If you are using OVO 7.10 or OVO 7.20, you must install the following patches to
upgrade to version B.08.33 of the Windows OS SPI.
- If you have OVO 7.10, the required patches are OVOW_00050 and OVOW_00075.
- If you have OVO 7.20, the required patch is OVOW_00075.
Upgrading from VPW 6.01/6.10
Policies can be automatically converted or imported into the OVO for Windows 7.20
release, with the following limitations:
- VPW Policies: MDC policies cannot be converted. The OVO for Windows 7.20 release integrates the configuration of data collections into the Measurement Threshold policy type and log data to CODA.
- VPO Policies: Automatic conversion and import are available for all policies except ECS, MOM, and MPE/ix templates.
Upgrading from ManageX 4.23
There is no automatic policy conversion.
Collected data in the ManageX reporting database is not be converted to the OVO for Windows reporting database.
CAUTION:
- All collected data is discarded during the upgrade process.
- If the collected data is required, it must be manually exported
on each node or collected via Service Reporter before upgrading.
- To view reports of historical data collected with ManageX, use
the ManageX console.
- Customized ManageX reports cannot be migrated to OVO for
Windows 7.20 and must be recreated with Crystal Reports.
WINOSSPI-IIScollector fails on Windows 2003 64-bit
WINOSSPI-IIScollector on NT4 needs MDAC 2.5 or greater
Novell setup requirements
Stand-alone WINOSSPI Reporter installation requires custom install
Limitation for the MS SQL Server policies
WINOSSPI-SysMon_DiskFullCheck policy shows incorrect error
WINOSSPI-IISCollector fails on Windows 2003 64-bit
The workaround is to change the default location of the IIS Logfiles to some other directory outside of the %systemroot% \system32 folder. This needs to be done on all the websites the WINOSSPI-IISLogFileCollector policy is configured to collect data for. This also needs to be done on all the Windows 2003 64-bit managed nodes where the policy is deployed. The steps to modify the default logfile path are as follows:
- Go to the Administrative Tools menu and launch the Internet Information Services (IIS) Manager.
- Right-click "Web Sites." The Properties page opens.
- In the Web Site tab, 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 greater. If you wish to use the
WINOSSPI-IISCollector policy on Windows NT 4.0 systems, you must make sure that
MDAC 2.5 or greater 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.
Novell setup requirements
Note: The Windows OS SPI 8.3 supports Netware 6.5. 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 will be 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 appears in the active message browser.
Setup Requirements: The Management Server must have Novell Client installed on the Management Server. 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, 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 find 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 Network Neighborhood.
3. Select Properties.
4. Select Service Tab.
5. Click the Add button.
6. Select 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. After you add
the service packs, reboot the server.
Stand-alone WINOSSPI Reporter installation requires custom install
When you install the WINOSSPI Reporter integration outside of the OVW Installer
(by running the .msi file directly), the SPI files are placed in C:\Program Files\HP
OpenView. If you specify a different installation directory, select "Custom" when
prompted for Setup Type.
In the Custom Setup dialog, change the "Install to:" directory to match the
installation directory you used when installing Reporter.
To install WINOSSPI Reporter on a stand-alone Reporter System:
- Double-click the WINOSSPI-Reporter.msi file.
- Select "Custom" and make sure that the WINOSSPI Reporter package is
installed in the same directory as the stand-alone Reporter installation.
- Click Next.
Limitation for the MS SQL Server policies
The Windows OS SPI SQL Server policies that monitor the Event Log and the SQL Server and SQL Server Agent processes do not work with named SQL Server 2000 instances, only the default instance.
WINOSSPI-SysMon_DiskFullCheck policy shows incorrect error
For every partition that does not need to be monitored, a rule can be added to the policy to skip processing of the diagnostic/utility partitions.
CR#: JAGaf20052
Description: WINOSSPI-ADS_SecErrorsLogon Policy generates false alarms.
CR#: JAGaf05274
Description: OVOW 7.x, ADSPI, winmgmt.exe consumes much CPU when querying WMI.
CR#: JAGaf06703
Description: WINOSSPI-ADS_GlobalCatalogWrites/Reads/Searches misleading.
©Copyright 2004 Hewlett-Packard Development Company, L.P.
All other product names are the property of their respective trademark or service mark holders and are hereby acknowledged.