Caching an Application.

Added the following note about using the Force Cache option with remote users:

NOTE:  In order to cache an application, it must be marked as Disconnectable. If the application is not marked as Disconnectable, the Force Cache option is not available. For instructions, see Configuring Applications as Disconnectable.

If you select the Distribute Always option and a remote connection is detected, ZENworks behaves as if the Force Cache and Check Point Restart options are enabled (even if you did not enable these options when you configured the Application object).

Always Show Icon.

Reworded the following paragraph to more accurately describe what is listed when a user views the requirements for a disabled application:

If you select this option and one or more rules is not met, the icon is displayed in a disabled state. Users can right-click the disabled icon, select Details, then select Requirements to view a list of all of the distribution requirements that were defined for the application.

Add.

Added information to describe new functionality that lets you copy a directory to a workstation.

Application Object Properties Where Macros Can Be Used.

Added information to describe additional fields in which macros can be used:

• Package Source Path (Common tab > Sources)
• Transform Path (MSI tab > Transforms)MSI Patch File (MSI tab > Patches)

Removed information to describe fields in which macros cannot be used:

• Find File, Find Next File, Add string (Distributions Options tab > Text Files page
• Custom Folders (Identification tab > Folders page)

Application Window Command Line Switches.

Changed information describing how the /restrictonline command line switch works when authentication to eDirectory is though the Middle Tier Server rather than through the Novell Client. The paragraph now reads:

This feature is not supported if authentication to eDirectory occurs through the Middle Tier Server (using the ZENworks Desktop Management Agent).

Associations Page.

Added the following note about associating applications:

NOTE:  Associating an Application object with a Group, Workstation Group, or other container object is the preferred method of associating the Application object in eDirectory. Associating the application to a large number of User or Workstation objects (for example, more than 250) might cause increased server utilization.

Caching an Application.

Added the following note about marking an application as Disconnectable before caching it:

NOTE:  In order to cache an application, it must be marked as Disconnectable. If the application is not marked as disconnectable, the Force Cache option is not available. For instructions, see Configuring Applications as Disconnectable.

Create Virtual CD.

Added the following note at the end of the section:

NOTE:  Some CD-burning software does not allow for leading periods in filenames. When you create a virtual CD, ZENworks creates the virtual CD using a leading period in the application directory file pathname. If your CD-burning software does not allow for leading periods in filenames, and converts the period to another character such as an underscore, the virtual CD will not be usable.

Currently, ZENworks does not support virtual CDs that are burned using the K3B CD-burning software.

Creating and Deleting Application Folders.

Added the following sentence to the Delete section under Step 7.

The change is applied the next time Application Launcher restarts.

Creating Distribution Rules.

Reworded the following paragraph under Step 4 to more accurately describe what is listed when a user views the requirements for a disabled application:

If you select this option and one or more rules is not met, the icon is displayed in a disabled state. Users can right-click the disabled icon, select Details, then select Requirements to view a list of all of the distribution requirements that were defined for the application.

Creating the Application Object from a Windows Installer (.MSI) File.

Added the following note under Step 3:

NOTE:  After you create the Application object, you cannot change the .msi filename; however, you can change the path to the .msi file. If you change the .msi filename, the installation will fail.

In the same step, removed the paragraph about not using macros in the Path to .MSI File field because it is possible to use macros here. Added the same sentence under Step 4 in the Administration Package Path section because you cannot use macros in this field.

Added the following note under Step 6:

NOTE:  Associating an Application object with a Group, Workstation Group, or other container object is the preferred method of associating the Application object in eDirectory. Associating the application to a large number of User or Workstation objects (for example, more than 250) might cause increased server utilization.

Creating an Application Object from a ZENworks snAppshot File.

Added the following note about specifying an operating system rule under Step 5:

NOTE:  The requirement for an operating system to be defined before an application is available has been removed.

In previous ZENworks versions, an OS platform had to be defined in the System Requirements before an application would be available for distribution and launching. This requirement has been removed.

The new behavior uses the following logic: If an application runs only on a specific operating system, define an operating system distribution rule. If an application does not require a specific operating system, there is no need to define a distribution rule. By default, applications without a defined operating system distribution rule are available on all supported platforms (Windows 98, Windows 2000, and Windows XP).

Added the following note about associating applications under Step 6:

NOTE:  Associating an Application object with a Group, Workstation Group, or other container object is the preferred method of associating the Application object in eDirectory. Associating the application to a large number of User or Workstation objects (for example, more than 250) might cause increased server utilization.

Configuring the Application in eDirectory.

Added the following note about specifying an operating system rule under Step 5:

NOTE:  The requirement for an operating system to be defined before an application is available has been removed.

In previous ZENworks versions, an OS platform had to be defined in the System Requirements before an application would be available for distribution and launching. This requirement has been removed.

The new behavior uses the following logic: If an application runs only on a specific operating system, define an operating system distribution rule. If an application does not require a specific operating system, there is no need to define a distribution rule. By default, applications without a defined operating system distribution rule are available on all supported platforms (Windows 98, Windows 2000, and Windows XP).

Added the following note about associating applications under Step 6:

NOTE:  Associating an Application object with a Group, Workstation Group, or other container object is the preferred method of associating the Application object in eDirectory. Associating the application to a large number of User or Workstation objects (for example, more than 250) might cause increased server utilization.

Configuring the Application in eDirectory.

Added the following note about specifying an operating system rule under Step 5.

NOTE:  The requirement for an operating system to be defined before an application is available has been removed.

In previous ZENworks versions, an OS platform had to be defined in the System Requirements before an application would be available for distribution and launching. This requirement has been removed.

The new behavior uses the following logic: If an application runs only on a specific operating system, define an operating system distribution rule. If an application does not require a specific operating system, there is no need to define a distribution rule. By default, applications without a defined operating system distribution rule are available on all supported platforms (Windows 98, Windows 2000, and Windows XP).

Added the following note about associating applications under Step 6:

NOTE:  Associating an Application object with a Group, Workstation Group, or other container object is the preferred method of associating the Application object in eDirectory. Associating the application to a large number of User or Workstation objects (for example, more than 250) might cause increased server utilization.

Configuring the Reporting Servlet.

Added the following information pointing to a TID to Step 2:

If you are using a database other than Sybase, modify the parameters, described below, as required by your database. If you are using a Microsoft SQL database, follow the directions in TID 10094306.

Configuring the Reporting Servlet to be Used with Apache.

Added entire section.

Configuring Window Settings.

Added the following information to the Watermark Source Path section:

Graphics files larger than 172 Kb cannot be used as the background wallpaper.

Determining Where Novell Application Launcher Runs.

Added the following note under the Application Launcher on Terminal Servers heading:

NOTE:  After installing Windows 2000 Service Pack 4 (SP4), some programs might not work correctly. For example, the Novell Application Launcher window might fail to display on a Windows 2000 terminal server. To fix this problem, see TID 10085889.

Disabling the Cache.

Under Step 5, added the following information to clarify the procedure to disable writing to the cache for workstation-associated applications.

NOTE:  The Enable Writing to the Cache option is available on both the User and Workstation tabs. You should use the appropriate tab, depending on whether you want to disable writing to the cache for user-associated applications or for workstation-associated applications. If you want to disable the cache for both user-associated and workstation-associated applications, you should perform the steps in this section on both the User and Workstation tabs.

Distribute in Workstation Security Space if Workstation Associated.

Added the following note at the end of the section:

NOTE:  If an application requires a reboot during installation, you must select Reboot if Needed or Reboot Always in the Reboot group box and Don't Prompt in the Prompt for Reboot group box.

Distribution Rules Page.

Removed the section on Authentication because the Authentication Rule functionality has been removed from ZENworks. The Local Workstation Authentication and Network Authentication features are no longer supported.

You can use the Disconnectable check box on the Identification > Icon page to ensure that the application is available when the user is disconnected from the network. For more information, see Disconnectable.

Drives to Be Mapped.

Added the following note:

NOTE:  Starting with ZENworks for Desktops 4.x, selecting the S1 or S16 option does not affect the system's global path. Only applications started by this NAL process will use this search path; applications external to the NAL process cannot use this search path.

Enabling Checkpoint Restart for File Downloads.

Added the following note about using the Force Cache option with remote users:

NOTE:  If you select the Distribute Always option and a remote connection is detected, ZENworks behaves as if the Force Cache and Check Point Restart options are enabled (even if you did not enable these options when you configured the Application object).

Force Run.

Added information explaining that if an application requires a reboot during installation, you must select Reboot if Needed or Reboot Always in the Reboot group box and Don't Prompt in the Prompt for Reboot group box.

Granting ODBC Property Rights to Users.

Added four properties: Host Server, Network Address, zendbUser, and zendbPassword.

Importing the Requirements After Opening the Distribution Rules Page.

Reworded the following paragraph under Step 5 to more accurately describe what is listed when a user views the requirements for a disabled application:

If you select this option and one or more rules is not met, the icon is displayed in a disabled state. Users can right-click the disabled icon, select Details, then select Requirements to view a list of all of the distribution requirements that were defined for the application.

Importing the Requirements When Opening the Distribution Rules Page.

Reworded the following paragraph under Step 5 to more accurately describe what is listed when a user views the requirements for a disabled application:

If you select this option and one or more rules is not met, the icon is displayed in a disabled state. Users can right-click the disabled icon, select Details, then select Requirements to view a list of all of the distribution requirements that were defined for the application.

INI Settings.

Added the following note:

NOTE:  For Application objects created for AOT/AXT applications, the Novell Application Launcher (NAL) handles the distribution of the INI settings and the distribution of the application. If you modify INI settings for an AOT/AXT application and the INI settings fail to distribute, the application itself fails and NAL rolls back the application's installation.

For Application objects created for MSI applications, NAL handles the distribution of INI settings and the Microsoft Windows Installer (MSI) handles distribution of the application. If you modify the Application object's INI settings for a MSI application and the INI settings fail to distribute, the application is installed by Windows Installer. As a result, the application might not function properly, depending on how the INI settings affect the application.

Installing the RDP and ICA Clients.

Changed the link to the Citrix client to the following:

Citrix ICA wficac.cab:

Installing the Reporting Servlet.

Removed a paragraph indicating that the zfdamrServlet.war file is available on the ZENworks 6.5 Desktop Management CD. This file is installed to the proper location by the installer.zip file during installation.

Meeting the Reporting Servlet Requirements.

Added the minimum version requirements to run the Reporting servlet on NetWare 6.5.

Metering Software Licenses.

Added the following note to Installing the Novell Client and Licensing Files to Workstations:

NOTE:  The nls32.dll and nlsapi32.dll files were inadvertently omitted from the Novell ZENworks 6.5 Companion 1 CD. They are included in ZENworks 6.5 Desktop Management Support Pack 1 download. For more information, see the Readme for ZENworks 6.5 Desktop Management Support Pack 1.

MSI Tab.

Added the following note under Add:

NOTE:  When Application Management distributes and installs an MSI application, it uses the AlwaysInstallElevated policy, which installs the MSI application using elevated (system) privileges. Because of this, in order to set the ALLUSERS property value to null so that the application is installed on a per-user basis, you need to leave the Value Data field empty. Using double quotation marks ("") causes the distribution to fail.

Operating System.

Added the following note about operating system rules:

NOTE:  The requirement for an operating system to be defined before an application is available has been removed.

In previous ZENworks versions, an OS platform had to be defined in the System Requirements before an application was available for distribution and launching. This requirement has been removed.

The new behavior uses the following logic: If an application runs only on a specific operating system, define an operating system distribution rule. If an application does not require a specific operating system, there is no need to define a distribution rule. By default, applications without a defined operating system distribution rule are available on all supported platforms (Windows 98, Windows 2000, and Windows XP).

Pre-Install Schedule Page.

Added information explaining that if an application requires a reboot during installation, you must select Reboot if Needed or Reboot Always in the Reboot group box and Don't Prompt in the Prompt for Reboot group box.

Pre-Installing an Application Immediately.

Added Step 5.c explaining that if an application requires a reboot during installation, you must select Reboot if Needed or Reboot Always in the Reboot group box and Don't Prompt in the Prompt for Reboot group box.

Properties Page.

Added the following paragraph under the Add heading:

For a list of properties and descriptions, see the Microsoft Developer Network (MSDN).

Reference: Macros.

Added the following note:

NOTE:  Be aware that using macros causes increased network traffic because the ZENworks^® macro lookup checks with NDS^® on the network before it checks the local environment.

Registry Settings.

Added the following note:

NOTE:  For Application objects created for AOT/AXT applications, the Novell Application Launcher (NAL) handles the distribution of the registry settings and the distribution of the application. If you modify registry settings for an AOT/AXT application and the registry settings fail to distribute, the application itself fails and NAL rolls back the application's installation.

For Application objects created for MSI applications, NAL handles the distribution of registry settings and the Microsoft Windows Installer (MSI) handles distribution of the application. If you modify the Application object's registry settings for a MSI application and the registry settings fail to distribute, the application is installed by Windows Installer. As a result, the application might not function properly, depending on how the registry settings affect the application.

Run.

Added the following note:

NOTE:  Some applications cannot be run in Minimized, Maximized, or Hidden mode. Depending on the application, the initial window size setting might be ignored. For example, calc.exe cannot be run in Hidden mode.

Running the Application Browser Under Windows XP SP2 or Later.

Added entire section describing changes to the Application Browser's behavior caused by security updates implemented in Windows XP SP2.

Schedule Page.

Added information to the Spread from Start Time (in Minutes) paragraph to more clearly describe how this option works.

Pre-Installing an Application Immediately.

Added information explaining that if an application requires a reboot during installation, you must select Reboot if Needed or Reboot Always in the Reboot group box and Don't Prompt in the Prompt for Reboot group box.

Setting Up Application Launcher As the Shell on Windows 98.

Changed the line that you must modify in the system.ini file in Step 2:

shell=c:\program files\novell\zenworks\nalwin.exe

to

shell=c:\progra~1\novell\zenworks\nalwin.exe

SnAppShot Limitations.

Added the following bulleted item:

The Application object template changed from version 4.0.1 to 6.5 to accommodate several functionality changes, including the change from system requirements to distribution rules. If you have a pre-ZENworks 6.5 environment, you must select the Create Pre 6.5 Application Object Template File option while creating the .aot file in order to use the file in your environment. If you use the default option, Create 6.5 Application Object Template File, the resulting .aot file is not usable in a pre-ZENworks 6.5 environment.

Understanding File System Rights to the NAL Cache in ZENworks 6.5 and in ZENworks 6.5 Support Pack 1 (SP1).

Added an entire section to describe changes in the default file system rights to the NAL cache directory from the initial release of ZENworks 6.5 to ZENworks 6.5 SP1.

Windows 2000/XP (Workstation-Associated Applications).

Added information about a secure/unsecure System user in the Launch (normal) row.