The Identification tab includes the following pages to help you configure how the Application object is displayed to users:
The Package Information property page, shown below, displays information about the Microsoft* Windows* Installer package file (.MSI file) associated with the application. This page is for informational purposes only; you cannot use this page to modify the package's information.
Displays the location of the .MSI file being used by the Application object.
Displays the version of the .MSI file.
Displays the creator of the .MSI file.
Displays the locale defined in the .MSI file.
Displays the Web location to visit for information and help about the application.
The Icon property page, shown below, determines the Application object's icon that Novell® Application LauncherTM /Explorer displays on a workstation. You can give the application icon a title, select the graphic to use for the icon, and give the icon a display order and force run priority. You can determine whether or not Application Launcher/Explorer should continue to display the Application object on the workstation when the user has disconnected from NDS®.
Enter the text you want to appear as the title for the Application object's icon wherever the icon is displayed. If necessary, you can use the Description page (Identification tab) for longer descriptions of the application.
Select the icon you want to appear wherever the Application object's icon is displayed. If you do not specify an icon, a default Application object icon is used.
Check this option to mark the application as being able to be run on a workstation that is disconnected from NDS.
IMPORTANT: The application must be distributed to the workstation before the user can run it in disconnected mode, or the application must be cached on the workstation. You can force the application to be distributed on the workstation by selecting the Force Run characteristic (Associations page). You can force the application to be cached to the workstation by selecting the Force Cache characteristic (Associations page).
This option applies only if the application and at least one other application are using the Force Run option (Associations page).
Check this option to force the application to wait until the application before it terminates. The application order is defined in the Order Icon Display (Also Determines Force Run Priority) field. Reboots will be queued until the final application has terminated.
This option dictates the order in which applications set as Force Run will be started. Select this option to enable it, and then use the Order list to select the application's position in the Force Run order.
IMPORTANT: Despite the field title (Order Icon Display), this option does not determine the order in which Application Launcher/Explorer displays icons. Icon order is determined by the user through the View > Arrange Icon setting in Application Launcher/Explorer.
You control the order in which the application is started by entering a numeric value in the Order box. A value of zero gives the application the highest priority. The maximum value is 999. For example, if you want this application to start after two other applications that have been given the order of 0 and 1, you would enter 2 in the Order box.
Application Launcher/Explorer will run the application without waiting for the previously started application to terminate, unless the Wait on Force Run option is enabled.
This option displays a progress bar to users anytime an application is distributed to or removed from their workstations. Turn off this option if you are distributing only a small change, such as a registry modification. Turn on this option if you are distributing or removing a large application and want to give the user an idea of how long the process will take.
This option appears only if the Application object uses a Microsoft Windows Installer (.MSI) package. During distribution of a .MSI Application object, Application Launcher/Explorer launches Windows Installer to install the application. As a result, rather than showing the standard Application Launcher/Explorer installation progress bar, Windows Installer uses the installation user interface established for the .MSI package. You can use the following settings to determine the amount of user interface the Windows Installer will display during installation.
Application Launcher/Explorer passes the selected setting to Windows Installer as a startup parameter. For more information about these settings, see the Microsoft Windows Installer documentation.
The Description property page, shown below, provides users more complete information about the Application object than the application icon title allows.
If you have enabled the Prompt User Before Distribution option (Distribution Options > Options page), users will see this description when Application Launcher/Explorer first distributes the application to them. They can also view an Application object's properties to see the description. To display the properties, right-click the Application object (on the workstation) > click Properties.
The Folders property page, shown below, lets you specify the folders where you want Application Launcher/Explorer to place the application when distributing it to a workstation.
You can add the application to two different types of folders: a custom folder and a linked folder.
A custom folder is a folder created specifically for the Application object. No other Application objects can be included in the folder. Custom folders support folders within folders, which means that you can create a custom folder structure. For example, although you could not have Calculator and Notepad in the same custom folder, you could create two subfolders within the same custom folder and place the two programs in the two subfolders (in otherwords, WINAPPS\CALCULATOR\CALC.EXE and WINAPPS\ NOTEPAD\NOTEPAD.EXE).
A linked folder is simply an association to an existing Application Folder object. The Application Folder object must already exist in NDS. If the Application Folder object includes multiple folders (a folder structure) you can add the application to any folder in the structure.
HINT: If you plan to create a complex folder structure for the applications you distribute, we recommend that you use an Application Folder object and then link Application objects to the Application Folder object. An Application Folder object requires you to define the folder structure one time only, whereas custom folders must be defined for each Application object. If you choose to use custom folders for your folder structure, make sure you use the same folder names when defining the custom folder structure for each Application object. Any variation will cause Application Launcher/Explorer to create different custom folder structures.
The Folders list displays the custom folders and linked folders (Application Folder objects) that the application has been added to. Application Launcher/Explorer will create (if necessary) the listed folders when distributing the application to the workstation.
Click Add to add a custom folder or a linked folder to the Folders list. If you want the application to appear in multiple folders, add each folder to the list.
When you add a custom folder, it appears in the list with New Folder as its title. You can select the folder in the list and use the Modify Selected Folder box to change the folder's name or to add subfolders to it (see Modify Selected Folders below).
Select a folder in the folder list > click Delete to remove the folder from the list.
The Modify Selected Folder box lets you modify name and structure information for the folder that is selected in the Folders list. You can modify information for custom folders and linked folders. However, after you modify a linked folder's information, it is converted to a custom folder.
Select the folder in the folder tree > click Add to add a subfolder to the folder. After you add a subfolder and Application Launcher/Explorer refreshes, users will see the application in the subfolder rather than in the folder.
Select the folder in the folder tree > click Delete to delete the folder.
Select the folder in the folder tree > click Modify to change the name of the folder.
If you want to add the application to a new subfolder of an existing folder, enter existing_folder_name\new_subfolder_name.
Application Launcher/Explorer can display folders on the Windows Start menu and in the Application Launcher/Explorer window (provided these locations are enabled on the Application object's Associations page). Select a folder in the Folders list > check the boxes for the locations where you want to use the folder.
If you don't select either location, Application Launcher/Explorer will still display the Application object on the Start menu and in the Application Launcher/Explorer window (if these locations are enabled on the Associations page), but the object will not appear in the folders you've defined.
The Contacts property page, shown below, lists the names, e-mail addresses, and phone numbers of the application's support staff. Users can access this information through the Application object's properties. To display the properties, right-click the Application object (on the workstation) > click Properties > click Help Contacts.
You can tailor the information to direct users to the support staff at their locations. If you enter the support contact's e-mail address, users will be able to send an e-mail message directly from the Help Contacts page of the Properties dialog box.
NOTE: Users must have the NDS rights required to read the E-Mail Address (MailboxID) and Telephone (Telephone Number) attributes of the users defined as contacts.
The Administrator Notes property page, shown below, lets you record notes for yourself or other administrators. For example, you could remind yourself about special settings for an application. Or, if you have several administrators, you could write a history of upgrades and file changes.
