Novell ZENworks 7 Desktop Management

1.1 NetWare 6.5 Limitation

If NetWare 6.5 SP2 is installed on the server where you authenticate workstations for ZENworks functionality, you will not be able to administer the eDirectory^TM tree or a server with ConsoleOne^® 1.3.6 until you upgrade the version of the Novell Client^TM installed on the machine to 4.9 SP2.

1.2 Novell Client 4.90.0 SP1a Limitation

We recommend that you do not install the version of the Novell Client (4.90.0 SP1a) that ships with eDirectory 8.7.3. This version requires additional patches in order to work with Windows Server 2003. Instead, we recommend that you install the Novell Client for Windows 4.91, which is available for download from the Novell Product Download Web site.

2.1 Linux Server Installation Issues

This section explains the issues that have been discovered with the installation of the Novell ZENworks 7 Desktop Management Services on Linux.

2.2 Desktop Management Server Installation Issues

This section contains information about the issues that might occur when you install the Desktop Management Server.

2.3 Middle Tier Server Installation Issues

This section contains information about the issues that might occur when you install the Middle Tier Server.

2.4 Desktop Management Agent Installation and Upgrade Issues

This section contains information about the issues that might occur when you install the Desktop Management Agent. For more information, see TID 10078667 in the Novell Knowledgebase.

IMPORTANT:  The version of the Desktop Management Agent that shipped with ZENworks for Desktops 4.0 is no longer supported. Prior to upgrading the Desktop Management Agent to ZENworks 7, users should replace this older version of the agent with the version of the agent shipping with the ZENworks 6 Suite (ZENworks for Desktops 4.0.1/SP1b) or later.

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

2.5 Microsoft RDP Client Installation Issues

The Microsoft RDP 5.1 client (msrdp.ocx) is included with the ZENworks 7 Launch gadget. When a user launches a terminal server application that you've configured to run in an RDP client session, the Launch gadget generates an error message indicating that the certificate for the file has expired.

If you click Yes in the error message to continue the installation, the Launch gadget installs the msrdp.ocx file to the c:\program files\novell\zenworks directory on the user's workstation and registers the OCX file.

If you install the msrdp.cab file to a workstation using the ZENworks Management Agent installation program, no error messages are displayed.

2.6 Workstation Imaging Installation Issues

This section contains information about the issues that might occur when you install the Workstation Imaging component of ZENworks 7 Desktop Management.

Imaging\NTa Components NOT successfully installed on 
<server_name> at <installation_path> 
Imaging\NTb Components NOT successfully installed on 
<server_name> at <installation_path>

3.1 ZENworks 6.5 Middle Tier Server Running on NetWare 6 Does Not Distribute Workstation Associated Group Policies

If you upgrade your ZENworks Desktop Management Server to ZENworks 7 (NetWare, Windows, or Linux server platforms) but do not upgrade the ZENworks 6.5 Middle Tier Server software to ZENworks 7, and if the Middle Tier Server is running on NetWare 6, workstation associated group policies will fail to distribute to workstations where the ZfD 4.x or ZENworks 6.5 Desktop Management Agent is installed.

To work around this issue, make sure you upgrade the Middle Tier Server to ZENworks 7.

3.2 Recommended Configuration for Upgrading the Desktop Management Agent

When configuring the upgrade Application object for the Desktop Management Agent, you should set the application to RUN ONCE, so that after the agent is installed the user can no longer see the application in the Novell Application Launcher. We also recommend that you do not enable uninstall for the Application Object.

Administrator rights are not needed to upgrade the Desktop Management Agent. The user's privileges are elevated temporarily by the Desktop Management Agent during the installation.

3.3 Upgrading the Desktop Management Agent to Version 7 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 version 7, 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 7 Desktop Management Administration Guide.

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

3.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 7 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=vamus

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 7 Desktop Management Administration Guide.

3.5 Desktop Management Agent Upgrade on Windows 98 Fails

If you upgrade the ZENworks Desktop Management Agent already installed on Windows 98 to the ZENworks 7 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=vamus

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 7 Desktop Management Administration Guide.

4.1 Middle Tier Server Installed on NetWare Requires Reboot After Editing Hosts File

Some NetWare servers might generate a 500-level error when you attempt to import workstations after editing the hosts file on that NetWare server.

To work around the problem, reboot the NetWare server where you installed the ZENworks Middle Tier Server and whose hosts file you edited for workstation import.

4.2 Unable to Authenticate to Windows 2000 Desktop Management Server with Active Directory and eDirectory Installed

If you try to authenticate through the Middle Tier Server to a Desktop Management Server installed on a Windows 2000 machine that already has Active Directory* (installed because the Desktop Management Server acts as the Primary Domain Controller) and eDirectory (installed to accommodate Desktop Management) both installed, the authentication fails unless the user logs on with a full context.

The reason for this failure is a contention for the default LDAP port between the Active Directory and eDirectory LDAP listeners. To work around this port conflict, during the install of eDirectory either choose an LDAP port other than the default of 389 or modify the LDAP Group object found in the server's container in ConsoleOne, then use the NSAdmin utility in the Middle Tier Server to configure the Middle Tier Server to communicate over that port.

To configure the port in NSAdmin:

1. In the Address box of Internet Explorer, type the URL for the NSAdmin utility. For example:

   http://server_name_or_IPAddress/oneNet/nsadmin

2. In the Value field of the LDAP Port configuration parameter, specify the LDAP port number you already set in eDirectory and which the Middle Tier Server should use to communicate with the Desktop Management Server > click Submit.

NOTE:  Do not attempt to use another Internet Browser (such as Mozilla Firefox) instead of Internet Explorer to run the NSAdmin utility. Other browsers fail to run NSAdmin properly.

For more information regarding this issue, see TID 10073537 in the Novell Support Knowledgebase.

4.3 Manually Unloading Middle Tier Server Handlers Causes a Server Abend

If you try to manually unload the Middle Tier Server Handlers (for example, xzen.nlm) running on NetWare 6, the server abends.

On NetWare 6, you should use NVXADMDN to unload Apache and Middle Tier handlers. Use NVXADMUP to restart Apache and Middle Tier handlers.

On NetWare 6.5, you should use AP2WEBDN to unload Apache and Middle Tier handlers. Use AP2WEBUP to restart Apache and Middle Tier handlers.

4.4 Using NDS Server Console on Windows 2000 Requires Administrator Rights

Using ndscons.exe on Windows 2000 to verify the connection between the Middle Tier Server and the Desktop Management Server does not work unless you have Administrator rights for the local Windows 2000 user.

4.5 Changing the eDirectory Password from a Security Dialog Box

A workstation with the Desktop Management Agent installed and running in Passive mode without the Novell Client presents the following option in a drop-down box when you click Change Password from a Windows Security dialog box (Ctrl+Alt+Delete):

<Novell Netidentity Credentials Provider>

This option for changing the eDirectory password from NetIdentity is currently non-functional. To change the password for the Agent running in Passive mode, open the Control Panel, click ZENworks Agent Options, and change the password in the appropriate dialog box.

4.6 Application Launcher Web View Does Not Activate the NetIdentity Login

If the Novell Client and the Desktop Management Agent are installed on the same workstation and the user logs in to the local workstation, then opens myapps.html and clicks the Work Online link in the Application Launcher Web View, the NetIdentity login does not work. This is designed behavior. If a workstation has the Novell Client and the ZENworks Management Agent both installed, Application Management always uses the Novell Client.

If only the Agent is installed on the workstation, in this same scenario, the Work Online link in the Web view activates the NetIdentity login.

4.7 Workstations Using the ZfD 4.x Agent Cannot Access Files from a Back End Windows Server through a Linux Middle Tier Server

Workstations that use the ZENworks for Desktops 4.x Desktop Management Agent cannot access files (such as applications to be cached) from a Desktop Management Server installed on Windows if the files must be accessed through a Middle Tier Server installed on a Linux machine (SLES 9 SP1 or OES Linux).

The problem occurs for two reasons:

1. The 4.x Agent does not have a ZENMUP to redirect communication directly to a Windows server.
2. The Linux Middle Tier Server does not have a full CIFS provider to obtain files from a Windows server.

You can work around this problem by installing a ZENworks 6.5 (or later) Desktop Management Agent, which uses ZENMUP to communicate directly to the Windows server.

4.8 Copying Files to a Workstation Through a Firewall Extends Login Times

Testing indicates that excessive login times result when workstations authenticate through a firewall and copy policy files or application files at login time.

To work around this issue, we recommend that you configure applications and policies to use DNS names for file locations on the back end, rather than IP addresses.

4.9 LDAP Authentication Consumes Two of User's Grace Logins When User Password Expires

LDAP authentication, which is launched when users log in and access ZENworks applications or policies, consumes two of the grace logins granted to a user when the user's password expires. Grace logins are set in ConsoleOne on the Restrictions page (password restrictions section) of the eDirectory User object.

For example, when eDirectory notifies a user that he or she has 2 grace logins left on a server, that user actually has no grace logins and will not be able to log in until the password is reset.

5.1 Automatic Workstation Import Fails if LDAP Port Is Set to a Port Other than 389

If, during eDirectory installation on a SLES 9 server, the LDAP port was set to listen on a port other than port 389, Automatic Workstation Import will fail when run on that server.

It is now possible to manually configure the novell-zdm-awsi.conf file to allow alternate ports to handle Automatic Workstation Import. Use the following steps to modify the .conf file:

1. Using a text editor, open /etc/opt/novell/zenworks/zdm/novell-zdm-awsi.conf on the Linux server.

2. Find the following line in the file:

   #LDAP_PORT = 389

3. Uncomment the line and change the port number from 389 to the port you want to use.

4. Save the file and close it, then restart the import service.

6.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 7 Desktop Management, even when Persist Workstation Settings is selected.

6.2 Group Policies Do Not Run Correctly on Windows XP Desktops

This section discusses some aspects of Windows Group policy administration that might not work properly or that might require further configuration in ZENworks 7 Desktop Management.

6.3 Renaming a Default User Account in a Windows Group Policy

If you launch the Microsoft Management Console (MMC) from ConsoleOne to edit a Windows Group Policy---specifically to rename a default user account (Administrator or Guest), you must not be logged in as the user whose default account name you are changing. If you log in using this default account and rename the account, the changes are not saved to the network path you designate in ConsoleOne and might remain on the administration machine.

6.4 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.

6.5 iPrint Printers Are Not Distributed to Windows 2000/XP Users by the iPrint Policy

After ZENworks 7 Desktop Management installation, iPrint printers are not distributed to users running Windows 2000/XP workstations, even after the ZENworks 7 Desktop Management iPrint policy is configured in the User Policy package (which installs the iPrint Client and pushes printer drivers to the users) and their workstations are rebooted.

To work around this problem in NetWare 6, modify the AllowUserPrinters value in the iprint.ini file in the \\server_name\sys\login\ippdocs directory from zero (0)---the default value---to one (1), which will allow the user to add the printer. In NetWare 6.5, the iprint.ini file is found in the \\server_name\sys\apache2\htdocs\ippdocs directory.

NOTE:  The iprint.ini file is available only if you have installed Novell Distributed Print Services^TM as part of a NetWare installation and if you have extracted the nipp.exe to that directory. If you do not have iprint.ini and nipp.exe, you can download them from Novell Support at http://support.novell.com. Search for TID 2968629.

6.6 iPrint Printers Are Not Distributed to Terminal Server User Sessions Outside a Firewall

If you use the iPrint policy to distribute printers through a firewall to a Windows 2000/2003 terminal server user session, the policy does not correctly set the required registry key to bypass the iPrint proxy address manual configuration.

Each terminal server session user who needs to print to printers from outside the firewall needs to use the following steps to set the proxy address:

1. In the User's Terminal Server session, click Start > Programs > Novell iPrint > iPrint Client, then click the Proxy tab.

2. Select the Use a proxy Server for iPrint Printing check box.

3. In the Proxy URL field, type the external firewall proxy address of the proxy server, then click OK.

When the proxy address is set, the printer policy distributes without a problem.

6.7 iPrint Printer Drivers Fail to Distribute to Workstations Authenticating to Linux Desktop Management Servers

If user authenticates to a Desktop Management Server installed on a Linux server (OES or SLES 9), the iPrint client will be distributed to their desktops, but the iPrint printer drivers will not be distributed to their desktops.

This is a known issue in one of the ZENworks Desktop Management Agent files and will be corrected in a future version of the Desktop Management Agent.

6.8 Novell iPrint Policy on Novell SUSE LINUX Enterprise Server 9 (SLES9) Does Not Run

The Novell iPrint policy (User and Workstation packages) does not run in a SUSE LINUX Enterprise Server 9 only environment. In order to run the Novell iPrint client, you must have at least one NetWare server in your system.

7.1 Nal.exe and Nalexpld.exe

Although nal.exe and nalexpld.exe are included in the product and still launch executables, their purpose is to facilitate the continued functioning of existing login scripts.

ZENworks 7 Desktop Management only supports switches that are supported by nalwin32.exe. To see a list of these switches, enter the following command:

nalwin32.exe /?

You see the same switches if you enter the following command:

nalwin.exe /?

7.2 Choosing File > Exit Application Explorer Does Not Close the Application Explorer Window

It is currently not possible to close the Application Explorer window using the Exit Application Explorer option on the File menu.

To close the Application Explorer, click the Close (X) button on the upper right-hand corner of the Application Explorer window.

7.3 Dragging an Application Icon from the Application Window to the Windows Desktop Results in a Broken Shortcut

Although you can drag an application icon from the right-hand pane of the Application Window view to the Windows desktop, doing so creates a broken shortcut that will not launch the application.

You can work around this issue by launching the Application Explorer view after you create the shortcut. Launching the Application Explorer causes the shortcut to work properly. Later, when you close the Application Explorer, the shortcut is removed from the desktop.

7.4 Using Myapps.html As a Desktop Background on a Windows XP Workstation

If a user sets the option of using a myapps.html as the Web page background for their Windows XP desktop, Windows XP generates script errors and myapps.html will not display applications.

If you want users to use this feature, you need to edit portions of the myapps.html that this feature can't handle. The easiest method is to extract the data from WriteData() function in the file and use it as the content of a new .html file.

The comments of the Web page will look like this:

<head>

<title>Novell Delivered Applications</title>

</head>

<body scroll='no' style='margin: 0; overflow:hidden'>

<object id="AxNalView" classid="CLSID:4F4B2E32-B44C-450E-8683-6903FE9DDCEA" width="100%" height="100%">

<!--param name="SingleTree" value="ZENWORKS_TREE"-->

<!--param name="PortalView" value="false"-->

<!--param name="BannerURL" value="http://www.company.com/banner.html"-->

<!--param name="BannerHeight" value="80"-->

<!--param name="ShowTree" value="true"-->

<!--param name="ShowTasks" value="false"-->

<!--param name="AppDisplayType" value="1"-->

<!--param name="ShowAppFrameNavigation" value="true"-->

<!--param name="ShowIEToolbarButton" value="true"-->

</object>

</body>

</html>

Save this file to the hard drive. You can then use it as an XP background.

7.5 Accessing a Web Page Containing Japanese Characters from the Apache Web Server

If you access a Web page served by the Apache Web Server, and if that Web page contains Japanese characters, such as the Japanese version of myapps.html, the characters on that page might appear garbled.

This is a known issue with the Apache Web Server, and can be corrected with a simple configuration workaround in Apache. To better understand the problem, see the Sun Developer Network site for an article entitled Creating Multilingual Web Sites with Apache. For specific information about how to work around the problem and configure the server, see the Apache HTTP Server Version 2.0 Documentation article entitled Content Negotiation.

7.6 Application Launcher Plug-In Does Not Support Thin Client Applications

The ZENworks 7 Desktop Management version of myapps.html (part of the Application Launcher Plug-in) does not include functionality to launch thin client applications from a Windows Terminal Server.

If you want users to launch thin client applications, you need to install the ZENworks Management Agent on user workstations.

The next release of ZENworks Desktop Management will add functionality to the Application Launcher Plug-in installation to allow launching of thin client applications from workstations.

7.7 Application Objects Are Not Visible if Launched from a Remote Terminal Session

The new Terminal Server system requirement on an Application object applies only to remote Terminal Server sessions. Sessions running at the Terminal Server console are considered to be remote sessions by default. This behavior can be changed by creating the following registry key on the Terminal Server itself:

HKEY_LOCAL_MACHINE\Software\Netware\Nal\ConsoleIsNotTS

Creating this registry key will cause sessions running on the Terminal Server console to be treated as non-Terminal Server sessions.

7.8 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.

7.9 Uninstalling Applications Does Not Force a Workstation Reboot

When a distributed application is configured to be uninstalled from a workstation, the workstation does not currently prompt for a reboot when the uninstall is complete.

Because the uninstall might affect the Windows registry, other applications reading the registry at startup might be adversely affected unless the workstation is rebooted. Users should always reboot manually after a distributed application is uninstalled.

7.10 Uninstalling an .Ini File Application

If you configure an .ini file application to be uninstalled with the Create Or Append To Existing Value attribute selected for uninstall, the value that was added during the original installation is not removed.

The only current workaround for this issue is a manual edit of the .ini file.

7.11 Using Software License Metering and Monitoring

A key component of Novell Licensing Services, nls32.dll, does not ship with the current Novell Client. 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 of the Companion 1 CD 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.

7.12 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.

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.

7.13 Error is Displayed When Installing a Workstation Associated MSI Application

If you try to distribute a workstation associated MSI Application that has not had the Distribute in Workstation Security Space if Workstation Associated option selected and if the workstation launch cache is disabled when the application distribution is attempted, an error will be generated to inform you that the application distribution is unsuccessful.

The distribution fails because the Application Launcher tries to read the MSI application attributes with user privileges. User privileges are not recognized because writing to the launch cache is disabled, and the user does not have privileges to the Application Object outside the cache.

To avoid this error, do one of the following:

• Make sure that the Distribute in Workstation Security Space if Workstation Associated option is selected for the MSI application.
• Do not disable writing to the launch cache on the workstation.
• Grant users Read rights to the MSI Application object in eDirectory.

7.14 Applications Configured for Force Cache Might Abend a CIFS Server

When several Application objects previously set for Force Cache are accessed by the Novell Application Launcher running against a NetWare 6.5 server with cifs.nlm loaded, the NetWare server might abend when the first application is cached.

We have identified the problem and fixed it in a NetWare 6.5 SP1 patch and in NetWare 6.5 SP2.

7.15 Workstation Associated Applications Are Not Available on Workstation Import

Workstation associated applications will be available to users on the first reboot following a successful import of the workstation to an eDirectory tree.

7.16 Cannot Import or Export AOT or AXT Files From ConsoleOne On a Windows XP Workstation With 4.x Agent Installed

If you run ConsoleOne and ZENworks 7 snap-ins locally from a Windows XP workstation where the ZENworks for Desktops 4 SP1b or 4.0.1 Desktop Management Agent has also been installed, you will not be able to import or export AOT or AXT files from ConsoleOne on that workstation. Doing so will cause ConsoleOne to crash.

We recommend that you avoid using this combination of software if you want to use ConsoleOne to import or export AOT or AXT files.

Instead, you should launch a local copy of ConsoleOne from a workstation that has the ZENworks 7 Desktop Management Agent installed. This copy should not contain the ZENworks for Desktops 4 SP1b or ZENworks for Desktops 4.0.1 snap-ins.

7.17 Error Displays When a SnAppShot of a Windows XP Application is Created

If you try to create an AOT/AXT of a Windows XP application using SnAppShot, an error might display informing you that the SnAppshot failed to copy a file from the c:\windows\softwaredistribution directory.

The error occurs because the c:\windows\softwaredistribution folder has not been added to the exclusion list.

If you have not yet begun to create the AOT/AXT, we recommend that you manually add c:\windows\softwaredistribution to the exclusion list.

If you have already begun the snAppShot process and received the error, we recommend the following workaround procedure:

1. From the error message, note the name of the file that could not be copied, then click Ignore on the error message dialog box to skip copying the file to the .fil directory.

2. Import the AOT/AXT into ConsoleOne.

3. Remove the entry for the uncopied file from the App Files tab of the AOT/AXT Application object.

7.18 Error Displays After Creating an Application in SnAppShot on Japanese Version of Windows XP

When you create an application in snAppShot on a Japanese-enabled Windows XP workstation and then browse the applications install directory, the following error might be displayed:

External Exception C0000006

This issue will be addressed in the next release of snAppShot.

7.19 Application Distribution from a Cluster Resource Times Out and Displays an Error During Cluster Migration

If you initiate the distribution of Application object from a cluster resource and then initiate a cluster resource migration before the distribution is complete, the distribution might time out before completing and will generate an error.

To work around this issue, you need to manually relaunch the distribution.

7.20 Importing Application Object Settings Fails if Files Are Located in a Path with a Long Name, Extended Characters, or Spaces

If you attempt to import an existing Application object's .fil files or registry keys when you create new Application object, the import of that information will fail if the location of the older information is located in a path that includes a folder name with a more than 8 characters, a space, or an extended character.

7.21 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 7 Desktop Management 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 7.

8.1 Upgrading to a Dynamic Disk System on Windows 2000 Workstations

Upgrading a Windows 2000 workstation hard disk from a Basic Disk System to a Dynamic Disk System changes the partition table so that it does not allow the workstation to boot to the production partition, only to the Desktop Management Linux* partition. No fixes for this issue are included in ZENworks 7 Desktop Management.

The Workstation Imaging component of ZENworks 7 does not support dynamic disks. If you upgrade your disks, you will no longer be able to use Workstation Imaging.

8.2 Unable to Choose an IP Address on a Windows 2000 Imaging Server with Multiple Network Interface Cards

If you install the ZENworks 7 Desktop Management Workstation Imaging component to a Windows 2000 server that has more than one network interface card (NIC), you do not have the option of binding the imaging proxy server to a specific IP address.

If you install Workstation Imaging to a NetWare server, you can bind the imaging proxy server to a specific IP address (that is, the NIC of your choice) by using the following switch:

load imgserv -i:IP_Address

8.3 ZENworks 7 PXE-On-Disk Does Not Support Some Network Adapters

The PXE-on-Disk Setup utility does not detect nor display drivers for PXE-compatible network adapters that are manufactured by NETGEAR, Inc.

8.4 Imaging Boot Diskettes Do Not Include USB Drivers

The five boot disks created with zimgboot.exe do not have enough room to include all files, including USB drivers.

If a workstation requires USB drivers, users may see error messages similar to one of the following:

Load USB Modules /bin/runme.s: /lib/modules/2.4.22/kernel/drivers/usb No Such File or Directory

or

Load USB Modules /bin/runme.s: /lib/modules/2.4.22/kernel/drivers/usb/storage No Such File or Directory

If users whose workstations require USB drivers encounter these errors, you should prepare an imaging boot CD for their workstations. An imaging boot CD has enough space to include the proper USB drivers.

9.1 Issues with the 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.

9.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.

9.3 Remote Control with a Full-Screen DOS Window

During a remote control session on the managed workstation, if you change the mode of display from DOS box application mode to full-screen mode, you do not receive updates until you change to the normal mode or close the DOS box.

9.4 Remote Control of Windows XP Workstations After a Remote Desktop Session

If a user uses the Remote Desktop Connection to connect to a Windows XP workstation, and then initiates a Remote Control session on that workstation, the Remote Control console will be black and you will not be able to remote control it.

Users with a Windows XP workstation should log in locally before you attempt to remote control their workstations.

9.5 Removing Wallpaper During a Remote Session

During a Remote Control session, you might not be able to remove the active desktop wallpaper on the managed workstation. This affects Remote Management performance.

To work around this problem, you must manually suppress the wallpaper of the managed workstation.

9.6 Behavior of Wallpaper Suppression on Windows XP

For wallpaper suppression, Windows XP behaves differently from other Windows operating systems. When you set the wallpaper, Windows XP creates a backup of it. When you disable the wallpaper, it is disabled from the primary location only. When you change the settings, the wallpaper might resurface.

9.7 Cursors Are Not Supported for Remote Management

Animated and the colored cursors on the managed workstation are not supported for Remote Management.

9.8 Mouse Cursor on a Windows XP Managed Workstation Flickers During a Remote Management Session

During a Remote Management session with a Windows XP managed workstation, if you place the mouse cursor on a window that is continuously changing (for example, Task Manager), the mouse cursor flickers at the managed workstation. This cursor behavior is apparent at the managed workstation only.

9.9 Wake-On-LAN Service Might Not Wake Up Target Workstations

Wake-on-LAN service running on NetWare 6.5 SP1a (and later) server might not wake up target workstations if the schedule is modified.

To work around this problem, try restarting the service.

9.10 DirectX Applications Do Not Run In Exclusive Mode During a Remote Control or a Remote View Session

On Windows 2000/XP workstations, DirectX applications do not run in exclusive mode during a Remote Control or a Remote View Session.

9.11 Novell ZENworks Remote Management Service Is Not Created If the Service Control Manager Is Running During the Remote Management Upgrade on Windows 2000/XP Workstations

If the Service Control Manager is running when the Remote Management Agent is upgraded to ZENworks 7, the Novell ZENworks Remote Management Service is not created, even after you restart the managed workstation.

To resolve this problem, ensure that the Service Control Manager is closed before upgrade.

9.12 The Status of the ZENworks Wake-On-LAN Service on a Linux Server Might Display as "Missing"

When you restart a Linux server where the ZENworks Wake-On-LAN service is installed, the boot login screen might display the Wake-On-LAN service as missing even though the Wake-On-LAN services run appropriately. You can ignore the message.

9.13 The Remote Management Password is Not Retained When Upgrading Remote Management Agent on Windows 98 Workstations

On a Windows 98 workstation, when you upgrade the Remote Management Agent from ZENworks for Desktops 4.0.1, ZENworks 6.5 Desktop Management or ZENworks 6.5 Desktop Management Support Pack 1 to ZENworks 7, the Remote Management password, if set, is deleted.

Workaround: At the command prompt, enter the following command:

msiexec /i "path_of_MSI zfdagent.msi" REINSTALLMODE=vamus

If you are installing via MSI application object, specify vamus in the REINSTALLMODE property.

IMPORTANT:  This workaround is applicable only if you are upgrading from ZENworks 6.5 Desktop Management or a later version of the Desktop Management Agent.

9.14 Remote Management Help 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.

9.15 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 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.

10.1 Reinstalling the Inventory Server or the Inventory Database on Linux

If you want to reinstall the Inventory Server or the Inventory Database on Linux, you must first uninstall the component you want to reinstall, then proceed with installing the component again.

10.2 The Inventory Service Might Fail to Start on a NetWare 6.5 SP2/SP3 or NetWare OES Server

If you install the Inventory server component of ZENworks 7 Desktop Management on a NetWare 6.5 SP2/SP3 or NetWare OES server, the Inventory service might fail to start after the installation.

Workaround: Manually start the Inventory service.

10.3 Double-Byte Characters Are Not Supported in the SCANDIR Path if the Novell Client Is Not Installed on Inventoried Workstations

If the Novell Client is not installed on inventoried workstations, and if you use double-byte characters in the Inventory Service object's scan directory (scandir) path, the .str files are not transferred to the Inventory server.

By default, the scandir path is the installation path where the Inventory server-side components and the database are installed (unless you manually changed it after the ZENworks 7 Desktop Management installation by configuring the Inventory Service object).

10.4 Navigating Inventory Reports Using the Keyboard

The Crystal Report Viewer window does not support keyboard functionality. You must use the mouse to perform all operations in the viewer window.

11.1 Launching an RDP or ICA Application from the Launch Item Gadget Generates an Error on a Windows XP SP2 Workstation

Launching an RDP or ICA application from the Launch Item Gadget on a Windows XP SP2 workstation generates the following error message:

To help protect your security, Internet Explorer stopped this site from installing software on your computer. Click here for options...

If users are using Windows XP SP2 (or greater) workstations, they can click on the information bar at top of Plug-in dialog box in order to install the Citrix ICA/RDP client. Alternatively, you can have users contact you for help with installing the Citrix ICA/RDP client.

11.2 No Support for DNS-Rooted or Federated Trees

ZENworks 7 Desktop Management does not support DNS-rooted trees or federated trees.

11.3 Some ConsoleOne Properties Pages Have Been Consolidated

In the shipping version of ZENworks for Desktops 4.x, the property pages for User, Workstation, and Container objects in ConsoleOne included an Application Launcher and an Applications tab.

With ZENworks 7 Desktop Management, these two pages are now consolidated under the ZENworks tab in the User, Workstation, and Container objects.

11.4 Workstation Import and Workstation Management Do Not Work with VPN

Workstation Import and Workstation Management (that is, policies pushed to workstations or users) may work differently when users connect through a VPN.For more information, see TID 10096902 in the Novell Support Knowledgebase.

11.5 ZENworks Database Might Display False Message

If you have installed either the Desktop Management Database or the Inventory Database on a NetWare server, the following error message might be displayed during database operations:

Connection terminated abnormally

This is a false message and can be ignored.

11.6 Creating a Stream Attribute Fails in ConsoleOne Running on a Windows Machine

If you are running ConsoleOne on a Windows machine configured with two different IP Addresses on two different networks, ConsoleOne will not be able to send data to eDirectory and will generate an error code.

You may see this behavior if you attempt to create a stream attribute against eDirectory running on a SUSE Linux server.

11.7 Interoperability with NSure SecureLogin

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

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