ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

FlushAgentEvents – Flush NSEs in Agent's Queue


Article ID: 179877


Updated On:


IT Management Suite Client Management Suite


When the Notification Server queues have reached the maximum number of NSEs and the Altiris Agent is directed to back off, the agent will queue its NSE to send at a later time. Over a period of time, it is possible that many agents will have queued NSEs that could overwhelm the Notification Server. It may be useful to disregard all incoming NSEs and also to direct the Altiris Agents to flush their local queues.


Step 1: If Time Critical Management > Persistent Connections are enabled, disable them in Notification Server :

Step 2: Enable FlushAgentEvents

NOTE: FlushAgentEvents is also in Core Settings.  In 8.5+ you can view Core Settings in the Console: Settings > Notification Server > Core Settings.

The registry key FlushAgentEvents (Reg_Dword located under HKEY_LOCAL_MACHINE > SOFTWARE > Altiris > eXpress > Notification Server) controls the ability to flush the local queue for the Altiris Agent. When set to 1, the Notification Server's Event Router will send the Altiris Agent an error response that will activate "flush local queues" on the Altiris Agent side. By default, this value is 0.

Note: This registry setting exits only on the Notification Server.

If the FlushAgentEvents registry key does not exist on your Notification Server, you can create it. In REGEDIT, click My Computer > HKEY_LOCAL_MACHINE  >  SOFTWARE > Altiris > eXpress. Right-click Notification Server, click New, click DWORD Value, type FlushAgentEvents and press Enter. Change the value to 1 to stop the Altiris Agents from reporting in. Change it back to 0 to have the Altiris Agents report in. 


REM Value of 0 Allows Agents to report it.
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\Notification Server" /v "FlushAgentEvents" /t REG_DWORD /d 0 /f 

Step 3: for fastest denial, restart the AeXSVC

Step 4: Validate that agents are being rejected by sending Basic Inventory from an (SMP) Agent UI:

SMP Logs also report: Unable to process client request from: (Unable to process request, 0x80056007)