1 Comments
 

When ever you want to automate some mundane work or setup steps on your Windows computer the word PowerShell seems to be starting to pop up. But before the fun even can begin one will hit a wall pretty quickly.

FailureRunningScript

Get scripting enabled

So how do we get scripts enabled? On the Technet site you will find a long list of possible options on what levels can be set to:

  • Restricted: Default execution policy, does not run scripts, interactive commands only. This is what the default setup is on Windows 8.1, Windows 8 and even good old Windows 7.
  • All Signed: Runs scripts; all scripts and configuration files must be signed by a publisher that you trust; opens you to the risk of running signed (but malicious) scripts, after confirming that you trust the publisher.
  • Remote Signed: Local scripts run without signature. Any downloaded scripts need a digital signature, even an UNC path.
  • Unrestricted: Runs scripts; all scripts and configuration files downloaded from communication applications such as Microsoft Outlook, Internet Explorer, Outlook Express and Windows Messenger run after confirming that you understand the file originated from the Internet; no digital signature is required; opens you to the risk of running unsigned, malicious scripts downloaded from these applications

This list was originally taken from HowTo-Geek on 31. December 2014.

For now I'll go with the Remote Signed level. As I'm not planning on downloading any scripts from the web or using scripts from a network share. If you do intend to use any scripts from the web or any network share that are not signed you might want to use the Unrestricted level. So enough talk lets change the level, open a PowerShell with administrative rights and run the command:

Set-ExecutionPolicy RemoteSigned

SetupRemoteSigned

Now you should be able to start writing the little helpers for your system with the help of PowerShell.

HTH

Comments

Comment by 3d

this is still does not make any sense at all

3d
Post comment