Run PowerShell Script From the Command Line and More

If you ’ re newly to the PowerShell script language and want to learn how to run PowerShell script, you ’ ve do to the correct web log mail. This web log will be a tutorial report common ways to run scripts and a few issues that may pop up .

Not a reader? Watch this related video tutorial!

Not seeing the video? Make sure your ad blocker is disabled.

Prerequisites

not a reader ? Watch this relate video tutorial ! This article will be a walkthrough for you about how to run PowerShell on your local computer. If you ’ d like to follow along, please be certain you have the adopt prerequisites in put before starting this article.

  • A Windows 10 computer with Administrator privileges.
  • Windows PowerShell version 5 or higher. You can also use PowerShell v7. This tutorial will focus on Windows PowerShell since the Windows operating system already has it.
  • Any text file editor

Dealing with the Execution Policy

If this is the foremost time you ’ re trying to execute a Windows PowerShell handwriting, you may run into a common problem. PowerShell will probably return an error message stating that a script “ can not be loaded because running scripts is disabled on this system ” .

PS> .\GetServices.ps1

 File C:\Temp\GetServices.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at
 https:/go.microsoft.com/fwlink/?LinkID=135170.
 At line:1 char:1
 .\GetServices.ps1
 ~~~~~ CategoryInfo          : SecurityError: (:) [], PSSecurityException
 FullyQualifiedErrorId : UnauthorizedAccess   

PowerShell returns the error message above when you try to run a PowerShell with an execution policy set to Restricted, Remote Signed or All Signed .

Restricted

Restricted is the default policy set for Windows client computers. If you are using PowerShell for the first base time, your nonpayment policy would credibly be set to restrict all the scripts .
You can still execute person commands in a terminal, but not a script charge. The restriction includes any file ending with .ps1xml, .psm1 or .ps1 .

Unrestricted

Unrestricted allows you to run any script however, it warns you before execution if the script is downloaded from the internet. This policy is normally the default for any non-windows devices .

Remote Signed

Remote Signed policy allows you to run any script that is either ( a ) digitally signed or ( b-complex vitamin ) any handwriting written on your local calculator with or without a touch .
If a handwriting is downloaded from the internet and not signed, you would need to unblock the file. You can do so by right-clicking on the file and choosing Properties. Or, you could use the Unblock-File PowerShell cmdlet for that particular script file .
Using a outside sign policy would be an ideal choice when running a script downloaded from the internet .

All Signed

All signed requires all the scripts to be signed digitally by a trust publisher. This includes the scripts downloaded from the internet and written locally on your computer .

Changing the PowerShell Execution Policy

To change the murder policy :

  1. Open Windows PowerShell with Run as Administrator to make sure you have the highest permission to make the policy changes.

Search PowerShell in Start MenuSearch PowerShell in Start Menu 2. When open, run the following PowerShell command to set your calculator ’ second execution policy. The execution policy, as covered above, can be one of three unlike types. This tutorial is using a useful so far still secure murder policy of RemoteSigned .
Since this tutorial assumes you ’ ve downloaded from the Internet the GetServices.ps1 script file, set the execution policy to RemoteSigned .

The RemoteSigned execution policy forces you to cryptographically sign every PowerShell script downloaded from the Internet before PowerShell will run it on your system .

3. You should see an output requesting to confirm the legal action. Enter Y and hit enter to confirm the policy change .

Execution Policy Change
 The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose you to the
 security risks described in the about_Execution_Policies help topic at https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to
 change the execution policy?
 [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): 

At this point, follow the next steps to explore different methods to run the PowerShell script on your computer .

How to Run PowerShell Script

To demonstrate running a PowerShell script, you actually need a handwriting file to run ! If you don ’ t have one handy, download this ZIP file and extract the PS1 file within. You ’ ll find a simple script file inside called GetServices.ps1 .

Write-Output "Listing Computer Services"
Get-Service

Every PowerShell script should end with a .ps1 extension.

Using the Console

once you have a script ready, there are a few different ways you can execute a PowerShell script file. One of the most common ways is via the PowerShell console .
To do indeed :

  1. Open the PowerShell console as shown above.

2. navigate to the file system location your script is located using the Set-Location PowerShell cmdlet or the cd alias. This tutorial ’ s script is found in the C : \Temp directory .

PS> cd C:\Temp\

3. Run the script using a dot ( . ) note. PowerShell is a blast that besides looks for command names. To differentiate between a PowerShell control and a script, you must preface the handwriting with a point. This point represents the current directory .

 PS> .\GetServices.ps1

How to Run a PowerShell Script from the Command Line via the PowerShell Location

If you can ’ thyroxine or would rather not run scripts via the PowerShell console table, you can besides do so with the good ol ’ command line ( command prompt ) .
To run scripts via the command motivate, you must first start up the PowerShell feasible ( powershell.exe ), with the PowerShell location of C:\Program Files\WindowsPowerShell\powershell.exe and then pass the script path as a parameter to it .

You can run scripts with parameters in any context by merely specifying them while running the PowerShell feasible like powershell.exe -Parameter 'Foo' -Parameter2 'Bar' .

once you open cmd.exe, you can execute a PowerShell handwriting like below. This model is running the locomotive and passing it the script path of C : \Temp\GetServices.ps1 .
Notice below that the exemplar below is using the PowerShell placement path to run the script. You ’ ll have to do this if the booklet international relations and security network ’ triiodothyronine in your PATH somewhere .

CMD> C:\Program Files\WindowsPowerShell\powershell.exe "C:\Temp\GetServices.ps1"

The PowerShell location for PowerShell 7 uses a different feasible named pwsh.exe typically located in C : \Program Files\PowerShell\7\pwsh.exe .

Below is a handy YouTube video recording that covers executing a script via a batch file which the cmd.exe executes .

Using the PowerShell ISE

If you create your own scripts or edit others ’, you ’ ll probably be using a handwriting editor program like the PowerShell ISE or possibly ocular Studio ( VS ) Code. Since the ISE comes with Windows, let ’ s focus on that method acting for this tutorial .
To invoke a script via the ISE :

  1. Navigate to Start Menu, search for PowerShell ISE and open it.

Search PowerShell ISE in Start MenuSearch PowerShell ISE in Start Menu 2. Click on FileOpen and find your script .
Open Script using File MenuOpen Script using File Menu 3. With the handwriting open, chink on the green run button to execute the script. This clitoris will invoke the script in the built-in PowerShell terminal at the bottom .
Run Script using PowerShell ISERun Script using PowerShell ISE

The Sample Script’s Output

A PowerShell handwriting can sometimes return end product. This happens when the script you ’ ra carry through is built to return objects which is a fundamental component of PowerShell .
If you run the sample GetServices.ps1 script, you will see the following. This handwriting runs the Get-Service cmdlet which returns all of the services installed on your local Windows computer.

PS> .\GetScripts.ps1
Listing Computer Services

Status   Name               DisplayName
------   ----               -----------
Running  aakore             Acronis Agent Core Service
Stopped  AarSvc_1b668d      Agent Activation Runtime_1b668d
Running  AcronisActivePr... Acronis Active Protection Service
Running  AcronisCyberPro... Acronis Cyber Protection Service
Running  AcrSch2Svc         Acronis Scheduler2 Service
Running  AdobeARMservice    Adobe Acrobat Update Service
Running  AdobeUpdateService AdobeUpdateService
Running  AGMService         Adobe Genuine Monitor Service
Running  AGSService         Adobe Genuine Software Integrity Se...
----Truncated----

Running a PowerShell Script from Within a Script

Let ’ s say you have two scripts and you ’ d like one to call the other. possibly you have a handwriting called GetUser.ps1 and one called ResetPassword.ps1. Inside of the GetUser.ps1 handwriting, you ’ d like to execute the ResetPassword.ps1 to reset a user password .
Inside of the calling script ( GetUser.ps1 ), you ’ d add a lineage to execute the other script precisely like you would call the script from the command argumentation .
You can see below you have a couple of options. You should typically choose to run the other script within the like session or scope to simplify things unless you have a specific reason to run the script in another PowerShell session .

## To run the other script in a new session
powershell.exe .\ResetPassword.ps1

## To run the other script in the same session
.\ResetPassword.ps1
informant : https://epicentreconcerts.org
Category : How To

Related Posts

Leave a Reply

Your email address will not be published.