Home / server / Questions / 610710
Accepted
Jason
Asked: 2014-07-08 09:51:58 +0800 CST

Running PowerShell scripts as an Application in MDT 2013

  • 772

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

EDIT:

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:

.\%SCRIPTROOT%

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
Dir

Execute this with
[fulle_Path_if_needed\]RunPowerShell.cmd App1.ps1
windows

2 Answers

  1. Best Answer

    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

    • 4

  2. 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.

    • 2