This question has been asked before (sorta) but wasn't really answered. I have a K1000 script that simply executes an uploaded batch file, which simply executes an executable on a network share. It doesn't appear to be running on machines that have been left in a locked state. The history shows that it was executed on all targeted computers, but there's no evidence that it ran (the executable restarts the machine at its end and writes logs all through the process - none of that occurs).

What settings need to be set so that this can run behind a locked console? The executable won't run if the user is logged off (I highly doubt it, anyway) but does need to run behind a locked console.
Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment

Answer Chosen by the Author

I can say that we have run KACE scripts that use command prompt to unlock local accounts, while the computer is locked (or not even logged on at all) and connected to the internet.
Answered 09/30/2015 by: alwayslearning30
White Belt

Please log in to comment


Answer this question or Comment on this question for clarity