I deployed Altiris agent to computers in one of our sites and then installed an agent on one of the server in the site and set it as task server for that site.
The next day I notice that none of the computers is managed by the task server that I configured.
I checked the configuration on the NS server and every think looked right. Then I notice something strange, under the configuration part, in the task server roll out there are two collections:
I notice that my new task server appeared under the IIS collection while other task servers appear under the HTTP collection.
I checked the task server and it had IIS installed (without any use of it). So I dig in it some more and found that when I installed the agent and then set it as task server, if the server has IIS installed it will try to use IIS instead of installing the Altiris HTTP server. For some reason it didn't play nice...
So, I removed both the agent and IIS, then installed the agent again, set the agent as task server and now the Altiris HTTP server installed correctly.
A few minutes later all the computers in the site moved under the new task server and the tasks started to run normally.
Dim WshShell, StopAltirisAgent, StartAltirisAgentSet WshShell = CreateObject("WScript.Shell")StopAltirisAgent = "NET STOP " & Chr(34) & "Altiris Agent" & Chr(34)StartAltirisAgent = "NET START " & Chr(34) & "Altiris Agent" & Chr(34)WshShell.RegWrite "HKLM\Software\Altiris\Communications\Proxy Auto Detect", 0, "REG_DWORD"WshShell.RegWrite "HKLM\Software\Altiris\Communications\Proxy Server", "", "REG_SZ"WshShell.RegWrite "HKLM\Software\Altiris\Communications\Proxy Port", 0, "REG_DWORD"WshShell.Run StopAltirisAgent, 0, TrueWshShell.Run StartAltirisAgent, 0, TrueSet WshShell = NothingWScript.Quit