Novell ZENworks 10 Configuration Management with SP1 (10.1)

May 13, 2009

2.7 CASA
2.11 Imaging
2.25 Zman

1.0 Overview

The issues included in this document were identified for Novell® ZENworks® 10 Configuration Management with SP1 (10.1).

For installation instructions, see the Novell ZENworks Configuration Management Installation Guide.

For information about the new features or enhancements, see the Novell ZENworks Configuration Management Upgrade Guide.

For administrative tasks, see the Novell ZENworks 10 Configuration Management with SP1 (10.1) documentation Web site.

This product contains undocumented utilities that Novell Technical Services might use to diagnose or correct problems.

The following table contains information on the documentation content changes that were made in this Readme after the initial release of ZENworks 10 Configuration Management (10.1):

Table 1 Readme Updates

Date

Readme Item Added or Updated

May 13, 2009

Modified The report layouts of the predefined reports can be modified only by the user who logs in to the Reporting Server with the username as Administrator.

December 3, 2008

Re-organized the information in Section 2.20, Reporting

October 8, 2008

August 18, 2008

Updated A Java exception error occurs when clicking the Vulnerabilities tab.

January 23, 2009

Added Unsupported workstation tasks and actions are enabled for Linux devices.

January 28, 2009

Added New patch content is no longer being downloaded.

2.0 Known Issues

This section contains information about ZENworks Configuration Management issues that might occur.

2.1 Installation

This section contains information about the issues that might occur when you install ZENworks Configuration Management.

2.1.1 DNS, if used, must be set up correctly for ZENworks Control Center to be accessible

If you are using DNS, it must be properly set up, or some features in ZENworks might not work. For example, the ZENworks Control Center (ZCC) icon that is installed to the desktop on the server might fail to open ZCC in the browser.

Workaround: Reconfigure DNS to work properly, then such issues as ZCC not displaying should be resolved.

2.1.2 Zenloader does not start after installing on a machine running Windows Server 2008

(Fixed in v10.1.1) The Novell ZENworks Loader service sometimes does not start after installing on Windows* Server* 2008.

Workaround: Manually start the Novell ZENworks Loader service.

2.1.3 Installing an external MS SQL database requires an existing path

If you select to install a new Microsoft* SQL database during installation of Configuration Management, the path must already exist. You cannot create the database’s directory during installation.

Workaround: Create the directory for the MS SQL database before starting the installation program.

2.1.4 Installing to an Oracle database fails to run the localization-updater.sql SQL script

The following error might be reported during installation to an Oracle* database:

Failed to run the sql script: localization-updater.sql, message:Failed to execute the SQL command: insert into zLocalizedMessage

Workaround: Change the character set on your Oracle database to UTF-8.

2.1.5 Installing a second server gives an error message

When you are installing the second server into a Management Zone, an error message might be displayed at the end of the installation that contains the following text somewhere in the message:

... FatalInstallException Name is null

However, the installation otherwise seems to complete successfully.

This error is being displayed erroneously because the program thinks that the server needs to be reconfigured, but it doesn't.

Workaround: Review the installation log file. If there are no errors there related to this error message, you can ignore it.

2.1.6 Configuration Management installation might fail on 64-bit Windows Server 2003 and 64-bit Windows Server 2008

If you are installing to a 64-bit Windows Server 2003 or 64-bit Windows Server 2008, the installation might fail because of the Windows msiexec utility. The following message is logged in the installation log:

Msiexec returned 1603:

Workaround: None.

2.1.7 Windows Server 2008 Core is not supported as a Primary Server or managed device

You cannot install the Primary Server or the ZENworks Adaptive Agent on Windows Server 2008 Core because the .NET framework is not supported on Windows Server 2008 Core.

Workaround: None.

2.1.8 Some ZENworks partitions must be fixed in order to work with Configuration Management

If your environment is running the Novell ZENworks Linux Management - Dell Edition and you created ZENworks partitions on your clients, when the partition is booted to update your clients to ZENworks 10 Configuration Management, the partition no longer works and fails the update.

Workaround: Before you install ZENworks 10 Configuration Management to your environment, create a scripted imaging task and force all ZENworks partitions to run it in preparation to update to Configuration Management.

Create the following script to fix the /etc/ZUpudate.sig file contained in the initrd resource file:

export PATH=/sbin:/usr/sbin:/bin:/usr/bin:/lbin
mount $ZENDEVICE /mnt/harddisk
cp /mnt/harddisk/boot/loader/initrd /initrd.gz
#make a backup of initrd
cp /mnt/harddisk/boot/loader/initrd /mnt/harddisk/boot/loader/initrd.sav
gunzip /initrd.gz
mount -o loop /initrd /mnt/cdrom
cp /mnt/cdrom/etc/ZUpdate.sig /
dos2unix /ZUpdate.sig
cp /ZUpdate.sig /mnt/cdrom/etc
umount /mnt/cdrom
gzip -v9c /initrd > /mnt/harddisk/boot/loader/initrd
umount /mnt/harddisk

2.1.9 Time synchronization causes invalid certificate errors

If time is not synchronized on the network before you install the ZENworks Configuration Management services, you see invalid certificate errors because the certificates have dates that are in the future, and therefore are considered invalid.

Workaround: Make sure that your network has its time synchronized before you install the Configuration Management services. Make sure to include ZENworks back-end servers in the synchronization.

2.1.10 ZENworks 10 Reporting Server with SP1 requires ZENworks 10 Configuration Management with SP1 to be installed

ZENworks 10 Configuration Management with SP1 must be installed on the Primary Server before installing ZENworks 10 Reporting Server with SP1.

2.1.11 ZENworks Reporting Server cannot be installed on 64-bit servers

You cannot install ZENworks Reporting Server to a Primary Server running a 64-bit operating system.

2.1.12 On Windows XP, installing the ZENworks Adaptive Agent with the Remote Management component through Remote Desktop Connection fails

If you remotely connect to a managed device by using Remote Desktop Connection (RDP), then download and install the ZENworks Adaptive Agent, the installation does not complete and the Remote Desktop Connection program stops working.

Workaround: To fix the issue, download the patch from the Microsoft Support Web site and install it on the managed device.

2.1.13 AdminStudio ZENworks Edition requires the Primary Server to be using ports 80 and 443

During product installation, you have the option to select ports other than the defaults of 80 and 443, but AdminStudio requires the Primary Server to use ports 80 and 443.

Workaround: None. To use AdminStudio, you must install it on a Primary Server that is using ports 80 and 443.

2.1.14 Only one instance of AdminStudio must be installed in a management zone

Only one instance of AdminStudio must be installed in a management zone. However, it is not possible to detect the machine that has AdminStudio installed in the ZENworks Control Center.

If you install more than one instances of AdminStudio in a management zone, the Invalid Usage error message is displayed when you run AdminStudio.

Workaround: To troubleshoot the Invalid Usage error message, do the following:

  1. Run the removeusage.exe utility located in c:\program files\macrovision\adminstudio\8.5\common.

  2. Uninstall the AdminStudio ZENworks Edition.

  3. Install the AdminStudio ZENworks Edition.

2.1.15 ConfigureAction fails because of an error detected by HotSpot Virtual Machine

If you are installing the first Primary Server on a Linux* device, and if at the end of the process that configures the database you see an error has occurred and you are given the option of continuing or rolling back, you should check the log file at /var/opt/novell/log/zenworks/ZENworks_Install_[date].log.xml. If you see the error specified below, it is safe to continue with the install.

ConfigureAction failed!:
select tableName, internalName, defaultValue from Adf where inUse =?#
An unexpected error has been detected by HotSpot Virtual Machine:
#SIGSEGV (0xb) at pc=0xb7f6e340, pid=11887, tid=2284317600
#
#Java VM: Java HotSpot(TM) Server VM (1.5.0_11-b03 mixed mode)
#Problematic frame:
#C [libpthread.so.0+0x7340] __pthread_mutex_lock+0x20

Workaround: Ignore the error message.

2.1.16 ZENworks Configuration Management uninstallation fails on Linux devices that have Mono 1.9-5

Workaround: None.

2.1.17 Unable to install NetIdentity from Novell Client 32 on a device that has ZENworks Configuration Management installed

When you try to install the NetIdentity agent that ships with Novell Client32™ on a device that has ZENworks Configuration Management installed, the installation fails with the following error message:

An incompatible version of Novell ZENworks Desktop Management Agent has been detected

This error is displayed because the NetIdentity agent must be installed before installing ZENworks Configuration Management

Workaround: Do the following:

  1. Uninstall ZENworks Configuration Management.

    For more information on how to uninstall ZENworks Configuration Management, see the ZENworks 10 Configuration Management Installation Guide

  2. Install the NetIdentity agent from Novell Client32.

  3. Install ZENworks Configuration Management.

    For more information on how to install ZENworks Configuration Management, see the ZENworks 10 Configuration Management Installation Guide

2.2 Actions and Quick Tasks

This section contains information about action and quick task issues when using ZENworks Configuration Management.

2.2.1 Unsupported workstation tasks and actions are enabled for Linux devices

Linux devices as workstations are not supported, but Linux devices are supported as Primary Servers and Satellite Servers. If you click Devices > Servers (or Workstations for a Satellite Server), then select a Linux device and click Action (or Quick Tasks), some unsupported workstation-related actions or quick tasks appear in the drop-down list as enabled. If you select an unsupported action or quick task, it will not work, giving an error or exception message.

Workaround: Do not use any of the following unsupported workstation-related actions on Linux devices:

  • Assign Policy

  • Assign Bundle

  • Remote Control

  • Remote Diagnostics

  • Unblock Remote Management

  • Take an Image

  • Apply Assigned Imaging Bundle

  • Apply Rule-Based Imaging Bundle

  • Cancel Imaging Work

Also, do not use any of the following unsupported workstation-related quick tasks on Linux devices:

  • Refresh Policies

  • Inventory Scan

  • Inventory Wizard

  • Install Bundle

  • Uninstall Bundle

  • Launch Bundle

  • Run Script

2.3 Accessibility

This section contains information about accessibility issues when using ZENworks Configuration Management.

2.3.1 Keyboard support for selecting an application on the toolbar is not working

By default, Windows does not provide keyboard support for the toolbar.

Workaround: Enable the accessibility options in Windows and use the Accessibility Wizard to enable mouse key settings. Then, mouse functions are controlled by using the numeric keypad.

2.4 Asset Inventory

This section contains information about the issues that might occur with Asset Inventory in ZENworks Configuration Management.

2.4.1 Apply the August 2008 (or later) PRU before upgrading to ZENworks Configuration Management with SP1 (10.1)

If you are upgrading to ZENworks Configuration Management with SP1 (10.1), it is recommended that you apply the August 2008 (or later) PRU to your current installation before performing the upgrade.

2.5 Asset Management

This section contains information about the issues that might occur with Asset Management in ZENworks Configuration Management.

2.5.1 The ZENworks Asset Management Migration Utility does not support Oracle databases

The Asset Management Migration Utility that is included in this version of ZENworks Configuration Management does not support migrating Asset Inventory or Asset Management data to or from an Oracle database.

Workaround: None.

2.5.2 Submit purchase record import files one at a time

When submitting multiple purchase record import files, wait until the previous file has finished importing before going on to the next.

2.5.3 The custom report screen does not show updated “last run” date until manually refreshed

After you run a custom report, the “last run” date is not refreshed automatically.

Workaround: Press F5.

2.5.4 The software usage custom report screen does not automatically show new or saved reports

If you create and run a new report, the report does not display in the report list.

Workaround: Navigate out and then back to the page.

2.6 Bundles

This section contains information about the issues that might occur when you use bundles in ZENworks Configuration Management.

2.6.1 Directive bundles might be shown as effective even though bundles cannot be assigned to Linux devices

Because Linux devices cannot have the ZENworks Adaptive Agent, you cannot assign bundles to be sent to them. However, in ZENworks Control Center, Directive bundles assigned to a Linux device might show as effective, which is incorrect.

Workaround: None.

2.6.2 The Registry Edit action cannot both back up the entire registry and edit HKEY_CURRENT_USER on Windows Vista

If you set up an action to both back up the registry and edit the HKEY_CURRENT_USER registry entry on Windows Vista*, the action fails because all user-initiated processes in Vista run as the lowest privileged user.

Workaround: Use two different registry actions, one to back up the registry in the system context, and another to edit HKEY_CURRENT_USER in the user context.

2.6.3 The Undo Install Actions action fails to uninstall a directory if the directory name contains spaces

When you create an Install Directory File bundle, the directory is installed even if its name contains spaces; however, it cannot currently be uninstalled by using the Undo Install Actions action.

Workaround: Avoid spaces in directory names if you want to enable the uninstallation of that directory.

2.6.4 If the Wake-on-LAN schedule on the managed device is behind the server’s time zone, the device fails to wake up

Workaround: None.

2.6.5 Unable to launch a RDP session from a 64-bit device

If you launch a Launch Windows Thin Client Application action configured with the RDP Session on a 64-bit managed device, the action might fail.

Workaround: Apply the KB925876 patch.

2.6.6 Unable to select an icon with the 64-bit Internet Explorer

If you use the 64-bit Internet Explorer to launch ZENworks Control Center, then click the browse icon to browse to and select an icon from the icon resources such as an.exe, .dll, or .ico file, the first icon of the resource file is selected by default. You cannot select any other icon.

Workaround: Use the 32-bit Internet Explorer to launch ZENworks Control Center.

2.7 CASA

This section contains information about the issues that might occur with CASA in ZENworks Configuration Management.

2.7.1 CASA fails to use HTTP proxy settings for initial authentication

CASA does not completely authenticate via the HTTP proxy during initial authentication, but instead contacts the Primary Server directly. After authentication, all CASA traffic goes through the HTTP proxy when using the ZENworks Adaptive Agent Logout/Login feature.

Workaround: Access rules must allow access to ports 80, 443, and 2645. Additionally, HTTP forward proxy settings must be configured in two locations:

  • Device Management in ZENworks Configuration Management uses the WinInet HTTP protocol. Therefore, forward proxy settings must be configured in Internet Explorer*: Click Tools > Internet Options > Connections > LAN Settings > Proxy Setting.

  • Device Management in ZENworks Configuration Management uses CASA authentication, which uses WinHTTP Services. WinHTTP requires proxycfg.exe. For example:

    proxycfg -p forward_proxy_IP_address:8080
    

    For more information on proxycfg.exe, see ProxyCfg.exe, a Proxy Configuration Tool.

2.8 Closest Server Rules

This section contains information about the issues that might occur when you use the Closest Server rules in ZENworks Configuration Management.

2.8.1 Using the Exclude the Closest Server Default Rule option

When you use this option, be sure to include at least one server in the Configuration section of the rule. Otherwise, after a managed device has been refreshed with this configuration, it cannot subsequently obtain new zone configuration data of any kind because it no longer knows of any servers to contact for this information.

2.8.2 L4 switch definitions are not synchronized across rules

After you create an L4 switch definition in the Default Closest Server Rules page, then add it to one or more custom Closest Server rules, any modifications that you make to the L4 switch definition (including definition deletions) are not propagated to any of the custom Closest Server rules.

2.9 Discovery and Deployment

This section contains information about the issues that might occur when you use the Discovery and Deployment functions in ZENworks Configuration Management.

2.9.1 Refreshing the Deployment page causes Discovery tasks to be repeated

It is normal for a Web browser to resend information in order to refresh a page. ZENworks auto-updates the data on a Deployment page every 5 seconds, so you should not need to refresh the Deployment page after running a Discovery task. If you do refresh the Deployment page in ZENworks Control Center after running a Discovery task, you are asked to confirm the resend in order to refresh the page. Do not do this, or the Discovery task runs again.

Workaround: Do not refresh the Deployment page after running a Discovery task. Instead, exit the page and return to see any changes.

2.9.2 Orphaned and deleted files are not cleaned up from a deployment task that uses a proxy

Orphaned or to-be-deleted files from a pre-task or post-task action during a deployment task that uses a proxy are not cleaned up.

For example, if you run the deployment task from a Linux server through a Windows proxy, there is a folder created in the zenworks_installation_directory\novell\zenworks\bin\_rfu_cache directory on the Windows device that contains the pre-task or post-task command file. If you delete the task in ZENworks Control Center, the command file is left on the Windows proxy device. However, all command files older than five days are removed when another deployment task is run by using the same Windows proxy.

Workaround: To immediately delete the orphaned files from the zenworks_installation_directory\novell\zenworks\bin\_rfu_cache directory, you must manually delete it.

2.9.3 Deployment of the ZENworks Adaptive Agent to Windows Vista or Windows Server 2008 does not prompt for a reboot

Even if you deselected the Do Not Prompt for Reboot option when you created the deployment task, you still do not get a reboot message when you deploy to Windows Vista or Windows Server 2008.

Workaround: None.

2.9.4 Creating an LDAP Discovery task for a Linux Primary Server prompts you to configure the Windows Proxy

(Fixed in v10.1.1) When you are creating the LDAP Discovery task for a Linux Primary Server, you are prompted to configure the Windows proxy even though the LDAP Discovery task for Linux Primary Server does not require the Windows proxy to be configured. However, you are not prompted to configure the Windows proxy if it has been configured at the management zone level.

Workaround: Before creating the a LDAP Discovery task, configure the Windows proxy at the management zone level:

  1. In ZENworks Control Center, click the Configuration tab.

  2. In the Management Zone Settings panel, click Discovery and Deployment > Windows Proxy.

  3. Configure the Windows Proxy settings.

2.9.5 Couple of ZENworks related files might be reported as a malicious software during the ZENworks Adaptive Agent installation

During the ZENworks Adaptive Agent installation, couple of ZENworks related files might be reported as a malicious software by the anti-virus software. Consequently, the installation abruptly stops.

Workaround: Do the following on the managed device where you want to install the ZENworks Adaptive Agent:

  1. Manually add System_drive:\windows\novell\zenworks to the Exclusion list of the anti-virus software installed on the managed device.

  2. Install the ZENworks Adaptive Agent.

2.10 File Access

This section contains information about the issues that might occur for access to files in ZENworks Configuration Management.

2.10.1 ActiveX controls are signed and Firefox extensions are activated for uploading files to ZENworks servers

You can uninstall ActiveX* controls or Firefox* extensions.

  • ActiveX Controls: Go to c:\windows\downloaded program files, right-click nfileupload class, then select Remove.

  • Firefox Extension: In Firefox, click Tools > Extensions, select Novell File Upload, then click Uninstall.

2.11 Imaging

This section contains information about the issues that might occur when using Imaging in ZENworks Configuration Management.

2.11.1 ZENworks Image Explorer (zmgexp) crashes when viewing the property of a file or directory within the add-on image

(Fixed in v10.1.1) The ZENworks Image Explorer (zmgexp) crashes when you select a file or directory within an add-on image, then click File > Properties.

Workaround: Use the following ways to view the property of a file or directory within an add-on image:

  • If you have the Imaging component of ZENworks 7 Desktop Management installed, use Image Explorer (imgexp.exe). For more information on Image Explorer (imgexp.exe), see the ZENworks 7 Desktop Management documentation.

  • If you have only ZENworks Configuration Management installed, contact Novell Support.

2.11.2 Adding, Removing, or Configuring the Imaging Satellite Server role on a managed device that is upgraded from the previous version of ZENworks Configuration Management might display error messages

(Fixed in v10.1.1) If you add, remove, or configure the Imaging Satellite Server role on a managed device that is upgraded from the previous version of ZENworks Configuration Management, the Imaging Satellite Server task is assigned to the device only during the next device refresh schedule. If you want the task to be immediately assigned, you must manually refresh the device in one of the following ways:

  • In the Configuration tab > the Server Hierarchy, select the check box next to the devices you want to refresh, click Action > Refresh Device.

  • On the managed device, right-click the ZENworks icon, then click Refresh.

However, the following error message might be logged in the device’s message log in ZENworks Control Center when you refresh the device even though the Imaging Satellite Server task has been successfully executed:

ERROR{}

The following error message might be additionally logged if the Imaging Satellite Server role is added to the device:

Promotion of the corresponding ZMD to Imaging Server Failed.Enable the Debug option and Check the ZMD Log file for more Details.

Workaround: Ignore the error messages.

2.11.3 Imaging does not work if the Primary Server uses the non-default ports

You cannot perform Imaging operations if the Primary Server does not use the default ports (80 or 443).

Workaround: Do the following:

  1. Manually edit novell-zenimgweb.conf to update HTTP_PORT and HTTPS_PORT with the values entered for HTTP and HTTPS during the ZENworks Configuration Management installation. The novell-zenimgweb.conf file is located in the /etc/opt/novell/zenworks/preboot/ directory on Linux and in the %ZENWORKS_HOME%\conf\preboot\ directory on Windows.

  2. Restart the Novell ZENworks Preboot service.

    • On Linux: At the server console prompt, enter /etc/init.d/novell-pbserv restart.

    • On Windows: Do the following:

      1. From the Windows desktop Start menu, click Settings > Control Panel.

      2. Double-click Administrative Tools > Services.

      3. Start the Novell ZENworks Preboot Service.

2.11.4 Imaging does not work on the Imaging Satellite Server if the Primary Server uses the non-default ports

(Fixed in v10.1.1) You cannot perform Imaging operations on the Windows Imaging Satellite Server if the Primary Server does not use the default ports (80 or 443).

Workaround: Do the following on the Imaging Satellite Server:

  1. Manually edit %ZENWORKS_HOME%\conf\preboot\novell-zenimgweb.conf to update HTTP_PORT and HTTPS_PORT with the values entered for HTTP and HTTPS during the ZENworks Configuration Management installation.

  2. Restart the Novell ZENworks Preboot service.

    1. From the Windows desktop Start menu, click Settings > Control Panel.

    2. Double-click Administrative Tools > Services.

    3. Start the Novell ZENworks Preboot Service.

2.12 Logging In

This section contains information about the issues that might occur when logging in to various locations in ZENworks Configuration Management.

2.12.1 Login to ZENworks Control Center fails in Internet Explorer when using unsupported DNS characters in the server name

A Microsoft security fix (see Microsoft Knowledge Base article 312461) disallows certain characters in DNS names by not returning cookies where those characters are used in the server’s name. Without cookies being returned, state information cannot be preserved across HTML requests, so the user cannot log in to ZENworks Control Center.

The only characters allowed in Windows for DNS names are the alphabetical characters (a‑z), numbers, and the hyphen. For example, you cannot use an underscore character. Use a hyphen instead.

This is not an issue with the Firefox browser, even when it is run on Windows.

Workarounds:

  • Reference the IP address instead of its DNS name.

  • Reference a valid DNS name for the IP address the server is using. For example, your server name might be A_Server.mycompany.com, but the DNS registration for the IP address might be Aserver.mycompany.com, which will work.

  • If you only use Internet Explorer to run ZENworks Control Center, do not use underscores in your server names.

2.12.2 Rebooting can take some time after a Windows Vista device has been re-imaged

After an image containing the ZENworks Adaptive Agent has been restored on a Windows Vista device, nothing is displayed to indicate what is happening. After awhile, the device suddenly reboots.

Workaround: None.

2.13 Migration

This section contains information about the issues that might occur during migration to ZENworks Configuration Management.

2.13.1 An MSI created by the converter does not actually delete the registry string entries

If you create an Application object in ZENworks 7 that creates or deletes a registry value in HKEY_LOCAL_MACHINE and then migrate it to ZENworks Configuration Management, the Migration Utility converts the Application object to an MSI. When the migrated MSI is installed, the registry entry is created or deleted in HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE.

Workaround: Perform the following steps to migrate applications with only registry changes as individual action instead of an MSI:

  1. Launch the Migration utility.

  2. Click the Migration Tool Settings icon, then click Application.

  3. Select the Migrate distributions options as individual actions option.

  4. Migrate the application with registry changes to destination zone. The application is migrated as a Windows Bundle with Regedit action.

2.13.2 Manually deleting the add-on images after migration

Add-on images that are created by exporting applications in traditional ZENworks are not valid in ZENworks Configuration Management. If these add-on images are migrated in combination with a base image or otherwise, they should be deleted.

Workaround: Manually delete the add-on image from ZENworks Configuration Management.

2.13.3 Migration of applications is slow on a Windows Vista device

Migration of AOT or AXT applications to MSI application is comparatively slower on a Windows Vista device.

Workaround: None.

2.14 Network Address Translation (NAT)

This section contains information about the issues that might occur when you use NAT with ZENworks Configuration Management.

2.14.1 Content is not pushed down to devices when using NAT

In both a public and private network where static NAT is configured between the networks, content might not be pushed down to the devices you are managing.

Workaround: Configure the DNS server with the DNS name of the ZENworks server, and map the DNS name to the public IP address.

2.15 Patch Management

This section contains information about the issues that might occur when you use Patch Management in ZENworks Configuration Management.

2.15.1 New patch content is no longer being downloaded

At the end of your paid patch subscription, your subscription license indicates an expired status and Patch Management ceases to download new patch content on a daily basis.

To renew a lapsed Patch Management subscription license, follow the instructions in TID 3077372 in the Novell Support Knowledgebase.

2.15.2 Superseded patches are shown as NOT APPLICABLE

In earlier releases of ZENworks Patch Management, a patch showed its status as PATCHED or NOT PATCHED, regardless of whether the patch was brand new or completely outdated. This often caused many more patches to show as NOT PATCHED than were actually necessary for deployment to a given target device.

This issue has been addressed in many of the new advanced content patches provided with the ZENworks 10 Configuration Management (10.1):

  • When a patch is superseded, it is automatically disabled

  • If the patch is re-enabled and detected, in most cases the patch shows NOT APPLICABLE because it has been replaced by a more recent patch

While this is inconsistent with the behavior of earlier versions of ZENworks Patch Management, clearly this change is for the better as only the patches that currently need to be installed are reported or analyzed on each device.

Workaround: None necessary.

2.15.3 Microsoft System Installer (MSI) might need to be updated for some patches

Deployment of certain .NET patches might require that the latest MSI be installed. Otherwise, you can receive errors when deploying those patches.

Workaround: Prior to deploying .NET patches, verify whether an MSI version is a prerequisite. If necessary, create a bundle to deploy the latest MSI (version 3.1 or later) to your systems. MSIs are available from Microsoft.

2.15.4 Patch deployment might not start when scheduled

If the deployment schedule type includes both the Recurring and Process Immediately If the Device Is Unable to Execute options, when the device becomes active, the deployment of the patch does not start on the first of its scheduled recurring dates.

Workaround: None. The patch will be deployed when the next recurring date occurs.

2.15.5 Multiple reboots might occur when rebooting the server after a patch has been deployed

After a patch has been deployed, the server might reboot several times until the Discover Applicable Updates function is able to run and report the results of the patch back to ZENworks.

Workaround: Always deploy patches to the ZENworks Servers separately, and without a reboot to avoid this issue. (A reboot is the default option in the Deploy Remediation wizard.)

2.15.6 A "Please try again later" error is given when running Patch Validation

An error similar to the following might be displayed when running Patch Validation:

The content for 12792c5f8d17904f39e1746310c2665a is not accessible at this time. Please try again later.

Workaround: Run Update Cache to re-fetch the content of the patch bundle.

2.15.7 A Java exception error occurs when clicking the Vulnerabilities tab

(Fixed in v10.1.1) If you use the Database Creation Utility to set up a ZENworks database, the default SQL file shipped with ZENworks 10 Configuration Management causes the Vulnerabilities tab in ZENworks Control Center to display a Java exception error.

Patch Management provides a different version of the SQL file that includes its information, which allows the Vulnerabilities tab in ZENworks Control Center to work properly.

Workaround: Do one of the following procedures for your database type to enable the Vulnerabilities tab:

2.15.7.1 Sybase SQL Anywhere (Embedded)
  1. From a command line on the Primary Server that’s hosting the database, run the following command:

    zman dgc
    
  2. Specify your ZENworks Management Zone username and password.

  3. When the database username and password are displayed, note the username and copy the password.

  4. To open the Sybase database administrative management tool, run the dbisql command on the Primary Server where the database is installed:

    Linux: /opt/novell/zenworks/share/bin32s/dbisql

    Windows: ZENworks_home\share\ASA\win32\dbisql

    This opens the Interactive SQL window and the Connect dialog box. For Linux, you must have the GUI running to display them.

  5. On the Identification tab in the Connect dialog box, specify the noted username in the User ID field and paste the copied password into the Password field.

  6. On the Database tab in the Connect dialog box, specify the database server name, select the ZENworks database file, then click OK to close the dialog box.

  7. In the interactive SQL window, click File > Open and select the following SQL file:

    ZENworks_installation_DVD\upgrade\disk1\instdata\sql\sql-anywhere\upgrade\pmr-r1\z-nrm-patchlink-sapphire-datamodel.sql
    
  8. Click the Execute button to apply the SQL script.

    Script execution actions are displayed while the script is running.

    The Vulnerabilities tab should display correctly in ZENworks Control Center after the script has finished running.

2.15.7.2 Sybase SQL Anywhere (External)
  1. On your Sybase database server, run the dbisql command.

    This opens the Interactive SQL window and the Connect dialog box. For Linux, you must have the GUI running to display them.

    To determine the dbisql command’s location, refer to your Sybase SQL Anywhere documentation.

  2. On the Identification tab in the Connect dialog box, specify the user ID and password for your external Sybase database.

  3. On the Database tab in the Connect dialog box, specify the database server name, select the ZENworks database file, then click OK to close the dialog box.

  4. In the interactive SQL window, click File > Open and select the following SQL file:

    ZENworks_installation_DVD\upgrade\disk1\instdata\sql\sql-anywhere\upgrade\pmr-r1\z-nrm-patchlink-sapphire-datamodel.sql
    
  5. Click the Execute button to apply the SQL script.

    Script execution actions are displayed while the script is running.

    The Vulnerabilities tab should display correctly in ZENworks Control Center after the script has finished running.

2.15.7.3 Microsoft SQL Server
  1. On your database server, open your MS SQL Server database administration management tool.

    Refer to your MS SQL Server documentation.

  2. Apply the following script to your ZENworks MS SQL Server database:

    ZENworks_installation_DVD\upgrade\disk1\instdata\sql\sql-server\upgrade\pmr-r1\z-nrm-patchlink-sapphire-datamodel.sql
    

    The Vulnerabilities tab should display correctly in ZENworks Control Center after the script has finished running.

2.15.7.4 Oracle
  1. On your database server, open your Oracle database administration management tool.

    Refer to your Oracle database documentation.

    You can also apply the SQL script manually against your Oracle database.

  2. Apply the following SQL script to your ZENworks Oracle database on your database server:

    Linux: /opt/novell/zenworks/share/datamodel/oracle/nrm-patchlink-sapphire-datamodel.sql

    Windows: ZENworks_home\share\datamodel\oracle\nrm-patchlink-sapphire-datamodel.sql

    where the ZENworks_home path refers to your Primary Server. The SQL file resides on your Primary Server, which might be different than your database server.

    The Vulnerabilities tab should display correctly in ZENworks Control Center after the script has finished running.

2.16 Policies

This section contains information about the issues that might occur when you use policies in ZENworks Configuration Management.

2.16.1 General Policy Issues

  • On 64-bit versions of Windows Server 2003 servers, only the Browser Bookmarks policy, SNMP policy, Printer policy, Local File Rights policy, and the Windows Group policy device-related settings are applied if they are associated to the device.

    Workaround: None.

  • In both a public and private network where static NAT is configured between the networks, a policy might not be pushed down to the devices you are managing.

    Workaround: Configure the DNS server with the DNS name of the ZENworks server, and map the DNS name to the public IP address.

2.16.2 Printer Policy Issues

  • Uninstall does not roll back the previously enforced Printer policies.

    Workaround: Disassociate the Printer policy from the users or devices to unenforce the policy. After unenforcing the policy, uninstall ZENworks.

  • The iPrint nipp.exe client installer does not support a silent installation.

    Workaround: Use iPrint nipp-s.exe or nipp.zip for a silent installation.

  • The policy does not support driver installation of .exe drivers.

    Workaround: None

  • The iPrint client is not supported on 64-bit versions of Windows Server 2003 and Windows Server 2008 devices.

    Workaround: None.

  • Support for network printer prompting for user credentials is not provided

    Workaround: None.

2.16.3 Windows Group Policy Issues

  • The Windows Group policy containing the local group policy settings is not applied if the operating system of the device where the policy is applied is different from the device where the policy is created.

    Workaround: Remove the System Requirement from the Windows Group policy and apply the policy. However, the security settings are applied only if the operating system version of the device where the policy is applied is later than the operating system version of the device where the policy is created.

  • Software restrictions in security settings are not enforced if the Apply only security settings option is selected.

    Workaround: In the Computer Configuration tab, select Apply all settings to enforce the software restrictions.

  • Log-on and Log-off scripts that launch GUI applications do not functional properly on terminal server and Windows Vista devices

    On the terminal server and Windows Vista devices, the log-on and log-off scripts launching GUI applications do not functional properly because the Graphical User Interface is not launched on the desktop.

    Workaround: Use Directive bundles to launch the GUI applications:

    1. Create a Directive bundle.

    2. Add a Launch Windows Executable action to launch a GUI application, such as mspaint.

    3. Assign the bundle to a device.

    4. Select Launch Schedule, then select the schedule type as Event.

    5. Select the User Login or User Logout event to trigger the schedule.

  • Environment variables for the user are not supported in the Group policy login scripts

    The Group policy login scripts do not support the environment variables for users on Vista, Win2k3, and Win2k8 devices.

    Workaround: None.

  • User settings fail to unenforce on Windows Server 2008 device

    On a Windows Server 2008 device, the Group policy user settings associated to a user are not unenforced when the user logs out.

    Workaround: None.

2.16.4 Browser Bookmarks Policy Issues

  • The Browser Bookmarks policy settings are not removed from the user’s Favorites when the ZENworks Adaptive Agent is uninstalled.

    Workaround: None.

2.16.5 Dynamic Local User Policy Issues

  • If both user-associated and device-associated policies are effective for a device, only the policy that takes precedence according to the Policy Conflict Resolution settings is applied. However, the Effective status for both policies is displayed as Success in the ZENworks Adaptive Agent icon.

    Workaround: None.

2.16.6 Roaming Profile Policy Issues

  • The Roaming Profile policy is not supported for the Windows Vista and Windows Server 2008 terminal session managed devices.

    Workaround: None.

2.16.7 Local File Rights Policy Issues

  • In the Local File Rights policy, if the Full Control access right is denied for the Administrators or Authenticated Users group and the Remove access control rules not configured by ZENworks option is selected, then the policy fails. However, if the Full Control access right is denied for the Administrators or Authenticated Users group, the policy is successful only during the first enforcement.

    Workaround: None

2.17 Personality Migration

This section contains information about the issues that might occur when you use Personality Migration in ZENworks Configuration Management.

2.17.1 Saving the settings and data to a PNP file

While saving the settings and data to a .pnp file, if you choose to use the Advanced File Options to span the content to multiple files, you must specify a password in the Password to encrypt the PNP file option.

Workaround: None

2.17.2 Unable to install the printer on the destination device

Workaround: Before migrating the printer settings from the source device to the destination device, do the following:

  1. Create a directory named PrinterDrivers in any of the logical drives such as C:, D:, or E:.

  2. Download and copy the unzipped driver to the PrinterDrivers directory

2.17.3 Security settings and the digital signatures of the Adobe Reader are not migrated

(Fixed in v10.1.1)The security settings and the digital signatures of the Adobe Reader* 7.0 on a Windows device are not migrated to Adobe Reader 8.0 on another Windows device.

Workaround: None.

2.17.4 Unable to create local users on the destination device by using bundles if the destination device is in the Active Directory domain

Workaround: Before migrating the personality settings, manually create the local users on the destination device and then launch the bundle to migrate the personality.

2.17.5 Unable to map multiple network connections from a source device to a destination device for migrating network settings

(Fixed in v10.1.1) Workaround: None

2.17.6 Unable to launch a bundle to migrate the personality settings of an Active Directory domain user currently logged in to the device

You cannot launch a bundle to migrate the personality settings of an Active Directory domain user currently logged in to the device if you specify the same user as domain name\username in The following user field (ZENworks Personality Migration Template Builder > Users tab > Add Users to Migrate > Add Users).

Workaround: To migrate the personality settings of the currently logged in Active Directory domain user, use the Migrate the settings for the currently logged in user option (ZENworks Personality Migration Template Builder > Users tab > Add Users to Migrate > Add Users) in the ZENworks Personality Migration Template Builder.

2.18 Registration

This section contains information about the issues that might occur with registration in ZENworks Configuration Management.

2.18.1 The zac unregister command help does not explain the -f switch

If you enter zac unr /?, the help shows an example using the -f switch, but doesn’t explain its purpose.

The -f switch forces a device to unregister in the event that the zac unregister command alone does not unregister the device.

2.19 Remote Management

This section contains information about the issues that might occur when you use the Remote Management feature in ZENworks Configuration Management.

2.19.1 Unable to lock mouse and keyboard on the Windows Vista managed devices during remote sessions

On Windows Vista managed devices, mouse and keyboard locks do not function if the Aero theme is enabled.

Workaround: Do not use the Aero theme.

2.19.2 Installation of the Remote Management viewer might fail

The Remote Management viewer installation might fail. This error is inherent to the MSI framework.

Workaround: Perform either of the following steps:

  • Uninstall the Remote Management viewer by using Add/Remove Programs, then reinstall it.

  • Use the Microsoft Windows Installer Cleanup Utility to clean up the application, then reinstall it. This utility can be downloaded from Microsoft Support.

2.19.3 The Remote Management viewer fails to launch on Windows Vista devices

On Windows Vista devices, the Remote Management viewer fails even though the security prompt is successfully completed.

Workaround: Add the server running ZENworks Control Center to the list of trusted sites and retry.

2.19.4 During the Remote Control session, clicking the Ctrl+Alt+Del icon on the Remote Management viewer might display the Secure Attention Sequence window without any controls

Workaround: Click the Ctrl+Alt+Del icon on the Remote Management viewer, then press the Esc key to exit the Secure Attention Sequence (SAS) window. Then, click the Ctrl+Alt+Del icon again on the Remote Management viewer.

2.19.5 Blanking the screen of a Tablet PC managed device during a remote session degrades the session performance

Workaround: None.

2.19.6 The Override Screen Saver functionality is disabled for Windows Vista and Windows Server 2008 platforms

Workaround: None.

2.19.7 Unable to wake up a powered-off device by using Wake-on-LAN

If the device is powered off by using a hard shutdown, you cannot use Wake-on-LAN to wake up the device.

Workaround: None.

2.19.8 Remote Control session on a Windows XP managed device fails

If you initiate a Remote Control session on a Windows XP device on which a Remote Desktop connection is active, the Remote Control screen blacks out.

Workaround: To remotely control a Windows XP device, ensure that the user has locally logged in to the device.

2.20 Reporting

The ZENworks Reporting solution is based on BusinessObjects Enterprise* XI. This section contains issues that might occur when you use ZENworks Reporting.

2.20.1 Reporting Limitations

The ZENworks Reporting solution has the following limitations:

  • The reporting universes in this release of Reporting Server will be enhanced to improve the user experience in Custom Reporting. A future release of Reporting Server will refresh the universes. However, the future release will not be backward compatible. Most of the Predefined reports will remain intact functionally, but custom reports created in this or previous releases of ZENworks Configuration Management will not be transferable to a future release of Reporting Server.

  • You cannot use Crystal Reports* with ZENworks Configuration Management Reporting Universe.

  • ZENworks Reporting is not supported on Windows Server 2008.

2.20.2 Reporting Issues

When you use the Reporting feature in ZENworks Configuration Management, you might see the issues listed below. To troubleshoot other error messages that you might encounter while working with BusinessObjects Enterprise XI, see the BusinessObjects XI Release 2 Error Message guide.

2.20.2.1 ZENworks Reporting does not work if the Reporting Server is installed on SUSE LINUX Enterprise Server (SLES) 10 SP1

Workaround: Restart the device.

2.20.2.2 Reporting does not work if the ZENworks database is an SQL Server database, and the authentication mode is Windows Authentication

Workaround: Do one of the following:

  1. Configure the DSN of the ZENworks database to set it to Windows NT Authentication:

    • 1a. From the desktop Start menu, click Settings, click Control Panel, then double-click ODBC Data Source.
    • The ODBC Data Source Administrator window is displayed.
    • 1b. Click the System DSN tab.
    • 1c. Select ZENworks Datastore, then click Configure.
    • The Microsoft SQL Server* DSN Configuration window is displayed.
    • 1d. Click Next to accept the default data source name and SQL server name.
    • 1e. Select With Windows NT authentication using the network Login ID, then click Next.
    • 1f. Click Next to accept the default values.
    • 1g. Click Finish.
    • 1h. In the ODBC Microsoft SQL Server Setup window, click Test Data Source.
    • The following message is displayed:
    • Tests Completed Successfully.
    • 1i. Click OK.
  2. Edit the properties of BusinessObjects Enterprise Services on the ZENworks server:

    • 2a. From the desktop Start menu, click All Programs > BusinessObjects XI Release 2 > BusinessObjects Enterprise > Central Configuration Manager.
    • The Central Configuration Manager window is displayed.
    • 2b. Right-click Web Intelligence Report Server, then click Stop.
    • 2c. Right-click Web Intelligence Report Server, then click Properties.
    • The Web Intelligence Report Server Properties window is displayed.
    • 2d. In the Log On As panel, deselect System Account, then specify the username and password of the domain account of the Windows server that hosts the MS SQL database.
    • 2e. Click OK.
    • 2f. Right-click Web Intelligence Report Server, then click Start.
    • 2g. Repeat Step 2b through Step 2f for all the services listed in the Central Configuration Manager window.
2.20.2.3 The BusinessObjects Enterprise InfoView might not be launched if the DNS name of the server with BusinessObjects Enterprise XI installed is not correctly resolved

Workaround: On the Windows server where ZENworks Control Center is launched, add the appropriate DNS entry in the %Windows_root%\systems32\drivers\etc\hosts file.

2.20.2.4 The BusinessObjects Enterprise InfoView might not be launched if BusinessObjects Enterprise XI is installed on a ZENworks Server that uses NAT

Workaround: On the Windows device where ZENworks Control Center is launched, add the appropriate DNS entry in the %Windows_root%\systems32\drivers\etc\hosts file.

2.20.2.5 Reporting Server uninstallation on Windows fails if another installation is in progress on the same device

The following message is logged into the %ZENWORKS_HOME%\logs\zrsuninstall.log file:

ERROR_INSTALL_ALREADY_RUNNING

Workaround: Do the following:

  1. Open the Windows Task Manager and stop all instances of msiexec.exe and setup.exe.

  2. Uninstall ZENworks Reporting Server.

2.20.2.6 You cannot migrate the modifications to the report layouts in the Predefined report folder

Workaround: None

2.20.2.7 The report layouts of the predefined reports can be modified only by the user who logs in to the Reporting Server with the username as Administrator

However, this is not recommended.

2.20.2.8 Unable to add the Message Description object while creating a Web Intelligence document

(Fixed in v10.1.1)On a SLES 10 server connected to a Sybase* database, you might encounter the following exception if you add the object Message Description while creating a new Web Intelligence document by connecting through the ZENworks Configuration Management Universe in the BusinessObjects Enterprise InfoView (BusinessObjects Enterprise InfoView > New > Web Intelligence document > ZENworks Configuration Management Universe > System Messages > System Message Details).

The server encountered an internal error () that prevented it from fulfilling this request.

The BusinessObjects Enterprise InfoView crashes after encountering this error.

Workaround: Do the following to restart the BusinessObjects Enterprise InfoView:

  1. Log in as root at the command line.

  2. Enter the command /etc/init.d/BobjEnterprise115 stop; /etc/init.d/BobjEnterprise115 start.

To avoid this error, do the following each time before you run the query to create the Web Intelligence document:

  1. In the Universe pane, go to System Messages > Message Filters and select Locale.

  2. Add Locale to the Query Filters pane.

  3. Click Filter to filter the locale for the de value.

  4. Click Values to view the locales in the list.

  5. Include all the values except de in to the Locale In List pane.

  6. Click Run Query to create a new Web Intelligence document.

2.20.2.9 ZENworks Reporting fails when you log in to the ZENworks Control Center by using an administrator account

ZENworks Reporting fails when you log in to the ZENworks Control Center by using an administrator account (such as Administrator@windowdomain.com) that was created by using the user source.

Workaround: To log in to the ZENworks Control Center with the administrator account that was created by using the user source, use only the username, such as Administrator.

2.21 System Update

This section contains information about the issues that might occur with System Update in ZENworks Configuration Management.

2.21.1 Upgrading your ZENworks system causes the ZCC timeout value to be reset to the default

If you changed the default timeout value for the ZENworks Control Center and then upgrade your ZENworks system, the timeout value is reset to the default setting of 30 minutes.

If you want to reset the value back to your preferred setting, you must change it manually. For more information, see Changing the Timeout Value for ZENworks Control Center in the ZENworks 10 Configuration Management System Administration Reference.

2.21.2 The sucd System Updates command hangs in a canceling state

If you attempt to use the zman sucd command to cancel an update that is already downloaded to your ZENworks Server, the update might remain in a canceling state and the following error message is displayed:

Unable to delete update until the cancellation process has completed. Please try again later.

Workaround: If the update that you want to cancel has already been downloaded, use the zman sudu --force command to delete the update and resolve the error.

2.21.3 Downloading an update does not resume after losing contact with the database

If a server’s connection to the ZENworks database is lost while downloading an update, the download does not resume after reconnecting. Attempting to use the Cancel Download action results in the update hanging in the Cancel state.

Workaround: Use the zman sudu --force command to delete the update.

2.21.4 Using spaces in the From field in the E-mail Notification panel causes the message to not be sent

If you use spaces between words in the From field in the E-mail Notification panel (Configuration tab > Configuration page > Infrastructure Management > System Update Settings > E-mail Notification panel), the message are not be sent.

Workaround: Do not use spaces. Use dashes instead of spaces.

2.21.5 After updating a Windows 2008 machine using the Prompt User to Reboot When Update Finishes Applying option, the machine reboots automatically

If you apply an update on a Windows 2008 machine and select the Prompt User to Reboot When Update Finishes Applying (Default) option, the machine might reboot instead of letting the user decide whether to reboot.

Workaround: Set the Do Not Reboot Device option.The device does not reboot; however, the user is periodically requested to reboot the device, which continues until the device is rebooted.

2.22 User Sources

This section contains information about the issues that might occur with authoritative user sources in ZENworks Configuration Management.

2.22.1 LDAP cannot read extended characters

The LDAP user cannot access fully qualified contexts that contain extended characters.

Workaround: None.

2.23 ZENworks Adaptive Agent

This section contains information about the issues that might occur with the ZENworks Adaptive Agent in ZENworks Configuration Management.

2.23.1 Linux Servers are not managed devices even though the Adaptive Agent is installed on them

The ZENworks Adaptive Agent is installed on Linux Primary Servers to enable software updates. Although Linux servers appear as managed devices in ZENworks Control Center, any actions performed on them, such as assignments, QuickTasks, and so on, will fail.

2.23.2 The ZENworks Adaptive Agent UI shows both English and the local language chosen for viewing

ZENworks resources are loaded according to the locale of the process that retrieves them. When using regional settings, the ZENworks Windows service might be configured to use a different language than the user is configured to use. The result is that the strings from both languages are displayed.

Workaround: Do one of the following:

  • Install the native language operating system

  • Change the default user language to match the language displayed by the user

2.23.3 If you use the ZENworks Icon to log into a Windows Vista managed device as a ZENworks user, the login fails

Workaround: On the Windows Vista managed device, use the login GINA to log in as a ZENworks user.

2.24 ZENworks Control Center

This section contains information about the issues that might occur when using ZENworks Control Center in ZENworks Configuration Management.

2.24.1 An HTTP request is not redirected to HTTPS if IIS is running on the Primary Server

During installation, the setup checks to see if the default HTTP port (80) and HTTPS port (443) are in use. If the ports are in use by another application (such as IIS), you are prompted to use alternative ports. In this case, you must access ZENworks Control Center via the port it is using and not access IIS.

Workaround: Although http://Primary_Server_IP_address works if ZENworks Control Center is using port 80, http://Primary_Server_IP_address:### (where ### is the port Tomcat is using) always works.

2.24.2 MS SQL Server 2005 provides multiple collation options that affect how lists display in ZENworks Control center

When Microsoft SQL Server 2005 is installed on non-English (U.S.), there are differing sort orders and collations offered. This means that the ordering of lists in ZENworks Control Center is affected, including devices, bundles, and so on.

Workaround: When you install an SQL Server, it selects a default based on the locale of the server. Review the Microsoft documentation to determine which collation option to use when installing your MS SQL Server.

2.25 Zman

This section contains information about the issues that might occur when you use the zman command in ZENworks Configuration Management.

2.25.1 When running the zman command in Linux, the password appears in plain text when switching from one user to another user

zman disables the echoing of passwords in Linux by turning the echo off on the controlling terminal. For example, /dev/pts/0. When you switch from one user to another user, the new user does not have file permissions on the controlling terminal.

Workaround: Before switching to the new user, give Read and Write file permissions to the new user on the controlling terminal. Run tty to display the current controlling terminal.

2.25.2 Zman help does not display in Chinese

Using the man zman command for Simplified Chinese and Traditional Chinese doesn’t display any help. It only displays the tilde (~) character.

Workaround: None.

2.25.3 The rpsv and rpgn reporting zman commands fail on SLES 10

Workaround: Before executing the rpsv and rpgn commands, ensure that the specified destination path has the read-write-execute (rwx) permissions for all Linux users.

3.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark

4.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2008-2009 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page and one or more additional patents or pending patent applications in the U.S. and in other countries.

For Novell trademarks, see the Novell Trademark and Service Mark list.

All third-party trademarks are the property of their respective owners.