The Launch Item gadget displays the applications from purchased packages. and launches the applications. It has the following configuration settings:
Display Name: Specifies the name that will be used when displaying the gadget on the portal page.
Window Height: Specifies the height of the window that lists the applications. If the application list is too long to fit in the window, the window will include a vertical scroll bar. The default setting is 150.
ZENworks Host Server: Specifies the IP address or DNS host name of the network server where ZENworks for Desktops is installed. This needs to be the same ZENworks server where you installed the OnDemand Services Usage Client files. It is also the server from which OnDemand Services will install the Novell Application LauncherTM files if the files do not already reside on a workstation where a desktop application is launched.
UsageServer: Specifies the IP address or DNS host name of the network server where the UsageServer process is installed.
Display Thin-Client Applications: Specifies whether or not to display thin-client applications in the list. These are applications distributed through Novell DeFrameTM. The default is TRUE.
Display Web Content: Specifies whether or not to display Web applications (or Web content) in the list. The default is TRUE.
Display Workstation Applications: Specifies whether or not to display desktop applications in the list. These are applications distributed through ZENworks for Desktops. The default is FALSE.
RDP: Specifies whether or not a Windows Terminal Services RDP session can be used when launching a thin-client application from a terminal server. The default is TRUE.
This setting applies only if the user is not already enabled as a DeFrame user in eDirectory (User object > DeFrame tab > DeFrame Properties page > DeFrame User setting). If the user is already a DeFrame user, the user's RDP Client setting in eDirectory is used (User object > DeFrame tab > DeFrame Properties page). Otherwise, the user is enabled as a DeFrame user and the RDP Client setting is populated from the value set here.
ICA: Specifies whether or not a Citrix MetaFrame ICA session can be used when launching a thin-client application from a terminal server. The default is TRUE.
This setting applies only if the user is not already enabled as a DeFrame user in eDirectory (User object > DeFrame tab > DeFrame Properties page > DeFrame User setting). If the user is already a DeFrame user, the user's ICA Client setting in eDirectory is used (User object > DeFrame tab > DeFrame Properties page). Otherwise, the user is enabled as a DeFrame user and the ICA Client setting is populated from the value set here.
DDU: Specifies whether or not you want DeFrame to dynamically create the user's account on a terminal server each time he or she launches an application from the server. DeFrame will create the user's account, using his or her eDirectory username, when the user starts the application. After the user exits the application, DeFrame deletes the user account.
This setting applies only if the user is not already enabled as a DeFrame user in eDirectory (User object > DeFrame tab > DeFrame Properties page > DeFrame User setting). If the user is already a DeFrame user, the user's Dynamic User setting in eDirectory is used (User object > DeFrame tab > DeFrame Properties page). Otherwise, the user is enabled as a DeFrame user and the Dynamic User setting is populated from the value set here.
Store Roaming Profiles -- Registry: This setting requires the DDU setting to be TRUE. It specifies whether or not a roaming profile will be used to store the user's Windows registry settings such as property settings for folders and preference settings for applications. Saving the registry settings ensures that any application modifications that are stored in the registry will persist from one session to another. If a roaming profile is not used, the registry settings will be lost when the user exits the application and his or her user account is removed.
The default is FALSE. If you set this to TRUE, you need to specify the profile storage location in the Profile Path setting. Individual user folders will be created under the profile storage location and the registry settings saved as username.dfr files (for example, \profiles\jsmith\jsmith.dfr).
This setting applies only if the user is not already enabled as a DeFrame user in eDirectory (User object > DeFrame tab > DeFrame Properties page > DeFrame User setting). If the user is already a DeFrame user, the user's Store Roaming Profiles: Registry setting in eDirectory is used (User object > DeFrame tab > DeFrame Properties page). Otherwise, the user is enabled as a DeFrame user and the Store Roaming Profiles: Registry setting is populated from the value set here.
Store Roaming Profiles -- Files: This setting requires the DDU setting to be TRUE. It specifies whether or not a roaming profile will be used to store the folders and files contained in the user's home directory (c:\documents and settings\username). Saving the user's home directory ensures that any application files (such as documents) saved to the user's home directory will persist from one session to the next. If a roaming profile is not used, the folders and files will be lost when the user exits the application and his or her account is removed.
The default is FALSE. If you set this to TRUE, you need to specify the profile storage location in the Profile Path setting. Individual user folders will be created under the profile storage location and the folders and files saved to that directory (for example, \profiles\jsmith\folders and files).
This setting applies only if the user is not already enabled as a DeFrame user in eDirectory (User object > DeFrame tab > DeFrame Properties page > DeFrame User setting). If the user is already a DeFrame user, the user's Store Roaming Profiles: Files setting in eDirectory is used (User object > DeFrame tab > DeFrame Properties page). Otherwise, the user is enabled as a DeFrame user and the Store Roaming Profiles: Files setting is populated from the value set here.
Profile Path: This setting is required if you set either of the Store Roaming Profiles settings to TRUE. It specifies the location where you want to store the roaming profiles.
You can enter a local drive path or a network drive path. If you enter a local drive path (for example, c:\profiles), the user's profile will be created on each terminal server's local drive. This means the user might not have consistent settings and files from one server to another.
If you enter a network drive path, the same profile will be used regardless of which terminal server the user logs in to. The terminal server's DeFrame Access Control Service, logged in to eDirectory through the DeFrame PASS_ADMIN user, creates the profile on the network drive. The PASS_ADMIN user has Admin-equivalent rights to the tree where it resides, so the DeFrame Access Control Service can create the profile location on any server in the tree. Use a valid UNC path (\\server\vol\directory) to specify the profile location.
You can also include the Windows %USERNAME% variable in the path as well. For example, if you want the user's profile saved to his or her user directory on a network server, you could specify \\server1\vol1\%USERNAME%. Because DeFrame always creates a user profile directory in the specified location, this would result in the profile being saved to a \\server1\vol1\username\username directory.
This setting overrides the user's Roaming Profile Path setting in eDirectory (User object > DeFrame tab > DeFrame Properties page) unless the setting is left blank. If the setting is left blank, the eDirectory setting is used.
Display Large Icons: Specifies whether application icons are displayed in the Windows small icon format or in large icon format. The default is FALSE, which means small icon format is used.
Number of Columns: This setting applies only if Display Large Icons is set to TRUE. It specifies the number of columns to use when displaying the icons. The default is 4.
Secure Sensitive Pages: Specifies whether or not the user's Web browser uses the Secure Socket Layer (SSL) protocol when transferring sensitive information to and from the Web server. The default is FALSE. If you set it to TRUE, make sure the Web server supports SSL connections.
iFolder Server Object: If you are using Novell iFolderTM to enable users to save files from thin-client applications to network storage locations, this setting specifies the iFolder servers you want available to users. Use typeless, leading dot delimited notation to specify the iFolder Server object's distinguished name (for example, .ifolderserver.services.novell). You can click New Value to specify more than one iFolder server.
This setting applies only if iFolder servers are not already associated with the user (User object > DeFrame tab > iFolder Servers page). If the user is already associated with iFolder servers, those servers are used.