---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Install Windows App activity

# Install Windows App activity {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

The Install Windows App activity
installs an application from an MSI package on a Windows target machine.
Hinweis:  
This activity replaces a Powershell activity by the same name available in releases prior to Geneva. If you have a workflow created in a previous version that uses the deprecated activity, your workflow will continue to work normally after upgrading to Geneva. However, all new workflows must use the custom version of this activity. This activity was built with the [PowerShell activity designer](https://servicenow-prod.fluidtopics.net/MjnUEg~6RmXMwQSzlAKDTA "PowerShell activities are configured to return data to a workflow from a host using Microsoft PowerShell."), which gives workflow administrators the ability to store input and output variables in the [databus](https://servicenow-prod.fluidtopics.net/8OYaonyVEUHUlQE7wAXD_w#t_ReuseDataInTheActivityDesigner "The Data tab in the Workflow Editor lists all custom activities used in the current workflow that produce data and displays that data for reuse in other custom activities.").

## Input variables

{#r_InstallWindowsAppActivity__table_e2z_mvs_hp__entry__2}

| Variable | Description |
|-|-|
| hostname | Hostname or IP address of the target Windows machine on which the service is installed. Use the Resolve DNS [MID Server capabilities](https://servicenow-prod.fluidtopics.net/Ixqp8gLvT6tnD2ksANEvaQ "MID Server capabilities define the specific functions of a MID Server within an IP address range.") to resolve hostnames into IP addresses. |
| installerpath | Path to the installer. The installer can be on any machine that is visible to both the MID Server and the target machine (local drive, UNC path, mapped drive, etc.). |
| installer | Name of the installer file, such as winzip150.msi. The installer must be an MSI package. |
| arguments | The parameter that contains the command line arguments to the MSI package. These are name=value pairs, separated by a space. For example, the argument might appear as: INSTALLDIR=c:\\myinstallfolder ADDDESKTOPICON=0. These arguments are dependent on the what the actual MSI being installed defines. If there are no arguments, leave the field empty. |
[Tabelle : 1. Install Windows App input variables]

{#r_InstallWindowsAppActivity__table_e2z_mvs_hp}

## Output variables

{#r_InstallWindowsAppActivity__table_rk2_cgv_jt__entry__2}

| Variable | Description |
|-|-|
| result | Either success or failure. |
| errorMessage | The executionResult.errorMessages from the [Activity designer parsing sources](https://servicenow-prod.fluidtopics.net/jecuRsCuzIyfFDyPkB_Ehw#r_ActivityDesignerParsingSources "This table lists the parsing sources available with each execution template."). |
[Tabelle : 2. Install Windows App output variables]

{#r_InstallWindowsAppActivity__table_rk2_cgv_jt}

## Conditions

The activity state tells the workflow engine what to do with the activity.{#r_InstallWindowsAppActivity__table_qqd_rws_hp__entry__2}

| Name | Description |
|-|-|
| Success | The Windows application was successfully installed on the target machine. |
| Failure | The Windows application failed to install on the target machine |
[Tabelle : 3. Install Windows App conditions]

{#r_InstallWindowsAppActivity__table_qqd_rws_hp}

## Enable WMI Windows Installer provider {#ariaid-title2}

To install software on Windows
machines using the Install Windows App activity, enable WMI Windows Installer provider on
all target machines.

### Vorbereitungen

* It is recommended that the MID Server, the target machine, and the installer source machine be on the same Active Directory domain. However, if these computers are on separate domains, those domains must have a [trust relationship](http://technet.microsoft.com/en-us/library/cc961481.aspx) established between them.
* If the installer path is a [UNC file sharing](http://compnetworking.about.com/od/windowsnetworking/g/unc-name.htm) machine, the Active Directory account of the target computer must be trusted for delegation. For instructions on this configuration, see the posting on the community for [installing and uninstalling Windows
  applications](https://community.servicenow.com/people/russ.sarbora/blog/2011/09/30/2540).
{#t_EnableWMIWindowsInstallProvider__ul_s5n_y5n_hp}

### Warum und wann dieser Vorgang ausgeführt wird

Hinweis:  
See [WMI Providers](http://msdn.microsoft.com/en-us/library/aa394570(v=vs.85).aspx) for a list of Windows operating systems that provide this tool by default.

### Prozedur

1. Open the Control Panel.
2. Go to Add or Remove Programs.
3. Select Add/Remove Windows Components.
4. Double-click Management and Monitoring Tools.  
   This action opens a secondary window displaying additional selections.
5. Select WMI Windows Installer Provider check box.
6. Click OK to return to the Windows Components Wizard window.
7. Click Next.  
   You might be asked for the Windows installation CD to complete this process.