Software Restriction Policy batch vs vbs

Question

Hi there,
I have recently implemented a Software Restriction Policy on a Computer level with Disallowed level as default.
I whitelisted the \\mydomain\SysVol so that my Group Policies could run.
I have a few batch files that run upon user logon. The batch files run but the the commands within them do not, they are being "access denied"
example of one of the batch files:
sc start servicexyz, killtask processxyz
if I were to convert my batch script into a vb script, would vb script be treated as a single file? unlike batch file which makes calls to other executables.
Thanks,

Answer 1

What you are trying to do cannot be done with a GP and  cannot be done with a script.  Thisis becsue what you are trying to do makes very little technical sense.  Either delegate the right or use another method.
¯\_(ツ)_/¯
This is how it worked for me just fine before I introduced SRP. 
When user logged off, a logoff batch script used "sc start service" to start service
When user logged on, a logon batch script used "sc stop service" to stop a service from running
Before SRP, all of my users were local administrators of their computers so permissions were not in a way. After the SRP introduction,
I had to remove all users local admin right and now experience this issue.
Do you mean it makes little technical sense with SRP or in general? Care to elaborate please?
Why do you think you have to start and stop the service all of the time?  It sounds like a design issue or an issue with  a bad service.
You can use SC to give users permissions on a service.  You can give out just start and stop (control) to a group thyne add or remove users from the group.
The group can be a domain group and GP can change the security on a service.
¯\_(ツ)_/¯