If you are using Novell ZENworks 10 Asset Management in the standalone mode (without ZENworks 10 Configuration Management), see the Asset Management Readme at the ZENworks 10 Asset Management documentation Web site.
The issues included in this document were identified for Novell ZENworks 10 Configuration Management SP3.
For information about the new features or enhancements, see the Novell ZENworks 10 Configuration Management Getting Started Guide.
For system requirements and installation instructions, see the Novell ZENworks 10 Configuration Management Installation Guide.
For administrative tasks, see the Novell ZENworks 10 Configuration Management SP3 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 Configuration Management SP3 (10.3):
Table 1 Readme Updates
|
Date |
Readme Item Added or Updated |
|---|---|
|
April 6, 2012 |
AdminStudio 11 is now supported. Added the following known issue to Section 5.3, AdminStudio: |
|
November 8, 2011 |
AdminStudio 10 SP2 is now supported. |
|
August 19, 2011 |
Added the following known issue to Section 5.3, AdminStudio: |
|
January 19, 2011 |
|
|
July 27, 2010 |
|
|
April 22, 2010 |
Added additional information to the following issue: |
You can upgrade Primary Servers and managed devices directly to ZENworks 10 Configuration Management SP3 from the following versions:
ZENworks 10 Configuration Management SP2 (10.2)
Update for ZENworks 10 Configuration Management (10.2.1)
Update for ZENworks 10 Configuration Management (10.2.2)
For detailed information about upgrading from a previous version of ZENworks 10 Configuration Management to ZENworks 10 Configuration Management SP3, see the ZENworks 10 Configuration Management SP3 Upgrade Guide.
In ZENworks 10 Configuration Management SP3, the registry structure has changed from HKLM\Software\Novell\ZENworks to HKLM\Software\Novell\ZCM. When you upgrade from a previous version of ZENworks 10 Configuration Management to ZENworks 10 Configuration Management SP3, the registry structure changes are automatically made.
IMPORTANT:If you have only ZENworks 10 Asset Management SP2 installed (without ZENworks 10 Configuration Management), and the check box for the agent feature is selected in ZENworks Control Center ( > > ), you must do the following before upgrading from ZENworks Asset Management 10.2.x to ZENworks 10 Asset Management SP3:
In ZENworks Control Center, click the tab.
In the Management Zone Settings panel, click .
Click .
Deselect the check box next to , then click .
Select the check box next to , then click
For a list of the resolved issues in ZENworks 10 Configuration Management SP3, see TID 7005455 in the Novell Support Knowledgebase.
This section contains information about ZENworks Configuration Management issues that might occur.
This section contains information about issues that might occur when you install ZENworks 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 the update fails.
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
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.
During the command line installation of ZENworks 10 Configuration Management SP3 on a Linux* server, if you choose to create an MS SQL Server* database or an Oracle* database, and subsequently specify an existing database username, the installation fails at the end.
Workaround: Specify a new database username while creating the database.
The installer prompts for the first reboot after completing the installation of ZENworks Asset Management. The server prompts for a reboot again to remove any additional packages that might have been installed while installing ZENworks Asset Management.
Workaround: None
In the ZENworks 10 Configuration Management SP3 Installation Wizard, the Select ZENworks Ports page does not prompt you to configure any other port if port 2645 is busy. The installation proceeds but authentication to the user source might not work.
Workaround: Before you install ZENworks 10 Configuration Management SP3, make sure that port 2645 is free.
(Fixed in v10.3.1) When you install ZENworks 10 Configuration Management on SLES 11, the server components and default ZENworks Adaptive Agent are installed. However, the ZENworks Server is unable to connect to the default agent because the default port 7628, which is used by the ZENworks Adaptive Agent, is not automatically opened. The following message is displayed in ZENworks Control Center ( > > click the device > > ):
Unable to connect through IP Address or Host Name
Workaround: Do one of the following:
Manually open port 7628.
Disable the firewall settings.
If you have a Windows Vista managed device that has ZENworks 10 Configuration Management SP3 (10.3.0) registered to a ZENworks 10 Configuration Management SP3 Primary Server, the managed device fails to contact the server after you upgrade the server to ZENworks 11.
Workaround: To reconnect the managed device with the ZENworks 11 Primary Server, do one of the following:
Option 1: Upgrade the managed device to 10.3.1, and then to ZENworks 11.
Option 2: If you choose not to upgrade the managed device to ZENworks 11, unregister the device from the ZENworks Configuration Management 10.3 zone and manually register it to the ZENworks 11 Primary Server by using the zac reg command.
This section contains information about accessibility issues with ZENworks Configuration Management.
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. When you do this, mouse functions are controlled by using the numeric keypad.
This section contains information about issues that might occur with AdminStudio 10 SP2 for ZENworks Configuration Management:
When you try to install AdminStudio 10 on a 64-bit Windows XP SP2 device, the following error message is displayed:
The system administrator has set policies to prevent this installation.
Workaround:To enable the installation of AdminStudio 10, perform the following steps:
Click > > > > .
In the left pane, right-click and select .
Click .
is displayed in the right pane.
Double-click and apply the software restriction policy to and .
Restart the device.
When you try to uninstall AdminStudio 11 on a 64-bit Windows 7 device, the following error message is displayed:
You must be an Administrator to remove this application. To remove this application, you can log on as an administrator, or contact your technical support group for assistance.
Workaround: Perform the following steps:
Click .
In the left pane, right-click and select .
Click .
Enforcement is displayed in the right pane.
Double-click and apply the software restriction policy toand .
Restart the device.
This section contains information about issues that might occur with Authentication.
If you change the Authentication mechanism for an Authentication server, you must stop and restart the ZENworks services before the change takes effect.
This section contains information about issues that might occur when you use bundles in ZENworks Configuration Management.
The File bundles assigned to a device are displayed on the managed device even if the Bundle Management module is disabled on the device. This is because the Inventory Management module is enabled on the device. You can install or launch the bundle through zac commands.
Workaround: None.
This section contains information about issues that might occur when you use Imaging in ZENworks Configuration Management.
You cannot take an image of the Linux device (Satellite or managed device) in the ZENworks Automated mode because the Linux device does not have the image-safe data.
Workaround: Take the image of the Linux device in the ZENworks Imaging Maintenance mode.
This section contains information about issues that might occur during migration to ZENworks Configuration Management.
If you run the ZENworks Configuration Management Migration utility on a device that has Firefox * 3.0.x set as a default browser, the help file is not displayed when you click the Help icon.
Workaround: Set Firefox 2.0 or Internet Explorer* as the default browser on the device.
This section contains information about issues that might occur when you use Patch Management in ZENworks Configuration Management.
Deployment of certain .NET patches might require that the latest Windows Installer be installed. Otherwise, you can receive errors when deploying those patches.
Workaround: Prior to deploying .NET patches, verify whether Windows Installer is a prerequisite. If necessary, create a bundle to deploy the latest Windows Installer (version 3.1 or later) to your systems. Windows Installers are available from Microsoft.
When you upgrade from Update for ZENworks 10 Configuration Management (10.2.2) to ZENworks 10 Configuration Management SP3 (10.3), all the cached patches are reverted to the uncached status and all baseline assignments are removed because ZENworks 10 Configuration Management re-creates all patches as a new type of bundle with new bundle attributes in a structured folder hierarchy. This helps you to easily replicate patch content to Satellites within the Management Zone. Additionally, the patch baseline functionality now includes reboot notification and prompting.
Workaround: After upgrading to ZENworks 10 Configuration Management SP3, you must allow time for the patch subscription replication to run and for patch detection to complete. To speed up this process, use the “Update Now” button to force an immediate download of the patch subscription. You must also allow the DAU (Discover Applicable Updates) cycle to run on all target devices within the network to re-populate the patch status tables. Finally you should re-cache the desired patch bundles and re-create all baselines.
This section contains information about issues that might occur when you use Personality Migration in ZENworks Configuration Management.
While saving the settings and data to a .pnp file, if you choose to use the to span the content to multiple files, you must specify a password in the option.
Workaround: None
Workaround: Before migrating the printer settings from the source device to the destination device, do the following:
Create a directory named PrinterDrivers in any of the logical drives such as C:, D:, or E:.
Download and copy the unzipped driver to the PrinterDrivers directory.
When you create bundles by using the Store Personality or Apply Personality actions, the bundles always run as a dynamic administrator. The dynamic administrator does not have the Read or Write access to the authenticated network shares, and therefore cannot store or apply a PNP file from authenticated network shares.
Workaround: To store and apply personalities, the user group should have Write and Read access to the shared location when you create bundles by using the Store Personality and Apply Personality actions.
This section contains information about issues that might occur when you use Policy Management in ZENworks Configuration Management.
(Fixed in v10.3.1) User configuration settings configured in the Group policy are not applied in the Terminal sessions of Windows* Server* 2003, Windows Server 2008, and Windows Server 2008 R2 devices.
Workaround: To enable the user configuration settings configured in the Group policy to be applied on the device:
Open the Registry Editor.
Go to HKLM\Software\Microsoft\Windows\CurrentVersion\Run.
Create a string called ZENUserDaemon, and set its value to ZENworks_installation_dir\bin\ZENUserDaemon.exe.
Go to HKLM\Software\Novell\ZCM.
Create a string called DisableUserDaemonHealing, and set the value to True.
Reboot the device.
NOTE:The Internet Explorer settings configured in the Group policy are not applied on the device even if you have adopted the suggested workaround. See TID 7005804 at Novell Support http://www.novell.com/support/microsites/microsite.do
This section contains information about the issues that might occur when you use the Remote Management feature in ZENworks Configuration Management.
If you remotely connect to a managed device through 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 Microsoft Support Web site and install it on the managed device.
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.
Modifying the report layouts of the predefined reports is not recommended.
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:
Delete the cookies from your browser.
Close all browser instances.
Log in to ZENworks Control Center, then launch the ZENworks Reporting Server InfoView.
Workaround: Click ( > ) 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 on the ZENworks Reporting Server InfoView page.
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.
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:
From the desktop menu, click > > > > to display the Central Configuration Manager window.
Click .
Wait 2 to 3 minutes for the services to restart.
On Linux: Restart the BusinessObjects Enterprise services:
Stop the BusinessObjects Enterprise services by running the following command as a root user:
/etc/init.d/BobjEnterprise120 stop
Wait 2 to 3 minutes for all the services to stop.
Start the BusinessObjects Enterprise services by running the following command as a root user:
/etc/init.d/BobjEnterprise120 start
Wait 2 to 3 minutes for all the services to start.
ZENworks Reporting might not contain a reference to users that were created by using the ZENworks 10 Configuration Management SP2 user source. Therefore, ZENworks Reporting fails when you log in to ZENworks Control Center by using an administrator account (such as Administrator@windowdomain.com) created in ZENworks Configuration Management 10 SP2.
Workaround: On the ZENworks Reporting Server, use the following command to create users for the administrator account that was created by using the ZENworks 10 Configuration Management SP2 user source:
zman rpau complete_user_name
where the complete_user_name is the administrator account, such as Administrator@windowdomain.com.
In the ZENworks Reporting Server InfoView, the Suites or Software Collection reports display inaccurate data if you add Installation dimensions to them. The Installation dimensions are located in > > > .
Workaround: None.
If you launch the ZENworks Reporting Server InfoView in Firefox 3.5, and you select as the target window in the Create Hyperlink dialog box while linking a ZENworks Report to a User Details Report, the User Details Report data is not displayed in the new browser window.
Workaround: While linking a ZENworks Report to a User Details Report in a Firefox 3.5 browser, select as the target window in the Create Hyperlink dialog box.
If ZENworks Reporting Server is installed on a Linux Primary Server, reporting does not work if the ZENworks database is an MS SQL Server database and the authentication mode is Windows Authentication.
Workaround: See TID 7006288 at Novell Support.
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.
This section contains information about issues that might occur with Satellite devices in ZENworks Configuration Management.
Workaround: After unretiring the Linux Satellite from the Management Zone, restart the novell-zenworks-xplatzmd service.
The Primary Server Replication and Satellite Server Replication settings for a bundle or policy that has content are inherited by default from the settings established for the Management Zone. In the Settings page of the bundle or policy in ZENworks Control Center, the value of is displayed as for the Primary Server Replication and Satellite Server Replication settings. Additionally, the bundle or policy is included to be hosted on a specified Primary Server and is excluded from being hosted on the specified Satellite.
If you change the settings for the Satellite to include the bundle or policy to be hosted on the server, the Satellite Server Replication inheritance setting in the bundle or policy is appropriately changed to the bundle or policy that been added to the Satellite. However, the Primary Server Replication Setting of the bundle or policy is also automatically modified.
Workaround: Manually revert the inheritance setting for the Primary Server Replication.
In ZENworks Control Center, do either of the following:
To revert the inheritance settings for the Primary Server Replication for a bundle, click the tab.
To revert the inheritance settings for the Primary Server Replication for a policy, click the tab.
Click the bundle or policy that you have manually included in the Satellite.
Click > .
Click .
Click .
A Linux Satellite fails to communicate with its Primary Server after you upgrade it from ZENworks Configuration Management 10.2.x to ZENworks Configuration Management 10.3.x if the Primary Server has multiple hostnames.
Workaround: Perform the following tasks on the Linux Satellite:
Update the /etc/opt/novell/zenworks/initial-web-service file with the URLs that consist of all the hostnames of the Primary Server with which the Satellite communicates. You must specify all the URLs on the same line by using semi-colon (;) as the delimiter.
The initial-web service file contains by default one hostname and the IP address of the Primary Server. For example, the default content is:
https://zcm-sles11-64:443;https://10.0.0.0:443;
If the Primary Server has an additional hostname as zcm-sles10-100, you must append the hostname in the initial-web service file as follows:
https://zcm-sles10-64:443;https://10.0.0.0:443;https:// zcm-sles10-100:443
Do one of the following:
Clear the ZENworks cache by executing the zac cache-clear command, then restart the ZENworks Adaptive Agent by executing the /etc/init.d/novell-zenworks-xplatzmd restart command.
Stop the ZENworks Adaptive Agent service by executing the /etc/init.d/novell-zenworks-xplatzmd stop command, then start the service with the --clean option by executing the /etc/init.d/novell-zenworks-xplatzmd start --clean command.
Upgrade the Satellite to ZENworks Configuration Management 10.3.x.
This section contains information about issues that might occur with the ZENworks Adaptive Agent in ZENworks Configuration Management.
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.
If you deselect the 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.
This section contains information about issues that might occur when you use ZENworks Control Center.
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. If cookies are not 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 runs 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 use only Internet Explorer to run ZENworks Control Center, do not use underscores in your server names.
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.
This section contains information about issues that might occur when you use the zman command line utility.
Using the man zman command for Simplified Chinese and Traditional Chinese doesn’t display any help. It only displays the tilde (~) character.
Workaround: None.
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 © 2010-2011 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.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.