forum.opsi.org

I am testing OPSI and its viability for deploying IIS 7 web apps to a Windows server environment with IIS. While I have already been able to script and deploy Firefox and Notepad++ without any issues, I am looking through the opsi-winst language but am not sure it will work. Does anyone have any knowledge of this use case? IS OPSI really meant for desktop deployments or is it capable of more?

Also, if opsi-winst cannot allow me to start/stop app pools, alter configurations within IIS, Powershell can (and I have written scripts to do so), but I am also trying to determine how to do a multi-script deployment via OPSI in which I can check for results of powershell scripts before starting the next and string them together successfully for each product I have

An example of how this SHOULD work via OPSI deployment:
Launch the deployment in opsi-configed web client
PS Script 1 stops an existing App Pool in IIS
PS Script 2 checks that it is stopped and then uninstalls the program
PS Script 3 checks that the program is no longer installed and then installs the new version (.exe/.msi)
PS Script 4 checks to see that the program has been installed and starts the App Pool in IIS
OPSI completes and logs the installation state

Thank you in advance for any thought you might have

Hello amarz,

if you are able to script the things you want in powershell, you could just run such scripts via an ExecWith section.
Please refer to the Winst manual where powershell is mentioned directly.

For checking the exit code you can use GetLastExitCode. This is also described in the manual.


With kind regards

N. Wenselowski