This project is read-only.

What is Deploy-Application.exe used for ?

Topics: Archive - General
Jan 7, 2015 at 5:14 PM
Maybe stupid question, but I always use the powershell script files....
But were is Deploy-Application.exe used for ?

is it a compiled version of the script files ?
Jan 7, 2015 at 8:29 PM

There are no stupid question but stupid answer.

From the documentation:
Performs the actual install / uninstall and is the only file that needs to be modified, depending on your level of customisation.
An optional executable that can be used to launch the Deploy-Application.ps1 script without opening a PowerShell console window. Supports passing command-line parameters to the script.
There are two ways to launch the toolkit for deployment of applications.
1.  Launch “Deploy-Application.ps1” PowerShell script as administrator.
2.  Launch “Deploy-Application.exe” as administrator. This will launch the “Deploy-Application.ps1” PowerShell script without opening a PowerShell command window. Note, if the x86 PowerShell is required (for example, if CAPICOM or another x86 library is needed), launch Deploy-Application.exe /32 
But I read a lot of peoples are using the exe. I don't know why..

Marked as answer by Pollewops on 1/9/2015 at 12:44 AM
Jan 8, 2015 at 9:40 AM
We are using the Toolkit along with SCCM 2007 for now.
What I like about the EXE file is the users don't see the PS screens appearing on their screens during the script initialization. The users are sometimes "smart" and quick enough to close the PS window (and terminating) the script execution.
You may also need to set the execution-policy when calling PS1 script file - with EXE, you don't have to worry about execution-policy in the command line.
Other then this the PS1 in general works as well, of course.

Jan 8, 2015 at 10:55 AM

Is it still true with SCCM 2012 R2? Package or Application model?
What is the difference with both if the exe does not provoke it?