Novell ZENworks 7 Server Management with Support Pack 1

June 09, 2008

1.0 Readme Updates

This document was updated in the following sections on the dates indicated:

1.1 June 09, 2008

The following changes were made:

2.0 Overview

Novell® ZENworks® 7 Server Management with Support Pack 1 (SP1) includes the following components:

The known issues included in this document are identified for this release of the product. For resolved customer-reported issues, see TID 10097369 in the Novell Support Knowledgebase.

The Novell ZENworks 7 Server Management Installation Guide provides detailed installation instructions. The guide (in HTML format) is available from a menu option when running the installation program from the Novell ZENworks 7 Server Management with Support Pack 1 Program CD. The PDF version is available from the Novell ZENworks 7 documentation Web site.

3.0 Installing ZENworks 7 Server Management with SP1

For detailed instructions, see the Novell ZENworks 7 Server Management Installation Guide.

3.1 Installation and Upgrade Prerequisites

Be sure to fulfill the prerequisites before upgrading to or installing ZENworks 7 Server Management with SP1:

  • Minimum Requirements: Your target servers and installation workstation must meet the minimum requirements as stated in Preparation in the Novell ZENworks 7 Server Management Installation Guide.

  • Schema Extensions: For installing only, you must extend the schema on the Novell eDirectory™ tree where you want ZENworks objects to be installed. When running the GUI installation program, select Server Management > Schema Extension and Product Licensing.

    For Linux-only systems, you must use the GUI installation program to extend the schema because the Linux installation script does not include a schema extension program.

    There are no new schema extensions between ZENworks 6.5 SP2 and ZENworks 7 with SP1. Therefore, you do not need to extend the schema when upgrading from ZENworks 6.5 SP2 or from ZENworks 7.

  • Novell iManager (optional): For Policy and Distribution Services, you can use Novell iManager in addition to Novell ConsoleOne® for managing the software. You must have iManager 2.5 or 2.6 installed on at least one NetWare®, Windows*, Linux*, or Solaris* server, because the version 7 with SP1 Policy and Distribution Services plug-ins are not compatible with any previous version of iManager.

    To install iManager 2.6 on NetWare or Windows servers, insert the Novell ZENworks 7 with Support Pack 1 Companion 1 CD and select Companion Programs and Files > Novell iManager.

    To install iManager 2.6 on Linux or Solaris servers, see Installing iManager > Installing a New Version of iManager on the iManager documentation Web site.

    To install iManager 2.5, obtain it from the Novell download Web site.

3.2 Installation Procedures

  1. Run the GUI installation program from the Novell ZENworks 7 Server Management with Support Pack 1 Program CD and extend the schema on the tree where you want the ZENworks objects created.

  2. Do one of the following:

    • For NetWare and Windows servers, go to the installation workstation, run the GUI installation program from the Program CD, and select the appropriate menu options:

      Server Management > Policy-Enabled Server Management (which includes Policy and Distribution Services, Server Inventory, and Remote Management)

      or

      Server Management > Management and Monitoring Services

    • To install Policy and Distribution Services or Management and Monitoring Services on Linux and Solaris servers, use an Xterm window to run the appropriate text-based installation script that is provided on the Program CD.

      To install Policy and Distribution Services on Linux, run:

      Program_CD/ZfS/TedPol/Linux/zfs-pds-install
      

      To install Policy and Distribution Services on Solaris, run:

      Program_CD/ZfS/TedPol/Solaris/zfs-pds-install
      

      To install Management and Monitoring Services on Linux, run:

      Program_CD/ZfS/SvrMgmt/mms/Linux/MMS_Linux_Install.pl
      

      Management and Monitoring Services is not supported on Solaris. Remote Management is not supported on Linux and Solaris. See Server Requirements in the Novell ZENworks 7 Server Management Installation Guide for details.

    • To install Server Inventory on Linux, run mount /media/cdrom to mount the Novell ZENworks 7 Server Management with Support Pack 1 Program CD, change to the CD mount directory, and run ./setup.

      Server Inventory is not supported on Solaris. See Server Requirements in the Novell ZENworks 7 Server Management Installation Guide for details.

  3. (Optional) To install the iManager plug-ins, if you have iManager 2.5 or 2.6 installed and you are running the GUI installation program, select Server Management > Web-Based Management Components.

3.3 Upgrade Procedures

You can upgrade directly to ZENworks 7 Server Management with SP1 from the following previous versions:

  •    ZENworks for Servers 3.0.2 or 3 SP2
  •    ZENworks 6.5 Server Management
  •    ZENworks 6.5 SP1 Server Management
  •    ZENworks 7 Server Management

You can upgrade using one of the following methods:

  • GUI Upgrade Program: Upgrades the following ZENworks components by using the installation program from the Novell ZENworks 7 Server Management with Support Pack 1 Program CD.

    •    Policy and Distribution Services
    •    Server Inventory
    •    Remote Management
    •    Management and Monitoring Services
  • Server Software Package: Upgrades the following ZENworks components using the .cpk files contained on the Novell ZENworks 7 with Support Pack 1 Companion 2 CD:

    •    Policy and Distribution Services
    •    Inventory Agent
    •    Remote Management

For more detailed upgrade information, see Upgrade in the Novell ZENworks 7 Server Management Installation Guide.

4.0 General Known Issues for ZENworks Server Management

The following are known issues affecting ZENworks Server Management in general:

4.1 Encrypted Attributes Not Supported

The ZENworks 7 Suite with SP1 does not support encrypted attributes, a feature included in Novell eDirectory™ 8.8x.

5.0 Known Issues for Policy and Distribution Services

The following sections list the software issues that are known for Policy and Distribution Services.

5.1 Installation Issues

The following are known installation issues.

5.1.1 Clusters do not fail over after installing ZENworks to an OES Linux cluster

When you attempt to fail over an OES Linux cluster after installing ZENworks Server Management, the services do not start. This is because the cluster load and unload scripts are not updated during installation of ZENworks on an OES Linux cluster (OES SP2 or earlier).

Workaround: As a prerequisite to installing ZENworks, you must patch the OES Linux cluster.

  1. If you upgraded to OES Linux SP2 using the support pack, run the oessp2prepatch.sh script.

    For information, see the OES Linux documentation.

  2. If you have not yet done so, purchase an activation code from Novell Customer Care for updating OES Linux.

  3. On your OES Linux cluster server, open a terminal window as root.

  4. Enter rug sl.

    This should display Novell_Update_server somewhere in the list.

  5. Assuming that Novell_Update_server is the second item listed, enter:

    rug act -s 2 1234567890 user@company.com
    

    where 2 identifies that you are selecting the second listed item, 1234567890 is your activation code, and user@company.com is your e-mail address.

  6. Then do one of the following:

    • For the entire OES Linux update (recommended), enter:

      rug pin -entire-channel oes
      
    • For only the applicable kernel and NCS patches that are required to resolve this problem, enter:

      rug pin patch-11078
      
      rug pin patch-11130
      
  7. Reboot the cluster.

  8. Install ZENworks to the cluster.

5.1.2 The NetWare cluster fails to load after installing ZENworks 7 with SP1

The installation unloads the NetWare cluster but does not try to reload it, because the timing cannot be predicted.

Workaround: Online the NetWare cluster after installation.

5.1.3 The Linux cluster fails to change its status after installing ZENworks 7 with SP1

The installation does not cause the Linux cluster to change its status.

Workaround: Offline, then online the Linux cluster after installation.

5.1.4 Cannot install the Subscriber software to a Windows XP device

In the Add Server dialog box during installation, Windows XP devices are not listed for selecting, nor can they be browsed for in Microsoft domains. Therefore, the Subscriber software cannot be installed to them.

Workaround: To enable the administrative share on the target Windows XP devices:

  1. In Windows Explorer, select the C: drive on the target Windows XP device, then select Tools > Folder Options > View.

  2. At the end of the Advanced Settings section, deselect Use Simple File Sharing (Recommended).

For more information, see TIDs 10097758 and 10098932 in the Novell Support Knowledgebase.

5.1.5 After installing, an “agentinfo.properties file not found” exception is given as the Server Management services are loading

After installing the product, an exception is given as the Server Management services are loading.

Workaround: Set each Subscriber’s working context at installation time.

5.1.6 On a Windows 2000 server using IIS 5.0, you cannot install Server Management NPMs using iManager's package manager

The error “Object not found (32)” is returned on a Windows 2000 server using IIS 5.0 (port 80) when attempting to use iManager's package manager to install the Server Management NPM files (located in the \NPM directory on the Novell ZENworks 7 Server Management with Support Pack 1 Program CD).

Workaround: To install the ZENworks NPM files, insert the Program CD on your workstation and select the following menu options: Server Management > Web-Based Management Components. This installs the zfs_polydistplugins.npm and zfsca.npm files.

5.1.7 Tomcat and iManager must be loaded during installation of the Policy and Distribution Services plug-ins

When installing the plug-ins using the Web-Based Management Components menu option, there is a wizard page that allows you to authenticate to the server. Tomcat and iManager must be loaded on the server before you authenticate to it.

5.2 Upgrade Issues

The following are known upgrade issues.

5.2.1 Upgrading to ZENworks 7 with SP1 fails to shut down the database

Even though the upgrade attempts to unload the database, it fails to do so, causing the upgrade process to end prematurely.

Workaround: Manually unload the database before running the upgrade.

5.2.2 Upgrading only Workstation Inventory or only Policy and Distributions Services when both are present on a server can cause the other service to not start

When you have both ZENworks 4.x Desktop Management Workstation Inventory and ZENworks 3.x Server Management Policy and Distribution Services installed and running on the same server, upgrading one but not the other to ZENworks 7 with SP1 can cause the other service to not start.

The problem lies with the ZENworks Web Server, which cannot properly start unless the upgraded service is started before the non-upgraded service.

Workaround: If you only upgrade Workstation Inventory, make sure that its service is started before you start the older Policy and Distribution Services service.

or

If you only upgrade Policy and Distribution Services, make sure that its service is started before you start the older Workstation Inventory service.

5.2.3 Services do not start correctly after upgrading them

If services have not started correctly after upgrading them, simply restart the services.

For more information, see Starting and Stopping Server Management Services in the Novell ZENworks 7 Server Management Installation Guide.

5.2.4 Upgrading from ZfS 3.0.2 causes Server Management to not work

When upgrading from ZfS 3.0.2 (ZENworks 6 Suite) to ZENworks 7 with SP1, information that is necessary for Server Management to function might not be created in the zfs-startup.xml file. Without this missing information, the upgraded Server Management software does not function.

This error only applies when upgrading from version 3.0.2 to ZENworks 7 Server Management with SP1. The lines are correctly created in the .xml file when upgrading from ZENworks 6.5 or 6.5 SP1 Server Management to version 7 with SP1.

Workaround: After upgrading to ZENworks 7 with SP1, do the following on each upgraded server:

  1. Open the zfs-startup.xml file in a text editor. It is located in the \zenworks directory.

  2. After the following line:

    <Parameter Name="Version2">Off</Parameter>
    

    insert these two lines:

    <Parameter Name="DistributorDN">Distributor_DN</Parameter>
    
    <Parameter Name="Password">distributor_password</Parameter>
    
  3. If the following line is also not present in the .xml file:

    <Parameter Name=Domain>Tree_Name</Parameter>
    

    insert it after the other two lines.

  4. Save the .xml file.

  5. Restart ZENworks on the server.

5.2.5 The upgrade summary sometimes fails to display when upgrading from ZfS 3.0.2

When upgrading to ZENworks 7 with SP1 from ZfS 3.0.2, the summary for the upgrade program sometimes fails to display and the log file is not created. When this happens, you receive no notification that the upgrade has finished.

Workaround: None. However, you can manually check the status of the upgrade. For more information, see the applicable upgrade section (Verifying That the Server Is Upgraded, Verifying That the Server Is Upgraded, or Verifying That the Servers Have Been Upgraded) in the Novell ZENworks 7 Server Management Installation Guide.

5.2.6 Unloading Java when upgrading NetWare 5.1 servers using the .cpk file creates long pauses

Although an upgrade performed on a NetWare 5.1 server using the Server Software Package is successful, a long pause, as much as 30 minutes, can occur after Java* has been unloaded by the upgrade program.

However, after the delay, Java reloads and the ZENworks services start.

Workaround: None.

5.2.7 Using a Server Software Package to upgrade from ZfS 3.0.2 fails

Using the Server Software Package (zsm7sp1_polydist.cpk) to upgrade from ZfS 3.0.2 can fail.

Workaround: Try restarting the services and verify that the services were not upgraded. If not, or the services do not restart or ZENworks fails to start, use the GUI upgrade method instead of the software package.

If the 3.0.2 version of the Server Management Database is loaded on a NetWare server, dbsrv7.nlm might not have unloaded. This causes an error in loading dbsrv8.nlm. To resolve this:

  1. On the DBSRV8 error screen, press the Spacebar to dismiss the message.

  2. Unload dbsrv7.nlm.

  3. Run mgmtdbs, which reloads dbsrv8.nlm.

5.2.8 ZENworks services occasionally fail to restart upon completion of a successful upgrade

Even though an upgrade appears to be successful, ZENworks can fail to restart.

Workaround: Do the following:

  • NetWare servers:  Execute the following NCF files in order:

    • 1. sys:\system\zfsstop.ncf
    • 2. sys:\system\zfs.ncf

    If ZENworks is installed to a volume other than sys:, such as in a cluster, change the volume name.

  • Windows servers:  Open the Services window and start the ZENworks services that are not running.

There is no upgrade path from Linux installations of ZfS 3.0.2; you must perform a new installation for Linux servers.

5.2.9 Erroneous error logged during database installation

When upgrading a ZENworks 6.5 or 6.5 SP1 server that already has Sybase* 8.0 installed, the summary might indicate that the database was not successfully upgraded. Because the server is already running Sybase 8.0, this error can be ignored.

5.2.10 The ZENworks 6.5/6.5 SP1 database is orphaned when upgrading to ZENworks 7 with SP1 on Windows servers

When upgrading the database from ZENworks 6.5 or 6.5 SP1 on a Windows server, a new copy of the database file is placed in an appended location, causing the 6.5/6.5 SP1 version of the database to no longer be used. Instead of placing the database file, such as zfslog.db, into \zenworks\database\pds, the upgrade places it into \zenworks\database\pds\zenworks\database\pds.

Workaround: Do the following:

  1. Open the Windows registry on the server.

  2. Access the following key:

    HKEY_LOCAL_MACHINE\SYSTEM\Current Control
    
    Set\Services\ASANYs_ZENWORKS\Parameters
    
  3. Double-click Parameters and remove the second set of \zenworks\database\pds from the path.

    The remaining path should now be:

    drive:\zenworks\database\pds\zfslog.db
    
  4. Access the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\NOVELL\ZENWORKS
    
  5. Edit the value in PDSDBPath by removing the second set of \zenworks\database\pds from the path.

    The remaining path should now be:

    drive:\zenworks\database\pds\zfslog.db
    
  6. Close the registry to save the changes.

  7. To recognize the changes, either restart the database service or reboot the server.

5.3 Tiered Electronic Distribution Issues

The following are known Tiered Electronic Distribution issues.

5.3.1 Distributions might fail because of certificate exceptions on Subscriber servers

When there are two or more Distributors sending Distributions to the same Subscriber, or a parent Subscriber in the routing hierarchy is also a Distributor, the end node Subscriber could reject a Distribution because the certificate was signed by a non-trusted Distributor, rather than the trusted Distributor that sent the Distribution.

  • Where two Distributors send to the same Subscriber, Subscriber configurations cached on the parent Subscriber from the different Distributors can cause this situation. Event logs indicate that the certificates need to be properly resolved, but doing so for the trusted Distributor does not resolve the problem.

    Workaround: Resolve certificates for the non-trusted Distributor so that the Subscriber recognizes it as a trusted Distributor and accepts Distributions from it.

  • Where a parent Subscriber is also a Distributor, the parent Subscriber's Distributor re-signs the Distributions before passing them on. This causes all of the downstream Subscribers to reject the Distribution because it is thought to be from an untrusted Distributor (because of a signature error or certificate exception).

    Workaround: Do not make a Distributor a parent Subscriber.

5.3.2 The Working Context field for a Solaris Subscriber is not disabled

Desktop Application Distributions are not supported on Solaris; however, in the Subscriber properties for a Solaris server, the Working Context field on the General tab appears to be available. It should be dimmed and inaccessible.

Workaround: Ignore this field for Solaris Subscriber servers.

5.3.3 Manual Distributions to Linux Subscribers require browsing for the working directory

For NetWare and Windows servers, the working directory is found by the Manual Distribution process. However, Linux server file systems are not recognized.

Workaround: Set up a share in Samba for the Linux servers. The Manual Distribution process then recognizes the Linux server's working directory as it would for a Windows server.

5.3.4 Encrypted Distributions do not work after upgrading to ZENworks 7 with SP1

After upgrading NetWare Subscribers to ZENworks 7 with SP1 from ZENworks 6.5, or from ZfS 3.0.2 via ZENworks 6.5, encrypted Distribution support is lost for the upgraded Subscriber servers.

Workaround: Reboot the upgraded NetWare Subscriber servers so that the encrypted Distributions can be extracted.

5.3.5 Exception given when upgrading a NetWare 6.5 SP3 (OES) server to ZENworks 7 with SP1 using the zsm7sp1_polydist.cpk file

When NetWare 6.5 servers are upgraded to SP3 (NetWare OES), a newer JVM* is installed that is incompatible with the zencommon.jar file in ZENworks 6.5, so the Server Policies and Server Software Package functionalities no longer work. Therefore, an exception is given when trying to upgrade OES servers to ZENworks 7 with SP1 using the Server Software Package.

Workaround: Choose one of the following options:

  • Install ZENworks 7 with SP1 using the GUI installation instead of using the .cpk file. The zencommon.jar file copied during the GUI installation of ZENworks 7 with SP1 is compatible with the JVM used by OES.

  • To install ZENworks 7 with SP1 using the .cpk file:

    Send the zencommon.jar file contained in the ZENworks 7 with SP1 download as a File Distribution to the target OES servers to replace the older zencommon.jar file with the ZENworks 7 with SP1 version.

    Restart ZENworks on the OES servers so that it recognizes the new zencommon.jar file.

    Send the zsm7sp1_polydist.cpk file as a Software Package Distribution to those OES servers to successfully upgrade them to ZENworks 7 with SP1.

  • To install ZENworks 7 with SP1 using the .cpk file, install ZENworks 7 with SP1 on the server before installing NetWare 6.5 SP3 (or OES) on the server. The ZENworks 7 with SP1 zencommon.jar file is compatible with the JVM used by OES.

5.4 Server Software Package Issues

The following are known Server Software Package issues.

5.4.1 For Text File components, a word followed by punctuation causes the word searched for to not be found

When creating a Server Software Package with a Text File component, if you configure the component to search for a word, but the word in the text file being searched is adjacent to a punctuation mark, the word is not discovered by the search. This is because the punctuation mark is considered by the search engine to be part of the word.

Workaround: Be aware of the possibility that punctuation can affect the ability of a search to locate words in a text file. You should account for that fact in your search patterns. When possible, review the text files to be searched to verify that your search pattern can be located.

5.5 Novell iManager or ConsoleOne Issues

The following are known Novell iManager issues.

5.5.1 XMLRPC error given when trying to set up a password for an older version of ZENworks Server Management

The password feature for Remote Web Console in iManager is new for ZENworks 7 Server Management with SP1. However, if you attempt to use this feature on servers running software older than ZENworks 7 Server Management with SP1, it fails because that software does not have the new code for the password feature, even though it appears to be available in Remote Web Console.

Workaround: None. Use the new password feature only on ZENworks 7 Server Management with SP1 servers.

5.5.2 iManager occasionally exits and sends the user to the iManager user/password login screen

The cause is currently unknown.

Workaround: Log in again and continue using iManager.

5.5.3 The FTP Distribution type does not support WU-FTP servers or Solaris 9 FTP servers

When creating an FTP Distribution type, if you attempt to connect to a WU-FTP server or a Solaris 9 FTP server, the plug-ins or snap-ins hang and browsing cannot be performed.

Workaround: None.

5.6 ZENworks Security Certificate Issues

The following are known security certificate issues.

5.6.1 Certificates cannot be re-minted when an error occurs

When you perform the following procedures you might receive an error message stating that the primary address and the DNS are mismatched:

  1. Start ZENworks (zfs.ncf) on a NetWare server where DNS is not set up.

  2. After the primary address has been acquired, stop ZENworks, then unload Java.

  3. Set up DNS.

  4. Restart ZENworks (zfs.ncf).

Workaround: The only way to solve the mismatch is to re-mint the security certificate on that server. To do this:

  1. Stop ZENworks.

  2. Delete the .keystore file.

  3. Delete the ted.cfg file from the following:

    • The Distributor sending the Distribution

    • Any parent Subscribers passing on the Distribution

    • Each end node Subscriber receiving the Distribution

    The ted.cfg file is re-created with the correct information when ZENworks is started again.

  4. Restart ZENworks.

  5. Re-resolve all Distributors' certificates for that server.

5.7 Sybase Issues

The following are known Sybase issues.

5.7.1 Erroneous Sybase error message

If you have installed Sybase on a NetWare server, the following error message might be displayed during the database operations:

Connection terminated abnormally.

Ignore this message.

6.0 Known Issues for Server Inventory

The following sections list the software issues that are known for Server Inventory.

6.1 Installation Issues

The following are known installation issues.

6.1.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 install the component again.

6.1.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 Server Management with SP1 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.

6.1.3 Issue with installing the Management and Monitoring Services Database on a machine that has the Sybase Inventory Database

If you install the Management and Monitoring Services database on a machine that has the Sybase Inventory database, the installation program changes the database cache size value from 128 MB to 99 MB in sys:\system\mgmtdbs.ncf. Consequently, the Sybase Inventory database does not work.

Workaround: After installing the Management and Monitoring Services database on a machine that has the Sybase Inventory database, do the following:

  1. Stop the Sybase Inventory database.

    For more information on how to stop the Sybase Inventory database, see Server Inventory in the Novell ZENworks 7 Server Management Administration Guide.

  2. Manually edit sys:\system\mgmtdbs.ncf to change the value of the database cache size to 128 MB. The database cache size is represented by the “-c” switch in mgmtdbs.ncf.

    A sample mgmtdbs.ncf in which the value of “-c” is 99 MB:

    load SYS:\ZENworks\Inv\DBEngine\dbsrv8 -gn 50 -c 99M -tl 300 -ti 0 -m -n server_name -x tcpip databases
    

    In the line mentioned above, change the value of “-c” to 128 MB, so the line is as follows:

    load SYS:\ZENworks\Inv\DBEngine\dbsrv8 -gn 50 -c 128M -tl 300 -ti 0 -m -n server_name -x tcpip databases
    
  3. Restart the Sybase Inventory database.

    For more information on how to start the Sybase Inventory database, see Server Inventory in the Novell ZENworks 7 Server Management Administration Guide.

6.1.4 Restarting Policy and Distribution Services on NetWare servers when installed with Server Inventory

During the ZENworks 7 Server Management with SP1 installation, if you choose to install Policy and Distribution services and the Inventory Standalone Pre-Configuration on NetWare servers, the ZENworks service starts after installation, but Policy and Distribution Services does not work.

Workaround: Do the following:

  1. Stop the ZENworks service by entering exit in the service window of the NetWare server.

  2. Restart the ZENworks service by entering zfs.ncf at the server console prompt.

6.1.5 ZENworks 7 with SP1 Inventory Server, Inventory Database, and the XML Proxy Service are not supported on NetWare 5.1 servers

Do not install the following Server Inventory components to a NetWare 5.1 server:

  •    Inventory Server
  •    Inventory Database
  •    XML Proxy Service

The GUI installation allows you to select NetWare 5.1 servers for installing these Server Inventory components, but this is not supported.

If you install Server Inventory on a NetWare 5.1 server, the server might abend while unloading Java.

Workaround: If you have already installed these components to a NetWare 5.1 server, you must perform the following tasks to prevent the Inventory services from being loaded on the server:

  1. Make a reliable backup of autoexec.ncf and mgmtdbs.ncf files, which are located in the sys:\system directory.

  2. Delete the following entries from the sys:\system\autoexec.ncf file:

     ; ZENworks Inventory Settings
    
    StartInv.ncf
    
  3. Delete the path to mgmtdb.db from the sys:\system\mgmtdbs.ncf file.

6.1.6 ZENworks service gives errors after installing Inventory Proxy

After you install Inventory Proxy, ZENworks service gives errors.

Workaround: You must perform the following tasks to prevent errors, after installing Inventory Proxy:

  1. Make a backup of /etc/opt/novell/zenworks/zws.properties.

  2. Edit /etc/opt/novell/zenworks/zws.properties.

    Modify the entry:

    Servlet.2.path =//etc//opt//novell//zenworks//XMLProxyServlet.jar
    

    to

    Servlet.2.path=/usr/share/java/novell//zenworks//common/XMLProxyServlet.jar
    

    Modify the entry:

    passwordFile=null//etc//opt//novell//zenworks//password.txt
    

    to

    passwordFile=//etc//opt//novell//zenworks//password.txt
    

    Save these file changes.

6.1.7 New database used after upgrading from ZSM 7 to ZSM 7 SP1

After updating to ZSM7 SP1 a new management database is being used and old entries will not be seen.

Workaround: If no distributions have been performed after the update to ZSM 7 SP1, then do as follows:

  1. Stop dbsrvr8.

  2. Change the path from volume:\zenworks\database\pds\zenworks\database\pds to volume:\zenworks\database\pds in the sys:/system/zenworks.properties and sys:/system/mgmtdbs.ncf files

  3. Start the database management with the sys:/system/mgmtdbs.ncf file.

6.2 Reporting Issues

The following are known reporting issues.

6.2.1 Navigating Inventory reports using the keyboard

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

6.3 Sybase Issues

The following are known Sybase issues.

6.3.1 Erroneous error message

If you have installed Sybase on a NetWare server, the following error message might be displayed during the database operations:

Connection terminated abnormally.

Ignore this message.

7.0 Known Issues for Remote Management

The following sections list the software issues that are known for Remote Management.

7.1 Remote Control Issues

The following are known remote control issues.

7.1.1 Remotely controlling Windows 2003 servers after a Remote Desktop session

If a user uses the Remote Desktop Connection to connect to a Windows 2003 server, and then initiates a Remote Control session on that server, the Remote Control console is black and you cannot remotely control it.

Workaround: Users with a Windows 2003 server should log in locally before you attempt to remotely control their servers.

7.1.2 DirectX applications do not run in exclusive mode during a Remote Control or Remote View session

On Windows 2000/2003 servers, DirectX* applications do not run in exclusive mode during a Remote Control or Remote View session.

7.1.3 Removing wallpaper during a Remote Control session

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

Workaround: Manually suppress the wallpaper of the managed server.

7.1.4 Remote Control with a full-screen DOS window

During a remote control session on the managed server, 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.

7.1.5 Remote Management Agent Help File Might Fail to Launch

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

Workaround: To view the help, navigate to the following location and double-click rcagent.chm:

zenworks_agent_directory\rmagent\nls\language_directory

7.2 Hardware and Software Behavior Issues

The following are known behavior issues for hardware and software.

7.2.1 Screen blanking

  • The screen blanking feature might not work properly in managed servers with some video adapter cards, such as Hawkeye Number 9 and ATI Rage* P/M Mobility AGP 2x. We recommend that you test the screen blanking feature with your video adapter before deploying the Remote Management Agent in your enterprise.

  • When you invoke the screen blanking option on your managed server and change the color resolution on the server to 256 colors, the managed server might hang.

    Workaround: Restart the managed server.

7.2.2 Wallpaper suppression on a Windows 2003 Server machine

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

7.2.3 Mouse cursor on the Windows 2003 Server managed server flickers during the Remote Management session

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

7.2.4 Cursor support for Remote Management

The animated and the colored cursors on the managed servers are not supported for Remote Management.

7.2.5 Multiple monitor support

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

8.0 Known Issues for Management and Monitoring Services

The following sections list the software issues that are known for Management and Monitoring Services.

8.1 General Issues

  • On a NetWare 6.5 server running only IPX™, the MIB services might not be discovered.

  • If SNMP traps arrive faster than twenty traps per second, continuously for more than four hours, you might experience the following problems:

    • Major, Minor, and informational traps might be dropped.

    • Ticker tape updating might stop.

    • If the Active Alarm View, Alarm History View, Alarm summary View, or any such view that displays the Alarm View is kept open in ConsoleOne, the Alarm Manager might not be able to process more than five alarms per second.

  • In ConsoleOne (both the console view and atlas view), the name of two or more segments might appear to be same.

  • The Computer System in the Selected Container report and the Alarms Detail report in the custom atlas do not list the information of sublevel containers. The reports provide information for only the computer system present in the container on which reporting has been launched.

  • The trend views display data only up to a week for the parameters that are monitored by default on a Linux server.

    You can change this by increasing the number of buckets for the monitored parameters in the configuration file and running the advtrend read_cfg command.

  • On a NetWare 6.5 server, the MIB browser does not display values for the agent addresses that are of type IPX. An error message is displayed. Click Resume to continue.

  • NXPLANZ fails to discover a NetWare server with the LANalyzer® agent installed if it has two NIC cards configured for load balancing. However, other LANalyzer agents on the same network that do not have load balancing configured are discovered correctly.

8.2 Upgrade Issues

The following are known upgrade issues.

8.2.1 Upgrading to NetWare 6.5 SP2 from NetWare 6 SP4 changes the commands in autoexec.ncf

If you upgrade a NetWare 6 SP4 server running the ZENworks Management and Monitoring Services component to NetWare 6.5 SP2, the sequence of commands in autoexec.ncf is changed, causing Management and Monitoring Services to not start.

Workaround: To correct the sequence of commands in sys:\system\autoexec.ncf:

  1. Stop Management and Monitoring Services by executing the following command at the server console prompt:

    For ZENworks 6.5 Server Management and later, enter stopmms -n.

    For ZfS 3.0.2, enter the following commands:

    • unmw (to stop all of the Management and Monitoring Services services)

    • mmsnaming -exit (to stop the Naming Server)

  2. To ensure that Java services have exited properly, enter java -showall at the console prompt.

    If this displays any services, enter java -killall to manually stop the services.

  3. Open sys:\system\autoexec.ncf and change the following sequence from:

    mwserver
    
    netxplor
    
    sloader
    
    mgmtdbs
    

    to:

    mgmtdbs
    
    mwserver
    
    netxplor
    
    sloader
    
  4. Save the file.

  5. To start Management and Monitoring Services automatically, reboot the NetWare server.

    or

    If you want to start the services manually, enter the following on the NetWare server console prompt:

    ZENworks 6.5 Server Management and later

      startmms
    

    ZENworks for Servers 3.0.2

      mgmtdbs
    
      mwserver
    
      netxplor
    
      sloader
    

8.3 Trend View Issues

The following are known Trend View issues.

8.3.1 Viewing Trends and Summaries with the ConsoleOne snap-ins

While using the ZENworks 7 with SP1 ConsoleOne snap-ins to view the Trend and Summary for a Windows 2000 Server running the ZfS 3.0.2 Agent, a communication error message pops up and no data is shown in the view.

Workaround: Update the ZfS 3.0.2 agent to ZfS 3.0.2 IR2 or later and restart the agents on the Windows 2000 server.

8.3.2 The Trend View incorrectly displays strings

In a Trend View, if an Adapter number has “E” in the string followed by a numeric value, then “E” is taken as an exponential in the string and zeros are displayed as its numeric value. For example, the Adapter number 1 008048134E10 is displayed as 1 0080481340000000000.

8.4 Event Logging Issues

The following are known event logging issues in Windows Server.

8.4.1 Performance Monitor counter failure messages are continually logged into the Windows Event log file

When you install the Server Management for Windows, several performance monitor counter failure messages are repeatedly logged into the Windows Event log file (event IDs such as 1008, 1009, 2001, 2002). For example:

The Open Procedure for service “Remote Access” in DLL “c:\winnt\system32\rasctrs.dll” failed. The performance data for this service is not available. Status code returned is data DWORD 0.

Sometimes the SNMP service crashes when these events are posted in the Events Viewer. For example, on a Windows 2000 machine with the AppleTalk* protocol installed and the performance enabled, the following events are posted in the Events Viewer and the SNMP service crashes:

  1. Unable to open the ATK device for R access. Returning IO status Block in Data.

  2. The open procedure for the “AppleTalk” in DLL “c:\winnt\system32\atkctrs.dll” has taken longer than the estimated time to complete. There may be a problem with this extensible counter or the service it is collecting data from or from s/m may have been very busy when this call was completed.

  3. The open procedure for service “AppleTalk” in DLL “c:\winnt\system32\atkctrs.dll” failed. Performance code data for this will not be available. Status code returned in data DWORD 0.

The Trending Agent (NTREND) of the Server Management Agent uses performance counters to obtain performance data. The performance monitor checks the availability of all the counters listed in the registry. Either a service is installed, but the performance counters are disabled, or vice versa. These events are logged into the Windows Event Log.

When the performance counters are queried, the extension performance counter's DLLs are loaded in the SNMP address space. If there is a problem in the extension performance counter's DLLs, the SNMP service crashes.

Workaround: To keep the SNMP service from crashing, disable the performance counters for the problem DLL by performing the following steps:

  1. Install the latest version for the specific Windows platform.

  2. Note the performance counter events that are logged in the Windows Event Log.

  3. For Windows 2000 onward, download and install the exctrlst_setup.exe file from the Microsoft* Web site. For Windows NT*, download and install the resource kit that contains the exctrlst_setup.exe file from the Microsoft Web site.

  4. Run exctrlst_setup.exe from the installed location.

  5. In the Windows event log, if the event is:

    The Open Procedure for service “Remote Access” in DLL “c:\winnt\system32\rasctrs.dll” failed. The performance data for this service is not available. Status code returned is data DWORD 0.

    This means that the performance counters are enabled, and the RAS is installed but might be disabled. Use exctrlst_setup.exe to enable the RAS service to function correctly and disable the performance counters:

    1. Select the service in the exctrlst window.

    2. Select Remote Access.

    3. Deselect the Performance Counters Enabled check box.

  6. Shut down and restart the machine.

For AppleTalk, disabling the performance counters for the service solves the problem.

8.5 Inactivity Node Monitoring Issues

The following are known monitoring issues.

8.5.1 Adding nodes to monitor for inactivity

The selected nodes are not added for monitoring when trying to add nodes to the monitored nodes for checking inactivity.

Workaround: If your preferred RMON Agent for the segment is a NetWare server, unload and reload the Traffic Analysis Agent on the server.

8.6 Sybase Issues

The following are known Sybase issues.

8.6.1 Erroneous error message

If you have installed Sybase on a NetWare server, the following error message might be displayed during the database operations:

Connection terminated abnormally.

Ignore this message.

8.7 Probe Manageability Issues

The following are known probe manageability issues.

8.7.1 Probe Manageability may not work over NCP

In case of SNMP over NCP™, if you use the Probe Manageability tool without logging in to the NetWare server, it does not prompt the user for authentication.

Workaround: Before using the the Probe Manageability tool, authenticate to the NetWare server.

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

10.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 http://www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2006 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 at http://www.novell.com/company/legal/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

For a list of Novell trademarks, see the Novell Trademark and Service Mark list at http://www.novell.com/company/legal/trademarks/tmlist.html.

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