All Collections
Onboarding & Offboarding
Software installation
Pre-install, post-install, and install check script (Windows Custom Software)
Pre-install, post-install, and install check script (Windows Custom Software)
Updated over a week ago

Dive into the latest feature of the Swif App: running test scripts before and after installing custom Windows applications. This tutorial outlines the steps to create and upload a custom application package, detail its specifications, and set up scripts for pre and post-installation.

Start by navigating to the section for uploading custom application packages.

Image

Step 1: Choose Windows as the operating system.

Image

Step 2: Assign a name to the custom application.

Image

Step 3: Enter a description and domain for the custom application. Remember, filling in the domain field is compulsory.

Image

Step 4: Upload the installer file for the application.

Image

Step 5: Indicate the application's version.

Image

Step 6: Add tags for the application.

Image

Step 7: If desired, upload the uninstaller file for the application.

Image

Step 8: If applicable, provide arguments for the installer and uninstaller files.

Image

Step 9: Implement the check script. This script runs as a check before the script execution. "Check script" runs before the pre-install script and has to return a 1 or 0 code.

Image

Step 10: Set up the pre-install command script.

Image

Step 11: Set up the post-install command script.

Image

Step 12: Review all the information, then click on continue to finish the application upload process.

Image

Step 13: Review all the settings.

Image

Step 14: Click on finish to complete the process.

Image

After successfully uploading the application,

Image

the application will install on the device, executing all necessary pre and post-install scripts.

Image

To revise or review the application,

Image

simply navigate to the edit option.

Image

This wraps up the tutorial on using Swif App's new feature for custom application installation with pre and post-installation checking scripts.

Did this answer your question?