<<<<USE COURIER REGULAR 10 FONT IF YOU WOULD LIKE TO PRINT THIS DOCUMENT>>>>
Trend Micro, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Case Diagnostic Tool ApexOne Exclusive 2020 for Microsoft (TM) Windows (TM)
version 3.0 - Build 1069
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TERMS AND CONDITIONS: This tool was developed by Trend Micro, Inc.
This tool has received limited testing and is for your internal use
only. THIS TOOL IS PROVIDED "AS IS" WITHOUT WARRANTIES OF ANY KIND.
TREND MICRO MAKES NO WARRANTY ABOUT THE OPERATION OR PERFORMANCE OF
THIS TOOL NOR DOES IT WARRANT THAT THIS TOOL IS ERROR FREE. TO THE
FULLEST EXTENT PERMITTED BY LAW, TREND MICRO DISCLAIMS ALL IMPLIED
AND STATUTORY WARRANTIES, INCLUDING BUT NOT LIMITED TO THE IMPLIED
WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT AND FITNESS FOR A
PARTICULAR PURPOSE. THIS TOOL IS SUBJECT TO CHANGE AND MODIFICATION,
INCLUDING, WITHOUT LIMITATION, CHANGES AND MODIFICATIONS WITH RESPECT
TO PERFORMANCE AND FUNCTIONALITY ANY TIME AT THE SOLE DISCRETION OF
TREND MICRO.
Contents
===================================================================
1. About Case Diagnostic Tool ApexOne Exclusive 2019 v3.0
1.1 Supported Trend Micro Products
1.2 Files Included in This Release
2. What's New
3. Documentation Set
4. System Requirements
5. Installation
6. Usage
6.1 Running the Main Program in UI Mode
6.2 Running the Main Program in Silent Mode
6.3 Running the Main Program in Background Mode (for OfficeScan
Toolbox integration only)
7. Known Issues
8. Release History
9. Contact Information
10. About Trend Micro
11. License Agreement
===================================================================
1. About Case Diagnostic Tool ApexOne Exclusive 2019 v3.0
========================================================================
Trend Micro (TM) Case Diagnostic Tool ApexOne Exclusive 2019 collects
Trend Micro software settings and environment setup specifications
from a user's computer. Trend Micro uses this information to
troubleshoot problems related to the software.
1.1 Supported Trend Micro Products
=====================================================================
Trend Micro Case Diagnostic Tool ApexOne Exclusive 2019 uses product
extension plug-ins in the "ExInterface" folder to support different
products.
- Trend Micro Apex One (TM) 2019
- Trend Micro Apex Central (TM) 2019
- Trend Micro Apex One (TM) as a Service 2019
- Trend Micro Apex Central (TM) as a Service 2019
- Trend Micro OfficeScan(TM) 11, XG, XG SP1, XG MDR
For internal users:
ExInterface_OSCE_client.dll/ExInterface_OSCE_client.ini :
Trend Micro OfficeScan Client for Windows NT/2000/XP/Server
2003 [5.58 - 7.3]
ExInterface_OSCE_server.dll/ExInterface_OSCE_server.ini :
Trend Micro OfficeScan (TM) Server [5.58 - 8.2]
ExInterface_OSCE_11client.dll/ExInterface_OSCE_11client.ini :
Trend Micro OfficeScan Client [10.65 - 11.0]
ExInterface_OSCE_11server.dll/ExInterface_OSCE_11server.ini :
Trend Micro OfficeScan (TM) Server [10.65 - 11.0]
ExInterface_OSCE_12client.dll/ExInterface_OSCE_12client.ini :
Trend Micro OfficeScan Client [11.95 - 12.0]
ExInterface_OSCE_12server.dll/ExInterface_OSCE_12server.ini :
Trend Micro OfficeScan server [11.95 - 12.0]
ExInterface_OSCE_13client.dll/ExInterface_OSCE_13client.ini :
Trend Micro OfficeScan Client [13.0 - 13.95]
ExInterface_OSCE_13server.dll/ExInterface_OSCE_13server.ini :
Trend Micro OfficeScan server [13.0 - 13.95]
ExInterface_OSCE_14client.dll/ExInterface_OSCE_14client.ini :
Trend Micro OfficeScan Client [14.0 - 14.0]
ExInterface_OSCE_14server.dll/ExInterface_OSCE_14server.ini :
Trend Micro OfficeScan server [14.0 - 14.0]
1.2 Files Included in This Release
=====================================================================
Running Case Diagnostic ToolCase Diagnostic Tool ApexOne Exclusive 2019 requires the following files:
FILE FUNCTION
-----------------------------------------------------------------
CDTApexOneExclusive2020.exe Main program UI.
CDTChild.exe CDT Child program.
CaseDiagnosticTool.dll Main framework that provides
functions for getting system and
product information.
CaseDiagnosticTool.ini Stores global and silent mode
configuration.
ExInterface_Common.dll Provides common extension
interface functions.
PSAPI.dll Retrieves system information.
ExInterface\*.ini Trend Micro products extension
INI file
ExInterface\*.dll Trend Micro products extension
DLL file
Tools\*.* Tools used by Case Diagnostic
Tool to execute product
related functions.
Licenses\*.txt Copyright messages of 3rd-party
modules used by Case Diagnostic
Tool
-----------------------------------------------------------------
After executing, Case Diagnostic Tool creates the following
files (not including the logs defined in the product extension
definition INI file):
FILE FUNCTION
-----------------------------------------------------------------
{output folder}\
ReadmeFirst.txt Summary information
{output folder}\System_Info\
msinfo.nfo Microsoft System Information
output
SystemInfo_Summary.txt System summary information
SystemInfo_InstalledProgram.txt List of system installed
programs
SystemInfo_RunningProcess.txt List of system running processes
SystemInfo_NetworkStatus.txt Status of system network
System.evt Event log for system error
records
IIS_Log.txt IIS log for system error records
Regist_Info.txt List of Trend Product(s) Registry
information
Security.evt Event log for Security audit
records
Application.evt Event log for Application error
records
CaseDiagnosticTool.ini The copy of configuration when
running Case Diagnostic Tool
CaseDiagnosticTool.log Case Diagnostic Tool debugging
information
(if there is any product selected)
{output folder}\{product name}\
ProductInfo.txt Product information
{output folder}\{product name}\CollectedFile\
RootRegKey.reg Product registry export
ProductFilesList.txt List of all files under the
product home directory
EventFilesList.txt List of all logs Case Diagnostic
Tool collected
{output folder}\{product name}\CollectedFile\Event#\
__FILELIST__.LOG The mapping from the original
log file location to the new one
in this folder
(log files defined in .INI file are collected and saved here)
-----------------------------------------------------------------
2. What's New
========================================================================
This release of Trend Micro Case Diagnostic Tool ApexOne Exclusive 2020(CDTApexOneExclusive2020) provides the
following new feature:
#Version 3.0
- Build 1069: ACC-6406: Add Program Ring upgrade log files.
- Build 1068: PCT-6825: Fix issue that can't create log folder.
- Build 1067: Add IPC log for DLP 5278 and later
- Build 1066: Collect SO files for both server and agent
- Build 1065: Update verifycert_A1.exe tool.
- Build 1064:
1. Integrate verifycert_A1.exe which is developed by iVP team into CDT tool
2. Add verifycert.log for troubleshooting OSF issue
3. Fix issue of collecting DLP log files
- Build 1063:
1. Collect XBC related registry key
2. Add more DLP debug log and config files
- Build 1062:
1. SEG-130342:Support dump all file lists under the Cloud Endpoint folder to "ProductFilesList.txt"
2. SEG-174752:Need to fix Apex Central Agent service can be stopped and deleted even under using CDT while upgrading to B11564.
- Build 1061:
1. Add UMH log collecting for UMH troubleshooting
- Build 1060:
1. Add XBC log collecting for EndpointBasecamp troubleshooting
- Build 1059:
1. Add more log collecting for DLP troubleshooting
- Build 1058:
1. Collect registry info for Vulnerability Protection (iVP).
- Build 1057:
1. Fixed the Apex One server after Patch3 OfcDebug log failing to be turned ON successfully issue
2. Adjusted the display order(server above agent) on the CDT log choosing console
3. Stopped collecting iES huge reports files, to avoid CDT package too big
- Build 1049:
1. Fixed the multi-thread issue no ProductFilesList.txt collected under server log folder or agent log folder
when both Apex One server and Apex One agent debug logs are enabled
2. Removed crash dump files creating under unhandled exception situation
- Build 1046:
Removed "SA Unload Tool" folder from Tools folder
- Build 1040:
1. Collect DLLBackup folder for XG version, preparing for XG Sp1 Patch3 release
2. Collect Apex One server OfcHotfixToolDebug.log, for XDR on boarding
3. Collect Apex One Agent EndpointBasecamp.log, for XDR on boarding
- Build 1038:
1. Now there are two executables, 'CDTApexOneExclusive2020.exe' is the entry point for the main program.
2. Changes to Firewall driver log collection
1> By default, CDT will no longer enable the LWF/WFP debug modes or collect driver debug logs. To enable Firewall driver log collecting,
the user needs to set the key 'EnableFirewallDriverLog' to 1 in file 'ExInterface_OSCE_1*agent.ini'.
2> Firewall log level changed to 0xFFFFFFFF when enabled.
3> Fixed the issue that sometimes CFWDBG is unable to turn OFF firewall driver debug mode.
4> Copy CFWDBG to agent install folder instead of C:\Windows\ folder in OSCE 14.
3. After log collection, log files left under C:\ and tmfilter.log will be removed.
4. Existing C:\Windows\TmFilter.log is now renamed before debug mode starts.
5. Fixed crash issue when disabling iES debug mode.
6. TMCOMM debug mode is no longer enabled.
7. CDT only collects IIS log files and HTTPERR log files that are created within seven days.
8. For UMH debug log collection, timeout is set to 10 min for ListDlls, which is used to enumerate all loaded DLLs for all running processes.
9. Set timeout to 10 min for MsInfo32.exe to run, to prevent CDT from running endlessly due to MsInfo32.exe not being able to stop.
10. Transferred AEGIS debug log into the "Behavior Monitor Issues" category, from "Scan Related Issues".
11. Fixed the issue that AEGIS debug mode can not be turned OFF sometimes.
Debug level=0 is now enforced instead of recovering original value.
12. Limited AEGIS debug logs collection to be within seven days only, this change is to avoid collecting too many huge AEGIS debug log files.
13. Added AEGIS_BM.log, AEGIS_BM_Server.log into Agent CDT collecting.
14. Added reminding message onto the UI: "if CDT crashed or stopped unexpectedly due to reboot,
user needs to re-run CDT and press Stop Debug Mode button again to stop all modules' debug mode".
15. Fixed the issue that C:\ofcdebug.log file can not be collected, only .7z files are collected.
16. Added a wrapper to ensure that debug mode is turned off when CDT is terminated unexpectedly.(except for when the computer is restarted during the collection.)
17. If the user allows for feedback function, CDT will send feedback data to Google Analytics when a user clicks buttons.
Collected info includes which button the user clicked on,
Trend Micro product name, version number, product GUID, and time consumed collecting logs.
Known Issue:
1> For OSCE XG, with non-updated Firewall components version, e.g. 5.83, and in some Apex One environments where copying CFWDBG to agent install folder may fail,
CDT will FAIL to enable FW driver log even when the key EnableFirewallDriverLog is set to 1.
2> In some agent environments, where all debug modes are enabled with a long log generation period,
log collection step may take a long time(20 -30 min) due to either the high log count or big-sized logs.
3> Forced 'CDTChild.exe' kill, without pressing debug off button, will trigger CDTApexOneExclusive2020.exe to turn debug-modes off.
In some agent environment, a 'Bad Image Error' message may show.
- Build 1004:
- Only works for Apex One, Apex One SAAS, Apex Central, OSCE 11, XG and XG SP1. Removed other products to accelerate product detection process.
- Improved agent service restarting performance in Debug ON/OFF process.
- Added a button, "Start Debug Mode Without Restarting Services", to disable restarting agent services as an option. It will accelerate the Debug ON/OFF process without restarting agent services.
- Improved the system and event log collecting performance.
- Used 7-zip instead zip-lib to improve log file zipping performance.
This release of Trend Micro Case Diagnostic Tool (CDT) provides the following new feature:
#Version 2.6
- Build 1253:
- [Apex One Agent]
Fix the issue where CDT will collect only 0x32 level debug logs if user selects more than one checkboxes under "Scan Related Issue".
The 0x32 debug log does not help any AEGIS SEG case.
Starting from build 1253, CDT will enable and collect 0xFF debug logs of AEGIS at MAX level, under any condition,
as long as user checks the AEGIS debug log sub menu under "Scan Related Issue" when starting debug mode.
Note: If you encounter hang or high CPU usage issue after enabling AEGIS debug logs using latest CDT,
we suggest you upgrade the AEGIS module versions to the latest(2.98.1180 or above) by installing the latest Apex One Hotfix or Critical Patch.
- [OSCE/ApexOne Agent]
To improve CDT's performance, for ProductFilesList.txt,
replace collecting files' information list under [C:\Windows\System32\]
with collecting files' information list under [C:\Windows\System32\drivers\] only
- [Apex Central]
Fix the issue that the log level of CMEFScheduler.NET.exe.config cannot be set correctly
- [Apex Central]
Fix the side effect of one previous change.
Final behavior: In saas mode (=CDT silent mode), UI message box should not pop up, otherwise, CDT would hang.
In on premise mode, the message box is shown as usual.
- [Apex One/OSCE Server]
Changed collecting PCCSRV\Download\Hotfix*.txt to collecting PCCSRV\Download\Hotfix*.*
- [WFBS-SVC]
When CDT turns on debug mode, it needs to stop and restart WFBS-SVC agent services.
If agent restart fails, agent may become offline on the web console.
To prevent agent restart failure, timeout value for stopping WFBS-SVC agent services is increased.
- Build 1242:
- Warning pop-up for service restart before start debug mode
- Fix the issue: the debug mode can't be restarted after turning it off
- Fix the issue: collecting huge/corrupted Server CDT package if user chooses to enable
* Smart Protection Network
* Collect integrated smart scan server debug information with patterns
- Collect sscfg.ini under PCCSRV when user chooses to collect Basic Information
- Rollback: Collecting today's log by default
- Rollback: Supporting Server Core platform
- Build 1241:
- Support Windows Server Core Platform
- Build 1240:
- Enable all debugging items at once
- Set collect today's log by default
- Build 1239:
- Support SMEX 14.0
- Update tool for WFBS exploit dump collection
- Build 1238:
- Support Apex One 2019 and Apex Central 2019 on-premise version
- Support Portal Protect 2.5 SP1
- Build 1237:
- [WFBS-SVC] Translate Endpoint Sensor and Application Control sections
- Build 1236:
- For OfficeScan Toolbox integration
- Build 1235:
- Support WFBS-SVC 6.6
- Build 1234:
- Support Apex One (TM) as a Service 2019, Apex Central (TM) as a Service 2019, Apex One (TM)(MAC) as a Service 2019
- Build 1233:
- Support WFBS-SVC 6.5 exploit dump collection
- Build 1232:
- Add Event13 to Category11 due to POP3 mail scan uses Osprey and Tmproxy module
- Build 1231:
- Support SMEX 12.5
- Build 1230:
- Support SMEX 11.7
- Build 1229:
- Support OSCE XG MDR Version
- TMEE: Enhance to obtain Log Server Logs during replication issues
- Build 1227：
- Update the copyright
- Build 1226:
- Add new log file into TMCM CDT log collecting
- Build 1225:
- Support WFBS 10
- Build 1224:
- Support SMEX12.5
- Enhance OSCE 12 agent and server log collecting
- Build 1223:
- Support WFBS-SVC 6.3
- Build 1222:
- [OSCE] Update AEGIS debug log flag
- Build 1221:
- Support OSCE XP SP1
- Support TMCM 7.0
- Support TMES 1.6
- [TMES] Fix log collecting issue
- [TMCM] Fix the issue of false set up the Diagnostic log folder permission
- Build 1220:
-To support trend micro endpoint sensor 1.6
- Build 1219:
-Support WFBS-SVC6.2
- Build 1218:
-[OSCE] Fix the FW debug log collecting issue for XG version
- Build 1217:
-[OSCE] Fix the issue of collecting FW debug log on Windows 7 environment
- Build 1216:
-For OSCE to allow TMSM 3.0 for Saas to collect debug information
- Build 1215:
-For WFBS 9.5 to collect debug information of RMAgent
- Build 1214:
-Add SMEX-11.6 support
- Build 1213:
-Support WFBS 9.5
-OSCE log collecting enhancement(hotfix_history.ini, OfUninst.ini, Agent.ini, Porduct.ini, web server log and ICRC debug log)
- Build 1212:
-Disable unsupported log collection for WFBSS 6.1
-Support PortalProtect 2.5
-Support DEP\ASLR
- Build 1211:
-Collect more logs for TMEE 6.0
- Build 1210:
-WFBSS6.1 is going to enter EB
- Build 1209:
-Fix the error and collect enough information for OSCE team
- Build 1208:
-Test the CDT Compatibility
- Build 1206:
-Add more log collecting for DLP troubleshooting
- Build 1205:
-Add some readme information for OSCE team
- Build 1204:
-Change CDT logo and add minimize UI button
- Build 1203:
-Support WFBS-SVC6.0
- Build 1202:
-OSCE team support .dll list for RD and QA check issue
- Build 1201:
-Support to detect OSCE12EB and collect some new feature logs
- Build 1200:
-Support to detect OSCE12 and collect some new feature logs
- Build 1198:
-Collect more logs for TMSM
- Build 1197:
-WFBS-SVC JA support request for a CDT official build with Japanese & English language.
- Build 1195:
-To support WFBS-SVC JA
- Build 1194:
-To support WFBS-SVC 5.9 product
- Build 1192:
-OSCE fixes an issu for UMH module collectiong on Windows8.1 platform
- Build 1191:
-Collect more ICAP debug logs for SPFS 6.0
- Build 1181:
- After collecting debug log, it will popup to let customer delete the debug log files
- Build 1178:
- Fix IS Reg cannot be collected on 64bit
- Fix IS File list cannot be collected on 64bit
- Build 1175:
- Update CDT to generate short-cut log file through the absolute path of the source log file
- Build 1174:
- Fix the issue in ExInterface for TMEAC 2.0 Agent support
- Build 1173:
- Allow CDT to collect OSCE upgrade log by default
- Fix incorrect behavior of WFBS log collecting
- Build 1172:
- Modify UI wording for WFBS-SVC product
- Build 1171:
- OSCE/WFBS/WFBS-SVC teams fix the hanging issue which happens on windows 10
- Build 1170:
- CDT Tool Support Windows 10
3. Documentation Set
========================================================================
In addition to this Readme.txt, the documentation set for this
product includes the following:
- Getting Started Guide -- Product overview, installation planning,
installation and configuration instructions, and basic information
intended to get you "up and running."
4. System Requirements
========================================================================
- Windows Server 2008
- Windows 7
- Windows Server 2008 R2
- Windows 8
- Windows Server 2012
- Windows 8.1
- Windows Server 2012 R2
- Windows 10
- Windows server 2016
5. Installation
========================================================================
No installation steps required.
6. Usage
========================================================================
6.1 Running the Main Program in UI Mode
=====================================================================
a. Execute the file CaseDiagnosticTool.exe. The Case Diagnostic
Tool Wizard will then guide users through the data collection
process.
b. Retrieve the data generated by Case Diagnostic Tool. Case
Diagnostic Tool saves all collected data in a password-protected
ZIP file (password is "trend").
6.2 Running the Main Program in Silent Mode
=====================================================================
a. Modify the CaseDiagnosticTool.ini file. Please refer to the
comments in CaseDiagnosticTool.ini to see how the values of each
variable can be set.
b. Run CaseDiagnosticTool.exe on the machine that is experiencing
problems.
c. Try reproducing the problem by performing the actions that lead to
it. These actions, as well as the error messages, will be included
in the debugging information.
d. Send the collected data to Trend Micro Technical Support either
through email or courier.
6.3 Running the Main Program in Background Mode (for OfficeScan Toolbox
integration only)
======================================================================
a. Read OfficeScan Toolbox Online Help or Administrative Guide for how
to run Case Diagnostic Tool from Toolbox.
b. Case Diagnostic Tool supported command line interface:
1) Usage:
CDTApexOneExclusive2019.exe -exn ExInterfaceName -eid EventID
[-cdl CDTDebugLevel]
[-edl ExInterfaceDebugLevel]
[-ipc ProcessCheckingInterval]
[-dir OutputLocation]
[-silrun RequireUserInteractionOrNot]
[-sdt DebuggingModeTime]
2) parameters:
-exn: The name of ExInterface.
Eg: For the OfficeScan 11 client, the name is "OSCE_11_client".
-eid: Event IDs in the specific ExInterface.
Eg: To select event 1, 2 and 3, the IDs are "1,2,3".
-cdl: Case Diagnostic Tool debug level.
-edl: ExInterface debug level (0 to 9).
-ipc: The interval of process checking in seconds.
-dir: Output location for Case Diagnostic Tool. By default, the
location is the folder containing the Case Diagnostic Tool.
-silrun: Require user interaction to enable/disable debug mode.
"1" means user interaction is required
"0" means user interaction is not required.
-sdt: Specifies the product's debugging mode time in minutes.
Eg: To specify a debug mode that executes for 10 minutes,
type "10".
To specify an endless debug mode, type "0".
3) Notes:
3.1) Use a semicolon to specify multiple values for -exn and -eid
Eg: To collect Events 1 and 2 for an OfficeScan 10.6 client
and Events 3 and 4 for an OfficeScan 10.5 client:
-exn=OSCE_10_6client;OSCE_10_5client -eid=1,2;3,4
3.2) The parameter value cannot contain the "hyphen" character
(-).
7. Known Issues
========================================================================
7.1 The generated NFO from Windows XP and Windows 2003 is not
supported on the Windows 2000 "winmsd" console.
7.2 On Windows 2000, for double-byte languages, the generated NFO
lacks the following two categories: Resources and Components.
7.3 Newer CPUs may not be recognized correctly.
8. Release History
========================================================================
VERSION Build RELEASE DATE
---------------------------------------------------------------------------------------------
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1061 JAN 25, 2022
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1060 DEC 27, 2021
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1059 DEC 15, 2021
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1058 OCT 14, 2021
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1057 Feb 02, 2021
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1049 OCT 16, 2020
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1046 SEP 24, 2020
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1040 JULY 16, 2020
Case Diagnostic Tool ApexOne Exclusive 2020 for Windows 3.0 1038 JUNE 22, 2020
Case Diagnostic Tool ApexOne Exclusive 2019 for Windows 3.0 1004 OCT 21, 2019
VERSION Build RELEASE DATE
---------------------------------------------------------------------
Case Diagnostic Tool for Windows 2.6 1253 OCT 17, 2019
Case Diagnostic Tool for Windows 2.6 1242 Jul 09, 2019
Case Diagnostic Tool for Windows 2.6 1241 May 29, 2019
Case Diagnostic Tool for Windows 2.6 1240 Apr 22, 2019
Case Diagnostic Tool for Windows 2.6 1239 Apr 02, 2019
Case Diagnostic Tool for Windows 2.6 1238 Mar 22, 2019
Case Diagnostic Tool for Windows 2.6 1237 Mar 22, 2019
Case Diagnostic Tool for Windows 2.6 1236 Mar 08, 2019
Case Diagnostic Tool for Windows 2.6 1235 Jan 24, 2019
Case Diagnostic Tool for Windows 2.6 1234 Nov 05, 2018
Case Diagnostic Tool for Windows 2.6 1233 Oct 23, 2018
Case Diagnostic Tool for Windows 2.6 1232 Sep 17, 2018
Case Diagnostic Tool for Windows 2.6 1231 Aug 17, 2018
Case Diagnostic Tool for Windows 2.6 1230 Jul 17, 2018
Case Diagnostic Tool for Windows 2.6 1229 Jun 08, 2018
Case Diagnostic Tool for Windows 2.6 1227 Feb 24, 2018
Case Diagnostic Tool for Windows 2.6 1226 Feb 06, 2018
Case Diagnostic Tool for Windows 2.6 1225 Jan 24, 2018
Case Diagnostic Tool for Windows 2.6 1224 Jan 12, 2018
Case Diagnostic Tool for Windows 2.6 1223 Dec 22, 2017
Case Diagnostic Tool for Windows 2.6 1222 Dec 18, 2017
Case Diagnostic Tool for Windows 2.6 1221 Nov 13, 2017
Case Diagnostic Tool for Windows 2.6 1220 Oct 13, 2017
Case Diagnostic Tool for Windows 2.6 1218 Jul 10, 2017
Case Diagnostic Tool for Windows 2.6 1217 Jun 26, 2017
Case Diagnostic Tool for Windows 2.6 1216 May 31, 2017
Case Diagnostic Tool for Windows 2.6 1215 May 04, 2017
Case Diagnostic Tool for Windows 2.6 1214 Apr 18, 2017
Case Diagnostic Tool for Windows 2.6 1213 Apr 12, 2017
Case Diagnostic Tool for Windows 2.6 1212 Apr 06, 2017
Case Diagnostic Tool for Windows 2.6 1211 Mar 01, 2017
Case Diagnostic Tool for Windows 2.6 1210 Feb 20, 2017
Case Diagnostic Tool for Windows 2.6 1209 Feb 03, 2017
Case Diagnostic Tool for Windows 2.6 1208 Nov 17, 2016
Case Diagnostic Tool for Windows 2.6 1206 Oct 25, 2016
Case Diagnostic Tool for Windows 2.6 1205 Oct 18, 2016
Case Diagnostic Tool for Windows 2.6 1204 Oct 18, 2016
Case Diagnostic Tool for Windows 2.6 1203 Sep 14, 2016
Case Diagnostic Tool for Windows 2.6 1202 Sep 12, 2016
Case Diagnostic Tool for Windows 2.6 1201 Aug 01, 2016
Case Diagnostic Tool for Windows 2.6 1200 Jul 18, 2016
Case Diagnostic Tool for Windows 2.6 1198 Jun 28, 2016
Case Diagnostic Tool for Windows 2.6 1197 Jun 23, 2016
Case Diagnostic Tool for Windows 2.6 1195 Jun 15, 2016
Case Diagnostic Tool for Windows 2.6 1194 May 13, 2016
Case Diagnostic Tool for Windows 2.6 1192 May 03, 2016
Case Diagnostic Tool for Windows 2.6 1191 Mar 08, 2016
Case Diagnostic Tool for Windows 2.6 1181 Dec 03, 2015
Case Diagnostic Tool for Windows 2.6 1178 Nov 09, 2015
Case Diagnostic Tool for Windows 2.6 1175 Nov 03, 2015
Case Diagnostic Tool for Windows 2.6 1174 Oct 09, 2015
Case Diagnostic Tool for Windows 2.6 1173 Sep 17, 2015
Case Diagnostic Tool for Windows 2.6 1172 Sep 10, 2015
Case Diagnostic Tool for Windows 2.6 1171 Sep 07, 2015
Case Diagnostic Tool for Windows 2.6 1170 Aug 05, 2015
9. Contact Information
========================================================================
A license to the Trend Micro software usually includes the right to
product updates, pattern file updates, and basic technical support
for one (1) year from the date of purchase only. After the first
year, Maintenance must be renewed on an annual basis at Trend Micro's
then-current Maintenance fees.
You can contact Trend Micro via fax, phone, and email, or visit us
at:
http://www.trendmicro.com
Evaluation copies of Trend Micro products can be downloaded from our
web site.
Global Mailing Address/Telephone numbers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For global contact information in the Asia/Pacific region, Australia
and New Zealand, Europe, Latin America, and Canada, refer to:
http://www.trendmicro.com/en/about/overview.htm
The Trend Micro "About Us" screen displays. Click the appropriate
link in the "Contact Us" section of the screen.
Note: This information is subject to change without notice.
10. About Trend Micro
========================================================================
Trend Micro Incorporated, a global leader in Internet content
security and threat management, aims to create a world safe for the
exchange of digital information for businesses and consumers.
A pioneer in server-based antivirus with over 20 years experience,
we deliver top-ranked security that fits our customers' needs, stops
new threats faster, and protects data in physical, virtualized and
cloud environments. Powered by the Trend Micro
Smart Protection Network(TM) infrastructure, our industry-leading
cloud-computing security technology and products stop threats where
they emerge, on the Internet, and are supported by 1,000+
threat intelligence experts around the globe. For additional
information, visit www.trendmicro.com.
Copyright 2013, Trend Micro Incorporated. All rights reserved.
Trend Micro, the t-ball logo are trademarks of Trend Micro
Incorporated and are registered in some jurisdictions. All other marks
are the trademarks or registered trademarks of their respective
companies.
11. License Agreement
========================================================================
Information about your license agreement with Trend Micro can be
viewed at:
http://us.trendmicro.com/us/about/company/user_license_agreements/
Third-party licensing agreements can be viewed by opening the folder
"Licenses" and then viewing the *.txt files related to the modules
used by CDT.