have non-admin execute script that repairs network connection

I wrote a batch file to execute all the commands that repairing a network normally executes:

Code:

ipconfig /renew
arp -d *
nbtstat -R
nbtstat -RR
ipconfig /flushdns
ipconfig /registerdns

I would like a non-admin to be able to execute this script.
Is there a way to configure the command so it runs with admin rights, without storing an admin username and password in clear text, or possibly give a specific user rights to those commands contained in the script?

 

Need to run it as system, used to do it at uni to get 'things' to run on a locked down pc. When you schedule a task (e.g. cmd.exe) on windows it runs as system, no matter what account you’re logged into. voids the need for admin rights.

 

Does that mean I'd have to schedule a time for it to run, or could I make a shortcut to execute the scheduled task?
(I want this to run each time the person executes the VPN client, and they should only execute that once every week or so.)

 

Don’t really know much about batch files, but all you'd need to do is catch the current system time, append 2 seconds to it then have it execute
"at [Time] batchfile.bat"

Put /interactive if you want the user to see it.

I don’t know you can catch the system time with batch files, but that’s the way I’d try and do it. There might be a simpler solution

edit: maybe use %time%, then some how append 2 seconds

 

bleh sorry to double post, i got board in work decided to look this up a bit more

A better way seems this

sc delete testsvc
sc create testsvc binpath= "cmd /K start" type= own type= interact
sc start testsvc

I’m pretty sure you can place your batch file in place of cmd and it will execute as system, with out having to mess with system scheduler

Source

 

at command requires admin privileges to run, due to you being able to use it as a privilege escalation (to system) hack.

Fascinating stuff, opening a cmd.exe window with at, then killing explorer, and relaunching it through the system account.

 

i think i've corrupted the security at work more than a few times now by fixing stuff on users accounts by manually creating a 'CMD' shortcut via remote desktop / SMS on their desktops to bypass the run command lockout ^_^