Novell ZENworks 6.5 Desktop Management Support Pack 2

2.3.1 Extracted Installation File Organization

The following directory structure is created in the network location where you extract the zen65sp2.exe file:

zen65sp2\ 
   |__install\... 
   |__readmes\ 
   |   |__en\ 
   |      |__readme_desktops.html 
   |      |__readme_servers.html     
   |      |__readme_zenworks.html 
   |__zdm\ 
   |   |__agentinstall\... 
   |   |__license_agreements\... 
   |   |__zen preboot services\... 
   |   |__zenworks\... 
   |__zsm\ 
   |   |__sounds\... 
   |   |__zfs\... 
   |__autorun.inf 
   |__winsetup.exe 
   |__winsetup.ini 

NOTE:  To run the SP2 installation, run winsetup.exe.

The following directory structure is created in the network location where you extract the zen65sp2compcd.exe file:

companion 
   |__codepageutility 
   |   |__encoding.class 
   |   |__encoding.cmd 
   |   |__readme.doc 
   |__database 
   |  |__mssql 
   |  |__oracle8i 
				   |  |__oracle9i 
   |  |__oracle9i_unix  
   |__desktop 
   |   |__desktop.zip 
   |__licensing 
   |  |__nls32.dll 
   |  |__nlsapi32.dll 
   |__zen65patch 
   |   |__inv 
   |       |__server 
   |           |__wminv 
   |               |__lib 
   |                   |__desktopcommonutility.jar 
   |__zenworks server management - software pkgs 
       |__invrm 
       |   |__RemStandAlonePacPro.zip 
       |   |__zsm65sp2_invagnt.cpk 
       |   |__zsm65sp2_remmgmt.cpk 
       |__pds 
           |__zsm65sp2_polydist.cpk

For more information about the contents of the companion1 folder, see 3.2.3 Using Software License Metering and Monitoring in this readme.

Most of the files in the companion2 folder are specifically for ZENworks 6.5 Server Management users, however you can also extract desktop.zip, which includes files required to perform Remote Management and Workstation Inventory operations without using Novell ConsoleOne^®. For detailed information about these operations, see the ZENworks 6.5 Desktop Management Administration Guide.

3.1.1 Windows Group Policies Configured in the Workstation Package to Run at Startup Might Not Be Processed Consistently

The startup scripts for Windows Workstation Group Policies configured in the Workstation Policy Package might not run consistently when scheduled for system startup in ZENworks 6.5 Desktop Management SP2, even when Persist Workstation Settings is selected.

3.1.2 Roaming Profile Usage Might Result In .001, .002, and .003 Profiles Being Created Locally

If network users with Roaming Profiles are seeing multiple c:\documents and settings\username.machine_name.nnn folders on a Windows workstation where they log in, or if users notice slow Windows logoffs or slow workstation shutdowns, it might be due to Windows registry keys being left open.

To work around this problem, see the information in TID 10096547 in the Novell Support Knowledgebase.

3.1.3 iPrint Secure Printers Might Not Be Distributed Through a Firewall to Workstations

An iPrint Policy configured to allow access to secure printers might not be distributed to workstations outside the firewall if the Novell iPrint Client version 4.05 (that is, the version shipping with NetWare 6.5 Support Pack 3) is installed on those workstations.

The problem does not occur when the workstations are inside the firewall, even when iPrint Client 4.05 is installed on them.

To work around the problem, use a newer version of the Novell iPrint Client (such as version 4.08 or 4.11).

NOTE:  As a best practice, you should always use the latest iPrint Client with ZENworks Desktop Management, unless otherwise documented.

3.2.1 Application Distribution Through the Middle Tier Fails When the Novell Client is Disconnected

If users have a version of the Novell Client^TM older than version 4.9 Support Pack 2 to login locally (that is, "Workstation Only"), the NWGINA will not authenticate to eDirectory and will not make any network requests. In addition, the Novell Client will have an unauthenticated or "monitored" connection to the eDirectory^TM tree determined to be the primary tree.

If the user subsequently authenticates from the Novell Application Launcher using the Middle Tier Login, the NetIdentity client authenticates to the ZENworks Management Server serviced by the Middle Tier Server.

Attempts made by the Application Launcher to distribute an application through this authentication will fail because the files to be distributed are located on the server where the client has created a monitored connection. Through this connection, the client sees the sys: volume on the server (all users have rights to the \login directory on the sys: volume of a NetWare server because older clients authenticated by running login.exe).

To work around this issue, the user must right-click the red "N" icon for the Novell Client in the system tray to log in to the server. Users should not right-click the Application Launcher icon in the system tray and select "ZENworks Middle Tier Server Login" to log in.

3.2.2 Application Distribution of Dependent Applications in a Chain Might Stall When Distributed to Windows 98 Workstations

If you distribute chained, dependent applications to a Windows 98 workstation in a ZENworks environment where the Middle Tier and Desktop Management Servers have been upgraded to ZENworks 6.5 Desktop Management SP2 but the Desktop Management Agent has not been upgraded from the 4.x version or from the 6.5 shipping version, the application distribution might fail with various errors.

In this situation, you might see the first few applications in the chain distribute normally, but a subsequent distribution of another application in the chain might seem to place the workstation in a disconnected state.

There are two methods of working around the problem:

• Exit the Novell Application Launcher and then relaunch it to restart the distribution.
• Upgrade the Desktop Management Agent to version 6.5 SP2.

3.2.3 Using Software License Metering and Monitoring

A key component of Novell Licensing Services, nls32.dll, does not ship with the current Novell Client and was omitted from the original ZENworks 6.5 Companion 1 CD. As a result, an error is generated when you try to use Software License Metering and Monitoring in Desktop Management.

To work around this problem, copy nls32.dll and nlsapi32.dll from the companioncd\companion1\licensing directory in the companioncd.exe download of Support Pack 2 to each workstation where you want to check application licenses. On Windows 2000/XP workstations, copy to the c:\winnt\system32 directory. On a Windows 98 SE workstation, copy to the c:\windows\system directory.

For more information, see Metering Software Licenses in the Novell ZENworks 6.5 Desktop Management Administration Guide.

3.2.4 No Icon for a Workstation Associated Application When the Workstation Reboots to an Offline Condition

The icon for a workstation-associated application set as disconnectable does not appear immediately when the user logs in to the workstation locally without authenticating to eDirectory.

To work around this problem. use the information in TID 10086332 in the Novell Support Knowledgebase.

3.2.5 AND/OR Combobox Does Not Display on the Distribution Rules Page of an Application Object

If you create distribution rules on the Distribution Rules page of the Availability tab in the properties of an Application object in ConsoleOne 1.3.6e, the AND/OR combobox used to change the operator does not display on the Add Rules to Control Availability of This Application list.

This display problem is caused by the JRE included in ConsoleOne 1.3.6e (this JRE is part of JVM 1.4.2_05). This version of ConsoleOne ships with NetWare 6.5 SP4/OES NetWare SP1.

Use one of the following options to work around the problem:

• Rename the JRE subdirectory in the ConsoleOne directory, then copy an earlier version of the JRE directory (from another, different version of ConsoleOne) in its place.
• In the Type column of the Add Rules to Control Availability of This Application list, click the AND or OR until it is selected, then either type A for AND or O for OR to select the operator you want. Alternatively, you can highlight the operator, then use the up or down arrow keys to switch between AND and OR.

3.3.1 Installing Support Pack 2 Disables Preboot Services for Workstation Imaging in a Novell Cluster Services Environment

If you previously followed the instructions to get Workstation Imaging working in a Novell Cluster Services environment and you subsequently install ZENworks 6.5 Desktop Management Support Pack 2, the critical changes you made to the dts.ini file for the SP1 workaround are overwritten.

As a result of the file being overwritten, a workstation booting with ZENworks Preboot Services does not read the Imaging policy for work to do and Workstation Imaging fails.

To work around the issue, install Support Pack 2, then follow the updated instructions in Configuring ZENworks 6.5 Workstation Imaging in a ZENworks Support Pack for a Novell Cluster Services Environment in the Novell ZENworks 6.5 Desktop Management Installation Guide to reconfigure dts.ini.

3.4.1 Screen Blanking Feature

• The screen blanking feature might not work properly with some video adapters such as VIA Tech VT8361/VT8601, Hawk Eye Number 9 and ATI Rage P/M Mobility AGP 2x that have been configured in the managed workstations. We recommend that you test the screen blanking feature with the video adapter that you have before deploying the Remote Management Agent in your enterprise.
• When you invoke the screen blank option on your managed workstation and change the color resolution on the workstation to 256 colors, the managed workstation might hang. To resolve this problem, restart the managed workstation.

3.4.2 Multi-Monitor Support

If a managed workstation has multiple monitors, a remote session from a management console manages only the primary monitor of the managed workstation.

3.4.3 Remote Management Agent Help File Might Fail to Launch

The Remote Management Agent help might not launch from the Remote Management Agent icon in the system tray of the managed device.

To work around the problem and view the Help, navigate to the following location and double-click rcagent.chm:

zenworks_agent_directory\remotemanagement\rmagent\nls\language_directory.

3.4.4 File Transfer Does Not Work With Desktop4.exe

File Transfer does not work when launched from desktop4.exe extracted from desktop.zip shipping with the Companion 2 CD.

To work around the problem, use the following steps:

1. Extract desktop.zip.

2. Remove the \jre directory extracted from desktop.zip.

3. Copy the \jre directory shipping with ConsoleOne 1.3.6 and paste it in place of the \jre directory you removed in Step 2.

3.5.1 Data Export Issue

From a Novell ConsoleOne installation having ZENworks 6.5 SP2 Inventory snap-ins, you cannot invoke the Data Export utility for a ZENworks 6.5 Inventory database by clicking Tools > ZENworks Inventory > Data Export.

To work around this issue, in ConsoleOne, right-click the ZENworks 6.5 Inventory database object, then click Data Export.

3.6.1 Uninstalling the Desktop Management Agent on a Windows 98 Workstation Might Fail

If you or a user uninstall the ZENworks 6.5 Desktop Management Agent from a Windows 98 workstation, the uninstall process might fail with the following error message:

Error 1605: This action is only valid for products that are currently installed

The failure is due to the Windows 98 MSI Installer incorrectly setting up the Windows registry for uninstall.

InstallShield Consumer Central has published a Knowledgebase resource that provides some steps for working around the problem. The workaround recommends that you run Windows Installer CleanUp Utility to clear registry entries from the workstation. The utility is available for download at the Microsoft Support site.

3.6.2 ZENworks 6.5 Desktop Management Agent Might Not Be Installed If Third Party Login Software Is Present

If you want to install the SP2 version of the ZENworks 6.5 Desktop Management Agent on a workstation that does not have the Novell Client or an earlier version of the Desktop Management Agent installed, and if certain third party network login GINAs are already installed on that workstation, the Desktop Management Agent does not install.

The ZENworks 6.5 Desktop Management Agent supports the following third party GINAs (that is, the Desktop Management Agent is compatible and will be installed alongside the following login GINAs):

• Cisco Aironet
• Citrix
• PCAnywhere
• Screenpass

If you want to force the installation of the Agent and overwrite a previously installed, but non-supported third-party GINA, you can use the IGNORE_3RDPARTY_GINA MSI property with a setting of 1:

IGNORE_3RDPARTY_GINA = 1

IMPORTANT:  Some other third party GINAs do not function if they are not the primary (that is, the first) listing in a Microsoft GINA chain. This causes a problem on workstations where the Desktop Management Agent is already installed: the Agent requires the primary listing in the chain and will disable the third party GINA.

3.6.3 Upgrading the Desktop Management Agent to Version 6.5 SP2 Removes Workstation Object Information from the Windows Registry

If you are logged in as a member of only the Users group when you upgrade the ZENworks Desktop Management Agent to the 6.5 SP2 version, the information in the HKLM\Software\Novell\Workstation Manager\Identification registry key might be lost. This results in the workstation no longer being registered (that is, it is no longer imported into the eDirectory tree).

This condition occurs because registry information is not read and saved prior to the uninstall. In some environments, this is not an issue because the workstation is re-imported at the next workstation reboot. In environments where import is dependent on the User (for naming or location) however, the user must log in as many times as specified in the User Login Limits field (specified in the Import Policy) before the workstation is re-imported.

NOTE:  You can avoid this issue if you change the permissions to the HKLM\Software\Novell\Workstation Manager\Identification key before you upgrade the Agent upgrade: grant Read access to the Users group. You can distribute registry permissions using ZENworks Group Policies by importing an INF file containing the desired permissions. For more information, see Windows Group Policy (User and Workstation Packages) in the Novell ZENworks 6.5 Desktop Management Administration Guide.

After the ZENworks 6.5 SP2 Desktop Management Agent is installed, the necessary permissions for the registry key are set for future upgrades.

3.6.4 Desktop Management Agent Upgrade on Windows 98 Fails

If you upgrade the ZENworks Desktop Management Agent already installed on Windows 98 to the ZENworks 6.5 SP2 version of the agent, the installation displays a message after the workstation reboot stating that an error has occurred in ncred9x.dll. No user login is possible after this failed upgrade and the workstation is left in a bad state.

The error occurs because of a flaw in the Windows 98 MSI engine that does not properly update certain files.

If you want to avoid this problem, you need to include the following property on the MSI Application object for Windows 98 workstations only:

REINSTALLMODE=vemus

This will properly place the files on the Windows 98 workstation.

For more information about setting MSI properties, see "MSI Tab" in "Reference: Application Object Settings" in the "Application Management" section of the ZENworks 6.5 Desktop Management Administration Guide.

3.7.1 Interoperability with NSure SecureLogin

The ZENworks 6.5 Desktop Management Agent Support Pack 2 does not work properly with versions of the NSure^® SecureLogin earlier than 3.51.1.

If you install the ZENworks 6.5 SP2 Management Agent on a workstation that has a version of SecureLogin earlier than 3.51.1 already installed, the user's login attempts will fail and the workstation will reboot.

If you have already encountered this problem, you can return the workstation to a working state by following the instructions in TID 10096513 in the Novell Support Knowledgebase.