Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Hot fixes and enhancements included in OfficeScan 10.6 SP2

    • Updated:
    • 12 Jan 2016
    • Product/Version:
    • OfficeScan 10.6
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Server Core
    • Windows 2008 Standard
    • Windows 2012 Enterprise
    • Windows 2012 Web Server Edition
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows 8 32-bit
    • Windows 8 64-bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Home
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary

Previous hot fixes and enhancements that are already included in OfficeScan 10.6 SP2.

Details
Public

Important: Solution details for every hot fix in this article are included in the latest version of the readme file.

Hot Fix Solutions for 10.0 SP1 (up to Patch5)
299830393045305230533062
306330793080
Hot Fix Solutions for 10.5 (up to Patch4)
124213022129214021422142.1
214321452147214921562160
216221642165216821682172
218321862187218921962214
221522182220222622322232.1
223322362236.1223922402241
224222432246224822532263
226622672275227722792322.2
3048
Hot Fix Solutions for 10.6
11161181120312061217.11232
1235.1124012431243.112441248
1258.11259.112631263.11263.21264
1268.112701270.11272.112771279
128312871289129112921294
12951299130013011301.11308
130913101312131613231328
133013321334133513371338
1338.113411342134413451349.1
1352204721032177
Hot Fix Solutions for 10.6 SP1 (up to Patch 1.1)
21512171217422032215.12243B
24082409.12411242024242426
2431.124322435243824452446
244924512452245524562457
2458246224642467.124702471
24742476

Important: Solution details for every hot fix in this article are included in the latest version of the readme file.

Hot Fix 1116

Issue: OfficeScan generates incorrect information on some fields when exporting the "OfficeScan exclusion settings.csv" file.

Hot Fix 1181

Issue: An OfficeScan 10.6 client will always try to connect to the Trend Micro ActiveUpdate server if it cannot connect to the OfficeScan server. However, the OfficeScan 10.6 client will not be able to connect to the ActiveUpdate server because the resource file specifies a wrong URL for the ActiveUpdate server.

Hot Fix 1203

Issue: The error message that appears when users input a name with underscore '_' for the Smart Protection Server in the OfficeScan console.

Hot Fix 1206

Issue 1: When users enable the Trend Micro Data Loss Protection(TM) device control feature and block access to USB devices, users can add entries to the "USB devices exception list" from the Web console. However, when users add several USB devices to the list and deploy the setting to clients, the client may not receive the complete list. This occurs because the size of the buffer for storing the exception list information in the client is insufficient.

Issue 2: OfficeScan clients create and delete the "C:\OSCE_DEBUG" folder repeatedly.

Note: The folder creation and deletion happens within a few milliseconds and can be detected only by using system monitoring tools such as FileMon for Microsoft(TM) Windows(TM).

Hot Fix 1217.1

Issue: The OfficeScan Digital Asset control definitions do not provide test validators for some regular expressions.

Hot Fix 1235.1

Issue: When users enable the "Add Manual Scan to the Windows shortcut menu on client computers" and the "Roaming Client" options before creating and deploying the client package, the first option disappears from the roaming client after client installation completes and the "Roaming Client" option is enabled in the client. As a result, users cannot scan files manually by right-clicking files.

Hot Fix 1240

Issue: On the OfficeScan management console, users cannot input server names with top-level domain (TLD) names that exceed eight characters. However, according to the Microsoft(TM) naming conventions (http://support.microsoft.com/kb/909264), DNS domain names can have up to 24 characters.

Hot Fix 1243

Issue: When customizing the firewall feature set, users do not have a way to deploy the "Feature" key globally from the OfficeScan server.

Hot Fix 1243.1

Issue: On the OfficeScan management console, users cannot input server names with top-level domain (TLD) names that exceed eight characters. However, according to the Microsoft(TM) naming conventions (http://support.microsoft.com/kb/909264), DNS domain names can have up to 24 characters.

Hot Fix 1242

Issue: The following message appears on computers running on the Microsoft(TM) Windows(TM) 2008 platform when OfficeScan 10.6 is installed on an Apache(TM) server and users run the script to set up an IIS Web server:

"Failed to create virtual host for LWCS in oscdebug.log. SVRSVCSETUP.exe returns without completing all the steps to install the server. IIS cannot load the management console."

Hot Fix 1248

Issue: The OfficeScan client console does not display the "Mail Scan" tab on computers running on a Microsoft(TM) Windows(TM) XP (32-bit) or Windows Server 2003 (32-bit) platform.

Note: The Microsoft Outlook(TM) mail scan function in the "Mail Scan" tab of the client is supported on Windows XP (32-bit) and Windows Server 2003 (32-bit) platforms only.

Hot Fix 1252

Issue: An unload password is required to unload an OfficeScan client. However, a vulnerability may allow malicious programs to retrieve a particular client's unload password or bypass the password authentication process.

Hot Fix 1258.1

Issue: If OfficeScan sets up multiple SPS servers, the OfficeScan client always connects to the secondary SPS server when it starts even when the primary SPS server is available and is the current SPS server. The OfficeScan client then switches to the primary SPS server several minutes after starting up.

Hot Fix 1259.1

Issue: According to Microsoft(TM) naming conventions (http://support.microsoft.com/kb/909264), DNS domain names can contain any number from 1 to 9 or a "-" character. However, users cannot input server names with top-level domain (TLD) names that use any of these characters.

Hot Fix 1263

Issue: When users upgrade an OfficeScan client from version 10.5 to 10.6, the client may report an "Onstart" event which triggers the server to check the domain information for the sorting rule feature. Under this situation, the server sends an "Id=42" command to the client to move domains even when there are no changes to the domain information. This can cause the client to repeatedly install the files in the installation folder.

Hot Fix 1263.1

Issue: While adding a firewall policy exception to a firewall policy on the "Network Computers > Firewall > Policies" page, when users select a registration key in the "Specify application registry key" option and save the changes, a different registry key appears on the corresponding exception information.

Hot Fix 1263.2

Issue: The "EnableApacheSSL()" function stores debug log information in the "szTemp" variable and the size of this variable is limited to 260 characters. However, since the "EnableApacheSSL()" function includes both the file path and computer name in debug log messages, the message length can exceed 260 characters. When this happens the "stprintf_s()" function, which utilizes the "szTemp" variable, stops unexpectedly.

Hot Fix 1264

Issue: A translation issue can prevent computers running on the Microsoft(TM) Windows(TM) Server 2008 or Windows XP platform from displaying the file version information for "svrsvcsetup.exe".

Hot Fix 1270

Issue: The OfficeScan DBServer.exe service hangs in an infinity loop when processing the Web Reputation Settings configuration record (WCSCfg) for non-existent client UIDs. This random issue causes a high-level CPU usage.

Hot Fix 1270.1

Issue: The Web Reputation Services(TM) in OfficeScan clients automatically tag Web sites that are in the list of blocked URLs as "DANGEROUS", however, the Trend Micro Control Manager(TM) server may record these Web sites as "SAFE (3)" in the database.

Hot Fix 1272.1

Issue: When users upgrade to OfficeScan 10.6 and some OfficeScan clients remain in version 8.0 due to company policy, the Web Reputation Services (WRS) settings configured in OfficeScan 10.6 are not applied to OfficeScan 8.0 clients.

Hot Fix 1277

Issue: The OfficeScan Database Service (DbServer.exe) stops unexpectedly while the OfficeScan server handles the data of Update Agents.

Hot Fix 1279

Issue: When the "AddTmListenServiceDependencies" key is set to a non-zero value, the "TmListen" service adds the "netprofm" service to its service dependency list. Since the "netprofm" service is only available on the Microsoft(TM) Windows(TM) Vista(TM) platform, the "TmListen" service on OfficeScan clients installed on the Windows XP or Windows 2003 platforms will not be able to start.

Issue: A logic issue in the OfficeScan server database causes the database backup task to fail.

Issue: An OfficeScan 10.6 client will always try to connect to the Trend Micro ActiveUpdate server if it cannot connect to the OfficeScan server. However, the OfficeScan 10.6 client will not be able to connect to the ActiveUpdate server because the resource file specifies a wrong URL for the ActiveUpdate server.

Issue: By default, the "Scan network drive" setting in both Manual and Real-time Scans is disabled. When the setting is enabled, an access rights issue may prevent Manual Scan from scanning files and folders on a network drive on a Microsoft(TM) Windows(TM) XP or 2003 platform. Real-time Scan can scan files on a network drive when the corresponding input/output files have been generated.

Hot Fix 1283

Issue: The OfficeScan Database Service (DbServer.exe) stops unexpectedly while the OfficeScan server handles the data of Update Agents.

Hot Fix 1287

Issue: The "Enable IntellTrap" option is displayed in the "Manual Scan Settings" page of the OfficeScan client console but this option is available for Real-time Scan only.

Hot Fix 1289

Issue: In OfficeScan clients installed on computers with multiple Network Interface Cards (NICs) bound with multiple IP addresses, TmListen retrieves the client IP address by resolving the client's host name without a DNS server. However, in this case, TmListen will only be able to retrieve one IP address which the client cannot use to connect to the OfficeScan server. Such OfficeScan clients will not be able to report the correct IP address to the OfficeScan server using the IP Template or IPTemplateDeploy feature.

Hot Fix 1291

Issue: Sometimes, the OfficeScan Master Service stops unexpectedly while running a visibility update task on the Update Agent.

Hot Fix 1292

Issue: A buffer overrun issue can cause the AEGIS module to stop unexpectedly while handling an invalid TMUFE activation code. The same issue can also prevent the NFC feature from working properly.

Hot Fix 1294

Issue: OfficeScan clients cannot successfully restore the deployed outbreak prevention policy for the "Deny write access to files and folders" option.

Hot Fix 1295

Issue: Sometimes, the OfficeScan server's header formatting method may not be able to add the SMTP server address after "@" in the "Message-ID" field of an email header which forces the OfficeScan server to send out email messages with "@(null)" in the header. Mail servers reject such email messages because according to a customized checking rule in TmNotify, the contents of the "Message-ID" header must follow the "random.time@smtpServer" format.

Hot Fix 1299

Issue: The OfficeScan server can support user account passwords up to 128 characters long but the warning message asks users to input passwords between one to 32 characters long only.

Hot Fix 1300

Issue: When users add a new role on the OfficeScan 10.6 server console "Administrator" > "User Roles" > "Add Role" page, they cannot add the permission needed to view and configure the Plug-in Manager.

Hot Fix 1301

Issue: A discrepancy in the time format can prevent scan logs from reporting the correct scans start and finish times.

Hot Fix 1301.1

Issue: Versions of the OfficeScan client (prior to 10.6) managed by an OfficeScan 10.6 server perform a high number of CGI calls resulting in a high CPU usage on the server.

Hot Fix 1302

Issue: When users attempt to install the Vulnerability Scanner (TMVS) on an OfficeScan client that does not have any domain information, the installation process will use an empty domain to call "cgiRemoteInstall.exe". However, in this situation, "cgiRemoteInstall.exe" will use "null" as the domain parameter. This can prevent users from logging on to OfficeScan and the TMVS installation fails. Solution: This hot fix enables OfficeScan to use "Unknown" as the domain name to call "cgiRemoteInstall.exe" when an OfficeScan client domain is unknown. This ensures that will be able to install TMVS on such clients.

Hot Fix 1308

Issue: The "JSON.parse" error message appears on the Web console when users attempt to view Trend Micro Behavior Monitoring logs. Repeating the query will then trigger the "OfficeScan Master Service is stopped" error message.

Hot Fix 1309

Issue 1:The access permission to the "widget\repository" widget folder is reset after users run "svrsvcsetup" with the "setprivilege" parameter.

Issue 2:Users encounter errors after uninstalling and re-installing OfficeScan Plug-in manager/widgets.

Hot Fix 1310

Issue 1: When users make changes to the "Scheduled Scan Settings" of an OfficeScan client with "Configure Scheduled Scan settings" privileges, the settings are rolled back to the previous configuration after the OfficeScan client performs Update Now.

Issue 2: After users enable the "Scan the boot sector of the USB storage device after plugging in" option in the Real-time Scan Settings and configure the "custom action" (real-time scan/manual scan/schedule scan) setting in the OfficeScan client user interface, the client setting is not applied to the database correctly This occurs because the "custom action" setting reverts to the default value after users perform a manual update from the OfficeScan client.

Hot Fix 1312

Issue: An issue prevents the Trend Micro Data Loss Prevention(TM) client from parsing the Chinese-language content of the subject header or body of email messages sent through Yahoo!(R) Web mail.

Hot Fix 1316

Issue: When the Web Reputation Service (WRS) Approved/Blocked List is exported through the OfficeScan server console's "Integrated Smart Protection Server" page, the exported CSV file is encoded in UTF-8 format. However, since the Microsoft(TM) Windows(TM) platform uses a different encoding format, the list is displayed with garbled characters on computers running on this platform.

Hot Fix 1323

Issue: On the OfficeScan client console "Manual Scan" page, users may not be able to view the items under each main item in directory or folder tree view.

Hot Fix 1328

Issue 1:OfficeScan compliance reports contain information on Web Reputation Services (WRS) even when the WRS license is inactive.

Issue 2:The "TmListen.exe" service may stop unexpectedly while the OfficeScan client sends a log for a detected virus to the OfficeScan server. The corresponding event log shows a "0xc0000005" exception code.

Hot Fix 1330

Issue: The OfficeScan Local Web Classification Server program encounters a memory leak issue.

Hot Fix 1332

Issue: The "JSON.parse" error message appears on the Web console when users attempt to view Trend Micro Behavior Monitoring logs. Repeating the query will then trigger the "OfficeScan Master Service is stopped" error message.

Hot Fix 1334

Issue: When users right-click on the OfficeScan client system tray icon while Microsoft(TM) Windows(TM) is in safe mode, the "OfficeScan Console" button is grayed-out. This prevents users from launching the Manual Scan function in Windows safe mode.

Hot Fix 1337

Issue: An issue prevents the OfficeScan server from sending email notifications when the Enhanced Simple Mail Transport Protocol (ESMTP) is enabled on the "Notification > General Settings" page of the OfficeScan server Web console.

Hot Fix 1338

Issue 1:When the computer restarts while Scan Now is running, the scan resumes automatically after the computer restarts. However, OfficeScan was not designed to exhibit this behavior

Issue 2:The OfficeScan client scan log shows the scan result as "Completed" even when the computer restarts while Scan Now is running.

Hot Fix 1338.1

Issue 1:The World Virus Tracking Center module, a legacy module which is no longer used, can cause the OfficeScan Master Service to stop unexpectedly.

Issue 2:The OfficeScan server's database process may stop unexpectedly while the database is running its backup operation.

Hot Fix 1341

Issue: An issue prevents users from changing the port number in the Virtual Desktop Infrastructure (VDI) Settings of the OfficeScan Plug-in Manager console.

Hot Fix 1342

Issue: After an OfficeScan client is set to be unreachable through the Web console, the client status remains as "Unreachable/offline" even when the client is actually online.

Hot Fix 1344

Issue: The OfficeScan Master service, "Ofcservice.exe", may stop unexpectedly while attempting to display the domain tree on the Web console. This occurs when the user interface attempts to access an address with the corresponding subdomain information which makes the address invalid.

Hot Fix 1349.1

Issue: The OfficeScan client installation process does not automatically remove AVG Antivirus(TM) 2012, a third-party antivirus product, before installing the OfficeScan client.

Hot Fix 1352

Issue: The OfficeScan Master Service, "Ofcservice.exe", may stop unexpectedly while searching for clients by IP address on the OfficeScan web console. This can occur when the OfficeScan web console retrieves an invalid IP address from the database and attempts to access it.

Hot Fix 2047

Issue: The OfficeScan server can support user account passwords up to 128 characters long but the warning message asks users to input passwords between one to 32 characters long only.

Hot Fix 2103

Issue: OfficeScan 10.5 : Missing "-setvirdir" switch for Svrsvcsetup.exe after Patch 2.2.

Hot Fix 2129

Issue: The OfficeScan server program, Trend Micro OfficeScan Master Service, crashes on a Microsoft(TM) Windows(TM) platform.

Hot Fix 2140

Issue 1:When the computer restarts while Scan Now is running, the scan resumes automatically after the computer restarts. However, OfficeScan was not designed to exhibit this behavior

Issue 2:The OfficeScan client scan log shows the scan result as "Completed" even when the computer restarts while Scan Now is running.

Issue 3:An OfficeScan client within range of unreachable clients clears its unreachable client settings upon loading.

Issue 4:Sometimes, an application error occurs while "NtRtScan.exe" is in the process of stopping.

Enhancement: Hot fix 2140 enables OfficeScan clients to generate the "scan_operation.csv" file in the client folder to record the results of a manual scan. Hot fix 2140 also adds the "scan folder" variable which records the scan path information in the "scan_operation.csv" file.

Hot Fix 2142

Issue: The OfficeScan server database service may hang during the backup operation of the database.

Hot Fix 2142.1

Issue: Several event logs about the OfficeScan Smart Scan performance counter (Perf_iCrcPerfMon) appear on the Microsoft(TM) Windows(TM) application event log.

Hot Fix 2143

Issue: The OfficeScan server generates unnecessary temporary files (dbADCompxxxx.tmp) in the "\PCCSRV\HTTPDB" folder, even after the folder has been removed and rebuilt.

Hot Fix 2145

Issue: Notification email messages for component update status contain garbled characters. This issue occurs because the notification email body is encoded in UTF-8 format which is then directly translated to Shift_JIS and JIS when the computer's default language is set to Japanese.

Hot Fix 2147

Issue: Log queries may time out when there is a large number of OfficeScan Behavior Monitoring logs. As a result, an empty log page appears on the OfficeScan server console.

Hot Fix 2149

Issue: The "Scan Exclusion" section of the "Scan Settings" page displays a truncated version of the exclusion path when the exclusion path is longer than the path length limit of the corresponding listbox.

Hot Fix 2151

Issue: The "EnableApacheSSL()" function stores debug log information in the "szTemp" variable and the size of this variable is limited to 260 characters. However, since the "EnableApacheSSL()" function includes both the file path and computer name in debug log messages, the message length can exceed 260 characters. When this happens the "stprintf_s()" function, which utilizes the "szTemp" variable, stops unexpectedly.

Hot Fix 2156

Issue: In certain environments, a MAPI error may prevent Microsoft(TM) Outlook(TM) from accessing the Exchange Server when both the Personal Firewall and the IDS SYN Flood Rule are enabled.

Hot Fix 2160

Issue: When "NTRtScan.exe" lists files for scanning, it also adds folders with attributes, such as "Read Only" and "Hidden" for example, to the list. Scheduled Scan scans these folders but Manual Scan skips these folders causing inconsistencies between manual scan results and scheduled scan results.

Hot Fix 2162

Issue 1:A user requests for a way to enable/disable the Firewall Application Filter function and globally deploy the setting to all OfficeScan clients.

Issue 2:Manual Scan cannot scan OfficeScan client folders and files which the current logon user does not have access rights to. Real-time Scan can scan such files when the corresponding input/output (I/O) file has been generated. This issue does not affect Scan Now and Scheduled Scan.

Hot Fix 2165

Issue: The question mark "?" character is not allowed in the "proxy script" or "regular URL" fields of the "Proxy Configuration" settings under the "Global Client Settings" page. When users attempt to input values that contain the character, the script address cannot be set which can prevent the OfficeScan client from retrieving the correct proxy settings.

Hot Fix 2168

Issue 1:In Microsoft(TM) Windows(TM) 7, the operating system enters hibernation mode during an OfficeScan scanning.

Issue 2:The OfficeScan client IP address is not displayed in the "Firewall" tab of the client console. This issue occurs when the client uses a special network adapter such as Softbank C02SW, because OfficeScan uses the Windows API IPv6 edition which cannot detect network connections from these adapters.

Hot Fix 2170

Issue: The Trend Micro Control Manager(TM) server displays an incorrect value for the number of OfficeScan clients. The issue happens when the value of the "Agent_GUID" configuration parameter in the "Common" section of the "Agent.ini" file is in capital letters.

Hot Fix 2171

Issue: The OfficeScan Web console "Component Update Logs" page cannot display logs by pattern version.

Hot Fix 2174

Issue: The "JSON.parse" error message appears on the Web console when users attempt to view Trend Micro Data Loss Prevention(TM) logs. Repeating the query will then trigger the "OfficeScan Master Service is stopped" error message.

Hot Fix 2177

Issue: The IDF plug-in module syncs the OfficeScan client tree in the IDF Management Console with the one in the OfficeScan database. If IDF cannot retrieve the parent of a particular OfficeScan client, the client's computer name becomes "computer name_1" in the client tree on the IDF Management Console.

Hot Fix 2183

Issue: When users make changes to the "Scheduled Scan Settings" of an OfficeScan client with "Configure Scheduled Scan settings" privileges, the settings are rolled back to the previous configuration after the OfficeScan client performs Update Now.

Hot Fix 2186

Issue: The OfficeScan Master Service may stop unexpectedly while attempting to display Behavior Monitoring logs on the OfficeScan console.

Hot Fix 2187

Issue: When users set Scheduled Scan to run "Monthly, on the i-th weekday of the month" and enable the "Delay Scheduled Scan" function, the "Skip this Scheduled Scan. The next Scheduled Scan runs on xxx" option in the scan warning dialog box shows the same date as the original schedule. In this case, the Scheduled Scan task will not be skipped even if users select the "Skip the scheduled Scan" option.

Hot Fix 2189

Issue: After users enable the "Scan the boot sector of the USB storage device after plugging in" option in the Real-time Scan Settings and configure the "custom action" (real-time scan/manual scan/schedule scan) setting in the OfficeScan client user interface, the client setting is not applied to the database correctly This occurs because the "custom action" setting reverts to the default value after users perform a manual update from the OfficeScan client.

Hot Fix 2196

Issue: When enable option "Add Manual Scan to the Windows shoutcut menu on client computers" and "Roaming Client" before create the client package and deploy this package to the client. After client installation complete successfully and enable "Roaming Client", the option "Scan with OfficeScan client" will disappear. Users couldn't scan file manually when they right-click the file.

Hot Fix 2203

Issue: Versions of the OfficeScan client (prior to 10.6) managed by an OfficeScan 10.6 server perform a high number of CGI calls resulting in a high CPU usage on the server.

Hot Fix 2214

Enhancement: Hot fix 2214 provides an enhanced "Block AutoRun function on USB devices" function on the OfficeScan Device Control. This enhanced function validates AutoRun items first and allows AutoRun to proceed when it finds that all executable files in the USB device are valid. The unenhanced version will always block AutoRun tasks when enabled.

This hot fix resolves the following issues:

Issue 1: An unload password is required to unload an OfficeScan client. However, a vulnerability may allow malicious programs to retrieve a particular client's unload password or bypass the password authentication process.

Issue 2: To prevent network disconnection, when OfficeScan disables the firewall, it only stops the firewall but does not remove the service and driver. The "RmvPFWifDisabled" setting should allow OfficeScan clients to remove the firewall service and driver when the firewall is disabled.

However, when the firewall is disabled in the "Product License" page of the OfficeScan server console, an OfficeScan client cannot remove the OfficeScan NT firewall service and driver even when "RmvPFWifDisabled =1" is set in the client.

Hot Fix 2215

Issue: When users add a new role on the OfficeScan 10.6 service pack 1 server console "Administrator" > "User Roles" > "Add Role" page, they cannot add the permission needed to view and configure the Plug-in Manager.

Hot Fix 2215.1

Issue: Selecting more than 49 clients from the client tree in the "Networked Computers > Client Management" page can prevent users from accessing the "Device Control Settings" and "Digital Asset Control Settings" pages trough the "Settings" menu.

Hot Fix 2218

Issue: The OfficeScan Master Service stops unexpectedly while the OfficeScan server handles database queries.

Hot Fix 2220

Issue: OfficeScan clients do not trigger an IP change event log after changing IP addresses when switching to roaming mode.

Hot Fix 2232

Issue: Microsoft(TM) Windows(TM) limited user accounts cannot edit the log management settings on the OfficeScan client console even when the "Client Security" level is set to "Normal".

Hot Fix 2232.1

Issue: When users integrate an Active Directory and add domain users or groups under "User Accounts" in the "Administration" page, sub-domain users will be able to log on to the OfficeScan management console but will not be able to see the client tree in the "Networked Computers > Client Management" page.

Hot Fix 2233

Issue: The Trend Micro OfficeScan Monitor (PccNTMon.exe) stops when the client runs on Windows server 2008 with the terminal service enabled.

Hot Fix 2236

Issue: The Windows IIS Worker Process (w3wp.exe) stops unexpectedly while the OfficeScan server handles CGI calls.

Hot Fix 2236.1

Issue: When an OfficeScan server runs on an "AMD64" CPU and one of its clients detects a virus during a conventional scan, the OfficeScan server sends a short version of the VSAPI pattern to Trend Micro Control Manager(TM). This can cause Control Manager to display the detected pattern version as "0.XXX.00" in the notification email message that it sends out.

Hot Fix 2239

Issue :The OfficeScan client TM_CFW drivers encounter blue screen of death (BSoD) while the Common Firewall Driver attempts to queue a fragment packet. BSoD then recurs when the NIC driver tries to send out the same fragment packet.

Hot Fix 2240

Issue: When users stop an OfficeScan server's Master Service, OfficeScan clients delete security risk logs instead of sending these to the OfficeScan server.

Hot Fix 2241

Issue 1: A discrepancy between the actual size of transferred data and the value of the "Content-Length" header prevents users from uploading files.

Issue 2: The OfficeScan Web Reputation function causes Microsoft(TM) Outlook(TM) Web Access to work slowly.

Issue 3: Users might experience the "Internet Explorer Cannot Display the Webpage" error when users log on to their Hotmail(TM) accounts.

Hot Fix 2242

Issue: The Behavior Monitoring module may come in conflict with certain remotely-launched applications.

Hot Fix 2243

Issue: The OfficeScan Database Service stops unexpectedly while the OfficeScan server queries logs.

Hot Fix 2243B

Issue: The OfficeScan server initially notifies the Update Agents before notifying the normal clients of a component update event. When there is a high number of Update Agents in an OfficeScan environment, there is a possibility that a few Update Agents do not get the notification. OfficeScan may possibly block the normal clients from receiving the notification, which downgrades the overall notification dispatch.

Hot Fix 2246

Issue: The OfficeScan server accepts domain names with a maximum length of 120 characters in the database. A CGI program determines the length of a domain name when a client's OnStart update runs and rejects the update when the domain name length exceeds the maximum. Multi-layered domains can cause the OfficeScan server to reject the domain name, even when the length of the name does not exceed the maximum.

Hot Fix 2253

Issue: When users query a large number of Web Reputation logs and click "Export to CSV" on the OfficeScan server console, the OfficeScan Master Service stops unexpectedly while the OfficeScan server exports the logs.

Hot Fix 2263

Issue 1 : Users can configure the OfficeScan client Web Reputation Service (WRS) query timeout setting locally through the following OfficeScan client registry key:

Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\NSC\TmProxy \Scan\Common\URLFilter\config\LookupTimeout

However, there is no way to configure a client's WRS query timeout setting from the OfficeScan server. Solution 1: This hot fix adds an option to configure the WRS query timeout setting through the OfficeScan server "ofcscan.ini" file and deploy the setting to clients.

Issue 2:It can take a few seconds longer for the rlogin connection prompt to appear when users launch the application while the OfficeScan firewall is active.

Issue 3:Sometimes, OfficeScan servers may send the wrong spyware scan engine version numbers to Trend Micro Control Manager(TM) which can cause Control Manager to display inconsistent spyware engine versions in daily reports.

Hot Fix 2266

Issue: When the OfficeScan client's Device Control setting in the database is set to an invalid value, the "Syntax Error: Syntax Error" warning message appears on the OfficeScan server console.

Hot Fix 2267

Issue 1:During remote installation, a program return error prompts the OfficeScan client to use the default client installation path even after users have specified another client installation path.

Issue 2:An OfficeScan client that is assigned the Update Agent role may become a normal client after a scheduled update.

Hot Fix 2275

Issue 1: A general protection fault occurs when users attempt to launch the OfficeScan client Management Console by selecting the option from the menu that appears after right-clicking the OfficeScan task tray icon. This can prevent users fro successfully launching the OfficeScan client Management Console through this option.

Issue 2: The Officescan server provides Client Grouping by custom client groups using Windows Active Directory (AD). Users can duplicate the AD structure into the OfficeScan client tree. Modifying the client tree structure when some clients were offline caused these clients to report their old domain information to the server when they became online. This caused the old domain structure to re-create itself on the console.

Hot Fix 2277

Issue: Sometimes, the OfficeScan server stops unexpectedly while users attempt to access the Web Reputation Settings through the OfficeScan Web console.

Hot Fix 2279

Issue: The URL Filtering Engine module may cause the OfficeScan TmProxy service to stop unexpectedly while decoding the authentication data that was returned by the Microsoft(TM) Windows(TM) NTLM authentication scheme.

Hot Fix 2322.2

Issue: If OfficeScan sets up multiple SPS servers, the OfficeScan client always connects to the secondary SPS server when it starts even when the primary SPS server is available and is the current SPS server. The OfficeScan client then switches to the primary SPS server several minutes after starting up.

Hot Fix 2408

Issue: The OfficeScan Master Service process (ofcservice.exe) stops unexpectedly while processing a corrupted virus log that exceeds the virus log size limitation of 635 KB.

Hot Fix 2409.1

Issue 1: A discrepancy between the actual size of transferred data and the value of the "Content-Length" header prevents users from uploading files.

Issue 2: The OfficeScan Web Reputation function may slow down the performance of Microsoft(TM) Outlook(TM) Web Access.

Issue 3: Users might experience the "Internet Explorer Cannot Display the Webpage" error while logging on to their Hotmail(TM) accounts.

Hot Fix 2411

Issue: Under certain conditions, the internal structure that the OfficeScan Behavior Monitoring Driver uses may become corrupted.

Hot Fix 2420

Issue: An issue prevents Apache web service and the Internet Information Services (IIS) x86 version from loading isapi protocol module of OfficeScan Local Web Classification Server service. This can prevent OfficeScan clients from connecting to the OfficeScan server and the server's Web Reputation Service(WRS) from working properly.

Hot Fix 2424

Issue: When the VSEncode tool attempts to restore several quarantined files with the same filename, only one of the files is restored.

Hot Fix 2426

Issue 1:Compliance reports incorrectly indicate that the 64-bit Behavior Monitoring Detection Pattern is 32-bit while the corresponding CSV output file indicates if the pattern is 32 or 64-bit which violates compliance specifications.

Issue 2:The OfficeScan summary page displays the wrong Virus Cleanup Engine (32/64-bit) and Spyware Scan Engine (32/64-bit) versions.

Hot Fix 2431.1

Issue: An error message is generated in the Web server log file when an OfficeScan client performs updates. This issue occurs because during updates, the OfficeScan client attempts to download the "ini_xml.zip" file from the OfficeScan server but this file is not in the OfficeScan server and is not used by OfficeScan.

Hot Fix 2432

Issue 1: Blue screen of death (BSoD) occurs when users start computers running on the 64-bit version of Microsoft(TM) Windows(TM) 7 and where both Data Loss Prevention 5.6 SDK and the Microsoft Application Virtualization (MS App-V) client are installed.

Issue 2: Trend Micro Data Loss Prevention(TM) 5.6 SDK agent cannot convert special Croatian characters either uppercase or lowercase characters.

Hot Fix 2435

Issue: When users configure the standard and outbreak notification settings in "Notifications > Administrator Notifications" on the Microsoft(TM) Internet Explorer(TM) 9 Web browser, a JavaScript(TM) error occurs after users click the "Windows NT Event Log" tab. This issue was resolved in OfficeScan 10.6 for the Internet Explorer 8 Web browser but has reoccurred in version 10.6 Service Pack 1 because of browser dependency since versions 8 and 9 of the Internet Explorer Web browser use different methods to convert characters.

Hot Fix 2438

Issue: The Trend Micro OfficeScan Monitor (PccNTMon.exe) stops when the client runs on Windows XP Pro platforms.

Hot Fix 2445

Issue: When the OfficeScan client Web Reputation Service (WRS) blocks a Web site after rating it as "Highly Suspicious", the corresponding pop up message incorrectly indicates the risk level as "Suspicious" only.

Hot Fix 2446

Issue 1:OfficeScan clients receive several notification messages from the OfficeScan server to download a hot fix file and update more than 30 files in the OfficeScan client install directory which prompts these clients to perform the updates repeatedly.

Issue 2:The OfficeScan client stops unexpectedly while the TmListen, PccNT, or PccNTMon service starts.

Hot Fix 2449

Issue: The OfficeScan client is unable to receive the unreachable network settings from the update agent.

Hot Fix 2451

Issue 1: The Behavior Monitoring module is not compatible with Microsoft(TM) Windows(TM) 8 and Windows Server 2012. Attempting to run OfficeScan in any of the two platforms triggers a Windows Program Compatibility Assistance warning message for the Trend Micro Common Module.

Issue 2: The OfficeScan 10.6 Service Pack 1 client program encounters blue screen of death (BSoD) on the Windows platform. This is caused by a possible interoperability issue between the LANDesk(TM) Endpoint Security driver and the Behavior Monitoring Driver.

Issue 3: The OfficeScan Unauthorized Change Prevention Service can delay the start up of a third-party stock software by at least 15 seconds.

Issue 4: In computers running the OfficeScan 10.6 Service Pack 1 client program on the Windows platform, users experience performance and system lockup issues when users attempt to attach documents in Microsoft Outlook(TM) or download files through a web browser. This is caused by a possible interoperability between the VSAPI scan engine and the Behavior Monitoring module.

Hot Fix 2452

Issue 1:On the OfficeScan client console "Manual Scan" page, users cannot view the items under each main item in directory or folder tree view.

Issue 2:When users set Scheduled Scan to run "Monthly, on the i-th weekday of the month" and enable the "Delay Scheduled Scan" function, the "Skip this Scheduled Scan. The next Scheduled Scan runs on xxx" option in the scan warning dialog box shows the same date as the original schedule. In this case, the Scheduled Scan task will not be skipped even if users select the "Skip the scheduled Scan" option.

Issue 3:In Microsoft(TM) Windows(TM) 7, the operating system enters hibernation mode during an OfficeScan scanning.

Issue 4:The OfficeScan Master Service ("ofcservice.exe") crashes when the "libCmdHndlrClientV2.dll" file (from OfficeScan) generates an exception to report an error about invalid data from the "isapiClient.dll" file. However, the OfficeScan Master Service does not accept the exception. Since the OfficeScan Master Service does not handle the exception, the OfficeScan Master Service crashes.

Issue 5:Notification email messages for component update status contain garbled characters. This issue occurs because the notification email body is encoded in UTF-8 format which is then directly translated to Shift_JIS and JIS when the computer's default language is set to Japanese.

Issue 6:When the NIC card is disconnected from the LAN cable, the Microsoft(TM) Windows(TM) Security Center displays a warning message that states that the OfficeScan Firewall is disabled. This occurs because the OfficeScan Firewall cannot function when it cannot retrieve any IP address. Solution 6: This hot fix ensures that the Windows Security Center warns users that the OfficeScan Firewall is disabled only when the OfficeScan Firewall is disabled by a local user or through all policies.

Hot Fix 2455

Issue: An unload password is required to unload an OfficeScan client. However, a vulnerability may allow malicious programs to change a particular client's unload password.

Hot Fix 2456

Issue: The OfficeScan Local Web Classification Server program encounters a memory leak issue.

Hot Fix 2457

Issue: The OfficeScan client is unable to update components from an Update Agent or the OfficeScan server. The "7z.exe" process does not return a successful decompression after the process finishes. OfficeScan constantly waits for a successful return value, even though the process is already completed.

Hot Fix 2458

Issue 1: When using Skype(TM) to send a message from OfficeScan client computers where Trend Micro Data Loss Prevention(TM) is also installed, users see delayed Skype messages, which only appear a few seconds on the Skype window.

Issue 2: An issue prevents Data Loss Prevention from detecting password-protected RAR files with unencrypted filenames.

Hot Fix 2462

Issue: An uninstall password is required to uninstall an OfficeScan client. However, users can use some OfficeScan server programs to bypass the password prompt during OfficeScan client uninstallation.

Hot Fix 2464

Issue: When certain issues occur on the OfficeScan database, such as when the database does not exist, the OfficeScan Master Service deletes the corresponding user account (TM_OSCE_<hostname>) and recreates it. However, the OfficeScan Master Service does not delete the corresponding directory with the account.

Hot Fix 2467.1

Issue: On the OfficeScan 10.6 Service Pack 1 proxy setting page, the server name field does not accept a fully qualified domain name (FQDN) if any of its parts is shorter than three alphanumeric characters.

Hot Fix 2470

Issue: The "VSEncode.exe" tool decrypts quarantined files (.qtn) and restores these files to the original folders. While restoring files, this tool converts filenames using the multibyte character set (MBCS), however, this tool could not properly convert filenames that contain Unicode characters.

Hot Fix 2471

Issue: After the Threat Intelligence Manager agent retrieves the Trend Micro Data Loss Prevention(TM) logs from the OfficeScan database and the Data Loss Prevention log table is emptied, the temporary file is left on the OfficeScan database.

Hot Fix 2474

Issue: The "TmfilterDisableCtProcCheck" setting can only be deployed to OfficeScan clients globally and these clients automatically download this setting from the OfficeScan server during updates. A user requests for a way to prevent the global deployment of this setting to be able to set different configurations of this setting on different clients.

Hot Fix 2476

Issue: For manual and scheduled scans, "Ntrtscan.exe" scans folders recursively. When scanning a very deep directory, the call stack may exceed the 1M stack size limit which can cause issues in "Ntrtscan.exe".

Hot Fix 2998

Issue: The Media Access Control (MAC) address shown in virus logs on the OfficeScan client Web console becomes "000000000000" when the actual OfficeScan client MAC address contains "00-00".

Hot Fix 3039

Issue: A general protection fault (GPF) occurs while "TmPfw.exe" attempts to retrieve the process information for the application filter. This issue may be caused by a race condition that occurs while "TmPfw.exe" attempts to retrieve the information shortly after starting up.

Hot Fix 3045

Issue: A sharing violation occurs when users save Microsoft(TM) Excel (.xls) or Word (.doc) files while the OfficeScan Real-time scan is running.

Hot Fix 3048

Issue: Trend Micro Control Manager(TM) Agent (CMAgent) sends the date/time value to the Control Manager server in the wrong format. This prevents the SQL server from executing the related store procedure. As a result, the Product Registration information is not stored in the Control Manager database and the Control Manager server will not be able to deploy the Product Registration information to the corresponding OfficeScan server.

Hot Fix 3052

Issue: A previous solution enables the OfficeScan client tree to show the firewall policy even when the firewall is disabled by checking a setting in the "ofcscan.ini" file under the server path using an OCX control. However, since the OCX control runs in a browser, "ofcscan.ini" will not exist if the browser is not opened in the server computer.

Hot Fix 3053

Issue : Web Reputation Service (WRS) approved Web site list deployment feature requires changes.

Hot Fix 3062

Issue: The "NTRtScan.exe" process stops unexpectedly while an OfficeScan client scans a long pathname by scheduled or manual scan. This occurs when the directory infrastructure is very complex such that the stack buffer of the scan directory function overflows and the error-handling mechanism of the string copy when determining exclusion folders cannot resolve the issue.

Hot Fix 3063

Issue: During a fresh OfficeScan client installation, the OfficeScan client is not uninstalled automatically even when only part of the OfficeScan registry is installed. While the OfficeScan Listener and monitor services work under this situation, the missing registry keys can cause Real-Time scan to stop unexpectedly.

Hot Fix 3079

Issue: Modules and registry keys for OfficeScan clients may be deleted unexpectedly when users execute the update package on the client.

This problem occurs when the OfficeScan tmlisten.exe or ntrtscan.exe services are unable to run successfully for any reason.

Hot Fix 3080

Issue: OfficeScan client scheduled scans do not run as scheduled after the Microsoft(TM) Windows(TM) daylight savings option is enabled on the client machine.

Important: Solution details for every hot fix in this article are included in the latest version of the readme file.

Hot Fix 1232

Enhancement: Hot fix 1232 allows OfficeScan 10.6 clients to move from one domain to another using the same computer name.

Hot Fix 1268.1

Enhancement: Hot fix 1258 adds an option to configure the checking interval for the OfficeScan Smart Protection Server (SPS) connection status for Web Reputation queries.

Hot Fix 1335

Enhancement: OfficeScan Web Reputation Service supports Mozilla(TM) Firefox 15 (and above) and can also work with the HTTPS plug-in.

Hot Fix 1345

Enhancement: This hot fix provides an option to allow users to configure OfficeScan to delete logs that are older than a specified number of days and globally deploy this firewall log maintenance setting.

Hot Fix 2172

Enhancement: When a laptop is under a particular ISP that is outside its company network, the telnet connection to the OfficeScan server will be tagged as "successful" even when the OfficeScan server is unreachable. In this situation, the laptop will use the internal network setting to connect to the OfficeScan server.

Hot Fix 2172 adds a mechanism to verify the response from the OfficeScan server to make sure the communication between the OfficeScan client and server is normal instead of verifying only if the ping was successful.

Hot Fix 2226

Enhancement: In some network environments, OfficeScan clients may not receive update notifications from the OfficeScan server and these notifications end up in the notifications queue for OfficeScan clients. This may prevent component updates in affected clients.

Hot Fix 2226 provides a function which enables users to set the OfficeScan server to regularly clean the notifications queue for OfficeScan client updates.

Note: There is a "Cancel Notification" button on the "Updates Summary" page of the server console which users can use to clean the notification queue manually.

Hot Fix 2248

Enhancement: This hot fix allows users to customize the format of the date/time strings in the "Notifications" page of OfficeScan 10.5 servers.

Hot Fix 2173.1

Enhancement: Hot fix 2173.1 provides an option to enable Scheduled Scan to scan network drives.

Hot Fix 2202.1

Enhancement: In the OfficeScan User Management settings, only users with root account or accounts with the Administrator (Built-in) role are allowed to configure the "User Accounts" option.

This hot fix provides an option for users to create a new (non-administrator) user role with the privilege to configure the "User Accounts" option in the OfficeScan User Management settings.

Note: When the option is enabled, newly-created accounts with non-administrator privileges can add roles with the "User Accounts" configure option enabled or disabled in the "Administration > User Roles" Web console.

Hot Fix 2203.1

Enhancement: An OfficeScan Global Client Setting can prevent OfficeScan from scanning compressed files if the file size exceeds the configured value. Hot fix 2203 provides an option to display a pop-up notification when the OfficeScan client skips a Real-time scan on a compressed file due to this setting.

Hot Fix 2214

Enhancement: Hot fix 2214 provides an enhanced "Block AutoRun function on USB devices" function on the OfficeScan Device Control. This enhanced function validates AutoRun items first and allows AutoRun to proceed when it finds that all executable files in the USB device are valid. The unenhanced version will always block AutoRun tasks when enabled.

This hot fix resolves the following issues:

Issue 1: An unload password is required to unload an OfficeScan client. However, a vulnerability may allow malicious programs to retrieve a particular client's unload password or bypass the password authentication process.

Issue 2: To prevent network disconnection, when OfficeScan disables the firewall, it only stops the firewall but does not remove the service and driver. The "RmvPFWifDisabled" setting should allow OfficeScan clients to remove the firewall service and driver when the firewall is disabled.

However, when the firewall is disabled in the "Product License" page of the OfficeScan server console, an OfficeScan client cannot remove the OfficeScan NT firewall service and driver even when "RmvPFWifDisabled =1" is set in the client.

OSCE 10.6 SP1 patch1

Enhancement 4: On the OfficeScan server console, users need to select each client icon under each server platform computer to configure and deploy the Web Reputation settings.

This patch adds the "Enable Web Reputation Policy for multiple server platforms" function for the OfficeScan Web Reputation settings. This function allows users to configure and deploy Web Reputation settings on multiple server platforms by directly selecting the Root Domain, Domain, or multiple clients on the server console "Client Management" page.

OSCE 10.6 SP1 patch1

Enhancement 5: This hot fix adds an option to enable OfficeScan to automatically perform a real-time scan on a USB storage device immediately after users plug in the device.

In addition, users can also enable OfficeScan to display a pop-up message to prompt users if they would like to scan a USB drive upon insertion during a manual scan or not. This gives users the option to perform scans on USB devices immediately or at a later time.

For more information, download the latest copy of the readme file.

Important: Always make sure that you have the latest copy of the readme file.

Premium
Internal
Rating:
Category:
Install
Solution Id:
1095513
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.