Dear Symantec,
At the moment, most tasks that are sent to the Client Task Agent in 7.5 SP1 seem to go from "Waiting for the agent to get the task" to "Failed" or "Success" and do not seem to show a status of "Running".
This is a bit of a problem for many companies where the task may take a long time, such as:
1) "Prepare for Sysprep" - is the process running or do I need to give the Agent a push - and
2) "Deploy Image" - I have set 10 machines to deploy an image and 3 have not started, is there a problem?
3) DOS Scripts may be doing something special.
In these cases, interupting the Prepare for Sysprep can result in a bad Agent with a GUID included in the registry (which would be bad) and the deploy image can take a long time and needing to know that it has not started can be essential for a good rollout. As for DOS scripts, well, they could be doing something important and knowing that they have started can be useful.
It has been tested and we have seen that even a script such as:
ECHO Hello PAUSE
Can result in the machine showing "Waiting for the agent to get the task" for the instance, rather than "Running", which is the correct situation.
So, when the Client Task Agent has actually got the task, can it PLEASE send back an event to the Console to say that it has got the task and that it is running?
If performance could possibly be an issue, could we also have an option in the Task to not send the running event?
Kindest regards,
QuietLeni