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

What's New in This Release

Changed functionality

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.

Policies removed
  1. WINOSSPI-ADS_DNSServ_FwdAllInformation
  2. WINOSSPI-ADS_FwdAllInformationDS
  3. WINOSSPI-ADS_FwdAllInformationFRS
  4. WINOSSPI-Ex55 Exchange Application Information
  5. WINOSSPI-Ex60 Exchange Application Information
  6. WINOSSPI-HPOmniBackIIc_FwdAllInformation
  7. WINOSSPI-HPOmniBackIIc_FwdAllWarnErro
  8. WINOSSPI-IIS40_FtpServerFwdAllSystemInformation
  9. WINOSSPI-IIS40_FwdAllApplicationInformation
  10. WINOSSPI-IIS40_FwdAllSystemInformation
  11. WINOSSPI-IIS40_IndexServerFwdAllApplicationInformation
  12. WINOSSPI-IIS40_NntpServerFwdAllSystemInformation
  13. WINOSSPI-IIS40_SmtpServerFwdAllSystemInformation
  14. WINOSSPI-IIS50_FtpServerFwdAllSystemInformation
  15. WINOSSPI-IIS50_FwdAllApplicationInformation
  16. WINOSSPI-IIS50_FwdAllSystemInformation
  17. WINOSSPI-IIS50_IndexServerFwdAllApplicationInformation
  18. WINOSSPI-IIS50_NntpServerFwdAllSystemInformation
  19. WINOSSPI-IIS50_SmtpServerFwdAllSystemInformation
  20. WINOSSPI-McAfee_FwdAllInformation
  21. WINOSSPI-MF_FwdAllSysInformation
  22. WINOSSPI-MSCertSv_FwdAllInformation
  23. WINOSSPI-MSIndexServer_FwdAllInformation
  24. WINOSSPI-MSMQ_FwdAllInfo
  25. WINOSSPI-MSPS20_FwdAllInformation
  26. WINOSSPI-MSS-EventLog-Information
  27. WINOSSPI-MTS20_FwdAllApplInfo
  28. WINOSSPI-NAV_FwdAllApplInfo
  29. WINOSSPI-NAV_FwdAllSysInfo
  30. WINOSSPI-NET_ACFwdApplicationInformation
  31. WINOSSPI-NET_BizTalkServerFwdApplicationInformation
  32. WINOSSPI-NET_CommerceServerFwdApplicationInformation
  33. WINOSSPI-NET_HostIntegrationServerFwdAllInformation
  34. WINOSSPI-NET_ISAServerFwdApplicationInformation
  35. WINOSSPI-NET_MobileInformationServerFwdApplicationServerFwdApplicationInformation
  36. WINOSSPI-SNA40_FwdAllInformation
  37. WINOSSPI-SMS20_FwdAllInformation
  38. WINOSSPI-SS30_AcmServerFwdAllApplicationInformation
  39. WINOSSPI-SS30_AuthServerFwdAllApplicationInformation
  40. WINOSSPI-SS30_CommerceServerFwdAllApplicationInformation
  41. WINOSSPI-SS30_CrsServerFwdAllApplicationInformation
  42. WINOSSPI-SS30_GathererServerFwdAllApplicationInformation
  43. WINOSSPI-SS30_LdapServerFwdAllSystemInformation
  44. WINOSSPI-SS30_ListBldrServerFwdAllApplicationInformation
  45. WINOSSPI-SS30_MsgBldrServerFwdAllApplicationInformation
  46. WINOSSPI-SS30_SearchServerFwdAllApplicationInformation
  47. WINOSSPI-SS30_SiteServerFwdAllApplicationInformation
  48. WINOSSPI-VeritasBackupExec_FwdAllInformation
  49. WINOSSPI-WTS_FwdAllSysInformation
Policies with changed names

Migration and Upgrade Requirements and Procedure


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

Known Problems and Possible Workarounds

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:

  1. Go to the Administrative Tools menu and launch the Internet Information Services (IIS) Manager.
  2. Right-click "Web Sites." The Properties page opens.
  3. In the Web Site tab, 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 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:
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:
  1. Double-click the WINOSSPI-Reporter.msi file.
  2. Select "Custom" and make sure that the WINOSSPI Reporter package is installed in the same directory as the stand-alone Reporter installation.
  3. 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.

Fixed CRs in This Release

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.