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

Create a technical support case if you need further support.

Best practices when upgrading to Officescan 10.6

    • Updated:
    • 7 Apr 2016
    • Product/Version:
    • OfficeScan 10.6
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2008 Enterprise
    • Windows 2008 Standard
Summary

This guide discusses the recommended steps and pointers when upgrading to OfficeScan 10.6.

Details
Public

Evaluate the need to upgrade

Discuss company’s challenges when upgrading and consider the following:

  • Seamless upgrade
  • Network disconnection
  • Application downtime
  • Low machine specifications
  • Upgrade failures

Check if the OfficeScan version is supported for upgrade to 10.6

Before upgrading the OfficeScan server and clients, take note of the following:

  1. The installation package includes updates to OfficeScan firewall drivers.
    If you have enabled the OfficeScan firewall in your current OfficeScan version, deploying the package may cause the following client computer disruptions:
  2. When Common Firewall Driver update starts, client computers will be temporarily disconnected from the network. Users are not notified before disconnection. An option on the OfficeScan 10 SP1 or later web console, which is enabled by default, postpones the Common Firewall Driver update until a client computer is restarted. To avoid the disconnection issue, ensure that this option is enabled. To check the status of this option:
  • Navigate to Networked Computers > Global Client Settings and go to the Firewall Settings section.
  • The option is Update the OfficeScan firewall driver only after a system reboot.
  1. After deploying the package, the OfficeScan TDI driver's previous version still exists on the client computer and the new version will not be loaded until the computer is restarted. Users are likely to encounter problems with the OfficeScan client if they do not restart immediately. If the option to display the restart notification message is enabled on the web console, users will be prompted to restart. However, users who decide to postpone the restart are not prompted again. If the option is disabled, users are not notified at all. The option to display the restart notification message is enabled by default. To check the status of this option:
  • Navigate to Networked Computers > Global Client Settings and go to the Alert Settings section.
  • The option is Display a notification message if the client computer needs to restart to load a kernel mode driver.
  1. The OfficeScan server cannot upgrade to this version if:
  • A client is running Login Script (AutoPcc.exe) at the time of server upgrade. Ensure that no client is running Login Script before upgrading the server.
  • The server is performing database-related tasks. Before upgrading, check the status of the OfficeScan database (DbServer.exe). For example, open Windows Task Manager and verify that CPU usage for DbServer.exe is 00. If CPU usage is higher, wait until usage is 00, which signals that database-related tasks have been completed.

If you run an upgrade and encounter upgrade problems, it is possible that database files have been locked. In this case, restart the server computer to unlock the files and then run another upgrade.

Choose which upgrade method fits company’s requirements

Know the different methods of upgrading to OfficeScan 10.6

Perform Post Upgrade checklist

  1. Verify the server and client upgrade. Check services, processes, program list, server web console, registry keys, clients, and server console version.
  2. Update the OfficeScan Components.

Check the server migrated default settings

Follow the procedure in this article: Importing configuration using the OfficeScan 10.6 server Migration Tool.

If upgrade fails, collect the following and send them to Trend Micro Technical Support:

  • System Information
    • Go to Start > Programs > Accessories > System Tools > System Information.
    • Click File > Save. Save it in *.NFO folder.
  • Event Logs
    • Click Start > Control Panel > Administrative Tools > Event Viewer.
    • Save a copy of Application event logs and System event logs in *.EVT format.
  • Copy the OfficeScan installation log from %windir%\OFCMAS.log.
  • Copy of the Ofcdebug.log file. To enable debug logging, refer to this KB article: Manually enabling debug mode in OfficeScan
  • Screenshots of any error that came up during upgrade
Premium
Internal
Rating:
Category:
Upgrade
Solution Id:
1060063
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.