How do I make a script "Run as administrator" on its own?

Question

Hello,
Win 8.1, VB scripts or PowerShell
Having discovered I previously failed to fully study UAC, I now understand why scripts transferred to a new Win 8.1 machine quit working.  They have to be 'Run As Administrator' on the new machine; then they work as before.  While I'm still
a little hazy on UAC, but continuing to study, it seems I'm left with a choice.  Please correct my perception of this choice if it's wrong:
1) I can change my UAC settings (which I actually prefer not to do - I'm a safety guy...)
2) I must always run my scripts by right clicking to the context menu and clicking "Run As Administrator"
3) I learn if there is a way for my script to "Run As Administrator" on its own
Assuming my choices above are correct, I would like to focus on choice 3.
I've done some amount of research, but I'm not sure any of the solutions I saw actually accomplish choice 3.  Most of those posts indicate that the individual still had to enter a password or perform some other interaction after the script ran, so I'm
not sure why the solutions posted were an answer to what was basically the same as my question here.
Can a script be setup to Run As Administrator without requiring any further user interaction?  I'm wondering if this is actually a self-defeating question, because if a script can be setup as such, then wouldn't it bypass the very purpose
UAC was put in place, for protection?  Am I thinking incorrectly?
If it is possible to write the script so it really runs without further interaction, please point me where I might need to study more.
Thanks.
Best Regards,
Alan

Answer 1

Hi jrv,
So, I think we've unofficially become friends since you answered my question in .vbs because you know that's where I've been.  I really am trying to transition to .ps1, but thanks for the thought. :-)  I actually did write a test .ps1 using get-vm
(which is very cool thank you) but wasn't able to execute it other than running a batch file from the context menu selection 'Run As Administrator'.  The following is the operative line I used in the batch file (it doesn't seem like the -Verb runas
worked as I expected it to):
powershell -executionpolicy remotesigned -file C:\batchFiles\ps\vmstatus.ps1 -Verb runas
I am getting a book on Powershell to study.
But, regarding your line above, I think I applied your guidance correctly.  I created a shortcut with the following line in the target box (I'm assuming this is what you were directing me to do. I also assumed I was supposed to add powershell.exe
at the beginning of the line you posted above):
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
start-process cscript C:\batchFiles\vmStatus.vbs -Verb RunAs
Windows seem to add the full path for powershell.exe automatically.  It runs without requiring the context menu selection "Run As Administrator", but it
still brings up the UAC message box for permission to continue, which is what I was trying to address in my initial post when I was speaking to the possible self-defeating nature of my question to allow
a script to bypass UAC.
I'm asking to confirm: having the UAC popup is in fact normal behavior that can't be side stepped unless other steps are taken.  So I guess I need to continue research to understand
what must be done to allow simple double-clicking of a shortcut to get a seamless execution without actually changing UAC.
Regarding STscripter's solution, I experienced the same UAC message box, so this post is also in response to that answer.
Thanks again for your help.
Best Regards,
Alan