User

This dialog box lists the configuration settings that apply when Novell^® Application Launcher^TM is accessing Novell eDirectory^TM on behalf of a logged-in user. These are general Application Launcher settings that apply regardless of the view (Application Window, Application Explorer, or Application Browser) being used.

IMPORTANT: Each setting has an Unset value. This value instructs Application Launcher to use the setting inherited from the parent container. If the setting is not specified in any parent container, the default value is used. The default value for each setting is indicated in the descriptions below.

Allow Users to Exit
Specify whether or not to allow the user to exit Application Launcher. If you allow the user to exit, you should let him or her know how to start Application Launcher again.

The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

Enable [All] Folder
Specify whether or not the user can see the [All] applications folder in Application Launcher. The [All] applications folder displays all applications the user has access to, regardless of the application's eDirectory tree or folder.

The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

Enable Manual Refresh
By default, when Application Launcher starts it reads the eDirectory information for all applications associated with the user. If an application's eDirectory information changes after Application Launcher starts, Application Launcher must refresh its information before the changes show up on the user's workstation.

Specify whether or not the user can manually refresh Application Launcher to distribute any changes made to application information since the last time Application Launcher read eDirectory. The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

The Enable Manual Refresh option and Enable Timed Refresh option (discussed below) are not connected in any way except that they both control refresh. One option does not need to be selected for the other to work.

Enable Personal Folders
Specify whether or not the user can create Application Launcher folders and move the icons in them as he or she sees fit. Only Application object icons (or associated application icons or shortcuts) can be moved into personal folders. Use caution when offering the option if you want to exert more control and thus reduce support calls.

The Application Browser displays personal folders and the Application objects that reside within the folders. However, when using the Application Browser, users cannot create or delete personal folders, or add or remove applications from personal folders.

The setting values are Yes, No, and Unset. The default value (No) is used if you select Unset and no parent container includes a customized setting.

Enable Timed Refresh (User)
By default, when Application Launcher starts it reads the eDirectory information for all applications associated with the user. If an application's eDirectory information changes after Application Launcher starts, Application Launcher must refresh its information before the changes show up on the user's workstation.

Specify whether or not Application Launcher automatically refreshes applications so the user doesn't need to manually refresh them. The setting values are Yes, No, and Unset. The default value (No) is used if you select Unset and no parent container includes a customized setting. If you set the option to Yes, the Set Refresh Frequency option (discussed below) determines how often Application Launcher refreshes applications.

Read Groups for Applications (User)
Specify whether or not you want Application Launcher to read Group objects to see if the user has been associated with any applications through membership in a group. Although groups are a convenient way of indirectly associating the user with applications, requiring Application Launcher to read Group objects can also decrease performance.

The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

Set Application Inheritance Level (User)
Specify how many parent containers Application Launcher should search for applications associated with the user.

The setting values are -1, 1 through 999, and Unset. Entering -1 instructs Application Launcher to search to the root of the eDirectory tree. The default value (1) is used if you select Unset and no parent container includes a customized setting.

Set Refresh Frequency (User)
This option applies only if Application Launcher is configured to perform a timed refresh (see Enable Timed Refresh above).

Specify how often you want Application Launcher to search eDirectory for new or changed Application objects associated with the user. A short timed refresh interval is very useful in situations where you want changes to refresh quickly. However, a short timed refresh interval can cause higher network traffic.

The setting values are 0 through 999,999,999 (seconds) and Unset. The default value (43200, which equates to 12 hours) is used if you select Unset and no parent container includes a customized setting.

Set the Random Refresh Spread
By default, when Application Launcher starts it immediately reads eDirectory to get information about the applications associated with the user. You can use this option to instruct Application Launcher to retrieve its application information from the user's cache directory during startup and then refresh that information from eDirectory at a later time. This allows you to reduce network traffic (generated by Application Launcher reading eDirectory) during peak times such as the morning login period.

The setting values are Custom and Unset. If you select Custom, specify a range from which Application Launcher can determine the initial refresh time. For example, if you specify 3600 seconds (1 hour), Application Launcher randomly selects a number between 0 and 3600 and does the initial refresh that long after starting. Entering 0 in the range field causes Application Launcher to refresh immediately upon starting.

If you select Unset and no parent container includes a customized setting, the default value (0) is used, which means that Application Launcher will refresh at startup.

Specify E-Mail Attribute
Specify the eDirectory attribute you want to use to display e-mail names on the Help Contacts tab of the Application object's Properties dialog box. If the user has problems with applications, he or she can contact people by e-mail to get help. The e-mail name that appears is pulled from the eDirectory attribute you specify here.

The setting values include all the eDirectory attributes and Unset. The default value (Internet E-mail Address) is used if you select Unset and no parent container includes a customized setting.

Users must have the eDirectory rights required to read the selected attribute for all users defined as contacts.

Unassociated Days to Uninstall (User)
Specify the number of days after which you want Application Launcher to uninstall an application when the user has been unassociated with the application.

The setting values are -1 through 730 and Unset. Specify 0 if you want the application to be uninstalled as soon as the user is no longer associated with it. You should use 0 only for users who are located in a high-availability environment such as a LAN environment. You should not use this setting for users whose workstations are using a wireless network connection or a LAN environment that is unreliable. Using 0 as the setting in either of these environments can result in applications being uninstalled if the workstation loses its network connection during an application refresh; the best practice is to use the -1 setting or a setting of 1 or greater.

Specify -1 if you don't want the application uninstalled when unassociated with the user. The default value (-1) is used if you select Unset and no parent container includes a customized setting.

Auto-Start Application Launcher
This setting applies only to pre-ZENworks 6.5 versions of Application Launcher. Beginning with ZENworks^® 6.5, this setting is replaced by the ability to designate a startup option in the ZENworks Desktop Management Agent installation program.

If you have pre-ZENworks 6.5 versions of Application Launcher, specify whether or not you want Application Launcher to be included in the user's Startup folder so that it is automatically started when the user logs on to the Windows* workstation. When Application Launcher starts, it displays the same view (Application Window or Application Explorer) that was being used at the time it was added to the Startup folder.

The setting values are Yes, No, and Unset. The default value (No) is used if you select Unset and no parent container includes a customized setting.

Enable Reading from Removable Cache
Specify whether or not you want to enable Application Launcher's ability to read information from the cache directory on removable media such as a CD, Jaz*, or Zip* drive.

If you set this option to No, you disable a user's ability to launch applications or install applications from removable media only. Application Launcher continues to read the cache on the local hard drive.

The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

Enable Writing to the Cache
Specify whether or not you want to enable Application Launcher's ability to write information to the cache directory.

The primary purpose of the cache directory is to enable users to work offline, disconnected from eDirectory. Setting this option to No disables the local cache, forcing users to be connected to eDirectory or a removable cache in order to access applications. To ensure that users don't manually go offline, the Work Offline feature in Application Launcher is also disabled.

The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

Enable the Checkpoint Restart Postpone Button
Distribution of a large application across a slow link can require a significant amount of time. Specify whether you want Application Launcher to display a Postpone button that enables the user to postpone the distribution of an application to his or her workstation. If you enable the Postpone button, it is only displayed when Application Launcher detects that the user's workstation is running in remote mode (see Configure Remote Access Detection Method below).

The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

Always Evaluate Referrals
Specify whether you want Application Launcher, when making a call to eDirectory, to evaluate the location of the eDirectory replicas and use the most accessible one at the time, or to force all eDirectory calls to go the first eDirectory replica found.

The setting values are Yes, No, and Unset. The default value (No) forces all eDirectory calls to the same replica and is used if you select Unset and no parent container includes a customized setting.

Enable Automatic Icon Cleanup
This setting applies only when Application Launcher is running on a terminal server (Microsoft* Windows Terminal Server or Citrix* MetaFrame*).

Specify whether or not you want Application Launcher, when exited, to remove application icons from the user's terminal server session desktop. In general, you should set this option to Yes to have Application Launcher clean up. However, if you have multiple terminal server users who log in with the same username to run applications, you should disable this option. Otherwise, when one user exits Application Launcher, the application icons disappear from all users' terminal server session desktops.

The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

Configure Remote Access Detection Method
If Application Launcher detects an active dial-up connection when it starts, it starts in remote mode. There are other times, besides when a dial-up connection is active, that you might want Application Launcher to start in remote mode. You can use this option to specify how Application Launcher detects whether it should start in local or remote mode. The setting values are:

User Will Always Be Local: Application Launcher functions as if the user is local.
User Will Always Be Remote: Application Launcher functions as if the user is remote.
Prompt: Application Launcher prompts the user to select local or remote.
Auto Detect Using Max Interface Speed: Application Launcher detects the maximum speed of the network interface card and determines from that speed whether or not the user is local or remote. If you select this option, you must establish the connection speed (threshold) that determines local or remote status.
Detect Using Network ID: Application Launcher uses the workstation's network ID (also known as the network address) to establish whether or not the user is local or remote.

If you select this option, you must specify the network ID that is used to establish whether the user is local or remote. To determine the network ID, take the bit-wise logical AND comparison of the 32-bit IP address and 32-bit subnet mask, then convert the resulting 32-bit network ID to dotted decimal notation.. In an AND comparison, the result of the two bits being compared is true (1) only when both bits are 1; otherwise, the result is false (0). For example:

10000001 00111000 10111101 00101001 (binary of 129.56.189.41 IP address)
11111111 11111111 11110000 00000000 (binary of 255.255.240.0 subnet mask)

10000001 00111000 10110000 00000000 (binary of 129.56.176.0 network ID)

If you want workstations whose network IDs match the specified network ID to be considered local, select Network ID Is Equal to This Network ID.

If you want workstations whose network IDs do not match the specified network ID to be considered local, select Network ID Is Not Equal to This Network ID.
Unset: The default value (User Will Always Be Local) is used if you select Unset and no parent container includes a customized setting.

Bring All Popup Windows to the Front
Specify whether or not you want Application Launcher to ensure that a launched application appears in front of any other currently-opened desktop windows. The setting values are Yes, No, and Unset. The default value (Yes) is used if you select Unset and no parent container includes a customized setting.

This setting has no affect on Windows 98 and Windows NT workstations because the default system configuration already forces pop-up windows to the front. However, the default system setting for Windows 2000 and Windows XP causes all pop-up windows to appear behind the current application's active window. With Application Launcher, this caused the launched application to appear behind the Application Launcher window. Enabling this option changes the Windows registry setting so that all pop-up windows, even the ones not generated by launching an application, will appear as the front window. This is similar to using the Microsoft Tweak UI utility (tweakui.exe) to change the registry setting.

Enable Middle Tier Login
Specify whether or not you want to add an Application Launcher menu item to enable the user to log in through a Middle Tier Server. The setting values are Yes, No, and Unset. The default setting (Yes) is used if you select Unset and no parent container includes a customized setting.

Attempt to Go Online During Refresh
Specify whether or not you want the logged-in user’s workstation to attempt to go online during a refresh. The default setting is Yes.

This setting helps avoid long refresh times if the workstation is not connected or is connected over a slow link.

Enable BITS
Specify whether or not you want Application Launcher to be able to use the Microsoft Background Intelligent Service (BITS) to transfer a user's applications to the workstation. Unlike Application Launcher's standard transfer method which competes with other applications for available network bandwidth, BITS uses idle network bandwidth to transfer files, increasing or decreasing the rate at which files are transferred based on the amount of idle network bandwidth available. For example, if a network application begins to consume more bandwidth, BITS decreases its transfer rate.

The setting values are Yes, No, and Unset. The default setting (No) is used if you select Unset and no parent container includes a customized setting.

For additional configuration tasks you must complete to enable Application Launcher to use BITS, see Using BITS.

Allow User to Override BITS Transfer
Because BITS uses idle network bandwidth to transfer applications, an application might not be available when a user attempts to launch it. Specify the action you want to occur in this case:

Yes (default): Causes Application Launcher to cancel the BITS job and immediately transfer the application itself.
No: Causes BITS to maintain control of the transfer; the user is unable to launch the application until the transfer is complete.
Prompt: Prompts the user as to whether or not to interrupt the BITS transfer and have Application Launcher immediately download the application.

ZENworks Desktop Management Online Documentation

A trademark symbol (^®, ^TM, etc.) denotes a Novell trademark. An asterisk denotes a third-party trademark. For more information, see Legal Notices.