ITCAM for Microsoft (R) Applications: 6.3.1-TIV-ITM_MSAPP-FP0013

Download Description

Copyright International Business Machines Corporation 2017.
All rights reserved.

Component: IBM® Tivoli® Composite Application Manager for
Microsoft® Applications: Version 6.3.1.13

Fix Pack: 0013
Component ID: 5724-U17
Date: July 21, 2017

1.0 General description
=======================
This fix contains the APARs and defects that are specified in the
"Problems fixed" section. This fix also includes the enhancements
that are made in the V6.3.1.13 release of ITCAM for Microsoft Applications product.

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

2.1 APARs
----------
For the SQL Server agent:
APAR: IV96443
Abstract: Job detail attribute group showing incorrect values for
jobs having double quotes in job name.
Additional Information: Job name was getting trucated when it contains
double quotes(") in it. For example : if jobname = test"new123 then on
portal it was shown as only "test". and remaining part "new123" was
getting trucated. Other attributes in the group were also getting
effected due to this and showing incorrect value.

For the Exchange Server agent:
APAR: IV97894
Abstract: Microsoft Exchange server agent shows server status as
DOWN,when MSExchangePOP3 service is not started for Exchange
Server 2016.

APAR: IV94497
Abstract: Microsoft Exchange server agent crashes while fetching data
from corrupted Forefront Exchange Scheduled Scanner perfmon object.

APAR: IV91630
Abstract: Exchange agent crashes while fetching data for MS
Exchange IS Private attribute group on Exchange server 2016.

APAR: IV90298
Abstract: Microsoft Exchange Server monitoring Agent crashes while
parsing the Exchange Server events having description greater than
2000 characters.

For the Active Directory agent:
APAR: IV87378
Abstract: SITUATION "KDC_AS_REQUESTS" DOES NOT ALLOW TO RESTORE
THRESHOLD VALUE I.E. 99999.
Additional Information: Situation editor does not allow value due
to RANGE: 0-100 set in the attribute.

2.2 DEFECTS:
-----------------
For the SQL Server agent:
DEFECT: 158215
Abstract: Implement query timeout for all thread based attribute groups
Additional Information: Added QUERY_THREAD_TIMEOUT varibale which
imposes timeout (in seconds) for all the thread based attribute groups
(Table Detail, Database Detail, Device Detail and Audit Detail) to
avoid prolonged execution of queries which could result in delayed data
collection which will result in nodata or not collected on the portal.

DEFECT: 158224
Abstract: Support of extended params for all attribute groups
Additional Information: Adding attribute group name in extended params
of configuration panel will disable the attribute group collection for
that attribute group.As a result,if pre-cursor is disabled, data will
not be collected for all the dependent cursors as well.Earlier it was
only catering to table and database threaded collection.

DEFECT: 161899
Abstract: Renaming of file <instance_name>_DBD_TEMP to
<instance_name>_DBD_PREV was failing and causing "nodata" on portal.
Additional Information: Agent reads data from <instance_name>_DBD_PREV
file and displays on portal.Due to rename failure which was only
attempted once, in such cases it usually showed "nodata" for database
detail attribute group. Now the changes has been made to try renaming
multiple times. Default value of retry count is 3 but it is
configurable using environment variable "COLL_DBD_FRENAME_RETRY_CNT".


DEFECT: 158348
Abstract: Data collection issue in Problem Detail and Problem Summary
attribute groups when ERRORLOG file size is more than 2GB
Additional Information: Earlier, Koqerr.exe was reading complete
ERRORLOG file every time hence it was taking longer time to execute
especially when the file size grew more than 2 GB thus blocking the
data collection for other attribute groups and leading to high CPU
usage of koqerr.exe. Changes done to read complete ERRORLOG file for
the first time only and from subsequent collections only newly added
errors will get read.

DEFECT: 159526
Abstract: Implemented NOLOCK for all the tables which may have huge
data.
Additional Information: Earlier, Agent query could get blocked because
system tables waits for the resources until lock on it gets released.
Now, blocking can be avoided by setting the COLL_DBCC_NO_LOCK
environment variable to value 1 so that it will not wait for lock to be
released and execute the query with “with (nolock)” hint.

DEFECT: 158581
Abstract: Current CPU Pct Used attribute value is wrongly calculated
Additional Information: In Process Detail attribute group the Total
CPU time(in second) of last process was getting reflected for all the
processes due to multiple source. Current CPU Pct Used attribute is
calculated from Total CPU time(in seconds) attribute. Incorporated
changes such that correct value will get displayed for both the
attributes.

DEFECT: 158164
Abstract: Last Database Size(MB) attribute value is wrongly calculated
Additional Information: Last Database Size(MB) attribute of Database
Detail attribute group shows database size of last interval which was
wrongly calculated. Incorporated changes such that correct value will
get displayed.




2.3 Enhancements
-----------------
For the SQL Server agent:
1. Dependency removed from external rougewave library.
2. General logging improved for various modules for debugging purpose.
3. Utility "koqpermission.exe" is added to check the permissions of
user.
It take MSSQL Server instance name, login name and password as
input and run TSQL query to check if the user has required
permissions to collect the data for MSSQL server agent. AS an
output it creates "koqpermission.txt" log file which has all the
details regarding user permissions on given MSSQL Server instance.
It also specify the attribute groups for which user does not have
sufficient permissions to collect data. It is present at location:
For 32 bit agent,
%candle_home%\TMAITM6\

For 64 bit agent,
%candle_home%\TMAITM6_x64

Output file "koqpermission_log.txt" will get generated at :
For 32 bit agent,
%candle_home%\TMAITM6\logs

For 64 bit agent,
%candle_home%\TMAITM6_x64\logs

Notes:
For getting details regarding the inputs given to the utility run
the it on command prompt with following parameters :
koqpermission.exe -H

4. Script "permissions" is added to grant required permissions to the
user for MSSQL Server Agent to collect data for all attribute
groups. Script and its help document are present at location :
For 32 bit agent,
%candle_home%\TMAITM6\scripts\KOQ\GrantPermission

For 64 bit agent,
%candle_home%\TMAITM6_x64\scripts\KOQ\GrantPermission


For the Active Directory Server Agent
1. Added Windows 2016 support :
Added support to the Windows 2016.

For the Exchange Server agent
1. Added Windows 2016 support :
Added support to the Windows 2016.

For the BizTalk Server Agent:
1. Added Windows 2016 support :
Added support to the Windows 2016
2. Added Currency Support:
- BizTalk Server 2016

For the Host Integration Server Agent:
1. Added Windows 2016 support :
Added support to the Windows 2016
2. Added Currency Support:
- HIS 2016
3. Added New Attribute Group:
- HIS_Microsoft_Client_for_MQ: This attribute group provides
information about the Perfmon object of the HIS Microsoft
Client for Message Queue (MQ)
4. Added new Availability Services:
- SDLC Link Service
- IPDLC Link Service
- Distributed Link Service
- Microsoft Service for DRDA
- HIS Vss Writer
- NVAlert
- SNA 5250 Demo

For the Lync Server Agent:
1. Added new attributes to following existing attribute groups:
a. Failure Summary:
- Failed Session Count Per: The percentage of sessions
that failed during a particular time period.
- Failed IM Count Per: The percentage of instant messages
that failed during transfer for a particular time period.
- Conf Failed Session Count Per: The percentage of
conference sessions that failed during a particular time
period.

b. FrontEnd Connectivity Details:
- Last Register In Days Hrs: The time (in days and hours)
that has elapsed since the server was last registered
with the system.
- Last Heart Beat In Days Hrs: The time (in days and hours)
that has elapsed since the last heartbeat was received from
the front-end server.
- Last Unregister In Days Hrs: The time (in days and hours)
that has elapsed since the server was last unregistered
from the system.

c. QoEMetrics Call Summary:
- Poor Call Count In Per: The total number of poor calls
(in percentage) that are made by the users.

For the Hyper-V Server agent:
1. Added currency support for following operating systems:
- Windows Server 2016 Datacentre
- Windows Server 2016 Standard
- Windows Server 2016 Essentials
- Microsoft Hyper-V Server 2016
2. Added following new attribute groups:
- VM Operating System: This attribute group provides
information about the operating system that runs on the
virtual machine.
- Virtual Machine Details: This attribute group provides
information about the virtual machine and the operating
system that runs on the virtual machine.
3. Added following new attributes to existing attribute groups:
- Virtual Machine
- UpTimeDay: The duration since the virtual machine
was last started. The format is DDHHMM, where DD indicates
the number of days, HH indicates the number of hours,
and MM indicates the number of minutes.
- VMStatusCrit: The number of virtual machines that
are in the critical state.
- Processor
- AvgProcessorLoad: The average load on the processor
of the virtual machine.
- Hyper V Server Disk
- Disk Utilization: The percentage of disk usage
of the server.
4. Added following new situations:
- HV Memory Utilization Crit
- HV Memory Utilization Warn
- HV Disk Utilization Crit
- HV Disk Utilization Warn
- HV VM Status Crit
- HV VM ProcessorLoad Crit

For the SharePoint Server agent:
1. RFE 90992: MS SharePoint ITM Agent - Monitoring Timer Jobs
Added new attribute group to monitor failed Timer Jobs.
2. Added currency support for SharePoint 2016
3. Added following new attribute groups:
- Timer Jobs: This attribute group displays information about
the top five hundred timer jobs that have failed to complete.
This attribute group is available for SharePoint 2016.
- Workflow Dispatcher: This attribute group monitors usage and
health statistics of the Workflow Dispatcher service.
This attribute group is available for SharePoint 2013 and 2016.
- Workflow Management: This attribute group monitors the usage
and health statistics of the Workflow Manager. This attribute
group is available for SharePoint 2013 and 2016.
- Workflow Operations: This attribute group provides details
about the operations of the Workflow Manager. This attribute
group is available for SharePoint 2013 and 2016.
- Workflow Sql Operations: This attribute group monitors the
workflow of the SQL operations. This attribute group is
available for SharePoint 2013 and 2016.

For the Cluster Server agent
1. Added currency support to following operating systems
- Windows Server 2016 Datacenter
- Windows Server 2016 Standard
2. Added following new attribute groups
- Node Details : This attribute group provides information
about the nodes in the cluster, such as node memory usage,
processor and the operating system.
- Resource Group Status : This attribute group provides
information about the status of the resource group running
on the preferred node.
- NodeToActive Group Details : This attribute group provides
information about the resource groups and status if the
Resource Group is running on the Preferred node.
- Node Weights : This group of data provides information about
the node weights.
3. Add the following attributes in Cluster Summary attribute group:
- Percent Nodes Down : The percentage of nodes that are down in
the cluster.
- Dynamic Quorum Enabled : Indicates whether the dynamic quorum
is enabled on the cluster or not.
- Witness Dynamic Weight : The dynamic weight of the witness
depending upon the number of witnesses participating in the voting.
4. Added following new situations:
- Nodes Down Warning : The percentage of nodes in the cluster that
have exceeded the warning threshold.
- Quorum Utilization crit : The usage of the quorum disk space has
exceeded the critical threshold.
- Quorum Utilization warn : The usage of the quorum disk space has
exceeded the warning threshold.
- Shared Disk Status Warning : A shared disk drive is in a warning
state, such as offline, pending, onlinePending, offlinePending,
initializing, inherited, or unknown.
- Node Memory Critical : The usage of the physical memory of the
node has exceeded the critical threshold.
- Node Processor Critical : The usage of the node processor has
exceeded the critical threshold.

For the .NET Data Collector:
1. Added currency support to following operating systems
- Windows Server 2016 Datacenter
- Windows Server 2016 Standard
- Windows Server 2016 Essentials
2. Added monitoring support for IIS 10
3. Support for ASP.NET MVC failed transactions.
4. Support for asynchronous WCF services calls through ASP.NET
applications.
5. configdc command enhancements

For the IIS agent:
1. Added currency support for following operating systems:
- Windows Server 2016 Datacentre
- Windows Server 2016 Standard
- Windows Server 2016 Essentials
2. Added following new attribute to existing attribute group
Websites_W3C_Logs
- Custom Fields: The comma separated list of custom fields
that are set by the administrator.

For the .NET Agent
1. Added currency support to following operating systems
- Windows Server 2016 Datacenter
- Windows Server 2016 Standard
- Windows Server 2016 Essentials
2. Datasources for attribute groups are changed to perfmon from WMI
(Refer section 2.5.3 for list of attribute groups)

2.4 Superseded fixes
----------------------
6.3.1.10-TIV-ITM_SQL-IF0001
6.3.1-TIV-ITM_MSAPP-FP0010

2.5 APARs and defects included from superseded fixes
----------------------

For the SQL Server agent:
APAR: IV89124
Abstract: Unable to recycle the ERRORLOG file.
Additional Information: The ERRORLOG recycle failed when agent was
monitoring the Error Events. When the ERRORLOG file was recycled, this
event triggered and agent locked the file. Hence, recycling the
ERRORLOG was failing.

For the Active Directory agent:
APAR: IV72817
Abstract: Agent Shows wrong value for “DCA PDC Master ",
"DCA RID Controller Availability “attribute group
Additional Information: Agent shows wrong value for "DCA PDC Master",
"DCA RID Master" and "DCA Infrastructure Master" attributes of
"Domain Controller Availability" attribute group, when DNS name and
NetBIOS name of Domain Controller machine are different.
APAR: IV52452
Abstract: Domain Name of the host machine is not fetched by AD Agent.
Additional Information: Agent is not able to fetch the domain
name of the host
machine because getaddrinfo API gives incorrect canonical name of
host machine.

APAR: IV52672
Abstract: Agent shows incorrect data for DNS ADIntegrated attribute
group.
Additional Information: Some SRV records (for Read only Domain
Controller) which are specific to sites get added under sites not
in the default location in DNS Manager. Hence agent fails to verify
the SRV records of sites and incorrect data displays for some of
the attribute of DNS ADIntegrated attribute group on TEP.

APAR: IV53500
Abstract: Agent Shows wrong count of Global Catalog Servers in a
Domain.
Additional Information: Agent Shows wrong count of Global Catalog
Servers in a Domain for Domain controller availability attribute
group. Agent does not consider the RODC with GC configured as
Global Catalog Server.

APAR: IV60416
Abstract: Agent shows wrong data of "DRA INTERSITE PARTNER COUNT"
attribute
Additional Information: Microsoft Active Directory Agent shows wrong
data of "DRA InterSite Partner Count" attribute. The Microsoft
Active Directory Agent displays correct data initially, but
sometimes it shows the incorrect value.

APAR: IV74419
Abstract: Active Directory 64-bit Agent does not connect to Tivoli
Enterprise Monitoring Server (TEMS) using IPSPIPE.
Additional Information: Due to incorrect value of PATH environment
Variable, Active Directory 64-bit Agent does not connect to Tivoli
Enterprise Monitoring Server (TEMS) using IPSPIPE.

For the Exchange Server agent:
APAR: IV84427
Abstract: Situations editor does not allow setting a value greater
than 1 n the situation formula for EX_Store_Int_RPC_Req_Fail_Crit
situation.
Additional Information: The attribute specification for the attribute
Percent of RPC\Requests Failed specifies the RANGE: 0-100, but it
should be 0-10000. Hence, Situation editor does not allow setting a
value greater than 1 in the situation formula for
EX_Store_Int_RPC_Req_Fail_Crit situation.

APAR: IV73298
Abstract: Microsoft Exchange Server Agent fails to fetch the data for
Email Statistics attribute group.
Additional Information: Microsoft Exchange Server Agent fails to fetch
the data for Email Statistics attribute group when monitored server
name has maximum allowed NETBIOS name.

APAR: IV73296
Abstract: Microsoft Exchange server agent shows wrong data for "MS
Exchange Reachability" attribute group.
Additional Information: "MS Exchange Reachability" attribute group
shows wrong data when user name having white spaces provided in the
agent configuration panel.

APAR: IV75572
Abstract: Microsoft Exchange Server Agent Guide shows incorrect
configuration parameters' name in ‘Remote installation and
configuration’ section.
Additional Information: Microsoft Exchange Server Agent Guide shows
incorrect name of below configuration parameters in ‘Remote
installation and configuration’ section.
1. Existing Name: EXCHSETTINGS.exch_event_interval
Correct Name: EXCHSETTINGS.exchange_event_interval

2. Existing Name: EXCHSETTINGS.exch_event_count
Correct Name: EXCHSETTINGS.exchange_event_count


2.5.2 Defects
--------------

For the SQL Server agent:DEFECT: 150095
Abstract: Agent failed to get non-english collation.
Additional Information: When named instance with name same as the
machine name agent was considering it as default instance. Hence,
there was failure in fetching non-english collation and default
English collation was considered.

DEFECT: 150097
Abstract: Logging improvement in Error Event Detail attribute group.
Additional Information: The logs in this attribute group were not
helpful in troubleshooting the issues. Hence, additional logs
are now added.

DEFECT: 151444
Abstract: HART1 cursor now gets the SRVSTATUS from TSQL query by
default.
Additional Information: The status of SQL Server was fetched using a
WMI query but multiple issues were seen during the execution. So, now
the Server status is fetched using TSQL and WMI is used as a fall back
when TSQL fails.

DEFECT: 153332
Abstract: Provided tolerance support on Windows Server 2016.
Additional Information: Windows Server 2016 is now released but agent
was not supporting it.

Defect: 146011
Abstract: Change default instance name from HOSTNAME to MSSQLSERVER
during upgrade.
Additional Information: When SQL Agent is upgraded from an old version
to 631FP10, then default instance will be identified as MSSQLSERVER
after upgrade.

Defect: 144293
Abstract: Some of the attributes in Database details attribute group
are showing negative value on portal.
Additional Information: Transactions /sec, Write Transaction/sec and
Log Bytes Flushed/sec were showing negative value.

Defect: 124592
Abstract: Excessive login failures logged in the ERRORLOG with wrong
user ID or password
Additional Information: While configuring agent if wrong user ID or
password is specified then agent keeps on trying to connect with SQL
server with wrong user id password. This result in excessive login
failure errors logged in SQL server ERRORLOG file.

Defect: 144290
Abstract: Restrict retry count while checking availability of MSSQL
service.
Additional Information: If environmental variable
'COLL_MSSQL_RETRY_CNT' is not set and agent fails to get the status
of SQL server service then agent keeps on trying to get the service
status for infinite time.

Defect: 146881
Abstract: Crash observed when Login Name in NULL.
Additional Information: When login name was not provided while
configuring agent then crash was observed.

2.5.3 Enhancements
--------------------
Enhancements in the SQL Server agent:
1. Added tolerance support for SQL Server 2016.
2. Added a check box ‘Monitor All Databases’ in the configuration
window.
3. Changed threshold and interval for some of the situations
4. NULL values returned by SQL server are handled gracefully.
5. Added Windows server 2016 support.

Enhancements in the Lync Server agent:
1. Added new attributes to existing attribute groups:
- Top 5 Active Users: Displays top 5 most active users based
on the call duration.
- FrontEnd Connectivity Details: Displays connectivity details
of the front-end server.
- Server Failure Count: Displays the total number of failed
requests on each server for a particular time duration
- Usage Summary: Displays the total usage of the server
services for a particular time period.
- Failure Summary: Displays the failures that occurred on a
server for a particular time period.
- Call Quality Distribution: Displays the distribution of
calls in various quality slabs.
- QoEMetrics Call Summary: Displays the number of poor calls
that are made by the users.

Enhancements in the BizTalk Server Agent:
1. RFE 78698: BizTalk Agent - Disabling BizTalk agent from
invoking BAM utility. Provided an option in Configuration panel
that allows the disabling of data collection for BAM related
metrics in the case where BAM is not configured on a BizTalk
server.

Enhancements in the Exchange Server agent:
1. Added support to monitor the existing attributes on Exchange
Server 2016 and its corresponding Exchange Server roles.

2. Added following new attribute groups :
- MS Exchange GoLocal Assistant: This attribute group monitors
the activity of the Managed GoLocal Assistant on the Microsoft
Exchange Server. This attribute group is available only in
Exchange Server 2016.
- MS Exchange HTTP Proxy Per Forest: This attribute group provides
information about the HTTP proxy for each Active Directory Forest.
This attribute group is available only in Exchange Server 2016.
- MS Exchange Oversize Email Count: This attribute group provides
the count of oversized emails that are sent in the last 10
minutes.
- MS Exchange Oversize Email Details: This attribute group provides
information about a maximum of 1000 oversized emails that the
server sent in the last 10 minutes.
- MS Exchange Service Proxy Pool: This attribute group provides
information about the Service Proxy Pool on Exchange Server.
This attribute group is available only in Exchange Server 2016.
- MS Exchange Shared Cache: This attribute group provides
information about the shared cache. This attribute group is
available only in Exchange Server 2016.
- MS Exchange DLP Policy Tips: This attribute group provides
information about the Policy Tips that are related to data loss
prevention (DLP). This attribute group is available only in
Exchange Server 2016.

3. Add the following attributes in existing attribute groups:
- MS Exchange OAB Request Handler
- Routing Failures: The number of requests that failed due to
routing errors.
- Routing Failures/Sec: The number of requests that failed per
second due to routing errors.
- Unknown Failures: The number of requests that failed due to
unknown errors.
- Unknown Failures/Sec: The number of requests that failed per
second because of unknown errors.
Note: Above attributes are available only in Exchange Server 2016.

- MS Exchange Transport Queues
- External Active Remote Delivery Queue Length: The number of
items in the active remote delivery that are queued for external
destinations.
- External Aggregate Delivery Queue Length: The number of external
items that are queued for delivery in all external queues.
- External Largest Delivery Queue Length: The number of external
items in the largest delivery queue.
- External Retry Remote Delivery Queue Length: The number of
external items that are queued for retry in the remote delivery
queues.
- Internal Active Remote Delivery Queue Length: The number of items
in the active remote delivery that are queued for internal
destinations.
- Internal Aggregate Delivery Queue Length: The number of internal
items that are queued for delivery in all internal queues.
- Internal Largest Delivery Queue Length The number of internal
items in the largest delivery queue.
- Internal Retry Remote Delivery Queue Length: The number of
internal items that are queued for retry in the remote delivery
queues.

4. APMUI77IF02 support: With MS Exchange Agent v6312IF01 agent,
APMUI77IF02 (and onwards) will display only mandatory and configured
services in Exchange APMUI dashboard.

5. Added following new attribute groups :
- MS Exchange Top Ten Senders: This data set provides information
about top ten email senders.
- MS Exchange Top Ten Receivers: This data set provides information
about top ten email receivers.
- MS Exchange Top Ten Largest Emails: This data set provides
information about top ten largest emails.

Enhancements in the Active Directory Agent:
1. Added support for DBCS character encoding.
2. RFE: 61487
Abstract: Timestamp comparison for "RPL Partner Last Success Time"
and "RPL Partner Last Attempt Time" attribute in situation formula.
Additional Information: Timestamp datatype is added for "RPL Partner
Last Success Time" and "RPL Partner Last Attempt Time" attribute.
Now timestamp comparison can be done in the situation formula for
these attributes. Enhancements in the Tivoli Common Reporting (TCR):
There are no enhancements in this section.
For more information about Tivoli Common Reporting, see the "Tivoli
Common Reporting for the monitoring agent" chapter in the agent
reference guides at the following location on the SMC wiki:
(https://www.ibm.com/developerworks/community/groups/service/html/
communityview?communityUuid=0587adbc-8477-431f-8c68-9226adea11ed#
fullpageWidgetId=W42ce7c6afdb9_42c2_a9ea_e1ba310bea8c)
3. Added following new attribute groups :
- K3z_Replication: This data set provides information to monitor
the directory service agent (DSA) on Active Directory.
- ADFS: This data set provides Statistics associated with AD FS on
Federation server.
- ADFS Proxy: This data set provides information associated with
AD FS Proxy o Federation Server.
- Asynchronous Thread Queue: This data set provides statistics
associated with Asynchronous Thread Queue.
4. Superseded the Replication Attribute group.
5. New Situations added in Active Directory:
- KDRA_Comp_Inbound_Bytes_Warning.htm
- KDRA_Comp_Outbound_Bytes_Warning.htm
- KDRA_Highest_USN_Critical.htm
- KDRA_Inbound_Bytes_Total_Warning.htm
- KDRA_Inbound_ObjUp_Warning.htm
- KDRA_Inbound_Obj_Appl_Pct_Warn.htm
- KDRA_Inbound_Obj_Filt_Pct_Warn.htm
- KDRA_Inbound_Prop_Appl_Pct_Warn.htm
- KDRA_Inbound_Prop_Filt_Pct_Warn.htm
- KDRA_Intersite_Percent_High_Warn.htm
- KDRA_NTP_Connection_Blocked_Warn.htm
- KDRA_Outbound_Bytes_Total_Warn.htm
- KDRA_Outbound_Obj_Filt_Pct_Warn.htm
- KDRA_Pending_Rep_Sync_Warning.htm
- KDRA_Uncomp_Inbound_Bytes_Warn.htm
- KDRA_Uncomp_Outbound_Bytes_Warn.htm
- KRep_InterSite_Repl_Prtnrs_Warn.htm
- KRep_SiteLinks_Warning.htm
- KRep_Site_BridgeHeads_Warning.htm

6. Added following New Workspaces:
- Federation Server
- Federation Proxy Server

Enhancements in the .NET Data Collector:
1. configdc getconfig command displays status of a component as
"Error" if it is not registered properly.
2. Failed transactions for ASP.NET MVC are now monitored. If a
controller generates response other than HTTP status code 2XX and
3XX then it will be marked as a failed transaction.
3. Calls to asynchronous WCF services (using IAsyncResult) are now
monitored.

Enhancements in the IIS agent:
1. Custom Fields Attribure
In IIS 8.5 administrator can provide a selection of optional fields
to log with the existing default logging fields. This selection of
optional fields and their values is displayed as comma separated
key value pair.

Enhancements in .NET agent:
1. For following attribute groups data sources are changed from WMI
to Perfmon
- NET_CLR_Exceptions
- NET_CLR_Interop
- NET_CLR_Jit
- NET_CLR_Loading
- NET_CLR_Threads
- NET_CLR_Memory
- NET_CLR_Remoting
- NET_CLR_Security
- Windows_Workflow_Foundation
- Windows_Workflow_Foundation_V4
- Workflow_ServiceHost_V4
- Service_Model_Svc_Host
- Service_Model_Svc_Host_V4

3.0 Architecture and prerequisites
====================================
For information about system requirements, go to the software product
compatibility reports website, and search for the ITCAM for Microsoft
Applications product:
(http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html).

3.1 Prerequisites for this fix
----------------------------------
The minimum required version of IBM Tivoli Monitoring is V6.2.3, Fix Pack 3.

4.0 Image directory contents
=============================
The following folder structure of the image is created:

- WINDOWS folder
This folder contains the binary files for installing the 32-bit and 64-bit
agents. 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
- Microsoft Lync Server agent
- .NET Data Collector
- Application LaunchPad and Discovery and Deployment support files
- Network Devices agent

- REPORTS folder
This folder contains subdirectories that include the .zip files of the agents.
The subdirectories are named according to the "K<agent code>" format. The .zip
files contain Cognos data models and reports.

- 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 the 32-bit and 64-bit agents.

5.0 Installation instructions
==============================
See the following publications for complete information:
- IBM Tivoli Monitoring Installation and Setup Guide
- Installation and configuration guides of agents.

You can view the Installation and Configuration guides at the ITCAM for Microsoft
Applications V6.3.1 Information Center
(http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/
com.ibm.itcamms.doc_6.3.1/welcome_msapps631.html).

6.0 Additional installation information
========================================

6.1 Installation instructions for agent baroc file
---------------------------------------------------
For information about installation and configuration of the baroc files,
see "Setting up event forwarding to Tivoli Enterprise Portal" in the IBM
Tivoli Monitoring Installation and Setup Guide.

6.2 Verifying the update
-------------------------
1. To verify whether 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.03.01.10.

After the agent is restarted, you can also use the GUI to verify whether the
agent was updated. For the agent on Windows systems, the version number is 06.03.01.10.

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 that all components have been installed, run the following command:
$CANDLEHOME/bin/cinfo -i

On Windows systems:
To validate that all components have been installed, run the following command:
%CANDLE_HOME%\bin\kincinfo –i

7.0 Known problems and workarounds
===================================
For the Hyper-V Server agent:
Abstract: The agent support files on the Tivoli Enterprise
Portal cannot be upgraded to V6.3.1 Fix Pack 13 by using the
self-describing agent feature.
Problem: The self-describing agent feature for the Tivoli
Enterprise Portal Server is enabled. When the Microsoft Hyper-V
Server agent support files for the Tivoli Enterprise Portal
Server are upgraded to V 6.3.1, Fix Pack 13, the support files
are not automatically upgraded to V 6.3.1, Fix Pack 13.
Workaround: Upgrade the Hyper-V Server agent support files for
the Tivoli Enterprise Portal Server manually to V6.3.1,
Fix Pack 13.

For the BizTalk Server agent:
Abstract: When you click cross-links in the views of the
Databases workspace of the BizTalk Server agent, the target
workspaces of the SQL Server agent do 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
When you click the "Databases" and "Log and Space Information"
cross-links in these views, the target workspaces of the SQL
Server agent do not open automatically. Workaround: After
clicking on the cross-links, when prompted, select the target
instance manually.

For the Exchange Server agent:
Abstract: On the Tivoli Enterprise Portal, the status for the two
situations is displayed as "problem”.
Problem: The Tivoli Enterprise Portal shows the status as 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 .NET Data Collector:
All the limitations that are mentioned in the Problems and
workarounds chapter in 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 has failed 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 web address:
http://www.microsoft.com/en-us/download/details.aspx?id=18471

Abstract: When the WCF service is being 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 ASP.NET impersonation for the service that
is being processed.

Abstract: When a one way web service is being 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, use the
following web address to download the Microsoft Visual C++ 2008
Service Pack 1 Redistributable Package (x86):
http://www.microsoft.com/en-us/download/details.aspx?id=5582
For a 64-bit operating system, use the following web address to
download the Microsoft Visual C++ 2008 Service Pack 1
Redistributable Package (x64):
http://www.microsoft.com/en-us/download/details.aspx?id=2092

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 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, as shown: ktj_ADOAggregation.Enabled=false.
3. Open the command prompt and browse to the bin directory of .NET
Data Collector.
4. Run the configdc activateconfig 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, as shown: ktj_ADOAggregation.Enabled=false.
3. Open the command prompt and browse to the bin directory of
.NET Data Collector.
4. Run the configdc activateconfig command.
5. Restart all the .NET applications.

Abstract: After remote or silent installation, .NET Data Collector
needs to be configured manually by going to a particular
installed instance.
Problem: .NET Data Collector is configured using its own utilities
either by using “configdc” or by UI tool “KK4ConfigProperties.exe”
present at “<CANDLE_HOME>\ k4\bin\PropertiesEditor”. In the ITM
architecture there is no way provided to provide inputs to these
configuration utilities remotely unlike any other agent using tacmd
or TEP GUI.
Workaround: Currently there is no work around for this problem.
User has to manually configure the .NET Data Collector using either
by “configdc” through command line or “KK4ConfigProperties.exe UI”.

For the Lync 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: There is no work around for this problem. It is a
Microsoft limitation.
For more information, refer the following link:
https://support.microsoft.com/en-us/kb/325413
For Tivoli Common Reporting (TCR):
There are no changes hence the agent package version is still
631FP2

8.0 Additional product information
====================================

For the Active Directory agent:
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 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.

For the Hyper-V Server agent:
1. The following attribute groups are not supported on the
Windows Server 2012 R2 operating system:
-Hyper V Virtual Machine Summary
-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:
-Hyper V Virtual Machine Summary
-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

For the Lync Server agent:
1. Partially supports archiving, monitoring, and CDR roles of
the Lync Server for version 2013 and Skype for Business 2015
2. 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 will
run on every Monday at the time that is configured by the user.
If a monthly scheduling frequency is set, then the scheduler
will run on the first day of every month at the time that is
configured by the user.
5. Configuration panel does not validate any parameters. The
user must follow the guidelines that are mentioned at every
field and enter the data in the correct format.

For additional technical resources, see the following web addresses:
-IBM Tivoli Monitoring Information Center:
http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.itm.doc_6.3
fp2/welcome.htm
-Tivoli Composite Application Manager for Microsoft Applications Information
Center:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamms
.doc_6.3.1/
welcome_msapps631.html
-Tivoli Composite Application Manager for Microsoft Applications website:
http://www.ibm.com/software/tivoli/products/monitoring-microsoft-applications/

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.

10.0 Notices
=============

{Add or remove non-IBM trademark names as appropriate. Mark the first
occurrence of IBM and special non-IBM trademark names with a '(R)'.
See http://www.ibm.com/legal/copytrade.shtml for a complete list of non-IBM
trademark names.}

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, o
ther 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.