KNOWN ISSUE: Configuring the Task Server client tickle port does not change the port properly
Last Updated May 20, 2009
When configuring the "Client to Task Server Tickle" port the changes are not properly applied if the automatically restart services box is not checked.
The configuration page will reflect the new port option after saving the settings and reloading the page. However, The Altrshost.exe does not properly apply the new settings. A reboot will not fix the issue and the symptoms mentioned still apply.
To workaround the issue the automatically restart services check box must be checked and the changes saved.
Follow these steps:
In the NS console open the All Settings Page
Navigate to Settings > Notification Server > Site Server Settings > Task Service > Settings > Task Service Settings
Check "Automatically restart services"
Click save changes
Open the Altiris Agent Settings on the Task Server
The changes should update in a few minutes as the Atrshost is restarted and initialized.
You can check the port that the atrshost.exe is using "netstat -an -b", procexp, or tcpview.
Applies To Task Server 7.0 SP1
ID: ETK 1672556
Etrack (Symantec) database
Imported Document ID: TECH42136
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe