How does the tickle function work with Task Server?
The Tickle Server is a subcomponent of Task Server. The Tickle Server component runs only on the SMP Server (Symantec Management Platform or Notification Server) and is responsible for notifying Task Servers of pending tasks for their clients. Task Servers also have the native ability to tickle their registered clients, which is separate from the Tickle Server component on the Notification Server.
The Tickle Server on the Notification Server sends an IP tickle packet to Task Server(s) when any of their registered clients have a job or task to run. Once the tickle packet is received, the Task Server will immediately request the task/job information from the Notification Server for its registered clients and will, in turn, tickle its clients. When the Client Task Agent receives the tickle packet, it will request the task/job information from its registered Task Server. Only after the Client Task Agent receives the task information will the task be executed. Status events for completed tasks are immediately sent back to the registered Task Server upon completion.
In the event that the tickle packets are blocked or otherwise unable to reach the destination, the Client Task Agent will automatically check back to its registered Task Server for any new job information every 5 minutes. This “Task Update Interval” is configurable in the Symantec Management Console by clicking on
Settings > Notification Server > Site Server Settings from the menu bar and then navigating to
Task Server Settings.
Note: Task Server task/job information is not received through the Symantec Management Agent configuration policy but is received directly by the Client Task Agent from its registered Task Server. As such, forcing the Agent to update its configuration policy will not force the Client Task Agent to receive pending task information.
By default, the Tickle Server uses port 50123 for Task Servers and Task Servers use port 50124 to tickle Client Task Agents and can also be adjusted by navigating to the same location as the Update Interval mentioned above.
The following is an example process workflow and assumes the Client Task Agent for ComputerA is registered with RemoteTaskServer1.