The Action - Launch Java Application dialog box lets you configure a Java program to be executed on the managed device. You can also specify the specific requirements that a device must meet for the action to be executed on the device.
To access this dialog box in ZENworks Control Center, click the Bundles tab. Click the underlined link of a bundle in the Name column of the Bundles list, click the Actions tab, click one of the action set tabs (Distribute, Install, Launch, Repair, Uninstall, Terminate, or Preboot), click the Add drop-down list, then select an available action.
The following sections contains additional information:
The General page lets you configure a Java program to be executed on the managed device.
Specify the Java program name. For example, com.novell.TestProg.
Specify the program parameters.
Specify the path to the Java Runtime Executable (JRE).
Specify the JRE parameters.
Specify what happens after the Java application launches:
No wait: The next action in the list is immediately performed.
When launch action is complete: The next action in the list is performed after the launch action completes.
Wait for _ seconds: Wait the specified number of seconds before proceeding to the next action.
Terminate action if wait period exceeded: If you select the Wait for _ seconds option, this option is enabled. If the specified number of seconds is exceeded and the action is not successfully performed, the action is terminated.
Click More Options to specify the Java application’s Run As settings.
System: Runs the application as the system account (as a service).
Administrator: Runs the application as a dynamic administrator user. A dynamic administrator is an administrator account that is created on the fly to perform certain procedures, such as installing applications or running scripts. Using a dynamic administrator is helpful when installing applications (some MSI applications, for example) that cannot be installed in the system space. When you select this action, the dynamic administrator is created, it performs the required tasks, and then the account is deleted.
NOTE:Performing this action as dynamic administrator on a Windows domain controller fails because Microsoft does not allow the use of local administrator accounts on domain controllers.
User: The application runs using the logged-in user’s credentials. For example, the application has the same rights to the registry and the file system as the logged-in user.
The following options are available for Linux:
Root: The application runs only if the root user is logged in to the device.
User: The application runs using the logged-in user’s credentials. For example, the application has the same rights to the registry and the file system as the logged-in user.
Click More Options to specify the Java application’s working directory.
Specify the initial working directory for the application.
Specify the non-zero success codes that the executable returns. You can specify multiple success codes separated by commas.
If an executable returns non-zero success codes, you should specify these non-zero success codes while launching the action. For example, explorer.exe in Windows returns a success code of 1. To successfully launch the Explorer application, you should add 1 as the success code while launching the action.
If you leave this field blank, zero will be considered as the success code. Specify the Success Return Code as * to enable any non-zero code returned by a script to be treated as success.
Click More Options to specify the Java application’s priority.
Specify the priority of the process that runs the application. This option lets you configure how much of the CPU usage the application process consumes. Select from the following priorities: Real Time, High, Above Normal, Normal, Below Normal, and Low.
On Windows 2000, Windows XP, Windows Vista, or Windows 7 device, the application executable can run in either the “user” space or the “system” space. By default, the Run normal option is selected, which causes the application to run in the “user” space and inherit the same workstation security level as the logged-in user.
If the logged-in user's security level does not provide sufficient rights and file access to run the application, you can configure the application to run in the “system” space or as a dynamic administrator, as described below:
Run as logged in user: The MSI application inherits the logged-in user’s credentials. For example, the application has the same rights to the registry and the file system as the logged-in user.
Select the application’s display mode: Normal, Minimized, Maximized, or Hidden. In Hidden mode, the application runs normally without a user interface available. This is useful if you want the application to process something, then go away without user intervention.
Select Grant administrator privilege to user during installation to provide administrator privileges to the logged-in user. However, providing administrator privileges to a user might pose security risks. If this option is selected, the user on the managed device is prompted to enter the password when the MSI is installed on the device. To install the MSI, the user must log in to the device with a user account that has a password configured.
NOTE:On a Vista device, if the administrator is logged in to the device and the Grant administrator privilege to user during installation is selected, the action is performed in the quiet mode.
Run as secure system user (Don't allow system to interact with desktop): The application is run under the Local System user and inherits Administrator-level credentials. For example, the application has full rights to the registry and the file system. Because the security level is set to Secure, the application's interface is not displayed to the user and the application is only visible in the Task Manager. This option is useful when running applications that require full access to the workstation but require no user intervention.
Run as dynamic administrator: A dynamic administrator is an administrator account that is locally created on the fly to perform certain procedures, such as installing applications. Using a dynamic administrator is helpful when installing applications (some MSI applications, for example) that cannot be installed in the system space. Because the dynamic administrator does not have access to the network, the network shares on which the MSI is available must be made publicly accessible. When you select this action, the dynamic administrator is created, it performs the required tasks, and then the account is deleted.
You cannot use mapped network drives to specify files and directories because dynamic administrators do not have access to mapped drives.
Select credential for network access: If the file or directory specified in the action are a part of the UNC path or network share that can be accessed only through credentials, then browse through the credential vault to select a credential that has access to the network.
For more information on Credential Vault and adding credential to the Credential Vault, see Adding a Credential
in the ZENworks Control Center Reference.
NOTE:Performing this action as a dynamic administrator on a Windows domain controller fails because Microsoft does not allow the use of local administrator accounts on domain controllers.
The Requirements page lets you define specific requirements that a device must meet for the action to be enforced on it. For information about the requirements, see Requirements.