File Name: dir4.22.00pf2_windows.txt IBM Director PE Critical Fix - peFix 2 For IBM Director Version 4.22 CONTENTS __________________________________________________________________ 1.0 Overview 1.1 Features or Support added 1.2 Issues Addressed 2.0 Supported Configurations 2.1 Supported Hardware Configurations 2.2 Supported Operating Systems 2.3 Supported Software Configurations 2.4 Limitations 3.0 Installation 3.1 Install Command Line Syntax 3.2 Package For The Web parameters 3.3 peFix Parameters 3.4 Install Examples 3.5 Limitations 3.6 XML Installation 4.0 Uninstallation 4.1 Uninstalling the peFix on IBM Director Agent 4.2 Uninstalling the peFix on IBM Director Server 5.0 Maintenance 5.1 dirpefixtool 5.1.1 dirpefixtool Command Line Syntax 5.1.2 dirpefixtool Parameters 5.1.3 dirpefixtool Examples 5.2 Upgrading to later versions of IBM Director 6.0 Technical Support and Information 7.0 Trademarks and Notices 8.0 Disclaimer 1.0 Overview __________________________________________________________________ 1.1 Features or Support added Installation of this peFix requires Windows Installer Version 3 to be installed on the target system. The peFix will automatically install Windows Installer Version 3 on the target system if it is not already installed. 1.2 Issues Addressed The following issues are addressed in this peFix: - APAR IC45960 Java out-of-memory errors caused by MPAConnections.dat - APAR IC47926 Incorrect temperature thresholds for IBM xSeries 255 - APAR IC46923 False temperature alerts for IBM ThinkCentre 8183 - No email sent for fatal ServeRAID battery-backup event - APAR IC47564 False voltage alerts for IBM xSeries 300 - Cannot add event user exit without modifying existing properties file classes/extensions/EventServerUserExit.properties - Access violation in twgipc.exe - APAR IC47566 Fans become loud on IntelliStation Z Pro - APAR IC47553 Java out-of-memory error while connecting to a service processor or management module - APAR IC47926 False voltage alert on IntelliStation Z Pro - APAR IC47910 wmicimserver crashes on Japanese agent - APAR IC48253 PegasusProviderAdapter stops unexpectedly in point-to-point environment This peFix is cummulative and includes fixes for the following issues that were addressed in dir4.22.00pf1: - APAR IC46730 A security condition has been identified such that the IBM Director server can be made inoperative from a remote location. - APAR IC46959 A security condition has been identified such that the IBM Director server can be made inoperative from a remote location. - APAR IC46662 IBM Director Software Distribution can not deploy multiple categories onto multiple systems. - APAR IC46862 IBM Director Software Distribution fails with "System Offline" error. - APAR IC46864 Software Distribution fails with "file not found error". - APAR IC47033 Fibre channel adapter field in inventory database is too short. dir4.22.00pf2 can be installed if dir4.22.00pf1 has already been installed. 2.0 Supported Configurations __________________________________________________________________ peFix dir4.22.00pf2 is intended for the configurations listed in this section. This peFix is not for use with other versions of the product and may cause serious functionality problems or data loss if misused. Do not install this peFix on versions or configurations other than those listed in this readme. 2.1 Supported Hardware Configurations dir4.22.00pf2.exe applies to any supported xSeries hardware running IBM Director Server 4.22 or IBM Director Agent 4.22. 2.2 Supported Operating Systems Windows 2003 Server (all editions) Windows 2000 Server (all editions) 2.3 Supported Software Configurations IBM Director 4.22 Server IBM Director 4.22 Agent 2.4 Limitations Administrator privileges are required for the account used to install the peFix. The NOREBOOT option must be specified for the install if using IBM Director software distribution to apply this peFix. Popups may be seen the target system during installation of the patch. These are harmless and can be ignored. After the package has been successfully installed, the target system must then be rebooted. 3.0 Installation __________________________________________________________________ Running the peFix executable will automatically extract the necessary files to a temporary location and start the installation process. Follow the resulting prompts to complete the installation unless doing a silent or unattended installation. 3.1 Install Command Line Syntax dir4.22.00pf2.exe -s -a [SILENT/UNATTENDED] LOG= VERBOSE DEBUG [NOREBOOT/FORCEREBOOT] 3.2 Package For The Web (PFTW) parameters -a Required by PFTW (-a Must appear before peFix parameters) -s Silent PFTW install 3.3 peFix Parameters SILENT Used for installs with no user interface (assumes unattended) UNATTENDED Used for installs that are unattended but not necessarily silent DONOTSTOPSERVICES Prevents IBM Director servives from stopping during the patch install, a reboot is required for the path to take effect. LOG= Allows user to specify alternate log file location VERBOSE Enable all MSI logging DEBUG Used to turn on higher level of logging NOREBOOT Suppresses reboots requested by the installer FORCEREBOOT Forces the system to reboot once the package installation is finished HELP Provides description of parameters 3.4 Install Examples Silent Install with reboot: dir4.22.00pf2.exe -s -a SILENT FORCEREBOOT Unattended Install without reboot: dir4.22.00pf2.exe -s -a UNATTENDED Silent install with a debug log: dir4.22.00pf2.exe -s -a SILENT LOG="c:\peFix.log" DEBUG NOTE: The -a argument must precede all peFix arguments. 3.5 Limitations The SILENT and UNATTENDED parameters should not be used in conjunction with each other. 3.6 XML Installation This patch can be installed by using the provided XML file with IBM Director Update Assistant. When you import this XML file into IBM Director, the IBM Director Update Assistant creates a software package. Then, you can use the IBM Director Software Distribution task to distribute this patch to the managed systems. 4.0 Uninstallation __________________________________________________________________ 4.1 Uninstalling the peFix on IBM Director Agent It is not required to uninstall IBM Director Agent peFixes before upgrading to a new version of IBM Director Agent. 4.2 Uninstalling the peFix on IBM Director Server In order to upgrade to a later version of IBM Director Server, the IBM Director Server peFix IC46862a must be uninstalled before upgrading. This can be accomplished through the Add/Remove programs utility within Control Panel. 5.0 Maintenance __________________________________________________________________ 5.1 dirpefixtool A patch utility, dirpefixtool.exe, is available in the \IBM\Director\Support directory. It is a command line executable that can be used to view and manage installed Director peFixes. 5.1.1 dirpefixtool Command Line Syntax dirpefixtool.exe LOG= DEBUG SILENT LIST 5.1.2 dirpefixtool Parameters LOG= Allows user to specify alternate log file location DEBUG Used to turn on higher level of logging SILENT Used with the log= parameter to allow for logging of the dirpefixtool results without displaying them to the screen (assumes unattended) LIST List the Director patches installed 5.1.3 dirpefixtool Examples List all peFixes and write them to the log file C:\Text.log dirpefixtool.exe "LOG=C:\Text.log" LIST 5.2 Upgrading to later versions of IBM Director In order to upgrade to a later version of IBM Director Server, the IBM Director Server peFix IC46862a must be uninstalled before upgrading. This can be accomplished through the Add/Remove programs utility within Control Panel. It is not required to uninstall IBM Director Agent peFixes before upgrading to a new version of IBM Director. 6.0 Technical Support and Information __________________________________________________________________ IBM Home Page http://www.ibm.com IBM Support Web Site http://www.pc.ibm.com/support IBM Universal Manageability Web Site http://www.pc.ibm.com/us/pc/um/index.html 7.0 Trademarks and Notices __________________________________________________________________ The following terms are trademarks of the IBM Corporation in the United States or other countries or both: AIX, IBM, Netfinity, Netfinity Director, Universal Manageability Services, IBM Director, OS/2, RS/6000, LANClient Control Manager, Remote Deployment Manager, Tivoli IT Director, and Tivoli Management Environment The following are trademarks of their respective owners: Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation IPX, Novell, and NetWare are trademarks of Novell, Incorporated UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited Java and Hot Java are trademarks of Sun Microsystems, Inc Other company, product, and service names may be trademarks or service marks of others. All other brand or product names are trademarks or registered trademarks of their respective holders. 8.0 Disclaimer __________________________________________________________________ THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. The following are trademarks of their respective owners: Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation IPX, Novell, and NetWare are trademarks of Novell, Incorporated UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited Java and Hot Java are trademarks of Sun Microsystems, Inc Other company, product, and service names may be trademarks or service marks of others. All other brand or product names are trademarks or registered trademarks of their respective holders.