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

Create a technical support case if you need further support.

High number of queued agents remains when deploying updates to clients in Apex One/OfficeScan

    • Updated:
    • 23 Sep 2020
    • Product/Version:
    • Apex One All
    • OfficeScan All
    • Platform:
    • Windows 2003 Datacenter 64-bit
    • Windows 2003 Enterprise
    • Windows 2003 Server R2
    • Windows 2003 Standard 64-bit
    • Windows 2008 Datacenter
    • Windows 2008 Datacenter 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2 Enterprise
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2008 Web Server Edition
    • Windows 2008 Web Server Edition 64-bit
    • Windows 2012 Datacenter R2
    • Windows 2012 Enterprise
    • Windows 2012 Enterprise R2
    • Windows 2012 Server Essential R2
    • Windows 2012 Server Essentials
    • Windows 2012 Standard
    • Windows 2012 Standard R2

The number of queued clients during update deployment stays high, but the number of notified agents does not increase.

The administrator has already tried updating the root certificates on the Apex One/OfficeScan server and client machines. However, the issue persists.


The queuing occurs when pending client update notifications get stuck in the notification queue, or when the Apex One/OfficeScan server tries to update too many clients at the same time.

Update the Apex One/OfficeScan server to the latest product build, and configure its update settings properly to address the issue. To do this:

Create more server update threads to handle the notifications. To do this:

  1. Go to the server's ..\PCCSRV\ installation directory.
  2. Open the Ofcscan.ini file in Notepad.
  3. Add the "Send_Notify_UA_Threshold" and "Send_Notify_Thread_Number" entries under the "INI_SERVER_SECTION" section in the Ofcscan.ini file.
  4. Save the changes and close the "Ofcscan.ini" file.
  5. Restart the Master Service via the Windows Services console (services.msc).

Another option is to use the Server Tuner tool to help optimize the performance of the Apex One/OfficeScan server.

When the Apex One/OfficeScan server fails to process client update notifications, succeeding entries in the notification queue may fail because previous queue entries are not deleted to allow the next ones to proceed.

Schedule regular notification queue cleanup using the steps in the Server notification queue cleanup KB article.

Set up Update Agents for segmented networks to balance the loading of the server for updates. Follow the steps in the Configuring clients/agents to act as Update Agents KB article.

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.