Add Powershell Script to Post-Installation Tasks
Now that windows comes with Powershell installed. It would be nice to be able to add Powershell scripts as Post-Installation Tasks instead of having to zip them and run them with a batch file.
Completed in version 5.0
Justino Garcia commented
I Also wish for this to be added for post-install tasks, so that I don't have to do some backwards things to get powershell to run,
Kent West commented
Attaching a file that must be opened in a separate tool, edited there, and then re-imported adds unneeded complexity.
Just let us create/edit the PowerScript right there in the window, as we can with BAT scripts.
You could also do the same with VB scripts, and perhaps with BASH scripts (assuming Windows ever makes that usable).
This also makes the post-install task more completely self-documenting. If a newbie comes in to replace my role as the K2000 guy, and he doesn't know what my script does, it's much easier to sort it out if it's right there in the window than if he has to add one more complexity to his learning-curve to get up-to-speed on the K2.
I came here specifically to post this request, but upon having found it already as a request, I'm voting for it instead.
While it would be nice to have "native" support, you can actually just attach the script and enter "%systemdrive%\Windows\System32\WindowsPowerShell\v1.0\powershell -nologo -executionpolicy bypass -noprofile -file MyScript.ps1" as the command line. I found this in a KB article.