First assign the name and description of the package. Likewise, select whether the package is to be generated from an MSI file, a Setup file, an AutoMATE file or a virtual application. The following steps will differ depending on the selected installation type.
MSI file
Depending on the installation type you have chosen, appropriate information is required in the second step. If you have selected the MSI file installation type, you have to add an MSI file or a folder by means of the corresponding button. If you add a folder, all subfolders will be scanned for MSI files as well. If there are several MSI files, the right file can be selected from a drop-down list.
Setup file
If you have selected a Setup file as installation type, you can here directly add a setup file or a folder. You can select the right setup file from a drop-down list. In addition you can enter installation parameter such as –quite for a setup that will run in the background. The exact parameters are listed in the documentation for the program to be installed.
In addition to the setup file you can specify an uninstall file as well as a repair file. These files are required to properly repair or uninstall the program. With the adjacent buttons you can add and manually supplement global variables (e.g. %PROGRAMFILES%). Alternatively, you can activate a dialog with the button Scan ACMP Datenbank after Uninstall commands to list all known uninstall information. This uninstallation information is read during the software inventory. The option Copy installation files once again before uninstalling serves to correctly uninstall the software if this data is required from the installation package.
AutoMATE file
If you want to create a client command with AutoMate files, you can enter one AutoMate file each for installation, repairs and deinstallation, just as in the case of the setup files. You can add these files by clicking the buttons next to the right margin and via the drop-down lists at the bottom.
Virtual application
If you want to create a client command with a virtual application, first select in the second step the type of the virtual application: a ThinApp application as an executable file or as an MSI file, a Cameyo application or another virtual application.
In the next step, first select the application file. Depending on the type of virtual application, further information is required:
ThinApp Application (executable file): Entry point / Required ThinReg file
ThinApp Application (MSI file): No further input is required.
Cameyo Application: No further input is required.
Other virtual Application: Install / uninstall / repair parameters
The following steps are once again independent of the type of installation.
Storage options
In the next step, you specify where the installation files are to be stored or from where the installation files can be retrieved. The installation files for installing the appropriate client can be transferred in six different ways. Depending on the choice, additional connection information must be provided. This information is listed below:
|
Upload files to the file repository and access it from there.
|
|
Connection information: |
none
|
|
|
The files have been loaded already to a file server and can be used from there.
|
|
Connection information: |
UNC path to the download directory as well as user name and password, if required.
|
|
|
The files have been loaded already to a file server and can be used from there.
|
|
Connection information: |
HTTP address for the download directory.
|
|
|
The files have been loaded already to an FTP server and can be used from there.
|
|
Connection information: |
Server name, base FTP path as well as user name and password, if required.
|
|
|
The files have been loaded already to a BITS server and can be used from there.
|
|
Connection information: |
HTTP or UNC path, authentication method as well as user name and password, if required.
|
|
BITS behavior: |
If the Wait until the BITS download is complete option is enabled, the download starts and the client command waits until all files have been downloaded and subsequently starts the installation All other client commands are blocked during this time. If this option is not enabled, the download starts and the client command ends. Once the download is complete, the client command is automatically resumed and the installation continues. Other client commands are not blocked during the download.
The Upload files to the file repository option ensures that the data are also loaded into the file repository to prevent a server failure.
|
|
|
Upload the files to the ACMP file repository and access it from there or from the mobile repository.
|
|
Connection information: |
none
|
|
Behavior: |
If the client, in which the subsequent client command is executed, is a mobile terminal, the data are loaded from a mobile file repository (see Chapter Mobile File Repository). If this is not possible, an ACMP file repository is automatically accessed. if the client is not a mobile device, the ACMP file repository is accessed directly. A function to be selected determines if a device is a mobile terminal or not.
|
|
|
The files are already stored in a mobile file repository. If necessary, they be downloaded from there, from the file repository or from a BITS server.
|
|
Connection information: |
HTTP or UNC path, authentication method as well as user name and password, if required.
|
|
BITS behavior: |
If the Wait until BITS download is complete option is enabled, the download starts and the client command waits until all files have been downloaded and subsequently starts the installation All other client commands are blocked during this time.
If this option is not enabled, the download starts and the client command ends. Once the download is complete, the client command is automatically resumed and the installation continues. Other client commands are not blocked during the download.
|
|
For more information, see the Chapter The Mobile File Repository. |
||
Note: |
The BITS server uses simple UNC-/HTTP shares of a computer/server. |
Note: |
If the required files are in the file repository of a client command, the file repository can be manually set as the share and the appropriate client command project can be specified as the UNC path. The file repository of each client command can be retrieved with the ID in the subfolder File Repository\projects below the ACMP installation folder.
In this case, you can identify the share as \\Server\Share\ProjectID e.g.:
\\192.169.1.100\projects\{93EDD300-AA4C-4923-BD02-08C16C6759EE}
\\1-MAINSRV-XP\projects\%PROJECT_ID%
\\1-MAINSRV-XP\{93EDD300-AA4C-4923-BD02-08C16C6759EE}
|
In the next step a function (see Chapter Functions) must be seleected, by means of which the subsequent client command can determine if the client is a mobile device or not. A mobile terminal means, for example, the notebook of a sales representative. A function that queries the IP address of the notebook is conceivable. If the IP address is within a particular range (e.g. of a VPN network that links the notebook to the corporate network), the notebook is classified as mobile. However, it is entirely at your discretion you would like to define this function in detail.
In the next step, you have to enter information on a Denial of installation. The purpose of this function is to enable users to temporarily cancel an installation/uninstallation/repair process on the client. This is useful, for example, if the user is already running multiple programs and an additional installation would increase the machine's load so that the user will not be able to continue working.
To activate this mechanism, select the appropriate option. You can then specify how many times the user may refuse an installation/uninstallation/repair before the process is enforced automatically. In addition, you can specify an interval after which a new attempt to install/uninstall/repair is made.
For this mechanism to work properly, you must specify the username and password of an account that has local or domain-wide administrator rights.
The sixth step is used to specify additional options. Here you can specify if the required files should be compressed. Simply enter - if necessary - the file name. The compressed file must then be indicated with the file extension .zip . If the data are already on a server, you can indicate if the data are to be compressed and the name of the file. Only zip files can be used.
A dialog language can be selected for dialogs, which may be displayed to a user by the ACMP. Currently you have here the option to choose between German and English.
The option Allow user to park and unpark files serves to ensure that before installation/uninstallation/repair a user can select via a dialog if the software files are to be cached locally on the client. The files will be automatically deleted after use.
The option Show message if install/uninstall/repair successfully competes shows a simple standard success message if one of the three options was successful.
The option "Include "Set software installed" entry activates a client command function, which makes an entry in the client to ensure that the installed software can be detected by means of the License Management Center. Since some MSI and setup packages do not leave any registry entries by means of which they can be detected in th License Management Center, such an entry can be added afterwards with the ACMP with this option.
The option "Enqueue the software scanner after run" is scanned once again after installing the existing software.
In the next step, you have the option, to run the corresponding client before and after the actual installation, uninstallation or repair of the software. This is done by means of the two events, OnStartScript and OnEndScript.
While the client command assigned to the OnStartScript event is run before the installation, uninstallation or repair of the software, the client command assigned to the OnEndScript event is run afterwards. The client command that should be executed can be select with the appropriate button, thereafter, the client command ID as well as the name of the client command is entered in the dialog. To do so, a client command requires the status Released. In both events an additional line is available for entering parameters. In this way, variables that are used in the selected client command are pre-defined with appropriate values. The values are indicated in the format /v:VariableoftheClientCommand=Value; if several variables are entered, they have to be seperated by a blank space.
After defining the OnStartScript and the OnEndScript event, you can allow client command functions (see Chapter Functions) to run dependent on certain events. To this end, all defined functions are listed.
Define a function by means of the tabs, which will run after the installation, uninstallation and repair. In addition, you can specify one function, which is to be executed after the software files have been parked (cached) or unparked (deletion of the cached files).
To define a function, select the desired function below the corresponding event and enter any required parameters (see Variables). If the parent folder Available functions is selected, no function will be executed.
In the final instance, you will get a summary of all settings. Click Next to create the package. A status bar will be displayed during this process. After the package is created, you can choose whether you want to Finish the wizard or open the recently created client command in the editor.
Last change on 10.03.2014