Daniel Schroeders aka deadlydog Programming Blog Provide A Batch File To Run Your Power. Shell Script From Your Users Will Love You For It. A while ago in one of my older posts I included a little gem that I think deserves its own dedicated post calling Power. Shell scripts from a batch file. Why call my Power. Shell script from a batch file When I am writing a script for other people to use in my organization, or for the general public or even for myself sometimes, I will often include a simple batch file i. Power. Shell script and then exits. I do this because even though Power. Shell is awesome, not everybody knows what it is or how to use it non technical folks obviously, but even many of the technical folks in our organization have never used Power. Shell. Lets list the problems with sending somebody the Power. Shell script alone The first two points below are hurdles that every user stumbles over the first time they encounter Power. Shell they are there for security purposes When you double click a Power. Shell script. ps. PC. When you do figure out you need to right click the. Open With Windows Power. Shell to run the script, it will fail with a warning saying that the execution policy is currently configured to not allow scripts to be ran. My script may require admin privileges in order to run correctly, and it can be tricky to run a Power. Shell script as admin without going into a Power. Runas Run This Program With Restricted Access' title='Runas Run This Program With Restricted Access' />Shell console and running the script from there, which a lot of people wont know how to do. A potential problem that could affect Power. Guide Different Ways to Open Command Prompt as Administrator in Windows Many times we need to open Command Prompt window as Administrator in Windows which is also. MKS Toolkit Product FAQs. General. What is the PTC MKS Toolkit product family Are PTC MKS Toolkit products POSIX compliant What standards does PTC MKS Toolkit support Windows operating system including Windows 7, Windows Vista and Windows XP allows multiple user accounts to be created on the computer, be it administrators or. You can fix some compatibility issues that are due to the changes made between Windows operating system versions. These issues can include User Account Control UAC. PsExec is a free computer server utility that lets you execute Microsoft Windows Server processes on a remote system and redirect output to the local system. Harden Windows 10 A Security Guide gives detailed instructions on how to secure Windows 10 machines and prevent it from being compromised. We will harden the system. Shell Pros is that its possible for them to have variables or other settings set in their Power. Shell profile that could cause my script to not perform correctly this is pretty unlikely, but still a possibility. So imagine youve written a Power. Shell script that you want your grandma to run or an HR employee, or an executive, or your teenage daughter, etc. Do you think theyre going to be able to do it  Maybe, maybe not. You should be kind to your users and provide a batch file to call your Power. Shell script. The beauty of batch file scripts is that by default the script is ran when it is double clicked solves problem 1, and all of the other problems can be overcome by using a few arguments in our batch file. Ok, I see your point. So how do I call my Power. Shell script from a batch file First, the code I provide assumes that the batch file and Power. PowerShell is a task automation and configuration management framework from Microsoft, consisting of a commandline shell and associated scripting language. Shell script are in the same directory. So if you have a Power. Shell script called My. ZuFWGKrWA/SfjmeUHJtjI/AAAAAAAAAEk/KzXaQE-Vmug/s1600/042909_RunAs.png' alt='Runas Run This Program With Restricted Access' title='Runas Run This Program With Restricted Access' />Power. Shell. Script. Run. My. Power. Shell. Script. cmd, this is what the batch file would contain. SET This. Scripts. Directorydp. 0. SET Power. Shell. Script. PathThis. Scripts. DirectoryMy. Power. Shell. Script. Power. Shell No. Profile Execution. Runas Run This Program With Restricted Access' title='Runas Run This Program With Restricted Access' />Policy Bypass Command Power. Shell. Script. Path. Line 1 just prevents the contents of the batch file from being printed to the command prompt so its optional. Line 2 gets the directory that the batch file is in. Line 3 just appends the Power. Shell script filename to the script directory to get the full path to the Power. Shell script file, so this is the only line you would need to modify replace My. Android Developers Manager Example. Power. Shell. Script. Power. Shell scripts filename. The 4th line is the one that actually calls the Power. Shell script and contains the magic. The No. Profile switch solves problem 4 above, and the Execution. Policy Bypass argument solves problem 2. But that still leaves problem 3 above, right Call your Power. Shell script from a batch file with Administrative permissions i. Run As AdminIf your Power. Shell script needs to be run as an admin for whatever reason, the 4th line of the batch file will need to change a bit. SET This. Scripts. Directorydp. 0. SET Power. Shell. Script. PathThis. Scripts. DirectoryMy. Power. Shell. Script. Power. Shell No. Profile Execution. Policy Bypass Command Start Process Power. Shell Argument. List No. Profile Execution. Policy Bypass File Power. Shell. Script. Path Verb Run. As. We cant call the Power. Shell script as admin from the command prompt, but we can from Power. Shell so we essentially start a new Power. Shell session, and then have that session call the Power. Shell script using the Verb Run. As argument to specify that the script should be run as an administrator. And voila, thats it. Now all anybody has to do to run your Power. Shell script is double click the batch file something that even your grandma can do well, hopefully. So will your users really love you for this well, no. Instead they just wont be cursing you for sending them a script that they cant figure out how to run. Its one of those things that nobody notices until it doesnt work. So take the extra 1. Power. Shell script. I typically use this trick for myself too when my script requires admin rights, as it just makes running the script faster and easier. Bonus. One more tidbit that I often include at the end of my Power. Shell scripts is the following code. If running in the console, wait for input before closing. Host. Name eq Console. Host. Write Host Press any key to continue Host. UI. Raw. UI. Flush. Input. Buffer Make sure buffered input doesnt press a key and skip the Read. Key. Host. UI. Raw. UI. Read. KeyNo. Echo,Include. Key. Up null. This will prompt the user for keyboard input before closing the Power. Shell console window. This is useful because it allows users to read any errors that your Power. Shell script may have thrown before the window closes, or even just so they can see the Everything completed successfully message that your script spits out so they know that it ran correctly. Related side note you can change your PC to always leave the Power. Shell console window open after running a script, if that is your preference. I hope you find this useful. Feel free to leave comments. Happy coding Update. Several people have left comments asking how to pass parameters into the Power. Shell script from the batch file. Here is how to pass in ordered parameters. Power. Shell No. Profile Execution. Policy Bypass Command Power. Shell. Script. Path First Param Value Second Param Value. And here is how to pass in named parameters. Power. Shell No. Profile Execution. Policy Bypass Command Power. Shell. Script. Path Param. Name Param 1 Value Param. Name Param 2 Value. And if you are running the admin version of the script, here is how to pass in ordered parameters. Power. Shell No. Profile Execution. Policy Bypass Command Start Process Power. Shell Argument. List No. Profile Execution. Policy Bypass File Power. Shell. Script. Path First Param Value Second Param Value Verb Run. As. And here is how to pass in named parameters. Power. Shell No. Profile Execution. Policy Bypass Command Start Process Power. Shell Argument. List No. Profile Execution. Policy Bypass File Power. Shell. Script. Path Param. Name Param 1 Value Param. Name Param 2 value Verb Run. As. And yes, the Power. Shell script name and parameters need to be wrapped in 4 double quotes in order to properly handle pathsvalues with spaces.