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:
- Go to the server's ..\PCCSRV\ installation directory.
- Open the Ofcscan.ini file in Notepad.
- Add the "Send_Notify_UA_Threshold" and "Send_Notify_Thread_Number" entries under the "INI_SERVER_SECTION" section in the Ofcscan.ini file.
[INI_SERVER_SECTION] Send_Notify_UA_Threshold=50 Send_Notify_Thread_Number=20
- Save the changes and close the "Ofcscan.ini" file.
- 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.