ZfD 4 introduces the following new features for Application Management:
Novell Application LauncherTM no longer has a dependency on the Novell Client. If a user's workstation has the Novell Client installed, Application Launcher will use the Client to access Novell eDirectoryTM and NetWare® servers. If not, access to eDirectory can be provided through the ZfD Management Agent (installed on the user's workstation) and the ZfD Middle Tier Server (installed on a network server). For more information, see Understanding Novell Application Launcher Components in Application Management in the ZENworks for Desktops 4 Administration Guide.
Terminology for Application Launcher has been changed to alleviate confusion when referring to different views that can be used with Application Launcher, and a new Web browser view has been added.
Novell Application Launcher or Application Launcher refers to the core application that must run on a user's workstation in order to distribute applications to the user.
Application Launcher includes three views that the user can run to display and launch distributed applications: 1) the Application Window, which is the standalone window that was previously referred to as Application Launcher or the Application Launcher window, 2) Application Explorer, which is the standalone window plus the Start menu, desktop, task bar, and system tray integration, and 3) a new Web browser view, the Application Browser, that enables distributed applications to be displayed and launched from a Web browser.
The ZfD Management Agent installation program installs the Novell Application Launcher files to the user's workstation and places an Application Window shortcut and Application Explorer shortcut on the Start menu (Start > Programs > ZENworks for Desktops 4). It also places an Application Browser button on the Web browser's standard button bar.
The Novell Application Launcher Web installation program, which can be used in place of the ZfD Management Agent installation program, enables users to install Novell Application Launcher (NAL) from a Web server. When Application Launcher is installed this way, only user-associated applications are supported because Workstation Manager and the Workstation Helper are not installed. In addition, only the Application Explorer and Application Browser views are available.
Because the application launcher service is not installed, the user needs local administrative rights to install or run NAL if the installation is completed using this method.
Novell Application Launcher now supports three modes: local, remote, and disconnected.
Local: Used when Application Launcher is connected to eDirectory through a fast connection (for example, a LAN connection).
Remote: Used when Application Launcher is connected to eDirectory through a slow connection (for example, a modem connection).
Disconnected: Used when Application Launcher does not have access to eDirectory (or when a user chooses to work offline). All directory information is retrieved from the workstation's local cache.
Checkpoint Restart provides users with a time estimate of how long it will take to download a standard application during distribution and enables users to postpone an in-progress download. When a user resumes a postponed download, Application Launcher resumes the download at the point it left off rather than starting over at the beginning. For more information, see Supporting Remote Users in Application Management in the ZENworks for Desktops 4 Administration Guide.
Remote Alternate Application enables you to specify an alternate application to use when a user is in remote mode rather than local mode. For example, when a user is accessing an application while in local mode, you might want the application run from a network server installation. However, when the user is accessing the application while in remote mode, you might want it run through a terminal server. You would accomplish this by specifying the terminal server version of the application as the remote alternate application for the network server installation version. For more information, see Supporting Remote Users in Application Management in the ZENworks for Desktops 4 Administration Guide.
Application Dependencies lets you establish a list of applications that must be installed before an application can be distributed. For example, assume that Application A requires Application B and Application C to be installed on a workstation before it will run. You can create a dependency list for Application A that includes applications B and C. During distribution of Application A, if either Application B or Application C are not installed, Application Launcher will install them as part of the Application A distribution process. For more information, see Configuring Application Fault Tolerance, Load Balancing, and Site Lists in Application Management in the ZENworks for Desktops 4 Administration Guide.
Application Launcher can generate event reports (install, uninstall, launch, cache, and so forth) in XML format and send the reports via standard HTTP or HTTPS protocol to a specified target URL. ZfD includes a Java* servlet, called the Application Management Reporting servlet, which can receive the XML reports, parse the XML data into an SQL query, locate the appropriate ZENworks Database object in eDirectory, and submit the SQL query to the database. If necessary, you can also create your own Java servlet rather than use the Application Management Reporting servlet. For more information, see Reporting Application Events in Application Management in the ZENworks for Desktops 4 Administration Guide.
The Application object for an MSI application now lets you define patches you want applied during the distribution process. It also lets you specify the actions (reinstall all files, reinstall old files, and so forth) you want to occur when a user verifies (repairs) an MSI application. For more information, see Application Object Settings in Application Management in the ZENworks for Desktops 4 Administration Guide.
When Application Launcher starts it immediately reads eDirectory to get information about the applications associated with the user. The new Random Refresh feature instructs Application Launcher to retrieve its application information from the user's local 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. For more information, see Configuring User Settings in Configuring Novell Application Launcher Settings in Application Management in the ZENworks for Desktops 4 Administration Guide.
Rogue Process Management lets you find out about and stop application processes not launched by Application Launcher.
What's New in Application Management for ZfD 4 SP1/4.0.1
In addition to the new features introduced in ZfD 4 (see What 's New in Application Management for ZfD 4 above), ZfD 4 SP1/4.0.1 introduces the following new features for Application Management. Unless otherwise noted, these features are available whether you used the ZfD 4.0.1 CD to create a new installation or used the ZfD 4 Support Pack 1 (SP1) or ZfD 4.0.1 CD to update an existing ZfD 4 installation.
The Web-based ZfD installation manager used to install the NAL plug-in now determines which version of Application Launcher or the NAL plug-in is installed:
If no version is installed, the installation manager installs the NAL plug-in.
If an older NAL plug-in is installed, the installation manager installs the new NAL plug-in.
If the Application Launcher included in pre-ZfD 4 versions is installed, the installation manager does not install the NAL plug-in.
If the Application Launcher included with the ZfD Management Agent (version 4 or higher) is installed, the installation manager does not install the NAL plug-in.
(Not available in ZfD 4 SP1) Novell DeFrameTM is a new component of ZfD Application Management that can be used to distribute thin-client applications. In addition, DeFrame provides application load balancing between terminal servers, disconnected session tracking and management, integration with Novell iFolder® for file storage, and migration of application information from the Citrix Published Application Manager utility into Novell eDirectory. While the ZfD 4 method of thin-client application distribution is still available, DeFrame is the recommended method for distributing thin-client applications. If you have used DeFrame previously, see What's New in ZfD DeFrame below.
The following changes have been made to DeFrame in this release:
DeFrame no longer includes DeFrame Dynamic User (DDU) functionality for creating and managing local user accounts and roaming profiles. If you have been using DDU, you will need to use ZfD Workstation Manager and Dynamic Local User (DLU) policies.
The DeFrame 2.01 services (DeFrame Access Control Service, DeFrame Watchdog Service, and DeFrame Disconnected Session Tracking Service) have been combined into one service called the Novell ZENworks Thin-Client Application Service (zentcas.exe).
A new utility, the DeFrame\OnDemand User Configuration utility, has been added. You can use the utility to enable multiple users as DeFrame users at one time. If you have ZENworks 6 Web Self-Service (formerly ZENworks OnDemand ServicesTM), you can also use the utility to configure OnDemand user settings.
Support for the Citrix Secure Gateway (relay mode only) has been added.
