How Task Server Uses the Tickle Mechanism

The tickle server is a component of Task Management. The tickle server component runs only on the Notification Server computer and is responsible for notifying task servers of pending tasks for their client computers. Tickle connection between Notification Server and task servers is also used for delivering new task server settings to task servers.
Task servers have the native ability to tickle their registered client computers. This tickle ability is separate from the tickle server component on the Notification Server computer.
The tickle server sends IP tickle packets to task servers when any of their registered client computers have a job or task to run. After the tickle packet is received, the task server immediately requests the task or the job information from Notification Server for its registered client computers. It also tickles its client computers. When the Client Task Agent receives the tickle packet, it requests the job or the task information from its registered task server. Only after the Client Task Agent receives the task information is the task executed. Status events for completed tasks are sent back to the registered task server upon completion.
If the tickle packets are blocked or otherwise cannot reach the destination, the Client Task Agent automatically checks back to its registered task server for any new job information. It performs this check every 30 minutes. This Task Request Interval is configurable in the Symantec Management Console. Task Server task and job information is not received through the Symantec Management Agent configuration policy. It is received directly by the Client Task Agent from its registered task server. If you force the Symantec Management Agent to update its configuration policy, it does 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.
Tickle mechanism does not function in Cloud-enabled Management (CEM) mode.
The following example assumes the Client Task Agent for ComputerA is registered with RemoteTaskServer1.
Sequence for how the task server tickle works
Sequence
Description
One
A Notification Server administrator assigns a task to run immediately on ComputerA.
Two
The Tickle Server on the Notification Server computer sends a tickle packet to notify RemoteTaskServer1 of the pending task.
Three
RemoteTaskServer1 receives the tickle packet and immediately requests the job information from Notification Server.
Four
RemoteTaskServer1 tickles ComputerA to notify it of the pending task.
Five
ComputerA receives the tickle packet and immediately requests the job information from its registered task server – RemoteTaskServer1.
Six
ComputerA receives the job information and executes the task.
Seven
Upon completion of the task, ComputerA sends a status event back to RemoteTaskServer1.
Eight
RemoteTaskServer1 caches the status event and immediately attempts to forward it back to Notification Server.
Nine
Notification Server receives the status event from RemoteTaskServer1 and records the information in the database.