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

Create a technical support case if you need further support.

Configuring the server to prioritize a specified number of Update Agents before normal clients in Apex One/OfficeScan

    • Updated:
    • 23 Sep 2020
    • Product/Version:
    • Apex One All.All
    • OfficeScan XG.All
    • 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

The Apex One/OfficeScan server initially notifies the Update Agents before notifying the normal clients about the availability of new updates or a configuration change. If there is a high number of Update Agents in an Apex One/OfficeScan environment, there is a possibility that some Update Agents will not get the notification (e.g. Update Agent(s) offline or unavailable). Apex One/OfficeScan may possibly block the normal clients from receiving the notification, which can result in the backing up of the notification queue. The resultant backlog can lead to agents not getting update notifications.


To avoid this situation, prevent the notification queue backlog from occurring by configuring the Apex One/OfficeScan server to notify normal clients before all update agents are notified:

  1. On the Apex One/OfficeScan server, open the Ofcscan.ini file in the \PCCSRV\ folder.
  2. Under the [INI_SERVER_SECTION] section, manually add the "Send_Notify_UA_Threshold" key and set the proper value for the Update Agent number. For example:

    Send_Notify_UA_Threshold = 10

    When the Update Agent number is 10 or less in the update queue, the server starts to notify normal clients for the update. Trend Micro recommends setting the value from 0 to 50. "0" disables the option.

    If the number of notifications in the notification queue is greater than 1000, only the first 1000 will be checked. It may be necessary to tweak this value to prevent a notification record in the queue from reaching its TTL and expiring.

    Below is an optional modification to the "Max_Search_Queue" parameter:

    • Still under the [INI_SERVER_SECTION] section, add the parameter "Max_Search_Queue" and put the value as "-1". For example:

      Max_Search_Queue = -1

      Setting the value to "-1" changes the Max_Search_Queue value to infinity.

  3. Save the changes and close the Ofcscan.ini file.
  4. Restart the Master Service.
Solution Id:
Did this article help you?

Thank you for your feedback!

*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.