Is there a way to make powershell scripts run under the applications list so that when you install from the MDT image you can select which scripts you want to run?

I can run the scripts fine as scripts but every attempt I've tried the scripts will not execute.

This is how I am trying to do it, but they don't execute. (I link to the Script under the Install Applications under Task Sequence. So far I've come to conclude Microsoft does not allow PowerShell Scripts to work this way without some serious hacking around.

enter image description here


So after trying several ways and doing research this is what I have now:

I am trying this:

powershell -noexit "& "'\\SERVER.com\ImageDeploymentShare$\Scripts\script_tes_2t.ps1'

Working Directory is:


But I am getting this: enter image description here

I saw something like this posted on technet but surely this is to the extreme?

Filename RunPowerShell.cmd
Powershell -Command Set-ExecutionPolicy Unrestricted
Powershell.exe -file "%~dp0%1"
Powershell -Command Set-ExecutionPolicy AllSigned

Filename App1.ps1

Execute this with
[fulle_Path_if_needed\]RunPowerShell.cmd App1.ps1
  • Have you tried doing this?: powershell.exe yourcommandsgohere /yadayadayada Jul 7, 2014 at 20:10
  • If you already tried this then look at this: poshoholic.com/2007/09/27/… Jul 7, 2014 at 20:12
  • If that answers you question then I will make an answer that fits the info I just gave you. Jul 7, 2014 at 20:12
  • Trying to make heads and tails out of that site. They have so many quotations in there. I do appreciate your help Elliot!
    – Jason
    Jul 8, 2014 at 2:50
  • Try this: powershell “\%SCRIPTROOT%\script_tes_2t.ps1 Where the Powershell script is in your servers' deployment share in the scripts folder along with your other LTI/ZTI scriptes Jul 8, 2014 at 12:57

2 Answers 2


I don't know about MDT, but running UNC-located PowerShell scripts from the commandline goes something like powershell -ExecutionPolicy bypass -file \\path\to\file.ps1.
It works from cmd (without any security prompts):

Running UNC-based PowerShell scripts from commandline

  • If you are running an unattended script I also recommend adding -NonInteractive -NoProfile when calling Powershell.exe
    – Greg Bray
    Aug 11, 2014 at 5:32

in the 'quiet install command' of your application:

powershell.exe -executionpolicy bypass -noprofile -noninteractive -file ".\[yourscriptfile].ps1"

There main issue with just putting the ps1 file as the command is the executionpolicy, since the default is restricted. Even changing executionpolicy to remotesigned the script will not run because it's a UNC path.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.