Greetings,
I would like to confirm if this is normal group policy behavior, or if we have a bug in one of our policies/scripts.
We are running several batch files/scripts using group policy. Lets say for example I am running the following from different policies: launch1.cmd, launch2.cmd, launch3.cmd
I have configured Task Manager to include the "Command Line" with the view. To do this click the Processes tab, click View, click Select Columns, scroll to the bottom, put a check mark in the Command Line option.
From this view, I can see the policies being run in Task Manager, and I can see batch files being called by policy, launch1.cmd, launch2.cmd, and launch3.cmd.
So my question is, after the policy runs the script, shouldn't the process exit memory when the script finishes?
If I am seeing those scripts in Task Manager, and they don't go away, does this mean something else in group policy is hanging those scripts?
Thanks.