Release Notes
Abstract
This release contains new features and enhancements for Microsoft Applications agent.
Content
Download Description
You can download the IBM Tivoli Composite Application Manager (ITCAM) for Microsoft Applications Version 6.3.1.18 installer from IBM Passport Advantage website by selecting the below package name and Part Number:
- IBM Tivoli Composite Application Manager for Microsoft Applications V6.3.1.18
- Advance Component Software for Multiple Platforms
- Part number: M036VML
Note: This installer is for new installs and for upgrade of an existing agent environment to 6.3.1.18.
Component: IBM(R) Tivoli(R) Composite Application Manager for Microsoft (R) Applications: ITCAMMA Version 6.3.1 Fix Pack 18
Date: Oct 04, 2021
- IBM Tivoli Composite Application Manager for Microsoft Applications V6.3.1.18
- Advance Component Software for Multiple Platforms
- Part number: M036VML
Note: This installer is for new installs and for upgrade of an existing agent environment to 6.3.1.18.
Component: IBM(R) Tivoli(R) Composite Application Manager for Microsoft (R) Applications: ITCAMMA Version 6.3.1 Fix Pack 18
Date: Oct 04, 2021
Contents
1.0 General description
2.0 Architecture and prerequisites
3.0 Problems fixed
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 Copyright and trademark information
10.0 Notices
1.0 General description
2.0 Architecture and prerequisites
3.0 Problems fixed
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 Copyright and trademark information
10.0 Notices
1.0 General description
===================
===================
This fix pack resolves the APARs and defects listed in the "Problems fixed" section.
This fix pack also includes few enhancements made in this release.
This fix pack also includes few enhancements made in this release.
2.0 Architecture and prerequisites
===========================
===========================
For information about system requirements, refer to the IBM Software Product Compatibility Reports (SPCR) and search for the IBM Tivoli Composite Application Manager for Microsoft Applications product:
https://www.ibm.com/software/reports/compatibility/clarity/index.html
https://www.ibm.com/software/reports/compatibility/clarity/index.html
2.1 Prerequisites for this fix pack
---------------------------------------
---------------------------------------
The minimum required version of IBM Tivoli Monitoring is V6.3.0, Fix Pack 7.
The default version of IBM Tivoli Monitoring is V6.3.0, Fix Pack 7.
The default version of IBM Tivoli Monitoring is V6.3.0, Fix Pack 7.
3.0 Problems fixed
===============
===============
The following problems are resolved in this fix pack.
3.1 APARs
-------------
-------------
Internet Information Services Agent
IJ34959: Failed to configure the IIS agent version 06.31.16.00 via remote deployment.
IJ34959: Failed to configure the IIS agent version 06.31.16.00 via remote deployment.
3.2 Defects
--------------
--------------
Active Directory Server Agent
DEFECT: 187787
Abstract: Co-existence of Active Directory Server agent version 06.31.15.00 and Active Directory Server agent version 06.31.16.00 caused failure in the enhancement features of Active Directory Server agent version 06.31.16.00.
DEFECT: 187787
Abstract: Co-existence of Active Directory Server agent version 06.31.15.00 and Active Directory Server agent version 06.31.16.00 caused failure in the enhancement features of Active Directory Server agent version 06.31.16.00.
3.3 Enhancements
----------------------
----------------------
Microsoft Exchange Server Agent
Added new workspace "Server Component State (Exchange Server 2013 Onwards)” in Navigator Item 'Server’.
Added new workspace "Server Component State (Exchange Server 2013 Onwards)” in Navigator Item 'Server’.
Active Directory Server Agent
Added the following new workspaces:
Added the following new workspaces:
- “Pending Certificate Requests Details” workspace in Navigator Item ‘ADCS’
- “Revoked Certificate Requests Details” workspace in Navigator Item ‘ADCS’
Modified the following workspace:
- Modified “Group Operations” workspace in Navigator Item ‘Group Membership’
Added the following new views:
- Added the following view in "Pending Certificate Requests Details" workspace
- Pending Certificate Requests Details Table view
- Added the following view in "Revoked Certificate Requests Details" workspace
- Revoked Certificate Requests Details Table view
- Added the following view in “Group Operations" workspace
- Local Group Operations Table view
- Added the following view in "Group Operations" workspace
- Universal Group Operations Table view
Modified the following view:
- Modified the following view in "Group Operations" workspace
- Global Group Operations Table view
Added new attribute groups:
- Pending Certificate Requests
- Revoked Certificate Requests
- Local Group Operations
- Universal Group Operations
Modified the following attribute group:
- Global Group Operations
Microsoft .NET Framework Agent
Removed IIS Metabase 6 Compatibility feature dependency.
Removed IIS Metabase 6 Compatibility feature dependency.
Microsoft .NET Data Collector
Prerequisite for Microsoft .Net Data Collector is changed to .NET Framework 4.7.2.
Removed IIS Metabase 6 Compatibility feature dependency.
Prerequisite for Microsoft .Net Data Collector is changed to .NET Framework 4.7.2.
Removed IIS Metabase 6 Compatibility feature dependency.
Internet Information Services Agent
“Website Load Speed” attribute is added in the existing “IIS_Web_Sites_Detail” attribute group.
The prerequisites for "Web Application" attribute group as data source is changed from PowerShell to C#.
Data type of “AppPool_State” attribute is changed from string to integer and ITM portal displays enumeration as string.
Added manual configuration properties file to enable/disable Current Executing Requests feature.
“Website Load Speed” attribute is added in the existing “IIS_Web_Sites_Detail” attribute group.
The prerequisites for "Web Application" attribute group as data source is changed from PowerShell to C#.
Data type of “AppPool_State” attribute is changed from string to integer and ITM portal displays enumeration as string.
Added manual configuration properties file to enable/disable Current Executing Requests feature.
- To enable monitoring of Current Executing Requests, edit the agent properties file %CANDLE_HOME%\TMAITM6_x64\KQ7_agent.properties by setting the variable MonitorCurrentRequests to Yes. The default value of MonitorCurrentRequests is No.
- When the Current Executing Requests is enabled, it increases CPU load.
- When the Current Executing Requests is disabled, it does not impact system performance.
Microsoft Cluster Server Agent
Added the following new workspace:
Added the following new workspace:
- Storage Pool
Added the following new attribute groups:
- Storage Pool
- Virtual Disks
Added the following views in the new "Storage Pool" workspace:
- Storage Pool
- Virtual Disks
3.4 Supersede fixes
-----------------------
6.3.1-TIV-ITM_MSAPP-FP0017
-----------------------
6.3.1-TIV-ITM_MSAPP-FP0017
3.5 APARs and defects included from supersede fixes
--------------------------------------------------------------
3.5.1 APARs
---------------
--------------------------------------------------------------
3.5.1 APARs
---------------
Internet Information Services Agent
APAR : IJ31714
Abstract: PowerShell Process KQ7_CurrentExecutingRequests.ps1 consumes high CPU.
APAR : IJ31714
Abstract: PowerShell Process KQ7_CurrentExecutingRequests.ps1 consumes high CPU.
3.5.2 Defects
----------------
----------------
Microsoft SQL Server Agent
DEFECT: 188230
Abstract: Change the way child process is executed to resolve ENV33-C vulnerability.
Additional Information: MS SQL agent was using system() C library function to execute child process.
This function is known to have vulnerability, so removed the call to system() function.
Abstract: Change the way child process is executed to resolve ENV33-C vulnerability.
Additional Information: MS SQL agent was using system() C library function to execute child process.
This function is known to have vulnerability, so removed the call to system() function.
DEFECT: 188231
Abstract: Remote configuration support for agent instance where CTIRA_SUBSYSTEM_ID is set to value other than agent instance name.
Additional Information: CTIRA_SUBSYSTEM_ID lets user change the MSN name for the agent instance on the TEP portal.
Agent was not able to perform remote configuration operations when agent instance had CTIRA_SUBSYSTEM_ID other than HOSTNAME of TEMA.
Abstract: Remote configuration support for agent instance where CTIRA_SUBSYSTEM_ID is set to value other than agent instance name.
Additional Information: CTIRA_SUBSYSTEM_ID lets user change the MSN name for the agent instance on the TEP portal.
Agent was not able to perform remote configuration operations when agent instance had CTIRA_SUBSYSTEM_ID other than HOSTNAME of TEMA.
DEFECT: 188332
Abstract: Crash is observed in AFUtil64.exe while performing agent silent configuration.
Additional Information: If there are more than 9 SQL server instances to be configured on the system, the silent configuration crashes.
Abstract: Crash is observed in AFUtil64.exe while performing agent silent configuration.
Additional Information: If there are more than 9 SQL server instances to be configured on the system, the silent configuration crashes.
DEFECT: 188674
Abstract: Crash in collector process when SQL Server user does not have permission on SQL Server.
Additional Information: If SQL server user ID used in agent does not have sufficient permissions on SQL server, collector process crashed. Crash is observed during collection for the Process Detail (KOQPRCD) attribute group.
Abstract: Crash in collector process when SQL Server user does not have permission on SQL Server.
Additional Information: If SQL server user ID used in agent does not have sufficient permissions on SQL server, collector process crashed. Crash is observed during collection for the Process Detail (KOQPRCD) attribute group.
To workaround this issue in earlier releases, user needs to grant permissions to SQL server user ID, refer to technote https://www.ibm.com/support/pages/node/564387.
DEFECT: 188762
Abstract: Database Detail, Filegroup Detail and Device Detail attribute groups show invalid data when agent fails to obtain disk free space.
Additional Information: If agent startup account user does not have permission on the drive or mountpoint of SQL server where data and log files are located, the data size related attributes of Database Detail, Filegroup Detail and Device Detail attribute groups show invalid data for the database files. To resolve this issue, grant modify permission recursively from the drive or mountpoint of SQL server until the folders where SQL server data and log files are located.
Abstract: Database Detail, Filegroup Detail and Device Detail attribute groups show invalid data when agent fails to obtain disk free space.
Additional Information: If agent startup account user does not have permission on the drive or mountpoint of SQL server where data and log files are located, the data size related attributes of Database Detail, Filegroup Detail and Device Detail attribute groups show invalid data for the database files. To resolve this issue, grant modify permission recursively from the drive or mountpoint of SQL server until the folders where SQL server data and log files are located.
DEFECT: 188681
Abstract: Customized SQL properties file conversion is wrongly handled when the file size is more than 1024 bytes.
Additional Information: If customized sql properties file (KoqCusSQL.properties) is in ANSI encoding and the file size is more than 1024 byes, some garbage values are encountered in the file on agent startup. To workaround this issue in earlier releases, make sure that customized SQL file is in UTF-8 BOM encoding.
Abstract: Customized SQL properties file conversion is wrongly handled when the file size is more than 1024 bytes.
Additional Information: If customized sql properties file (KoqCusSQL.properties) is in ANSI encoding and the file size is more than 1024 byes, some garbage values are encountered in the file on agent startup. To workaround this issue in earlier releases, make sure that customized SQL file is in UTF-8 BOM encoding.
DEFECT: 188764
Abstract: On TEP UI, link from Filetable Detail workspace to Table Information workspace shows data for all tables.
Additional Information: TEP links are used to filter the data on resultant workspace. In case of Filetable Detail workspace, the link shows data for all tables from the server. The link should show data for the related table where it is applied from Filetable Detail workspace.
Abstract: On TEP UI, link from Filetable Detail workspace to Table Information workspace shows data for all tables.
Additional Information: TEP links are used to filter the data on resultant workspace. In case of Filetable Detail workspace, the link shows data for all tables from the server. The link should show data for the related table where it is applied from Filetable Detail workspace.
DEFECT: 189123
Abstract: Incorrect permission details are showed for msdb database when agent is configured with MSA user account in permission utility.
Additional Information: When permission utility is used to check the permission for msdb database, some permissions are showed incorrectly in log file.
Abstract: Incorrect permission details are showed for msdb database when agent is configured with MSA user account in permission utility.
Additional Information: When permission utility is used to check the permission for msdb database, some permissions are showed incorrectly in log file.
Microsoft Exchange Server Agent
DEFECT: 188502
Abstract: Unable to configure MS Exchange Server agent via remote command tacmd.
DEFECT: 188502
Abstract: Unable to configure MS Exchange Server agent via remote command tacmd.
DEFECT: 188501
Abstract: There is an error message after remote installation was successful.
Active Directory Server Agent
DEFECT: 187787
Abstract: Co-existence of Active Directory Server agent version 06.31.15.00 and Active Directory Server agent version 06.31.16.00 caused failure in the enhancement features of Active Directory Server agent version 06.31.16.00.
Additional Information: Enhancements of Active Directory Server agent version 06.31.16.00 are showed in the agent instance of earlier version when both agent instances co-existence on ITM and ITM has Active Directory Server agent version 06.31.16.00 support.
DEFECT: 187787
Abstract: Co-existence of Active Directory Server agent version 06.31.15.00 and Active Directory Server agent version 06.31.16.00 caused failure in the enhancement features of Active Directory Server agent version 06.31.16.00.
Additional Information: Enhancements of Active Directory Server agent version 06.31.16.00 are showed in the agent instance of earlier version when both agent instances co-existence on ITM and ITM has Active Directory Server agent version 06.31.16.00 support.
Microsoft .NET Data Collector
DEFECT: 186201
Abstract: Hard-coded strings are showed on UI.
Additional Information: The strings "Actions", "Search", "Enable Filtering" are hard-coded on Selective Filtering tool.
DEFECT: 186201
Abstract: Hard-coded strings are showed on UI.
Additional Information: The strings "Actions", "Search", "Enable Filtering" are hard-coded on Selective Filtering tool.
3.5.3 Enhancements
-------------------------
-------------------------
Microsoft SQL Server Agent
STORY: 188716
Abstract: RAS logs should be generated in candle home with proper name.
Additional Information: Agent RAS log was generated in C:\ drive. This was observed in SP5 Framework of 6.3.1-TIV-ITM_MSAPP-FP0015 (KOQ version 06.31.20.00) release. Added support to generate the logs in candle home with a proper name.
STORY: 188716
Abstract: RAS logs should be generated in candle home with proper name.
Additional Information: Agent RAS log was generated in C:\ drive. This was observed in SP5 Framework of 6.3.1-TIV-ITM_MSAPP-FP0015 (KOQ version 06.31.20.00) release. Added support to generate the logs in candle home with a proper name.
RFE ID: 145798
Abstract: MS SQL agent supports monitoring database size of over 20TB.
Additional Information: Added support to monitor database of database size over 20TB.
Abstract: MS SQL agent supports monitoring database size of over 20TB.
Additional Information: Added support to monitor database of database size over 20TB.
TASK: 188747
Abstract: Certified SQL Server agent for using Virtual Service account, Managed Service Account (MSA) and Group Managed Service Account (gMSA).
Additional Information: Agent can collect data with Virtual Service account, MSA and gMSA. To collect data by using these accounts, the minimum required permissions must be granted on the accounts.
Abstract: Certified SQL Server agent for using Virtual Service account, Managed Service Account (MSA) and Group Managed Service Account (gMSA).
Additional Information: Agent can collect data with Virtual Service account, MSA and gMSA. To collect data by using these accounts, the minimum required permissions must be granted on the accounts.
For list of permissions, check the topic "Running as a non-administrator user" in Agent Installation and Configuration Guide.
For more details, check the topic "Configuring agent with service account" in the Agent Installation and Configuration Guide.
TASK: 189049
Abstract: Changed default query timeout and set deadlock priority to minimum to resolve deadlock.
Additional Information: In SQL Server agent, the default query timeout is set to 0, so the query can take indefinite time to execute. Also, if agent's SQL query are in deadlock with the user's query, deadlock cannot be resolved. So, the default query timeout for demand-based collections is updated to 20 seconds.
Abstract: Changed default query timeout and set deadlock priority to minimum to resolve deadlock.
Additional Information: In SQL Server agent, the default query timeout is set to 0, so the query can take indefinite time to execute. Also, if agent's SQL query are in deadlock with the user's query, deadlock cannot be resolved. So, the default query timeout for demand-based collections is updated to 20 seconds.
For threaded data collection, the query timeout value is remained as default value, i.e. 0.
In this release, when the agent setups a database connection, the DEADLOCK_PRIORITY is set as -10. In case of deadlock, agent query is stopped and deadlock is resolved.
To change the default query timeout (in seconds), user can set QUERY_THREAD_TIMEOUT (for threaded collections) and QUERY_TIMEOUT (for demand-based collections) in Override Local Settings.
In this release, when the agent setups a database connection, the DEADLOCK_PRIORITY is set as -10. In case of deadlock, agent query is stopped and deadlock is resolved.
To change the default query timeout (in seconds), user can set QUERY_THREAD_TIMEOUT (for threaded collections) and QUERY_TIMEOUT (for demand-based collections) in Override Local Settings.
TASK: 189250
Abstract: Added ILMT tag file for this ITM release.
Additional Information: IBM license metric tool (ILMT) tag enables MSSQL application for automated inventory.
Abstract: Added ILMT tag file for this ITM release.
Additional Information: IBM license metric tool (ILMT) tag enables MSSQL application for automated inventory.
Microsoft Exchange Server Agent
Added the new “Email Transport Queues” workspace in Navigator Item “Server”.
Added the new “Mailbox Database Configuration Details" attribute group in “IS Store” workspace in Navigator Item “IS Mailbox”.
Added the new “Content Index State” attribute in the existing “MS Exchange Replication” attribute group .
Removed support of MS Exchange Server Version 2010 and earlier.
Added the new “Email Transport Queues” workspace in Navigator Item “Server”.
Added the new “Mailbox Database Configuration Details" attribute group in “IS Store” workspace in Navigator Item “IS Mailbox”.
Added the new “Content Index State” attribute in the existing “MS Exchange Replication” attribute group .
Removed support of MS Exchange Server Version 2010 and earlier.
Active Directory Server Agent
Added the following new Navigator Item:
Added the following new Navigator Item:
- ADCS
Added the following new workspaces:
- “Expiring Certificates” workspace in Navigator Item ‘ADCS’
- “Logon Peak Hour Usage” workspace in Navigator Item ‘User Information’
- “Empty Group Details” workspace in Navigator Item ‘User Information’
Added the following new views:
- Added the following views in " Empty Group Details" workspace:
- Empty Group Names Details
- Group Details Chart
- Added the following view in "Logon Peak Hour Usage" workspace:
- Logon Peak Hour Usage Plot Chart
Added the following view in "User Information" workspace:
- User Count with Old Password
Added the following new attribute groups:
- Expiring Certificates
- Empty Group Names Details
- Empty Group Count Detail
- Logon Peak Hour Usage
- User Count with Old Password
SharePoint Server Agent
Added the following new workspace:
Added the following new workspace:
- Audit Log
Added the following new views in the "Audit Log" workspace:
- SharePoint Audit Log
- Added new Attribute Group
- SharePoint Audit Log
Skype for Business Server Agent
Added the following attributes in the existing ‘Usage Summary’ attribute group:
Added the following attributes in the existing ‘Usage Summary’ attribute group:
- App Sharing Count
- Conf App Sharing Count
Added the following attributes in the existing ‘Failure Summary’ attribute group:
- AppSharingCount
- FailedAppSharingCount
- ConfAppSharingCount
- FailedConfAppSharingCount
- FailedAppSharingCountPer
- ConfFailedAppSharingCountPer
Added the following situations for Navigator item "Server Usage Statistics":
- KQL_FailCnfAppSharing_info
- KQL_FailedAppSharing_info
Internet Information Services Agent
Added following enhancements:
Added following enhancements:
- Data source is changed from PowerShell Script to C# for 31 attribute groups.
- MSIIS agent can be silently configured by using response file as input.
- Added the following attribute in the existing “WPROCESS” attribute group:
- Apdex score
Microsoft Cluster Server Agent
Added following view in the existing "Cluster Shared Volume File System Statistics" workspace:
Added following view in the existing "Cluster Shared Volume File System Statistics" workspace:
- Cluster Storage Setting
Added the following new attribute group:
- Cluster_Storage_Setting
- NIC_Team_Members
Added the following view in the existing "Network Interfaces" workspace:
- NIC Team Members
Added the following situations for "Operational Status" attribute:
- NIC_Failure_Critical
Microsoft Hyper-V Server agent
Added the following new workspace in the existing Navigator Item “Network”:
Added the following new workspace in the existing Navigator Item “Network”:
- Virtual Switch Processor
Added the following new attribute group:
- Virtual Switch Processor
Microsoft .NET Data Collector
Added following enhancement:
Added following enhancement:
- Ported the current .Net DC (KK4) Agent from 32-bit to 64-bit compatibility.
Microsoft BizTalk Server Agent
Added support for BizTalk Server 2020.
Added support for Windows Server 2019 OS.
Added support for BizTalk Server 2020.
Added support for Windows Server 2019 OS.
Microsoft Host Integration Server Agent
Added support for Host Integration Server 2020
Added support for Windows Server 2019 OS
Added support for Host Integration Server 2020
Added support for Windows Server 2019 OS
General enhancements
Removed 32-bit platform support.
Removed TCR support.
Upliftment to Visual Studio 2013.
Added support for IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 7.
Removed 32-bit platform support.
Removed TCR support.
Upliftment to Visual Studio 2013.
Added support for IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 7.
4.0 Image directory contents
=======================
=======================
This fix contains the following folder structure:
This fix contains the following folder structure:
- WINDOWS folder
This folder contains the binary files for installing 64-bit agent. The folder also contains the Prereqchecker utility in the prereqchecker folder for the following agents:
- Microsoft Active Directory agent
- Microsoft BizTalk Server agent
- Microsoft Cluster Server agent
- Microsoft Exchange Server agent
- Microsoft Hyper-V Server agent
- Microsoft Internet Information Services agent
- Microsoft .NET Framework agent
- Microsoft SharePoint Server agent
- Microsoft SQL Server agent
- Microsoft Host Integration Server agent
- Skype for Business Server agent
- .NET Data Collector
- Application Launch Pad and Discovery and Deployment support files
- Network Devices agent
- UNIX folder
This folder contains the non-Windows agent support files for the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Desktop client, and Tivoli Enterprise Browser client. The folder contains the agent support files for 64-bit agents.
5.0 Installation instructions
=====================
=====================
To install this fix, see the following publications:
IBM Tivoli Monitoring Installation and Setup Guide
Installation and Configuration Guide of the respective agents. For more information, see ITCAM for Microsoft Applications Knowledge Center.
IBM Tivoli Monitoring Installation and Setup Guide
Installation and Configuration Guide of the respective agents. For more information, see ITCAM for Microsoft Applications Knowledge Center.
6.0 Additional installation information
==============================
6.1 Installation instructions for agents baroc file
--------------------------------------------------------
For information about installation and configuration of the baroc files, see the "Setting up event forwarding to Tivoli Enterprise Console" section from IBM Tivoli Monitoring Installation and Setup Guide.
==============================
6.1 Installation instructions for agents baroc file
--------------------------------------------------------
For information about installation and configuration of the baroc files, see the "Setting up event forwarding to Tivoli Enterprise Console" section from IBM Tivoli Monitoring Installation and Setup Guide.
6.2 Verifying the update
----------------------------
1. To verify if the agent is updated correctly, use the tacmd command to view the current version of the agent after the agent is restarted. Ensure that you log on to the Tivoli Enterprise Monitoring Server before you view the agent version. For example,
On 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 OQ
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 OQ
Note: The component (-t) for the tacmd listSystems command is specified as two characters (OQ), not three characters (KOQ).
When the agent is updated, the agent version is changed to 06.31.17.00 except for the MS SQL agent (KOQ).
For the MS SQL agent, the version is 06.31.22.00.
For all other agents, the agent version is 06.31.18.00.
After you restart the agent, you can also use the GUI to verify the agent updates.
----------------------------
1. To verify if the agent is updated correctly, use the tacmd command to view the current version of the agent after the agent is restarted. Ensure that you log on to the Tivoli Enterprise Monitoring Server before you view the agent version. For example,
On 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 OQ
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 OQ
Note: The component (-t) for the tacmd listSystems command is specified as two characters (OQ), not three characters (KOQ).
When the agent is updated, the agent version is changed to 06.31.17.00 except for the MS SQL agent (KOQ).
For the MS SQL agent, the version is 06.31.22.00.
For all other agents, the agent version is 06.31.18.00.
After you restart the agent, you can also use the GUI to verify the agent updates.
2. To verify whether the agent support files are updated correctly, use the kincinfo command on Windows systems or the cinfo command on Linux or UNIX systems.
On UNIX or Linux systems:
To validate if all components are installed, run the following command:
$CANDLEHOME/bin/cinfo -i
On Windows systems:
To validate if all components are installed, run the following command:
%CANDLE_HOME%\bin\kincinfo –i
On UNIX or Linux systems:
To validate if all components are installed, run the following command:
$CANDLEHOME/bin/cinfo -i
On Windows systems:
To validate if all components are installed, run the following command:
%CANDLE_HOME%\bin\kincinfo –i
7.0 Known problems and workarounds
==============================
==============================
Microsoft Exchange Server Agent
Abstract: Duplicate workspace is displayed after agent upgrade from 631FP15 to 631FP16
Workaround : If agent is upgraded from 631FP15 to later release version, “Policy and Compliance” navigator item is displayed twice.
User can ignore the first navigator item in the list. You can follow the workaround steps as follows :
1. Remove support of 631FP15 from TEPD and TEMS (uninstall support).
2. Install support of higher version on ITM side, and point the upgraded agent to TEMS.
Abstract: Duplicate workspace is displayed after agent upgrade from 631FP15 to 631FP16
Workaround : If agent is upgraded from 631FP15 to later release version, “Policy and Compliance” navigator item is displayed twice.
User can ignore the first navigator item in the list. You can follow the workaround steps as follows :
1. Remove support of 631FP15 from TEPD and TEMS (uninstall support).
2. Install support of higher version on ITM side, and point the upgraded agent to TEMS.
Active Directory Server Agent
Abstract: Remote Upgrade from v631FP16 to v631FP17 through tacmd commands shows incorrect status.
Problem: Remote Upgrade from v631FP16 to v631FP17 through tacmd commands shows incorrect status in deployment status summary and agent remains in stopped state.
Workaround: Manually start the Active Directory Agent.
Problem: Remote Upgrade from v631FP16 to v631FP17 through tacmd commands shows incorrect status in deployment status summary and agent remains in stopped state.
Workaround: Manually start the Active Directory Agent.
BizTalk Server Agent
Abstract: When you click the "Databases" and "Log and Space Information" cross-links in these views, the target workspaces of the SQL Server agent does not open automatically.
Problem: The Databases workspace of the BizTalk Server agent contains the “Databases Information” and "Log and Space Information" cross-links in the following views:
Abstract: When you click the "Databases" and "Log and Space Information" cross-links in these views, the target workspaces of the SQL Server agent does not open automatically.
Problem: The Databases workspace of the BizTalk Server agent contains the “Databases Information” and "Log and Space Information" cross-links in the following views:
- Management Database
- MessageBox Database
- Rule Engine Database
- BAM Database
- Tracking Database
- Single Sign-On Database
Workaround: After you click the cross-links, when prompted, select the target instance manually.
Problem: List of attribute groups and workspace names that are no longer supported by BizTalk Server agent in ITCAMMA Version 6.3.1 Fix Pack 17.
- Attribute Groups:
- Human_Workflow_Services
- SOAP_Receive_Adapter
- SOAP_Send_Adapter
- SQL_Receive_Adapter
- SQL_Send_Adapter
- Windows_SharePoint_Services
- Windows_SharePoint_Services_Adapter
- BizTalk_NET_Adapter_for_Oracle_DB
- BizTalk_NET_Adapter_for_Oracle_EBusiness_Suite
- BizTalk_NET_Adapter_for_SAP
- BizTalk_NET_Adapter_for_Siebel
- BizTalk_NET_Adapter_for_SQL
- BAM_Interceptor
- Distributors
- Events
- Subscriptions
- Notifications
- Delivery_Channels
- Event_Providers
- Generator
- Vacuumer
- Subscribers
- RFID_Devices
- RFID_Processes
- Workspace:
- Human Workflow Services
- SOAP Receive Adapter
- SOAP Send Adapter
- SQL Receive Adapter
- SQL Send Adapter
- Windows SharePoint Services Adapter
- BAM Interceptor
- Distributors and Subscriptions
- Events
- Notifications
- Delivery Channels and Event Providers
- Generator
- Vacuumer
- Subscribers
- Business Activity Monitoring
- RFID
Workaround: None
Microsoft Host Integration Server Agent
Problem:List of attribute groups and workspace names that are no longer supported by HIS Server agent in ITCAMMA Version 6.3.1 Fix Pack 17.
Problem:List of attribute groups and workspace names that are no longer supported by HIS Server agent in ITCAMMA Version 6.3.1 Fix Pack 17.
- Attribute Groups:
- APPLICATION_INTEGRATION_HIP
- APPLICATION_INTEGRATION_WIP
- MANAGED_APPLICATION_INTEGRATION
- MQBRIDGE_CHANNEL
- MQBRIDGE_SERVICE
- MQBRIDGE_CONNECTED_NETWORK
- MQBRIDGE_MESSAGE_PIPE
- Workspace:
- HIP Method Execution Statistics
- HIP Host Request Statistics
- WIP Byte Transfer Statistics
- WIP Host Response Statistics
- WIP Method Call Statistics
- Managed WIP Calls Request Response Stats
- HIP Byte Transfer Statistics
- Application Integration
- HIP Work Flow Process Statistics
- Channel and Message Pipe Configuration
- Message Integration
Workaround: None
Microsoft Exchange Server Agent
Abstract: On the Tivoli Enterprise Portal, the status for the two situations is displayed as a "problem”.
Problem: The Tivoli Enterprise Portal shows the status as a problem due to the incorrect formula that is specified in the Manage Situations window for the following situations:
Abstract: On the Tivoli Enterprise Portal, the status for the two situations is displayed as a "problem”.
Problem: The Tivoli Enterprise Portal shows the status as a problem due to the incorrect formula that is specified in the Manage Situations window for the following situations:
- EX_Replication_Failed_Warn
- EX_Replication_Suspended_Warn
Workaround: Modify the formula or create a custom situation with the correct formula. The correct formula is as follows:
For the EX_Replication_Failed_Warn situation: Replication_Failed EQ Yes
For the EX_Replication_Suspended_Warn situation: Replication_Suspended EQ Yes
For the EX_Replication_Failed_Warn situation: Replication_Failed EQ Yes
For the EX_Replication_Suspended_Warn situation: Replication_Suspended EQ Yes
Microsoft .NET Data Collector
All the limitations that are mentioned in the "Problems and Workarounds" chapter of the .NET Data Collector Troubleshooting Guide V7.3.2 are still applicable. In addition to these problems and workarounds, the following problems and workarounds are applicable:
Abstract: When only .NET Framework 4.0 is installed on a server that runs on a 64-bit operating system, an error that is related to the ttapi.dll is generated.
All the limitations that are mentioned in the "Problems and Workarounds" chapter of the .NET Data Collector Troubleshooting Guide V7.3.2 are still applicable. In addition to these problems and workarounds, the following problems and workarounds are applicable:
Abstract: When only .NET Framework 4.0 is installed on a server that runs on a 64-bit operating system, an error that is related to the ttapi.dll is generated.
Problem: If the ISAPI or HTTPModule components of the .NET Data Collector are enabled and the .NET Framework 4.0 is installed on a server that runs on a 64-bit operating system, error messages are generated while processing a web request.
If the ISAPI component is enabled, the following error message is displayed:
"Service Unavailable"
If the ISAPI component is disabled and the HTTPModule component is enabled, the following error message is displayed:
"Unable to load DLL ttapi.dll:
This application fails to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)"
Workaround: Install the Microsoft Visual C++ 2005 Service Pack 1 Redistributable package (x64) on the computer where the .NET Data Collector is installed. You can download this package from the following website:
https://www.microsoft.com/en-in/download/details.aspx?id=26347
Abstract: When the WCF service is processed, the application name is displayed as w3wp and the component name is displayed as Microsoft .NET in the Transactions workspace of the Transaction Reporter agent on the Tivoli Enterprise Portal.
Problem: This problem occurs when a WCF service is processed for which ASP.NET impersonation is not enabled.
Workaround: Enable the ASP.NET impersonation for the service that is processed.
Abstract: When a one-way web service is processed, an asynchronous arrow from the client is displayed in the Transaction topology from where this method was initiated. In the Transactions workspace, the application name of the web service is displayed as .asmx.
Problem: One-way web services are called asynchronous and the user does not wait for a response from the server. As all the interception points of the SOAP component of the .NET data collector are not called, the asynchronous arrow is seen in the Transaction topology.
Workaround: None
Abstract: If a SOAP request is sent from a client computer where the .NET Data Collector is not installed to a server where the .NET Data Collector is installed, the web service node is displayed as .asmx or .svc in the Transaction topology.
Problem: If all interception points for the SOAP component of the .Net Data Collector are not called, the web service nodes are displayed as .asmx or .svc. If the .NET Data Collector KD4 logging is enabled, the following message is seen in the logs: object reference not set to an instance of an object.
Workaround: None
Abstract: Visual Studio 2008 runtime environment should be installed before you upgrade the .NET Data Collector from V7.3.1 to V7.3.2 or V7.3.2, Fix Pack 1 or V7.3.2, Fix Pack 2.
Problem: When you unregister the .NET Data Collector, the .dll files of the Microsoft Visual C++ 2008 redistributable package are required.
Workaround: Install the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package. For a 32-bit operating system, download the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (x86) from:
https://www.microsoft.com/en-us/download/details.aspx?id=26368
For a 64-bit operating system, download the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (x64) from:
https://www.microsoft.com/en-us/download/details.aspx?id=26368
Abstract: When the database calls are made by using ODBC, the component name is shown as Microsoft .NET in the Transactions workspace of the Transaction Reporter agent.
Problem: This problem occurs due to the aggregation of ODBC events.
Workaround: Disable the ADO Event Aggregation by completing the following steps:
1. Open the dotNetDcConfig.properties.inactive file.
2. Change the value of the ktj_ADOAggregation.Enabled property to false, for example, ktj_ADOAggregation.Enabled=false.
3. Open the command prompt and browse to the bin directory of the .NET Data Collector.
4. Run the configdc activate config command.
5. Restart all the .NET applications.
Abstract: When database calls are made from a stand-alone client, ADO.NET nodes are not generated.
Problem: This problem occurs when ADO Event Aggregation is enabled in the properties file. When a database call is made from a stand-alone client, the instance at which the user closes the application is not known to the .NET Data Collector because of which the ADO events are not aggregated.
Workaround: Disable the ADO Event Aggregation by completing the following steps:
1. Open the dotNetDcConfig.properties.inactive file.
2. Change the value of the ktj_ADOAggregation.Enabled property to false, for example, ktj_ADOAggregation.Enabled=false.
3. Open the command prompt and browse to the bin directory of the .NET Data Collector.
4. Run the configdc activate config command.
5. Restart all the .NET applications.
Abstract: After remote or silent installation, the .NET Data Collector needs manual configuration by going to a particular installed instance.
Problem: The .NET Data Collector is configured using its own utilities by using “configdc” or by UI tool “KK4ConfigProperties.exe” present at “<CANDLE_HOME>\ k4\bin\PropertiesEditor”. In the ITM architecture, there is no way to provide inputs to these configuration utilities remotely unlike any other agent using tacmd or TEP GUI.
Workaround: Currently, there is no workaround for this problem. The user needs to manually configure the .NET Data Collector using either “configdc” through command line or “KK4ConfigProperties.exe UI”.
Abstract: Upgrade to .NET Data Collector Version 6.3.1 Fix Pack 17 from earlier version is not supported.
Problem: KK4 agent upgrade from 631FP16 to 631FP17 is not supported.
Workaround: To use the current 64-bit .NET Data Collector, install the .NET Data Collector Version 6.3.1 Fix Pack 17.
Problem: KK4 agent upgrade from 631FP16 to 631FP17 is not supported.
Workaround: To use the current 64-bit .NET Data Collector, install the .NET Data Collector Version 6.3.1 Fix Pack 17.
Internet Information Services Agent
Abstract: Unable to configure and start the agent through remote deploy command.
Problem: Agent remained in unconfigured and stopped state when user tries remote deploy.
Workaround: Configure and start the agent in Silent mode OR GUI Mode.
Abstract: Unable to configure and start the agent through remote deploy command.
Problem: Agent remained in unconfigured and stopped state when user tries remote deploy.
Workaround: Configure and start the agent in Silent mode OR GUI Mode.
Skype for Business Server Agent
Abstract: Task Scheduler behavior at Daylight Saving Time transitions and other events.
Problem: The behavior of the Microsoft Task Scheduler is not specified for tasks that are scheduled to run during the transition hours of the Daylight Saving Time. Other events can also affect the actual time at which a scheduled task runs.
Workaround: None
Abstract: Task Scheduler behavior at Daylight Saving Time transitions and other events.
Problem: The behavior of the Microsoft Task Scheduler is not specified for tasks that are scheduled to run during the transition hours of the Daylight Saving Time. Other events can also affect the actual time at which a scheduled task runs.
Workaround: None
SharePoint Server Agent
Abstract: TEP shows navigator item name Logs twice after agent upgrade from 631FP15 or 631FP16 to 631FP17.
Workaround: - User can ignore the first navigator item in the list or perform the following steps:
1. Remove the existing ITCAM for Microsoft Applications version 6.3.1 Fix Pack 16 or earlier version from TEPD and TEMS.
2. Install ITCAM for Microsoft Applications version 6.3.1 Fix Pack 17 at ITM side.
3. Point upgraded agent to TEMS.
Abstract: TEP shows navigator item name Logs twice after agent upgrade from 631FP15 or 631FP16 to 631FP17.
Workaround: - User can ignore the first navigator item in the list or perform the following steps:
1. Remove the existing ITCAM for Microsoft Applications version 6.3.1 Fix Pack 16 or earlier version from TEPD and TEMS.
2. Install ITCAM for Microsoft Applications version 6.3.1 Fix Pack 17 at ITM side.
3. Point upgraded agent to TEMS.
8.0 Additional product information
===========================
===========================
Active Directory Server Agent
1. To run the agent as a non-administrator user, provide the following permissions to the user:
1. To run the agent as a non-administrator user, provide the following permissions to the user:
- Read access to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\NTDS\Parameters directory
- Read access to the C:\Windows\NTDS directory
- Full access to the HKEY_LOCAL_MACHINE\SOFTWARE\Candle directory
2. When you run the agent as a non-administrator user, the following attribute groups display the incorrect data:
- Active Directory Database Information
- Moved or Deleted Organizational Unit
- Password Setting Objects
- Containers
- LDAP Attributes
3. To run a Take Action command, run the Active Directory agent as an administrator user.
Hyper-V Server Agent
1. The following attribute groups are not supported on the Windows Server 2012 R2 operating system:
1. The following attribute groups are not supported on the Windows Server 2012 R2 operating system:
- Hyper V Task Manager Detail
- Hyper V Task Manager Recent Time
- Hyper V VM Association with Virtual Network
- Hyper V Legacy Network Adapter
2. The HV_VMMigrate_Info situation is not supported on the Windows Server 2012 R2 operating system.
3. The following attribute groups are not supported on the Windows Server 2016 operating system:
3. The following attribute groups are not supported on the Windows Server 2016 operating system:
- Hyper V Task Manager Detail
- Hyper V Task Manager Recent Time
- Hyper V VM Association with Virtual Network
- Hyper V VM IO APIC
- Hyper-V Virtual IDE Controller
Microsoft Cluster Server Agent
To get data of ‘NIC Team Members’ view , run the agent as a domain administrator and allow Internet access.
Skype for Business Server Agent
1. Partially supports archiving, monitoring, and CDR roles of the Lync Server for version 2013 and Skype for Business 2015 and 2019.
2. The agent does not support remote monitoring of the SQL RTC buffer manager.
3. To get data in the Lync Topology workspace, run the agent as a domain administrator, and change the agent startup from automatic to manual.
4. For the configuration settings for the Synthetic Transaction, if a weekly scheduling frequency is set, then the scheduler runs every Monday at the time that is configured by the user. If a monthly scheduling frequency is set, then the scheduler runs on the first day of every month at the time that is configured by the user.
5. The configuration panel does not validate any parameters. The user must follow the guidelines that are mentioned in every field and enter the data in the correct format.
To get data of ‘NIC Team Members’ view , run the agent as a domain administrator and allow Internet access.
Skype for Business Server Agent
1. Partially supports archiving, monitoring, and CDR roles of the Lync Server for version 2013 and Skype for Business 2015 and 2019.
2. The agent does not support remote monitoring of the SQL RTC buffer manager.
3. To get data in the Lync Topology workspace, run the agent as a domain administrator, and change the agent startup from automatic to manual.
4. For the configuration settings for the Synthetic Transaction, if a weekly scheduling frequency is set, then the scheduler runs every Monday at the time that is configured by the user. If a monthly scheduling frequency is set, then the scheduler runs on the first day of every month at the time that is configured by the user.
5. The configuration panel does not validate any parameters. The user must follow the guidelines that are mentioned in every field and enter the data in the correct format.
For additional documentation information, see the following websites:
- IBM Tivoli Monitoring Knowledge Center:
- Tivoli Composite Application Manager for Microsoft Applications Knowledge Center:
- Tivoli Composite Application Manager for Microsoft Applications website:
9.0 Copyright and trademark information
================================
A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
================================
A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
10.0 Notices
==========
==========
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 jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
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.
Third-Party License Terms and Conditions, Notices and Information
----------------------------------------------------------------------------
The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices, and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.
Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third-party software code identified below are "Excluded Components" and are subject to the following terms and conditions:
-The Excluded Components are provided on an "AS IS" basis
-IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
-IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive, or consequential damages with respect to the Excluded Components.
Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
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.
Third-Party License Terms and Conditions, Notices and Information
----------------------------------------------------------------------------
The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices, and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.
Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third-party software code identified below are "Excluded Components" and are subject to the following terms and conditions:
-The Excluded Components are provided on an "AS IS" basis
-IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
-IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive, or consequential damages with respect to the Excluded Components.
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDKXQ","label":"Tivoli Composite Application Manager for Microsoft Applications"},"ARM Category":[{"code":"a8m50000000L1hcAAC","label":"ITCAM-for-Applications->ITCAM-for-Microsoft-Applications"}],"Platform":[{"code":"PF033","label":"Windows"}],"Version":"6.3.1"}]
Was this topic helpful?
Document Information
Modified date:
18 October 2021
UID
ibm16496477