Run Powershell script in windows Task Scheduler(Windows 7)

Question

Hi I've got a Script and are trying to start it in Task Scheduler.

this poses Two problems for me.

1. is that the script will activate a Application that requires the GUI to be running and shown. so how can I make Task Scheduler to log in to windows automatically at a specific time. The computer will never/rarely be turned off or rebooted.

2. I have yet to Successfully start a Powershell script from the Task Scheduler. I've tried Following:

powershell.exe -noexit -executionpolicy bypass -command &'Y:\Run Test\StartPowershellScript.ps1'

And

 powershell.exe -noexit -ExecutionPolicy Bypass -File 'Y:\Run Test\StartPowershellScript.ps1'

And a variation of the above.

powershell.exe -noexit -ExecutionPolicy Bypass &'Y:\Run Test\StartPowershellScript.ps1'

and I've tried some variations with and without &"" &'' & and so on.

now I'm not really sure if it can be done. but I hope I can get some help here.

Edit 1. I just tried the following.

powershell -noexit -ExecutionPolicy Bypass &'Y:\Run Test\StartPowershellScript.ps1'

after I did this in powershell.

set-executionpolicy -scope Process -executionPolicy Unrestricted -force
set-executionpolicy -scope CurrentUser -executionPolicy Unrestricted -force
set-executionpolicy -scope LocalMachine -executionPolicy Unrestricted -force

However How do I make sure that this will persist after the computer has been rebooted ?

Edit 2. as it seems I can't make Scheduled task log in or unlock the computer, is there Anyway to set up a task to run at a specific time to log in to the computer so the scheduled task can run at this time ?

Answer 1

1. You can't log into the GUI with a scheduled task. Enable automatic logon if you need an interactive desktop.

2. Remove -NoExit from the argument list, otherwise PowerShell will keep running after the script completes. Also replace your single quotes with double quotes.

The execution policy is persistent unless it's superseded by a local or group policy (in which case Set-ExecutionPolicy should throw an error) or you're logged in with a temporary profile.

If that doesn't help you need to provide more details. Doesn't the task start at all? Do you get an error? What do the task history and eventlog say? What is the output of Get-ExecutionPolicy?