Patch Name: PHSS_29794 Patch Description: s700_800 11.X OV EXSPIa.03.30 Intermediate Patch for OVO/U Creation Date: 04/01/02 Post Date: 04/02/11 Repost: 04/03/26 The Patch Description and Products information in the patch documentation was updated to more accurately describe the patch contents. Hardware Platforms - OS Releases: s700: 11.00 11.11 s800: 11.00 11.11 Products: HP OV SPI for Microsoft Exchange A.03.30 Filesets: EXSPI.EXSPI,fr=A.03.30,fa=HP_UX_10/11,v=HP Automatic Reboot?: No Status: General Release Critical: No Category Tags: defect_repair general_release Path Name: /hp-ux_patches/s700_800/11.X/PHSS_29794 Symptoms: PHSS_29794: Change Request: 8606331634 Metric 610 produces wrong values. The Mailbox Summary reports display incorrect data for some of the mailbox stores. This value is the result of an overflow condition. Generally but not necessarily it will be much greater than the correct result. Change Request: 8606331606 Metric 843-844 does not take into account the users who are in a different container than the default 'Users' container. An example of the symptom: In the trace file only users from the "Users" container show up (CN=Users). See following sample line from the trace file: Binding string is: LDAP://CN=MSXSPIANSER,CN=Users,DC=msg-im,DC=smtp, \ DC=agilent,DC=com In this case IM enabled users are located in the IMusers container which does never show up in the trace file. There are currently more than 500 users configured one of which is myself. These users should show up with their real name (e.g. John Taylor). The Users container only holds generic accounts like e.g. MSXSPI. Note that IM enabled users may be in general located in several different containers with arbitrary names. As far as I can see they are distinguished by several IM specific attributes being set vs. not being set for users that are not IM enabled. So they cannot be identified by just their location in the AD structure. Change Request: 8606331641 The metric 6 with exspi_e2k reports wrong numbers. Trace indicates it is looking for the logfiles at the wrong location or retrieving wrong size values. This seems to work correctly with Exchange 5.5 (on a different server). Change Request: R555018707 Due to a Microsoft bug in processing DOS shell scripts, "EXSPI Add Data Source" configuration step, will fail on managed nodes that run NT4 and OpenView Performance Agent (also known as MeasureWare Agent). As a result of this failure MeasureWare EXSPI logfiles will not be created and Exchange SPI will not be able to log metric data. "EXSPI Add Data Source", however, works fine on managed nodes running Windows 2000 or any managed node using the new HP OpenView subagent (also known as CODA) included with OVO 7.0. Defect Description: PHSS_29794: Change Request: 8606331634 Metric 610 produces wrong values. The Mailbox Summary reports display incorrect data for some of the mailbox stores. This value is the result of an overflow condition. Generally but not necessarily it will be much greater than the correct result. Resolution: The data type is corrected to prevent overflow which was causing the problem. Change Request: 8606331606 Metric 843-844 does not take into account the users who are in a different container than the default 'Users' container. An example of the symptom: In the trace file only users from the "Users" container show up (CN=Users). See following sample line from the trace file: Binding string is: LDAP://CN=MSXSPIANSER,CN=Users,DC=msg-im,DC=smtp, \ DC=agilent,DC=com In this case IM enabled users are located in the IMusers container which does never show up in the trace file. There are currently more than 500 users configured one of which is myself. These users should show up with their real name (e.g. John Taylor). The Users container only holds generic accounts like e.g. MSXSPI. Note that IM enabled users may be in general located in several different containers with arbitrary names. As far as I can see they are distinguished by several IM specific attributes being set vs. not being set for users that are not IM enabled. So they cannot be identified by just their location in the AD structure. Resolution: This problem is resolved and now this metric takes into account the users who are in a different container than the default 'Users' container. Change Request: 8606331641 The metric 6 with exspi_e2k reports wrong numbers. Trace indicates it is looking for the logfiles at the wrong location or retrieving wrong size values. This seems to work correctly with Exchange 5.5 (on a different server). Resolution: EXSPI has been fixed to list all the correct transaction logging paths for an Exchange 2000 server and calculate the correct free disk space (metric 0005) and the total size of logging files for each storage group (metric 0006). Change Request: R555018707 Due to a Microsoft bug in processing DOS shell scripts, "EXSPI Add Data Source" configuration step, will fail on managed nodes that run NT4 and OpenView Performance Agent (also known as MeasureWare Agent). As a result of this failure MeasureWare EXSPI logfiles will not be created and Exchange SPI will not be able to log metric data. "EXSPI Add Data Source", however, works fine on managed nodes running Windows 2000 or any managed node using the new HP OpenView subagent (also known as CODA) included with OVO 7.0. Resolution: EXSPI has been fixed so that the script responsible for adding the data source works fine on machines running NT4 and OVPA. Enhancement: No SR: 8606331641 8606331634 8606331606 R555018707 Patch Files: EXSPI.EXSPI,fr=A.03.30,fa=HP_UX_10/11,v=HP: /opt/OV/EXSPI/bin/EXSPI-Reporter.msi /var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/ nt/monitor/exspi_e2k.exe.Z /var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/ nt/monitor/exspi_e55.exe.Z /var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/ nt/cmds/exspiDDF.bat what(1) Output: EXSPI.EXSPI,fr=A.03.30,fa=HP_UX_10/11,v=HP: /opt/OV/EXSPI/bin/EXSPI-Reporter.msi: None /var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/ nt/monitor/exspi_e2k.exe.Z: None /var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/ nt/monitor/exspi_e55.exe.Z: None /var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/ nt/cmds/exspiDDF.bat: None cksum(1) Output: EXSPI.EXSPI,fr=A.03.30,fa=HP_UX_10/11,v=HP: 1022529627 5357 /var/opt/OV/share/databases/OpC/mgd_node/ customer/ms/intel/nt/cmds/exspiDDF.bat 2989219191 250691 /var/opt/OV/share/databases/OpC/mgd_node/ customer/ms/intel/nt/monitor/exspi_e2k.exe.Z 3759996579 153761 /var/opt/OV/share/databases/OpC/mgd_node/ customer/ms/intel/nt/monitor/exspi_e55.exe.Z 302792778 637440 /opt/OV/EXSPI/bin/EXSPI-Reporter.msi Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: SPISOL_00001: sparcSOL: 2.6 2.7 2.8 Patch Package Size: 870 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_29794 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_29794.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_29794. If you do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHSS_29794.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_29794.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_29794.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_29794: This patch contains the Exchange SPI reporter MSI (Microsoft Installer) package. After installing the patch on the management server machine, the reporter package gets copied under the location - /opt/OV/EXSPI/bin/EXSPI-Reporter.msi The above specified MSI file needs to be copied to the Windows machine on which OV Reporter has been installed on. Note: Before installing the MSI file on the Windows machine, the following actions need to be performed - + Check if Exchange SPI reporter MSI is already installed on the machine. + If already installed, have any of the reporter templates for Exchange SPI been altered/customized after the installation ? If these customizations need to be saved/retained, then please rename or save the changed reporter templates under a name different from the original one. + After performing the above step, remove the Exchange SPI reporter package using 'Add or Remove Programs' applet in the Control Panel. + Now, install the newly copied EXSPI-Reporter.msi.