Before upgrading the OfficeScan server and clients/agents, 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/agent computer disruptions:
   
   • When the Common Firewall Driver update starts, client/agent 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/agent 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 (10.6) or Agents > Global Agent Settings (11.0) or Agents > Global Agent Settings > Agent Control (XG). Proceed to the Firewall Settings section, then enable and apply the Update the OfficeScan firewall driver only after a system reboot setting.

   • After deploying the package, the OfficeScan TDI driver's previous version still exists on the client/agent computer and the new version will not be loaded until the computer is restarted. Users are likely to encounter problems with the OfficeScan client/agent 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 (10.6). You may also go to Agents > Global Agent Settings (11.0) or Agents > Global Agent Settings > Agent Control (XG). Proceed to the Alert Settings section, then enable and apply the Display a notification message if the client computer needs to restart to load a kernel mode driver setting.

2. The OfficeScan server cannot upgrade to this version if:
   • A client/agent is running Login Script (AutoPcc.exe) at the time of server upgrade.
     

     Ensure that no client/agent 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.