Calling a PowerShell Custom Action Calling a PowerShell Custom Action InstallShield 2012 Spring Project: This information applies to the following project types: • Basic MSI • InstallScript MSI Windows PowerShell is a.NET Framework–based command-line shell and script language that enables system administrators to automate system configuration tasks. InstallShield lets you include in your installations custom actions that run PowerShell scripts (.ps1).

You may want to add this type of custom action to a project to perform system configuration tasks at installation run time. Target System Requirements for Running PowerShell Scripts PowerShell is installed on only some operating systems by default. If an installation launches a PowerShell custom action but PowerShell is not installed, the custom action fails. To check that PowerShell is installed on a target system, you can add the predefined system search for PowerShell to your project, and configure your PowerShell custom action to run only if the system search determines that PowerShell is installed. You can also use this system search to determine which version of PowerShell is installed, and you can include a condition for the custom action that triggers its launching only on appropriate target systems.

The PowerShell execution policy, which determines whether PowerShell scripts can be run on a target system, is set to restricted by default. This default execution policy does not permit PowerShell scripts to be run. If an installation launches a PowerShell custom action but the execution policy does not permit scripts to be run, the PowerShell custom action fails. If you want your installation to override the target system's execution policy with an appropriate one for your installation's PowerShell custom actions, you can set the Windows Installer property IS_PS_EXECUTIONPOLICY equal to the name of the appropriate execution policy.

Getting/setting a global variable in InstallShield. Call MsiSetProperty to set it, and write your custom action's. Add a New Set Property and I was good. We can easily use Set Property Custom Action to set Windows Installer Property, but sometimes we wish to set the property directly in VbScript.

Setting this property affects how the PowerShell custom actions are run in your installation; however, it does not alter the policy of the target system. Thus, any PowerShell scripts that are run subsequently outside of your installation, or during other subsequent installations, are not affected by use of the IS_PS_EXECUTIONPOLICY property. Some of the execution policies require that the PowerShell script (.ps1) be digitally signed. InstallShield does not include support for digitally signing PowerShell scripts. Tip: You can sign your PowerShell scripts from the PowerShell command prompt.

To learn more, enter the following command at the PowerShell command prompt: Get-Help About_Signing Adding a PowerShell Custom Action to Your Project The following procedure describes how to include and configure a PowerShell custom action in your project. The procedure includes adding the PowerShell system search to your project and defining the IS_PS_EXECUTIONPOLICY property. To add a PowerShell custom action to your project: 1. Build Your Own Stadium Software Reviews. Add to your project the predefined PowerShell system search that checks to ensure that PowerShell is installed: a.

In the View List under Behavior and Logic, click System Search. Right-click the grid in this view and then click Add Predefined Search.

The Add Predefined Search dialog box opens. Select the PowerShell search and then click OK.

If PowerShell is installed on a target system, the PowerShell system search sets the ISPOWERSHELLINSTALLED property. Berlin Emotional Database. To indicate which execution policy you want your installation to use for your PowerShell custom actions, define the IS_PS_EXECUTIONPOLICY property: a.

In the View List under Behavior and Logic, click Property Manager. Click the New Property button. InstallShield adds a new row at the bottom of the view.

In the Name column, enter the following: IS_PS_EXECUTIONPOLICY d. In the Value column, enter the name of the execution policy that you want to use to run PowerShell custom actions in your installation. Available options are: • AllSigned—This policy allows only digitally signed PowerShell scripts to be run. • Bypass—This policy allows all PowerShell scripts to be run, regardless of whether they are signed.