Troubleshoot Task Server Issue
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:
- Task server with HTTP.
- Task server with IIS.
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.
About Endpoint Management Community Blog
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments
Proxy Settings Can Also Cause Issues
In our environment we use a proxy server for web browsing.
Even though we do not use or need the proxy settings internally to communicate with the NS, the Altiris Agent picked up the proxy settings from Internet Explorer.
This prevented the Client Task Server Agent from registering with the Task server.
I found KB Article# 41982 which talks about this very issue. The article says to change the registry values on the machine not reporting and then restarting the Altiris Agent on the machine afterwards.
I wrote a VBScript to do this for me and deployed it with SWD. Worked like a charm.
VBScript Follows:
Dim WshShell, StopAltirisAgent, StartAltirisAgent Set 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, True WshShell.Run StartAltirisAgent, 0, True Set WshShell = Nothing WScript.QuitWould you like to reply?
Login or Register to post your comment.