Novell ZENworks 6.5 Desktop Management Support Pack 1

2.4.1 Extracted Installation File Organization

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

zen65sp1\ 
   |__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 SP1 installation, run winsetup.exe.

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

companion1 
   |__licensing 
       |__nls32.dll 
       |__nlsapi32.dll 
companion2 
   |__codepageutility 
   |   |__encoding.class 
   |   |__encoding.cmd 
   |   |__readme.doc 
   |__desktop 
   |   |__desktop.zip 
   |__zen65patch 
   |   |__inv 
   |       |__server 
   |           |__wminv 
   |               |__lib 
   |                   |__desktopcommonutility.jar 
   |__zenworks server management - software packages\...

For more information about the contents of the companion1 folder, see 3.2.4 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 SP1, 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, download and use the Microsoft User Profile Hive Cleanup Service, a utility that closes open registry keys in the user hive, allows Roaming Profiles to be deleted normally at logoff time, and allows faster workstation logoffs and shutdowns.

We recommend that you use the Novell Application Launcher^TM to distribute this MSI application to all affected workstations.

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 new version of 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 version of the Novell iPrint Client released prior to version 4.05.

3.2.1 Application Launcher Overrides REINSTALLMODE Property of MSI Applications Being Upgraded

When you attempt to apply a minor version upgrade (such as ZENworks 6.5 SP1) to an MSI application, the Novell Application Launcher overrides the REINSTALLMODE setting of "vamus," replacing it with the "vomus" value. The letter "o" in this value means that only files that are older will be replaced, while the "a" in "vamus" indicates that all files are to be replaced.

This is an issue because, during the SP1 upgrade, even if an SP1 file has a newer date than the file being upgraded, the newer file is not copied unless the file version is newer (that is, greater) than the file currently installed on the system. Because the file date is newer, you might expect the new file to be copied, but it will not be copied unless the version of the file has been updated to a later version.

You can work around this upgrade issue by using a simple application to call msiexec on the command line. Use the following syntax:

msiexec.exe /i path_to_new_version_of_msiapp(minorupgrade) REINSTALL=ALL REINSTALLMODE=vomus /qn

NOTE:  You need to run this application as an Unsecure System User.

The following section explains the different elements of this command line syntax.

msiexec.exe /i Launch the Windows Installer engine to perform the install.

<path . . .> Self explanatory.

REINSTALL=ALL Reinstall all components that were previously installed with the last version.

REINSTALLMODE=vomus Replace only those files with a date stamp older than those of the new object.

/qn Perform a silent install.

NOTE:  You could also use the /qb switch for this parameter. This will display a progress bar but not all the interactive pages in the installation interface.

3.2.2 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.3 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 SP1 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 SP1.

3.2.4 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 CD 1. 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 1 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.5 No Icon for a Workstation Associated Application When the Workstation Reboots to an Offline Condition

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

Due to a delay built into the code, the icon reappears on the desktop if you refresh the Novell Application Launcher after waiting for five minutes.

3.3.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.3.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.1 Data Export Issue

If you manage the network from an instance of Novell ConsoleOne where the ZENworks 6.5 SP1 Inventory snap-ins are installed, 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.5.1 User-Based Uninstall of the Desktop Management Agent Should Be Accomplished With Add/Remove Programs

We recommend that you do not configure the Desktop Management Agent MSI object to allow for a user-based uninstall because the workstation does not currently prompt for a reboot when the user executes an uninstall by right-clicking the Application object icon.

If you grant Administrator rights to the user, he or she can uninstall the Desktop Management Agent using Add/Remove Programs. In this case, the workstation does display a prompt for reboot. You can use the agentdistributor.exe utility located in the sys:public\mgmt\consoleone\1.2\bin folder of the Desktop Management Server when ZENworks 6.5 SP1 has been applied to that server. Using this utility, you can "push" the latest agent to workstations based on their IP address.

3.5.2 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.5.3 Installing the ZENworks 6.5 Desktop Management Agent Prevents Third Party Login Software from Working

Installing the ZENworks 6.5 Desktop Management Agent on a workstation will overwrite some third party network login GINAs. The ZENworks 6.5 Desktop Management Agent supports the following third party GINAs (that is, they will not be overwritten by the Desktop Management Agent installation):

• Cisco Aironet
• Citrix
• PCAnywhere
• Screenpass

If some other third-party GINA (that is, a GINA not in this list) is already installed on the user workstation, the Desktop Management Agent will not install. You can use the IGNORE_3RDPARTY_GINA MSI property with a setting of 1 to force the installation of the Agent and overwrite the third party GINA.

IMPORTANT:  Some other third party GINAs will 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.5.4 Upgrading the Desktop Management Agent to Version 6.5 SP1 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 SP1 version, the information in the HKLM\Software\Novell\Workstation Manager\Identification registry key is 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 SP1 Desktop Management Agent is installed, the necessary permissions for the registry key are set for future upgrades.

3.5.5 Desktop Management Agent Distributor Might Use Excessive CPU Cycles on the Workstation

The Desktop Management Agent Distributor (agentdistributor.exe) included with ZENworks 6.5 SP1 can cause excessive CPU cycling on the Windows workstation that you use to distribute the agent. The problem occurs when several configuration elements are selected. Desktop Management Agent features, the Middle Tier address, and the ZENworks tree name all contribute to lengthen the command line. If the command line string becomes too long (approximately 240 characters) the ZDPAService used to deploy the agent uses excessive CPU cycles. This can possibly lock up the machine.

One way to reduce the length of the command line is to select all of the features that can be installed with the Desktop Management Agent. This will result in an abbreviated command line (ADDLOCAL=ALL) being passed to the buffer so that the Agent Distributor will run normally.

IMPORTANT:  This procedure installs all the features of the Desktop Management Agent. Depending on your business needs, you might not want to install all of these features on user desktops in your organization. We do not recommend that you install Agent features one at a time.

For more information about the Agent Distributor, see Using the Desktop Management Agent Distributor to Deploy the Agent in the Novell ZENworks 6.5 Desktop Management Installation Guide.

3.6.1 Interoperability with NSure SecureLogin

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

If you install the ZENworks 6.5 SP1 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 Knowledgebase.