My scripts do not longer report back if they complete or fail in the "run now status"
This counts for all scripts, also the default scripts in kace like force check-in.
The scripts are running and do what they should be doing, but I do not get any feedback after they are done running.
This was not the case before we updated to 5.3
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Do you get feedback on other logs (shown in the inventory detail of a machine)?

What are your agent log retention settings? You'll find this in the agent settings or if on an org-enabled box then in the org settings
Answered 10/11/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
I am also noticing this. i just upgraded recently the server to 5.3 and pushed out the 5.3 client, which has completed. The scripts do appear to be running correctly but I don't have logs for the script in each machine inventory item and the Scripting > Run Now Status shows 0/89 complete or whatever. I do have my agent logs re-enabled after I completed the server upgrade, which I had disabled according to the instructions. Other things (like the new client push) were logged for each machine, just not new scripts.

Anyone have some ideas or direction on this?
Answered 10/28/2011 by: stcoleman
Senior Yellow Belt

Please log in to comment
We are also having the same problem after upgrade to 5.3 , our Scripting update interval is 4 hours and Agent Log Retention setting is to save all agent logs.
Answered 02/07/2012 by: afzal
Fourth Degree Green Belt

Please log in to comment
Are these machines part of a replication share label?

If so, the Server and Client patch due out sometime in February should result this
Answered 02/08/2012 by: KevinG
Blue Belt

Please log in to comment