Windows Executable Delivery Method
There are many different ways in which an application can be delivered to an end user and which one you choose to use could depend on a number of factors such as the type of device they are using, who owns the device or where they are physically located, as a few examples. The Windows Executable delivery method is intended for managed machines and allows you to automatically trigger the installation of an application on the target device. This works in a similar way to SCCM by launching an installer (located local to the device) in order to provide permanent access to an application.
The Windows Install delivery method was renamed in version 2.2 to Windows Executable to better reflect the scope of its potential use. This delivery method is not specifically for launching installers but can be used to launch any executable file on the target Windows device.
Before you start
Configuring Windows Executable
The Windows Executable delivery method relies on a Cloudpaging package in order to execute installers on the end device with system privileges, even if the user is a standard user. In order for you to be able to use this delivery method therefore, you will need to add this package to your Cloudpaging server and tell AppsAnywhere where it can be found.
Note: The below steps are completed during server installation. If this is not in place, please contact AppsAnywhere Support
Copy the Remote Application Launcher STP from the AppsAnywhere installation package
Place the STP file in your Cloudpaging repository
Using the Cloudpaging Admin UI
Add the application
Rename to AppsAnywhere Launcher
Publish it to your Paging servers
Add an unrestricted license for it's use
Copy the License GUID
You then need to configure AppsAnywhere to point to this package:
From the AppsAnywhere admin portal, search for Cloudpaging, or go to Settings > Cloudpaging in the navigation menu
Select the Cloudpaging Environment where you added the remote installer package
Enter the GUID of the Cloudpaging License you created in the Remote Installer License GUID box
Click Submit to save the details
You are now ready to begin creating and launching Windows Executable delivery methods.
Common Delivery Method Settings
All delivery methods share some basic, common settings that you will need to understand before continuing. Make sure you have read the Common Delivery Method Settings article before continuing.
Once you understand the common settings and how they work, you can go to the application you want to manage:
From the AppsAnywhere admin portal, in the navigation menu, go to Applications > Applications, or search for Applications or related terms
Click Edit next to the application you wish to manage
Creating the delivery method
Adding a new delivery method:
On the application management page, select the Delivery Methods tab
Under the list of current delivery methods, you will see the Add New Delivery Method section
Select Windows Executable from the Delivery Method dropdown
Click Add Delivery Method
The form for adding a new Windows Executable delivery method will then load up on the right-hand side
Complete the required details (described below)
Set the Operating System Compatibilities and the Restrictions for your delivery method
If the save was successful, you will see the form replaced with the following message and your new delivery method will be added to the bottom of the list on the left-hand side
If there were any errors with the data you entered, you will be prompted to correct these before you can continue.
Delivery Method Fields
The following table describes each field and setting available for this delivery method, it's intended value and an example for each
The command that you want to execute on the target device
The full command to be executed, as it would be if you were running it from command prompt on the target machine, including the full path to the executable if necessary
The parameters to be sent to the executable when it is triggered
The full list of parameters to be sent to the executable, typed as you would if running the command from command prompt
Install As Local System
Indicates whether to run the command under the local system account or run it as the logged on user
Yes or No, depending on the privileges that the command needs in order to complete the required tasks
For most application installs, local system privileges would be required to complete the installation
Allow Multiple Executions
Indicates whether the command is a one-time execution or something that can be run multiple times on the same device (by the same user)
Yes or No, depending on whether the command is something you would want to be run more than once
For most application installs, this would be No, however if the command is used to trigger the launch of an application this might be set to Yes
In order for files stored on a network location to be executed as local system (for example, any file on a network share that needs admin privileges to execute), that network location will need to allow anonymous access so that the local system account on the target device can access the file on the share. If the file being executed does not require admin privileges then leave 'Install As Local System' un-ticked, in which case the file will be accessed and executed using the logged-in user's account.
If it is not possible to enable anonymous access to a network share and the executable requires admin privileges to run then you will need to consider another means of deploying the file to the local file system of each machine before it can be executed, there is currently no way to access a file on a network share that requires user privileges and execute it as local system.
Now that your delivery method is in the list of those available, it is important that you prioritize it accordingly to determine exactly when it will be used.
To understand this process completely, take a look at the Prioritizing delivery methods article.
The Windows Executable delivery method was originally designed as a substitute for SCCM deployments for those that didn't have access to SCCM in that it allows the administrator to initiate an installer file that is locally available (either on the device itself or on a network share) without requiring that the logged in user has admin privileges on the device. While this is still its main purpose, the fact that it basically allows you to run any command on the target device means it can have a wide range of uses.