When changing the Task Server port bindings on the Settings page (
Notification Server |
Site Server Settings, then expand on the left:
Settings and select
Task Service Settings), the new ports don't bind, leaving either some unbound ports, or the product bound to the wrong / old ports.
There are a few possibilities for why this may be happening:
Changes being changed but not saved in the Console.
The changes are not being correctly applied to the Services.
The services are not being restarted to accept the changes to the port(s).
There are some work-arounds we can apply to this situation, and Development is researching why the changes are not automatic.
Workarounds: To resolve the first scenario, make sure that "Automatically restart services when configuration changes" is checked on the Task Service Settings Page and be sure to save your changes. If you would not like have the services automatically restart, then the three listed services (Object Host Service, Client Task Dataloader, WWW Publishing) will need to be restarted manually.
To resolve scenarios 2 and 3, using the following steps should change the ports:
Go to the Task Server Settings Page and change the ports.
Click 'Save changes' to the apply these settings.
When the page reloads, verify that the changed ports are preserved.
Update the Configuration on the Local Agent (located on the NS machine)
Restart the 'Altiris Service' (service name 'AeXSvc').
The port will take a few moments to bind on the new port.
To verify the bound ports have changed, open a command prompt and run 'netstat -an' to display bound ports.
Applies To Notification Server 7.0, SP1, SP2
Imported Document ID: TECH47328
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe