Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

NS7 "Run Script" Task Still Executing Even Though No Longer Scheduled

Created: 23 Feb 2011 • Updated: 02 Mar 2011 | 5 comments
This issue has been solved. See solution.

I created a "Run Script" task to perform a custom inventory using VBScript.  During the timeframe that it was being used, I had it scheduled to run every four hours on all computers.  Once I had the information that I needed, I deleted all schedule instances from the task.  Even with no schedules existing, I'm finding that an indeterminate number of computers are still running the task at least once daily.  On the computers I'm aware of, I have verified that they are checking in successfully with the NS and getting configuration updates.  There also seems to be no issue communicating with the Task Server (which, in this case, happens to be the NS).

Do I have to go so far as to delete the task itself?  Is there something I can remove on the task server(s), or is there some remnant of this task on the client machine somewhere that needs to be removed?

Comments 5 CommentsJump to latest comment

jharings's picture

the clients aren't being notified the task schedule is turned off. I would check the logs in the client, see what they think is happening. The data should be stored in the client .xml policy, but having to edit that manually for every client seems a bit extreme.

Can you just disable the task for now?

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Zac Truelove's picture

AFAIK there is no way to disable the task.  Unlike policies, there is no "On/Off" button. (see attached image)

I've searched both the task server and one of the client machines that continues to run the task for the GUID of the task, and the only result that comes back is in the TaskHistory.xml file on the client.  I can find no reference to it in any file on the task server.

2-24-2011 7-32-02 AM.jpg
jharings's picture

and I should be ashamed, I was indeed thinking of a policy. I guess the only option is to delete the task, which really shouldn't be necessary at all.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Zac Truelove's picture

While the cause of the issue is unknown, cleaning up the task management cache on each of the client machines has resolved this occurrence.

Deployed the following script via DS:

---------------------------------------------------------
REM Get the Altiris Agent install path
FOR /F "tokens=2*" %%A IN ('REG.EXE QUERY "HKLM\Software\Altiris\Altiris Agent" /V "installdir"') DO SET AgentDir=%%B
set tempbat=%temp%\AgentClean.bat"

REM Create temporary batch file to execute while the agent restarts
echo "%AgentDir%\aexagentutil" /stop > %tempbat%
echo rmdir "%AgentDir%\TaskManagement" /s /q >> %tempbat%
echo ping localhost -n 30 >> %tempbat%
echo "%AgentDir%\aexagentutil" /start >> %tempbat%
echo exit >> %tempbat%

REM Executes temporary batch file
start "" /MIN %tempbat%
---------------------------------------------------------

SOLUTION