Add a PowerShell script or an executable command to one or all Application Manager deployment processes to run specific actions before and/or after installing new application versions.
Example uses:
- Remove a previous application version from the endpoint prior to installing a new version
- Show users a notification to close the application before installation
- Apply the organization's default settings to the application after it installs
Known Issue: Currently, the Additional Installation Parameters setting will not work in conjunction with pre-/post-scripting. Additional uninstallation parameters are not affected. This issue will be fixed in an upcoming release.
To add a pre- or post-install action:
1. Navigate to the Install Actions section in your deployment process settings or global settings, depending on whether you are adding an install action to one deployment process or all deployment processes.
- Single deployment: From the Deployment Processes page, click the ellipsis (...) to the right of the deployment process and select Manage Settings. In the Deployment process settings side panel, click Advanced.
TIP: You can run install actions for an individual application by creating a deployment process that includes only that one application.
- All deployments: From the Settings page, click the Settings cog to the right of the environment. On the Environment Settings page, click Deployment Processes > Advanced.
2. In the Install Actions section, enable the Pre Install Action or Post Install Action option by changing the setting to 'Yes'.
3. In the Pre/Post Installation Action side panel that opens, select Script or Executable.
Script
- Select Use inline script to add your PowerShell script directly within the inline editor.
- Select Specify UNC path to script file to add a folder path under Additional Files & Folders. Files included here are copied to the RecastAM folder in your application's deployment package. To reference files in the installation scripts, prefix them with the relative path. Ex. RecastAM\Script.cmd
Executable
- Enter an Installation Command and optional Parameters.
- You must add the installation command under Additional Files & Folders if it does not already exist on the device. Files included here are copied to the RecastAM folder in your application's deployment package.
- Add Parameters to your command (optional). You can include variables (Application, Publisher, Architecture, Language, Version) by choosing one or more from the drop-down menu.
- The full install command will display below the field as you build it. Ex. /silent/log:"%temp%\Microsoft\Office 365_1.022.1076.log"
NOTE: Add quotation marks around executable names that include spaces.
3. Save your changes.