Novell ZENworks 10 Asset Management SP2

February 01, 2009
3.5 CASA
3.13 Zman

1.0 Overview

The issues included in this document were identified for Novell ZENworks 10 Asset Management SP2.

For system requirements and installation instructions, see the Novell ZENworks 10 Asset Management Installation Guide.

For administrative tasks, see the Novell ZENworks 10 Asset Management documentation Web site.

This product contains undocumented utilities that Novell Support 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 Asset Management SP2 (10.2):

Table 1 Readme Updates

Date

Readme Item Added or Updated

December 15, 2009

The issues fixed in Update for ZENworks 10 Asset Management SP2 (10.2.2) are identified with the phrase (Fixed in v10.2.2).

September 24, 2009

In Reporting does not work if the ZENworks database is an MS SQL Server database, and the authentication mode is Windows Authentication, added the error message.

August 19, 2009

The issues fixed in Update for ZENworks 10 Asset Management SP2 (10.2.1) are identified with the phrase (Fixed in v10.2.1).

July 7, 2009

June 26, 2009

In The Report Engine Server fails to initialize after installing ZENworks Reporting Server, added the workaround for Linux.

2.0 Issues Resolved in ZENworks 10 Asset Management SP2

For a list of the resolved issues in ZENworks 10 Asset Management SP2, see TID 7003225 in the Novell Support Knowledgebase.

3.0 Known Issues

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

3.1 Installation

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

3.1.1 Time synchronization causes invalid certificate errors

If time is not synchronized on the network before you install the ZENworks services, you might 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 ZENworks services. Make sure to include ZENworks back-end servers in the synchronization.

3.1.2 Support for testing Windows 7 Release Candidate

ZENworks 10 Asset Management SP2 is not supported on Windows* 7 Release Candidate. However, if your testing environment includes Windows 7 Release Candidate 32-bit or 64-bit, you can begin testing ZENworks 10 Asset Management SP2 on those platforms.

3.2 Accessibility

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

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

3.3 Asset Inventory

This section contains information about issues that might occur with Asset Inventory.

3.3.1 Event-based and On Refresh schedules fail for the inventory scan and collection data form

If an administrator configures an event-based or On Refresh schedule for an inventory scan and collection data form, the inventory agent fails to invoke the inventory scan and collection data form.

Workaround: Configure only a Recurring schedule for the inventory scan and collection data form.

3.3.2 Inventory reports list duplicate components during an inventory scan in ZENworks Control Center

Workaround: To troubleshoot the issue, see TID 7003350 in the Novell Support Knowledgebase.

3.3.3 Inventory data of a device reregistered from one Management Zone to another is not displayed

If a device is reregistered from one Management Zone to another, the inventory data is not displayed for the device in ZENworks Control Center.

Workaround: Initiate an inventory scan twice on the device.

3.4 Asset Management

This section contains information about issues that might occur with Asset Management.

3.4.1 Requirements for Oracle 10.1 and 10.2 client when using the ZENworks Asset Management Migration Utility

You can migrate Oracle to Oracle databases. For migration purposes, these databases can be Oracle 9.2, Oracle 10.1, or Oracle 10.2.

If you are using an Oracle database, please observe the following:

  • The Oracle client must be installed on the machine that runs the migration utility. For versions 10.1 and 10.2, this must be Administrator, not InstantClient.

  • For the Oracle 10.2 client, you must apply patch 5473334 (Doc ID 387818.1). Of the several data access components included in the patch, Oracle Provider for OLEDB version 10.2.0.2.20 is required.

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

3.5 CASA

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

3.5.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: The forward proxy server's firewall 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 Asset 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 Asset 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.

3.6 Closest Server Rules

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

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

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

3.7 Discovery and Deployment

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

3.7.1 ZENworks-related files might be reported as malicious software during the ZENworks Adaptive Agent installation

During the ZENworks Adaptive Agent installation, some ZENworks related files might be reported as malicious software by anti-virus software. Consequently, the installation abruptly stops. This is because the deployment packages (PreAgentPkg_Agent.exe and PreAgentPkg_AgentComplete.exe) contain another EXE file (ZENPreAgent.exe). If an EXE file is embedded in another EXE file, it is considered as malicious software because this is the behavior of a trojan.

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.

3.7.2 ZENworks Adaptive Agent might crash if the managed device does not have the latest .NET Framework patches

The ZENworks Adaptive Agent runs on Microsoft .NET Framework. For better performance and stability, you should upgrade to the latest support packs and patches of .NET 2.0 through Windows Automatic Updates or Patch Management.

.NET 2.0 SP1 is the latest version supported by Microsoft on Windows 2000, and .NET 2.0 SP2 is the latest version of .NET 2.0 supported by Microsoft on Windows XP, Windows Server* 2003, Windows Server 2008, and Windows Vista.

On Windows XP and Windows Server 2003, you can directly download and install .NET 2.0 SP2 or upgrade to .NET 3.5 SP1, which includes .NET 2.0 SP2. On Windows Vista and Windows Server 2008, you must upgrade to .NET 3.5 SP1 to get the .NET 2.0 SP2 update installed.

3.8 Logging In

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

3.8.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 when 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 for DNS names in Windows 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 Mozilla* 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.

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

3.9 Registration

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

3.9.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 if the zac unregister command alone does not unregister the device.

3.10 Reporting

The ZENworks Reporting solution is based on BusinessObjects Enterprise* XI. This section contains issues that might occur when you use ZENworks Reporting. To troubleshoot other error messages that you might encounter while working with BusinessObjects* Enterprise XI, see the BusinessObjects XI 3.1 documentation Web site.

3.10.1 Reporting Limitations

The ZENworks Reporting solution has the following limitation:

  • The reporting universes in this release are enhanced to improve the user experience in Custom Reporting. The custom reports created in the previous releases of ZENworks Asset Management are not transferable to this release of Reporting Server. The reports must be re-created in this release of the Reporting Server.

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

The following error might be displayed while running the reports:

A database error occurred. The database error text is:
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user "NT
AUTHORITY\ANONYMOUS LOGON"..(WIS 10901)

Workaround: Do the following:

  1. Edit the properties of ZENworks Reporting Server Services on the ZENworks Server:

  2. From the desktop Start menu, click All Programs > ZENworks Reporting Server > ZENworks Reporting Server > Central Configuration Manager.

    The Central Configuration Manager window is displayed.

  3. Right-click Server Intelligence Agent (ZENReporting), then click Stop.

  4. Right-click Server Intelligence Agent (ZENReporting), then click Properties.

    The Server Intelligence Agent (ZENReporting) Properties window is displayed.

  5. 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 ZENworks Reporting Server database. For a non-domain user, the username and password must be the same on the MS SQL server database and ZENworks Reporting Server.

  6. Click OK.

  7. Right-click Server Intelligence Agent (ZENReporting), then click Start.

3.10.3 The ZENworks Reporting Server 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.

3.10.4 The ZENworks Reporting Server 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.

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

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

Workaround: None

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

Modifying the report layouts of the predefined reports is not recommended.

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

(Fixed in v10.2.1) 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.

3.10.9 Unable to launch the ZENworks Reporting Server InfoView after the session has expired

You might encounter the following error message when the ZENworks Reporting Server InfoView session expires:

Unable to reconnect to the CMS <server-name>:6400. The session has been logged
off or has expired. (FWM 01002)

Workaround: Do the following:

  1. Delete the cookies from your browser.

  2. Close all browser instances.

  3. Log in to ZENworks Control Center, then launch the ZENworks Reporting Server InfoView.

3.10.10 Closing the ZENworks Reporting Server InfoView page without logging out to end the session fails to relaunch the ZENworks Reporting Server InfoView

Workaround: Click ZENworks Reporting Server InfoView (ZENworks Control Center > Reports) two times to relaunch the ZENworks Reporting Server InfoView page.

All the cookies that were created in the prior session are deleted on the first click, and the ZENworks Reporting Server InfoView page is displayed on the subsequent click.

To end the ZENworks Reporting Server InfoView session, ensure that you click Logout on the ZENworks Reporting Server InfoView page.

3.10.11 Unable to launch the ZENworks Reporting Server InfoView

This problem might occur if the Central Management Server failed to start. The following error message is displayed in the %zenworks_home%\logs\zcc.log file:

cause:com.crystaldecisions.enterprise.ocaframework.OCAFrameworkException$NotFoundInDirectory: Server <Server_name>:6400 not found or server may be down (FWM 01003)
cause:java.net.ConnectException: Connection refused: connect
detail:Server <Server_name>:6400 not found or server may be down (FWM 01003) Connection refused: connect
detail:Server <Server_name>:6400 not found or server may be down (FWM 01003) Connection refused: connect

Workaround 1: See the Business Objects Board forum.

Workaround 2: Contact Novell Support.

3.10.12 The Report Engine Server fails to initialize after installing ZENworks Reporting Server

The following error message is displayed when the Report Engine Server fails to initialize:

Cannot initialize Report Engine server. (Error: RWI 00226) (Error: INF)

This problem might occur if the Report Engine Server is not running, and you are trying to create or access the reports.

Workaround: Manually initialize the Report Engine Server before launching the ZENworks Reporting Server InfoView:

On Windows: Restart the Server Intelligence Agent:

  1. From the desktop Start menu, click Programs > ZENworks Reporting Server > ZENworks Reporting Server > Central Configuration Manager > Server Intelligence Agent to display the Central Configuration Manager window.

  2. Click Restart.

  3. Wait 2 to 3 minutes for the services to restart.

On Linux: Restart the BusinessObjects Enterprise services:

  1. Stop the BusinessObjects Enterprise services by running the following command as a root user:

    /etc/init.d/BobjEnterprise120 stop

  2. Wait 2 to 3 minutes for all the services to stop.

  3. Start the BusinessObjects Enterprise services by running the following command as a root user:

    /etc/init.d/BobjEnterprise120 start

  4. Wait 2 to 3 minutes for all the services to start.

3.11 ZENworks Adaptive Agent

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

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

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

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

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

3.11.4 Uninstallation of the User Management Agent Feature on a Windows 2000 device fails

If you deselect the User Management Agent Feature in ZENworks Control Center (Agent Features panel on the ZENworks Agent page), the User Management feature is not uninstalled on a Windows 2000 device.

For more information on customizing the agent features, see Customizing the Agent Features.

Workaround: None.

3.11.5 Installation of only the Asset Management feature uninstalls the traditional ZENworks agent

(Fixed in v10.2.1)If you choose to install only the Asset Management feature of ZENworks Adaptive Agent (ZENworks Control Center > Configuration > Device Management > ZENworks Agent > Agent Features) on a device that already has traditional ZENworks Agent installed, the Adaptive Agent installation uninstalls the traditional ZENworks Agent.

Workaround: None.

3.11.6 The ZENworks icon is not visible in the notification area of the device

If you upgrade from ZENworks 10 Asset Management 10.1 or ZENworks 10 Asset Management 10.1.x to ZENworks 10 Asset Management SP2 (10.2), the ZENworks icon might not be visible in the notification area of the device.

Workaround: Do one of the following:

  • Log out and log in to the device.

  • Reboot the device.

  • Terminate and restart the explorer.exe process through the Windows Task Manager.

3.12 ZENworks Control Center

This section contains information about issues that might occur when using ZENworks Control Center.

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

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

3.13 Zman

This section contains information about issues that might occur when you use the zman command line utility.

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

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

5.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 © 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.