Custom Search

---

Guy's Review of
Computer Utilities

 1) FreePing
 2) Engineer's Toolset
 3) Xobni
 4) PuTTY
 5) WMI Monitor
 6) BgInfo
 7) Net-SNMP
 8) IP Address Tracker
 9) DNS Stuff
10) WinDiff Compare

---

PowerShell 3.0 Schedule Task

How To Schedule Tasks for PowerShell Scripts

The situation: You have a PowerShell 3.0 script that you want to run every day, or every week.  Alternatively, you want to execute PowerShell 3.0 commands after a particular event occurs.

My advice is don't re-invent the wheel, run your PowerShell script with the built-in Windows Task Scheduler.

• Step 1: Create the PowerShell Payload File
• Step 1a: Test Your Code in PowerShell
• Step 2: Save Your Payload File
• Step 3: Launch the Task Scheduler
• Step 3a: Configure the Actions Tab
• Step 4: Testing Your Task

 ♣

Step 1: Create the PowerShell Payload File

This is just an example PowerShell script for the Task Scheduler. While the script is feeble and ripe for modification, at least it produces output in the form text file containing a list of processes.

Note 1: I used $Location to remind us to change the path to the file created by this script.

Step 1a: Test Your Code in PowerShell

Before you ask the Task Scheduler to run this code I would test by running the command in the PowerShell ISE.  In particular I would like to see that SchedulePr.txt was created and take note of its Date Modified.

Step 2: Save Your Payload File

Save the above PowerShell script as say - ProcessTask.ps1.  Take a note of your full path:  e.g. D:\PShell\ProcessTask.ps1

Step 3: Launch the Task Scheduler

I use the Windows 'Search' dialog box for finding the built-in Windows Task Scheduler. Once launched seek the Actions pane then Create Task  (Swerve the basic task.)

General: Give the task a name, e.g. GuyProc.  Whilst at this tab check the options.

Trigger: We will fire the PowerShell script at a specified time, e.g. 12:30 every day.

Actions: This is where we instruct the scheduler what to do when the trigger fires.

Step 3a: Configure the Actions Tab

We have reached the crucial stage, the key point is to type just 'PowerShell' in the Program/script dialog box. See screenshot below right.

Mistake: Don't put the name of the script in the Program/script box, just leave one instruction here 'PowerShell'.

Add arguments: This is where you tell PowerShell what to through parameters:
-File D:\PShell\ProcessTask.ps1

or better enclosed with double quote speech marks

 -File "D:\PShell\Process Task.ps1"

The " Double Speech Marks" are required if the path has spaces.  Incidentally, ' Single speech marks' don't cut it here. 

-ExecutionPolicy Bypass will ensure that the PowerShell scheduled task will run even thought the computer has a restricted script policy.  However, there is a secret, and that is to ensure this parameter is at the beginning of the arguments thus:
-ExecutionPolicy Bypass -File "D:\PShell\Process Task.ps1"

See more PowerShell options here.

Names of Recap:

• What's the name of your PowerShell .ps1 file?  (D:\PShell\ProcessTask.ps1)
• Where to look for the output file?  ($Location = "C:\SchedulePr.txt")
• Name of the Task (GuyProc)

Step 4: Testing Your PowerShell Task

This tip saved me a lot of time in testing tasks: Right-click and 'Run'.

Once this works, then by all means revert to creating a timetable under the Trigger tab so that you can schedule a PowerShell script.

If the task fails even though it works in the PowerShell ISE, then I would consider appending -ExcecutionPolicy Bypass

Other ideas for tasks to schedule

• Update-Help

Guy Recommends:  SolarWinds' Free Bulk Import Tool

Import users from a spreadsheet.  Just provide a list of the users with their fields in the top row, and save as .csv file.  Then launch this FREE utility and match your fields with AD's attributes, click to import the users.  Optionally, you can provide the name of the OU where the new accounts will be born.

There are also two bonus tools in this free download, and all 3 have been approved by Microsoft:

1. Bulk-import new users into Active Directory.
2. Seek and zap unwanted user accounts.
3. Find inactive computers.

Download your FREE bulk import tool.

More PowerShell Parameters

I hope these help you, in particular, you may need the -ExecutionPolicy bypass parameter.

Summary: Creating a PowerShell Task Schedule

If you want to run a PowerShell 3.0 script run every day, or every week then don't re-invent the wheel, call for the assistance of the Windows Task Scheduler.  Remember that the name of the Script / Program is PowerShell, the actual script is referenced by the -file parameter.

See more Microsoft PowerShell tutorials:

• PowerShell Home   • Test-ServerHealth  • Test-SystemHealth   • Test-Connection  • Test-Path

• PowerShell Logon Script  • PowerShell add printer  • PowerShell Schedule Task

• Map Network Drive  • Exchange 2010 PowerShell Cmdlets   • Exchange 2010 Performance Monitor

Please email me if you have a better script examples. Also please report any factual mistakes, grammatical errors or broken links, I will be happy to correct the fault.

 *

Custom Search Site Home

Guy Recommends: WMI Monitor and It's Free! Windows Management Instrumentation (WMI) is one of the hidden treasures of Microsoft operating systems. Fortunately, SolarWinds have created the Free WMI Monitor so that you can actually see and understand these gems of performance information.  Take the guess work out of which WMI counters to use for applications like Microsoft Active Directory, SQL or Exchange Server. Download your free copy of WMI Monitor

Author: Guy Thomas Copyright © 1999-2012 Computer Performance LTD All rights reserved. Please report a broken link, or an error to: