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.

How do I modify the tickle port used by Task Server and the Client Task Agents?


Article ID: 181152


Updated On:


Management Platform (Formerly known as Notification Server) Task Server




How do I modify the tickle port used by Task Server and the Client Task Agents?


By default, Task Server utilizes port 50124 to tickle Client Task Agents when a pending task needs to run.  The tickle port is defined on the Task Servers in the Altiris.ClientTask.Server.config file, located at %ProgramFiles%\Altiris\Client Task Management. To modify the port:

  1. Open Altiris.ClientTask.Server.config on the Task Server and update the ClientTcpPort attribute to the desired value.
  2. Restart the Altiris Object Host Service on the Task Server.

Note that each Task Server manages the tickle for all of the agents that are registered to it. If you have multiple Task Servers in your environment, it would be required to modify the port for each individual Task Server to make the tickle port consistent throughout the entire environment. 

Also note that it is possible to disable the tickle entirely by specifying the port value as "-1" or "0". By disabling the tickle, the Client Task Agent will no longer be notified of pending tasks in real time by its Task Server, but will rely on the Task Request Interval. See article 34931 for more information about the tickle functionality.

For Task Server 7.0 see KB 47232.