Use Task Scheduler to Run a PowerShell Script

The first option that we are going to look at is using the task scheduler in Windows to run a PowerShell Script. The Windows Task Scheduler originates from Windows 95! and is a great way to schedule tasks in Windows.

o run PowerShell scripts with the task scheduler, we can’t simply select the PowerShell file that we want to schedule. What we are going to do is run the “program” PowerShell and use the arguments to select the file that we want to run.

1. Open Task SchedulerClick on Start and type “Task scheduler” to open it. Or select it in the Start Menu under Windows Administrative Tools (or Windows Tools when using Win 11)
2. Create a new basic taskClick on Create Basic Tasks… in the action bar on the right side and give your task a name.
   (I recommend organizing your tasks in folders, create them on the left side first)

3. Schedule the taskThe trigger determines when the task should be executed. Choose a trigger, for example, Weekly, and click Next to configure when exactly the tasks need to be executed.

4. Set the ActionHere comes the important part, for the action, we are going to Start a Program

5. Start a Program – PowerShellThe program that we want to run is PowerShell. Just enter PowerShell in the Program/Script field (see screenshot in step 6), you don’t need to find the exact path to the executable.

6. Add ArgumentsIn the arguments field, we are going to add the argument -File and path to the PowerShell script. It’s also a good idea to add the PowerShell switch -NoProfile and set the -ExecutionPolicy to ByPass.

If your scripts require any parameters then you can add them after the path (for example the -Output parameter):

-NoProfile -ExecutionPolicy Bypass -File “C:\scripts\ADHealth.ps1” -Output “HTML”

7. Start inAlways set the Start in location to the same path as where your script is located. This way any exports that your script generates will be stored in the same location as your script. Otherwise, the output will be saved in C:\Windows\System32

8. FinishClick on Next and review your settings on the finish screen. Make sure that you select Open the properties dialog … so we configure some more settings.

9. Advanced Settings

There are two settings that we need to change for our scheduled PowerShell task. We will need to make sure that the script runs even when we are not logged on, which you do on the General tab.

And we want to make sure that the script stops if it’s running for more than a day. Change this setting under Settings and set Stop the task if it runs longer than to 1 day or less.

10. Save the taskClick Ok and enter your password, so the task can run when you are not logged on. It is always a good idea to test your task, right-click on it, and choose Run to run the task now.

Fix for PowerShell Script cannot be loaded because running scripts is disabled on this system error

On trying to run a PowerShell script from the PowerShell console, I received this error message: “File C:\temp\GenerateRpt.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 CategoryInfo: SecurityError PSSecurityException FullyQualifiedErrorId : UnauthorizedAccess”

Set the Execution Policy

Set the execution Policy with the following command:

Set-ExecutionPolicy RemoteSigned

You’ll see a security risk warning. Type “Y” or “A” when prompted to proceed. That’s all! This should solve the issue.