39.1 Disconnected Mode Overview
Application Launcher runs in disconnected mode when neither the user nor the workstation is authenticated to eDirectory. User authentication occurs whenever the user logs into eDirectory through the Novell Client™ or the ZENworks® Middle Tier Server. Workstation authentication occurs only if 1) the workstation has been imported as a Workstation eDirectory object and 2) Workstation Manager is installed and can perform the authentication.
Disconnected Mode Indicators
There are several ways you can tell when Application Launcher is running in disconnected mode:
-
File menu: The File menu in the Application Window, Application Explorer window, and Application Browser window includes a option. When Application Launcher is in disconnected mode, is displayed.
Figure 39-1 Application Explorer Window Showing the Work Online Option Available on the File Menu
-
Application Explorer: The Application Explorer desktop icon changes. The icon on the left below indicates connected mode. The icon on the right indicates disconnected mode.
In addition, the Application Explorer system tray icon changes. The icon on the left below indicates connected mode. The icon on the right indicates disconnected mode.
The NAL Cache
In disconnected mode, Application Launcher reads application information from the NAL cache on the workstation's local drive. Any applications that have been distributed or cached to the workstation continue to be displayed on the workstation. The NAL cache is a critical component of disconnected mode. If you have not already done so, you should review the information in Section 24.0, Novell Application Launcher: Managing the Cache.
Work Offline
Application Launcher includes a Work Offline option that lets users force Application Launcher into disconnected mode while remaining authenticated to eDirectory. Work Offline causes Application Launcher to start reading the workstation's NAL cache directory for application information rather than eDirectory. The corresponding Work Online option enables users to switch back to connected mode.
Disconnected Applications
When you create an Application object, the application is automatically configured as being disconnectable. After a disconnectable application is distributed or force cached to a workstation, Application Launcher continues to display the Application object icon even after the user has disconnected from eDirectory. When the user double-clicks the Application object icon, Application Launcher launches the application.
If an application is not marked disconnectable, Application Launcher does not display the Application object icon when the user disconnects from eDirectory.
Only applications that can run on a disconnected workstation should be configured as disconnectable. Applications that rely on network resources should not be configured as disconnectable if the network resources is not available. This includes:
-
Applications that access a network database
-
Client/server applications
-
Applications that depend on network drive mappings or print captures
-
Applications that use eDirectory macros (other than %CN%) in any of the Application object property fields
-
Applications that require a persistent connection to the network