Packaging PowerShell Scripts
When creating a package for PowerShell, specify "powershell.exe" as the process. Unlike KiXtart and AutoIt, you cannot simply include the process in the Additional Files section of the ScriptPackager. Execution of PowerShell scripts requires installation of Windows PowerShell (which itself may be scripted). For command line installation details, see this article at AppDeploy.com.
For arguments, you may specify any desired powershell.exe command line arguments, such as:
-Version
used to start the specified version of Windows PowerShell.
-NoLogo
used to hides the copyright banner at startup.
-NoExit
used to specify that it should not exit after running startup commands.
-NoProfile
used to specify that the user profile should not be used.
-Noninteractive
used to suppress the interactive prompt normally displayed to the user.
For a full list of supported arguments, type powershell.exe -help at a command prompt