This module allows you to launch applications on your client machines during or after Script Start execution.
Filter:
Select the name of the filter you want assigned to this configuration element.
Filespec:
Enter the full path to the executable. Surrounding quotes are automatically added to the filespec.
NOTE: Drives mapped by the Drive Mapping configuration module are not available.
Arguments:
Enter any arguments required by the executable. Arguments are not automatically quoted.
Timing:
Choose whether your application should launch during or after Script Start execution.
Hide Progress During Execution:
Selecting this option will hide the Script Start progress display while your application executes. This option is not available if you enable Run Asynchronously.
Run Asynchronously:
By default, Script Start waits for your application to terminate prior to continuing. When this option is selected, Script Start will not wait for your application to terminate.
Schedule:
Choose the schedule your application should execute on.
Frequency:
Choose the frequency your application should execute on.
UID:
The UID is a unique identifier that is automatically generated by Script Start. Normally, the UID does not need to be changed. Changing the UID will reset the execution history associated with the application. For example, if you chose a frequency of One Time (User) and you want the application to run a second time, changing the UID will cause the application to execute again. This option does not apply if you choose a Frequency of Every Logon.
Tracking Path:
The Tracking Path designates the UNC name of the network share Script Start will use to store execution history. When you create the share, you will need to grant write permission to all users using Script Start. If this share is unavailable or does not have write permission, Script Start will not execute the application. This option does not apply if you choose a Frequency of Every Logon.
NOTE: Inside the share Script Start will create a folder named after the UID of the application. Therefore, it is safe to use the same share as the Tracking Path for multiple applications. If you wish to reset the execution history for an application, you can delete the folder associated with the application's UID.
Example:
Filter: Global Settings
Filespec: C:\Program Files\Adobe\Acrobat 6.0\Acrobat\Acrobat.exe
Arguments: "\\ATLFS01\public\Employee Handbook.pdf"
Timing: After Script Execution
Run Asynchronously: Enabled
Schedule: Everyday
Frequency: One Time (User)
UID: gtnj8nvrp4oe38m
Tracking Path: \\ATLFS02\apptrack$$
The above example will launch Adobe Acrobat and open the file Employee Handbook.pdf one time for each user. Since Run Asynchronously has been enabled, Script Start will not wait for the user to close the Acrobat reader. The Arguments passed to the Filespec have been surrounded with quotes as Employee Handbook.pdf contains a space.
NOTE: The share name used for the Tracking Path is \\ATLFS02\apptrack$. Since $ is a KiXtart reserved character, it has been escaped with $$.
|