ITCAM for Microsoft(R) App: Exchange Server 6.2.3-TIV-ITM_EXCHG-IF0009

Download Description

(C) Copyright International Business Machines Corporation 2012. All
rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager for
Microsoft(R) Applications:Microsoft(R) Exchange Server Agent,
Version 6.2.3


Component ID: 5724B98EO

Interim Fix 0009, (6.2.3-TIV-ITM_EXCHG-IF0009)

Date: Oct 22, 2012

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices


1.0 General description
=======================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4.

2.0 Problems fixed
==================
The following problems are addressed by this fix.

2.1 APARs
----------
APAR: IV28174
Abstract: "IS Mailbox Size" attribute shows incorrect value.
Additional Information: Microsoft Exchange Server Agent 6.2.3 shows
incorrect value of "IS Mailbox Size" attribute in "MS Exchange
IS Private" attribute group.

APAR: IV28175
Abstract: Exchange agent shows garbage value if recovery database
is configured.
Additional Information: Microsoft Exchange Server Agent 6.2.3 shows
garbage instances for "MS Exchange IS Private" attribute group
if Recovery mailbox database is configured.


2.2 Defects
-------------
None.

2.3 Enhancements
-----------------
Microsoft Exchange Server 2010 SP2 support

2.4 Superseded fixes
--------------------
6.2.3-TIV-ITM_EXCHG-IF0008
6.2.3-TIV-ITM_EXCHG-IF0007
6.2.3-TIV-ITM_EXCHG-IF0006
6.2.3-TIV-ITM_EXCHG-IF0005
6.2.3-TIV-ITM_EXCHG-LA0004
6.2.3-TIV-ITM_EXCHG-IF0003
6.2.3-TIV-ITM_EXCHG-IF0002
6.2.3-TIV-ITM_EXCHG-IF0001

2.5 APARS and defects included from superseded fixes
-----------------------------------------------------
6.2.3-TIV-ITM_EXCHG-IF0008
--------------------------
APAR: IV24956
Abstract: Exchange agent has high memory consumption while fetching
data for exchange topology.
Additional Information: Exchange Agent has high memory consumption
while fetching data for Exchange Topology workspace.This
was causing when querying data for "Exchange topology" from
AD.Following error was reported in agent logs at
location \IBM\ITM\TMAITM6\logs.
"-----> ADS Get Column failed <-----"
"HResult: 0x80005008, Return Code: ADS5008, Msg: Message
text not found."

6.2.3-TIV-ITM_EXCHG-IF0007
--------------------------
APAR: IV23457
Abstract: Reachability Test result is NO sometimes even though
target email address is reachable.
Additional Information: When Microsoft Exchange Server Agent
6.2.3, is configured to test the reachability on Exchange
Server 2010, sometimes Exchange Web Service API throws
exception while checking response email. Due to that
agent shows target email address as unreachable even
if response mail is received.

APAR: IV23053
Abstract: 'KEX_REQD_SERVICES' key is not updated if Topology
Interval is blank in config panel.
Additional Information: When Microsoft Exchange Server Agent
6.2.3, is configured on Exchange Server, Agent does
not update 'KEX_REQD_SERVICES' registry key if no
value is provided for "Exchange Topology Interval"
config parameter during agent configuration.

APAR: IV22849
Abstract: Microsoft Exchange Server agent crashes while fetching
the mailbox details attribute group data.
Additional Information: Sometimes "Mailbox_Details.log" file
contains garbage lines at the end of file. If
"Mailbox_Details.log" file contains such garbage
lines agent crashes while fetching mailbox details
attribute group data from portal.

APAR: IV21670
Abstract: Mailbox Details workspace shows zero value for
"Mailbox Size" and "Mailbox Max Size" attributes.
Additional Information: Mailbox Details workspace shows zero value
for "Mailbox Size" and "Mailbox Max Size" attributes if
locale is set to other than English.

APAR: IV20910
Abstract: Reachability feature does not work if configured user
is created outside the "Users" container of the active
directory.
Additional Information: When Microsoft Exchange Server Agent 6.2.3
is configured to test Reachability on Microsoft Exchange
Server 2010, it is failing to test the reachability of
target email address.

6.2.3-TIV-ITM_EXCHG-IF0006
--------------------------
APAR: IV15395
Abstract: "ROUND TRIP RESPONSE TIME" ATTRIBUTE IS ALWAYS
SHOWN AS 0.00 ON THE PORTAL.
Additional Information: When MS Exchange Server Agent is configured
on Exchange Server 2010 or Exchange Server 2007 with
"MS Exchange Reachability" enabled, it always shows value
of "Round Trip Response Time" as 0.00 irrespective status
of Reachability.

APAR: IV16560
Abstract: AGENT CRASHES ON EXCHANGE SERVER 2010 HAVING ONLY
CLIENT ACCESS AND HUB TRANSPORT ROLE INSTALLED.
Additional Information: When MS Exchange Server Agent is installed on
the Exchange Server 2010 having only Client Access and Hub
Transport Role it crashes immediately.

APAR: IV16561
Abstract: "ACTIVATION PREFERENCE" ATTRIBUTE SHOWS INCORRECT VALUE ON
THE PORTAL.
Additional Information: When MS Exchange Server Agent is configured
on Exchange Server 2010, value shown for
"Activation Preference" does not match with value configured
in the Exchange Management Console.

APAR: IV17642
Abstract: In Mailbox Details and Public Folder Details, data columns
for some instances get shifted to left.
Additional Information: When Microsoft Exchange Server Agent is
installed on the Exchange Server 2007 having Japanese Locale,
agent fails to parse Mailbox Details and Public Folder
Details log files correctly. Due to this data columns get
shifted.

6.2.3-TIV-ITM_EXCHG-IF0005
--------------------------
APAR: IV13135
Abstract: EXCHANGE AGENT CRASHES ON NON-MAILBOX ROLE WHEN HDC IS
CONFIGURED FOR IS PUBLIC ATTRIBUTE GROUP
Additional Information: When we configure Historical Data Collection
for IS Public attribute group on Exchange server which
doesn't have Mailbox role, the data for other attribute
groups take a long time to display on the portal. Also the
agent crashes in a couple of days.

6.2.3-TIV-ITM_EXCHG-LA0004
--------------------------
APAR: IV12832
Abstract: TEC Server fails to start with kex.baroc file
Additional Information: When kex.baroc file is added to rule base in
TEC server then TEC server fails to start.

6.2.3-TIV-ITM_EXCHG-IF0003
--------------------------
APAR: IV09199
Abstract: IF THE CUSTOMER SETS THE CTIRA_HOSTNAME VIA MTEMS,
IT DOES NOT GET REFLECTED ON THE PORTAL.
Additional Information: When the CTIRA_HOSTNAME is set via MTEMS,
it does not get reflected on the Portal.

6.2.3-TIV-ITM_EXCHG-IF0002
--------------------------
APAR: IV08715
Abstract: EXCHANGE AGENT SHOWS SERVER STATUS DOWN.
Additional Information: When Exchange Server Agent configured to
monitor Exchange Server 2003, it always shows Server Status
as down irrespective of the status of Exchange Services.

6.2.3-TIV-ITM_EXCHG-IF0001
--------------------------
APAR: IZ99715
Abstract: Exchange Agent hung while fetching data for Server Status.
Additional Information: Exchange Agent hung while fetching data for
Server Status workspace.This was causing when querying
data for "Percent Log Free space" attribute from AD.
Following error was reported in agent logs at location
<%CANDLE_HOME%>\IBM\ITM\TMAITM6\logs:

"-----> ADS Get Column failed <-----"
"HResult: 0x80005008, Return Code: ADS5008, Msg: Message
text not found."

3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in the IBM
Tivoli Monitoring For Microsoft Applications:
Exchange Agent User's Guide, version 623.

http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

The following link is for the Tivoli platform and application
support matrix. Please refer to this matrix for the latest
certification information.

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

3.1 Prerequisites for this fix
------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring, Version 6.2.2 FP2 onwards
- IBM Tivoli Composite Application Manager for Microsoft
Applications, Version 6.2.3 : Microsoft Exchange Server Agent.

As this fix is cumulative, it can be installed on any fix level
for this version, release and mod level above the prerequisite.

4.0 Image directory contents
============================
This fix image contains the following files:
- 6.2.3-TIV-ITM_EXCHG-IF0009.README - This README file
- 6.2.3-TIV-ITM_EXCHG-IF0009.tar - Fix archive .tar format
- 6.2.3-TIV-ITM_EXCHG-IF0009.zip - Fix archive .zip format.

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file
if you are working in a Windows(R) environment.

The tar file and zip file contains the following files:
- 6.2.3-TIV-ITM_EXCHG-IF0009/kex_tems_teps_tepd_if0009.zip
- 6.2.3-TIV-ITM_EXCHG-IF0009/kex_tems_teps_tepd_if0009.tar
- 6.2.3-TIV-ITM_EXCHG-IF0009/kex_winnt_tema_if0009.cab
- 6.2.3-TIV-ITM_EXCHG-IF0009/kex_wix64_tema_if0009.cab
- 6.2.3-TIV-ITM_EXCHG-IF0009/KEXWINNT.dsc
- 6.2.3-TIV-ITM_EXCHG-IF0009/KEXWIX64.dsc
- 6.2.3-TIV-ITM_EXCHG-IF0009/ex_dd_062300000.xml
- 6.2.3-TIV-ITM_EXCHG-IF0009/ex_dd_062300009.xml
- 6.2.3-TIV-ITM_EXCHG-IF0009/ex_dd.properties.
- 6.2.3-TIV-ITM_EXCHG-IF0009/itmpatch
- 6.2.3-TIV-ITM_EXCHG-IF0009/itmpatch.exe

Each tar or cab file has updates to the IBM Tivoli Enterprise
Monitoring Server component for a specific platform. The platform
that each file applies to is included in its name.

5.0 Installation instructions
=============================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.

5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled
'Prerequisites for this fix' must be installed before this fix
can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(6.2.3-TIV-ITM_EXCHG-IF0009.tar or .zip) to a temporary
directory on the system that contains the agent code to be
updated. For the purpose of this README, the symbol
<TEMP> represents the fully qualified path to this directory.
Note: On Windows systems, this includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Use the "itmpatch" command to install the fix for that agent
platform. For more information on the "itmpatch" command, see
section 6.2.

On Windows systems, if the fix was expanded to
<TEMP>\6.2.3-TIV-ITM_EXCHG-IF0009, then navigate to
<TEMP>\6.2.3-TIV-ITM_EXCHG-IF0009 directory and run below command.


For 32 bit Agent:
> itmpatch -h <CANDLEHOME>
-i kex_winnt_tema_if0009.cab

For 64 bit Agent:
> itmpatch -h <CANDLEHOME>
-i kex_wix64_tema_if0009.cab

5.3 Remote agent update
-----------------------
1. Transfer the appropriate archive file
(6.2.3-TIV-ITM_EXCHG-IF0009.tar or .zip) to a temporary
directory on the IBM Tivoli Enterprise Monitoring Server system.
For the purpose of this README, the symbol <TEMP> represents
the fully qualified path to this directory.
Note: On Windows systems, this path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. To add the agent fix bundles into the remote deploy depot, use
the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems.
For more information on the "tacmd addBundles" command,
see the IBM Tivoli Monitoring Administrator's Guide.

For 32 bit deployment:

On UNIX systems,
if the fix was expanded to <TEMP>/6.2.3-TIV-ITM_EXCHG-IF0009:

> $CANDLEHOME/bin/tacmd addBundles -n
-p WINNT
-i <TEMP>/
6.2.3-TIV-ITM_EXCHG-IF0009

On Windows systems,
if the fix was expanded to <TEMP>\6.2.3-TIV-ITM_EXCHG-IF0009:

> %CANDLE_HOME%\bin\tacmd addBundles -n
-p WINNT
-i <TEMP>\
6.2.3-TIV-ITM_EXCHG-IF0009

For 64 bit deployment:

On UNIX systems,
if the fix was expanded to <TEMP>/6.2.3-TIV-ITM_EXCHG-IF0009:
> $CANDLEHOME/bin/tacmd addBundles -n
-p WIX64
-i <TEMP>/
6.2.3-TIV-ITM_EXCHG-IF0009

On Windows systems,
if the fix was expanded to <TEMP>\6.2.3-TIV-ITM_EXCHG-IF0009:

> %CANDLE_HOME%\bin\tacmd addBundles -n
-p WIX64
-i <TEMP>\
6.2.3-TIV-ITM_EXCHG-IF0009

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.
-p Specifies the platform code or codes of the products to add.
The platform value corresponds to the value that is
displayed in the Host Type field as a result of running the
viewDepot or listBundles command.

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM
Tivoli Monitoring Administrator's Guide.

On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> $CANDLEHOME/bin/tacmd updateAgent -t EX
-n <Managed system name>
-v 062300009

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t EX
-n <Managed system name>
-v 062300009

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (EX), not three characters (kex).
- The node (-n) for the "tacmd updateAgent" command is the
managed system name of the operating system (OS) agent to be
updated. The target node for an updateAgent command is always
an OS agent.

5.4 Agent support update
------------------------
Use the following steps to update the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise
Portal Desktop.

1. Transfer the appropriate archive file
(6.2.3-TIV-ITM_EXCHG-IF0009.tar or .zip) to the IBM Tivoli
Enterprise Monitoring Servers, IBM Tivoli Enterprise Portal
Servers, or Tivoli Enterprise Portal Desktops.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Expand the archive file (kex_tems_teps_tepd_if0009.tar or .zip)
that contains the updates for Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise
Portal Desktop using the "tar" command on UNIX systems or an
extract utility on Windows systems. This creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.

GUI installation option
------------------------
The GUI can be started by using one of the following commands
from within the CD-ROM directory.

On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-j <JAVAHOME> - Optional. The fully-qualified path to the
"bin" directory where Java(R) is installed.
The location of Java on your system might
vary.

When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not
the component directory. The installer can install updates for
multiple components at the same time.

The next panel presented by the Application Support Installer
asks for the selection of which Tivoli Monitoring components
you want to add application support to.
For this fix, the check boxes should be set as follows:

checked - Tivoli Enterprise Monitoring Server(TEMS)
checked - Tivoli Enterprise Portal Server(TEPS)
unchecked - Tivoli Enterprise Desktop Client(TEPD)

Continue through the remaining GUI panels selecting the
Microsoft Exchange Server 06.23.00.09 support to complete the
installation.

If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise
Portal Browser was running when the update was installed, it
must be restarted.

Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory.

Note: Using the silent installation option for Linux and zLinux
operating systems requires the following files contained in
interim fix 6.2-TIV-ITM_ASI-IF0001 for ITM to be copied to
CD-ROM directory:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0001.README".

On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]

On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-r <response file> - Required. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and
modified as per your environment.

-j <JAVAHOME> - Optional. The fully-qualified path to the
"bin" directory where Java(R) is installed.
The location of Java on your system might
vary.

6.0 Additional installation information
=======================================
This patch is to be applied on top of the GA version of IBM
Tivoli Monitoring Version 6.2.3, Exchange Server Agent.


6.1 Installation instructions for agent baroc file
--------------------------------------------------
The fix 6.2.3-TIV-ITM_EXCHG-IF0009 also includes changes to the
baroc file (available in 6.2.3-TIV-ITM_EXCHG-LA0004). If you
have already installed the baroc file from the
6.2.3-TIV-ITM_EXCHG-LA0004,there are no additional installation
steps to follow .If not , refer to IBM Tivoli Monitoring,
Version 6.2.2 FP2, Installation and Setup Guide under
"Installing monitoring agent .baroc files on the event server" in
" Setting up event forwarding to Tivoli Enterprise Console" section
for more information.

6.2 Additional information on using "itmpatch" command
----------------------------------------------------
The "itmpatch" command has the following syntax:

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t <patch_file_directory> | <patch_file>

itmpatch -h <installation home>
-i <patch_file_directory> | <patch_file>

where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be
installed
-t Generates a report of the actions to be taken by the patch.


For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this must include the
drive letter.
<TEMP> represents the fully qualified directory
specification, where the fix is located. On Windows systems, this
must include the drive letter.

6.3 Verifying the update
------------------------
1. To verify the agent was updated correctly, use the "tacmd"
command to view the agent's current version after the agent is
restarted. You are required to log in to a Tivoli Enterprise
Monitoring Server prior to viewing the agent version.

For example:
On a UNIX systems, where $CANDLEHOME is the IBM Tivoli
Monitoring installation directory, the default location is
'/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t EX

On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\ibm\itm'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %CANDLE_HOME%\bin\tacmd listSystems -t EX

Note: The component (-t) for the "tacmd listSystems" command is
specified as two characters (EX), not three characters (KEX).

When the agent update is successful, after recycling the agent
version is: 06.23.00.09

2. To verify the agent support files were updated correctly, use
the "kincinfo" command on Windows systems or the "cinfo" command
on Linux or UNIX systems. The sample output below shows the
versions of the Tivoli Enterprise Portal Server, Tivoli
Enterprise Monitoring Server, or Tivoli Enterprise Portal
Desktop systems after this fix has been successfully applied.

On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

*********** Wed Oct 22 16:31:54 EDT 2012 ******************
User: root Groups: root bin daemon sys adm disk wheel
Host name : esx3-pg3-440 Installer Lvl:06.22.08.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory

a4 Monitoring Agent for i5/OS
tms Version: 06.22.08.00

ax IBM Tivoli Monitoring Shared Libraries
li6263 Version: 06.22.08.00
lx8263 Version: 06.22.08.00
lx8266 Version: 06.22.08.00

cq Tivoli Enterprise Portal Server
lx8263 Version: 06.22.08.00

cw Tivoli Enterprise Portal Browser Client
lx8263 Version: 06.22.08.00

ex Monitoring Agent for Microsoft Exchange Server
tms Version: 06.23.00.09
tps Version: 06.23.00.09
tpw Version: 06.23.00.00

gs IBM GSKit Security Interface
li6243 Version: 07.40.27.00
lx8266 Version: 07.40.27.00

hd Warehouse Proxy
lx8266 Version: 06.22.08.00
tms Version: 06.22.08.00
tps Version: 06.22.08.00
tpw Version: 06.22.08.00

it TEC GUI Integration
tps Version: 06.22.08.00
tpw Version: 06.22.08.00

iv IBM Tivoli Enterprise Portal Server Extensions Update
li6263 Version: 06.10.35.00

iw IBM Tivoli Enterprise Portal Server Extensions
li6263 Version: 06.10.35.00


On Windows Systems:
--------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

*********** Monday, October 22, 2012 11:58:44 AM ************
User : Administrator Group : NA
Host Name : PS7426 Installer : Ver: 062300000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory

IN Windows Install Component
WINNT Version: 06.23.00.00 Build: 201108030209

IN TEP Desktop Windows Install Component
WINNT Version: 06.23.00.00 Build: 201108030209

IN TEMS Windows Install Component
WINNT Version: 06.23.00.00 Build: 201108030209

IN TEP Server Windows Install Component
WINNT Version: 06.23.00.00 Build: 201108030209

IN ITM 6.x Agent Install Component
WINNT Version: 06.23.00.00 Build: 201108030209

CJ Tivoli Enterprise Portal Desktop Client
WINNT Version: 06.23.00.00 Build: d1228a

CQ Tivoli Enterprise Portal Server Agent
WINNT Version: 06.23.00.00 Build: d1228a

CQ Tivoli Enterprise Portal Server
WINNT Version: 06.23.00.00 Build: d1228a

CW Tivoli Enterprise Portal Browser Client
WINNT Version: 06.23.00.00 Build: d1228a

EX Microsoft Exchange Server Support
WINNT Version: 06.23.00.09 Build: 22923

EX Microsoft Exchange Server Support
WINNT Version: 06.23.00.09 Build: 22923

EX Microsoft Exchange Server Support
WINNT Version: 06.23.00.00 Build: 10801

EX Microsoft Exchange Server Support
WINNT Version: 06.23.00.00 Build: 10801

GL Tivoli Enterprise Monitoring Agent Framework
WINNT Version: 06.23.00.00 Build: d1228a

GS IBM GSKit Security Interface
WINNT Version: 07.40.27.00 Build: d0111a

HD Warehouse Proxy Agent
WINNT Version: 06.23.00.00 Build: d1228a

HD Warehouse Proxy
WINNT Version: 06.23.00.00 Build: d1228a

HD Warehouse Proxy
WINNT Version: 06.23.00.00 Build: d1228a

HD Warehouse Proxy
WINNT Version: 06.23.00.00 Build: d1228a

HD Warehouse Proxy
WINNT Version: 06.23.00.00 Build: d1228a

IT TEC GUI Integration
WINNT Version: 06.23.00.00 Build: d1211a

IT TEC GUI Integration
WINNT Version: 06.23.00.00 Build: d1211a

IT TEC GUI Integration
WINNT Version: 06.23.00.00 Build: d1211a

IU IBM HTTP Server
WINNT Version: 07.00.00.00 Build: d1211a

IW Tivoli Enterprise Portal Server Extensions
WINNT Version: 07.00.15.00 Build: d1211a

JM Embedded JVM
WINNT Version: 05.12.01.00 Build: e1211a

KF IBM Eclipse Help Server
WINNT Version: 06.23.00.00 Build: d1211a

MS Tivoli Enterprise Monitoring Server
WINNT Version: 06.23.00.00 Build: d1228a

NT Monitoring Agent for Windows OS
WINNT Version: 06.23.00.00 Build: 12161

NT Monitoring Agent for Windows OS
WINNT Version: 06.23.00.00 Build: 12161

NT Monitoring Agent for Windows OS
WINNT Version: 06.23.00.00 Build: 12161

NT Monitoring Agent for Windows OS
WINNT Version: 06.23.00.00 Build: 12161

SY Summarization and Pruning Agent
WINNT Version: 06.23.00.00 Build: d1177a

SY Summarization and Pruning Agent
WINNT Version: 06.23.00.00 Build: d1177a

SY Summarization and Pruning Agent
WINNT Version: 06.23.00.00 Build: d1177a

SY Summarization and Pruning Agent
WINNT Version: 06.23.00.00 Build: d1177a

SY Summarization and Pruning Agent
WINNT Version: 06.23.00.00 Build: d1177a

T1 File Transfer Enablement
WINNT Version: 07.30.00.00 Build: 201000000000

UE Tivoli Enterprise Services User Interface Extensions
WINNT Version: 06.23.00.00 Build: d1228a

UI Tivoli Enterprise Services User Interface
WINNT Version: 06.23.00.00 Build: 201108030209


7.0 Known problems and workarounds
==================================

Abstract: Remote agent update fails for OS agent version
06.22.02.00
Problem: In case of Remote agent update using OS agent (version
06.22.02.00), the update of agent fails with the error:

KDY1031E: The agent installation command
<CANDLEHOME>\bin\itmpatch.exe -h <CANDLEHOME> -i
<CANDLEHOME>\tmaitm6\agentdepot\XX\062300009\
XXX_winnt_tema_if009.cab
returned an error with the return code 34 . The agent
was not installed because there is not enough disk
space on the server or you do not have permission to
install the agent.

Workaround: This is the problem with OS agent version 06.22.02.00
and has been fixed in version 06.22.03.00.
For successful remote agent update use OS agent version
06.22.01.00 or 06.22.03.00.

Abstract: Upgrading from an IF/LA to another IF/LA or Provisional
does not work (IZ84841)
Problem: Upgrading from an Interim Fix to an Interim Fix or
Provisional does not work and the following message is
displayed:

KDY0041E: The agent bundle XX is already updated to the
highest version 062300010 found in the depot and deployed
to <hostname>.

Workaround: The fix for this APAR is contained in the following
maintenance packages:
6.2.2-TIV-ITM-FP0004

Abstract: Applying 32-bit program updates with itmpatch on 64-bit
Windows systems fails (IZ73759)
Problem: Using the itmpatch utility to update 32-bit programs
fails to update machines running IBM Tivoli Monitoring
6.2.2 Fix Pack 1 on 64-bit Windows platforms. The
returned user message states that the update is not
applicable to the machines architecture.

Workaround: The fix for this APAR is contained in the following
maintenance packages:
6.2.2-TIV-ITM-FP0003

Abstract: The version of the patches that is displayed in
"Deployment Summary workspace" of the "Enterprise"
navigator item is incorrect.(IZ84841)
Problem: The version of the patches that is displayed in
"Deployment Summary workspace" of the "Enterprise"
navigator item. e.g The version displayed is of the
format "062101040" but the expected is "062101004".

Workaround: Issue is solved with OS and ITM (TEMS) version 622FP4.

Abstract: Wrong password type is used on a 64-bit machine.
(IZ96600)
Problem: When configuring the MS Exchange agent via remote
deploy, the 64-bit version of the cryptographic
routines are used with the 32-bit agent and the MS
Exchange agent configuration fails. The problem occurs
on a 64-bit Windows system running a 64-bit NT agent
and a 32-bit MS Exchange Server agent.

Workaround: The fix for this APAR is contained in the following
maintenance packages:
6.2.2-TIV-ITM-FP0006

8.0 Additional product information
==================================
None.

9.0 Notices
===========
This information was developed for products and services offered in
the United States. IBM may not offer the products, services, or
features discussed in this document in other countries. Consult your
local IBM representative for information on the products and services
currently available in your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is
the user's responsibility to evaluate and verify the operation of any
non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document
does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.

Some states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply to
you.

Trademarks and service marks
------------------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered
trademarks of International Business Machines Corp., registered in
many jurisdictions worldwide. Other product and service names might
be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the Web at "Copyright and trademark
information" at www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.

Java and all Java-based trademarks are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United
States, other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.