The information in this Readme pertains to:
NOTE:This document has been updated to include the ZENworks Reporting section.
This section includes the following:
For detailed information about the new features or enhancements in ZENworks 11 SP3 Beta, see Whats New in ZENworks 11 SP3 Beta
.
The new platforms that are supported in ZENworks 11 SP3 Beta include the following:
Primary Server Support
Windows 2012 Server Standard x86_64
Red Hat Enterprise Linux 5.8, 5.9, 6.3, and 6.4 x86_64
Managed Device Support
Windows 8 x86 and x86_64
Windows 2012 Server Standard x86_64
Red Hat Enterprise Linux 5.8, 5.9, 6.3, and 6.4 x86_64
Browser Support
Firefox ESR version 10 and 17
Firefox version 20 and 21
Internet Explorer versions 8, 9, and 10
For additional information on the System Requirements and for instructions on how to install ZENworks 11 SP3 Beta, refer the ZENworks 11 SP3 Server Installation Guide.
For detailed information on prerequisites and instructions for upgrading Primary Servers, Satellites, and managed devices to ZENworks 11 SP3 Beta, refer theZENworks 11 SP3 Upgrade Guide.
This Readme lists the issues specific to ZENworks 11 SP3 Beta. For all other ZENworks 11 SP3 Beta documentation, see Novell ZENworks 11 SP3 documentation Web site.
This section contains information about issues that might occur while you work with ZENworks 11 SP3 Beta:
Section 1.5.2, The System Update progress is not visible on Windows 8 and Windows 2012 devices
Section 1.5.6, Unable to share Preboot and Patch bundles with Subscribers
Section 1.5.15, Novell ZENworks File Upload plug-in will not work with Internet Explorer 10.
Section 1.5.16, Full Disk Encryption is not supported on Windows 8 devices that use UEFI BIOS
Section 1.5.17, Full Disk Encryption is not installed on upgraded devices
Section 1.5.21, The Audit log tab shows events that are not applicable for Linux and Mac devices
On a Windows 8 machine, if you right-click the ZENworks bundle shortcut in the Start screen and choose the uninstall option in the charms bar, the ZENworks bundle shortcut fails to point at the underlying application or msi installer in the Add or Remove Programs screen of the Control Panel.
The uninstall option that is in the charms bar of the Windows 8 Start screen is not supported for ZENworks bundle.
Workaround: None
When you perform a System Update on a Windows 8 or Windows 2012 device, the System Update progress is not displayed as a notification on the Start screen.
Workaround: None
The ZENworks Control Center Upgrade Primary Server Notification message for ZENworks 11 SP3 system upgrade shows an incorrect list of Primary Servers. After a 32-bit Primary Server is migrated to a 64-bit Primary Server, the details of the 32-bit Primary Server are still displayed in the list as the old entries on the servers are not deleted automatically.
Workaround: After a successful migration, delete the old entries on the Primary Servers manually.
While installing a Primary Server on a Windows Server 2012 machine, a Windows pop-up displays this error message on the Post Installation page:
.Workaround: Enable .Net 3.5 on the machine before installing the ZENworks Primary Server.
Workaround: Create multiple bundles with a smaller number of content files at the Publisher zone before starting the replication session.
The following types of bundles cannot be shared with subscribers:
Preboot bundles: ZENworks servers host content files that are a part of the content repository. Preboot bundles might contain.zmg files that are not a part of the ZENworks content repository. The Subscribers cannot download the .zmg files and replicate the Imaging bundle. As a result, you cannot share a Preboot bundle or assign it to Subscribers, Subscriber groups, or Subscriber folders.
Patch bundles: Sharing of Windows, Linux, or Macintosh Patch bundles is not supported. A ZENworks subscription does not ensure that the modules and services related to Patch Management are enabled and running in a Subscriber zone. Hence, the replication of Patch bundles is prevented. You cannot share a Patch bundle, or assign it to Subscribers, Subscriber groups, or Subscriber folders. The content in the /Bundles/ZPM folder for Patch bundles cannot be replicated even if it contains other bundles because they are automatically filtered.
Workaround: None.
If you upload a 32-bit.wim file on a server and boot a 64-bit device into the PXE, you can see the option. However, you will be unable to boot into the third-party distro because the required files are not available on the server.
Workaround: If booting into the third-party distro fails, ensure that the.wim file for that particular architecture has been uploaded to the server by checking the availability status in ZENworks Control Center.
The TFTP replication action synchronizes the TFTP content of the Satellite Server with that of the latest upgraded ZENworks server. As a result, the Image Restore operation from the older version of the Satellite fails.
Workaround: Exclude the older version of the Satellite server from TFTP replication.
In a Firefox browser, when you try to scroll through the logged audit events in the dashboard or any other audit-related pages, or the content in the audit event configuration settings tree, it does not scroll effectively like a normal Web page.
Workaround: Disable the smooth scrolling option in Firefox:
In the Firefox browser, click
.Click the
tab.Under
, uncheck the option.When you upload the tntfs.zip file on a ZENworks 11 SP3 Server and replicate it on all Primary and Satellite Servers, the bootcd_tntfs.iso file creation fails on RHEL devices. This is because the genisoimage RPM file is not installed on RHEL Servers.
Workaround: Install the latest genisoimage RPM (genisoimage-1.1.9-11.el6.x86_64.rpm) file on RHEL Servers.
When you restore a Windows 8 image from a Virtual Machine on a VMwareESX Server by using the legacy NTFS driver, the system does not boot up to the login screen and a blank screen appears after the restoration.
Workaround: None.
When the Startup Location is set at the device, folder or zone level, you can select the time for which this is effective on an agent by using the
option in ZENworks Control Center. The default value for this setting is 2 minutes. The maximum value is 10 minutes. However, the agent remains in the Startup Location only for 2 minutes regardless of the time selected.Workaround: None.
The Collection role is used to upload all Audit events from the agent to the server. However, the Audit role is displayed in the
screen even though it does not exist. This issue does not have any impact on the functionality and will be resolved before the final shipment of ZENworks 11 SP3.Workaround: Not applicable.
When you import more than five administrators from the user source, the relevant audit events are not generated.
Workaround: Do not import more than five administrators from the user source at a time.
You cannot use the Novell ZENworks File Upload plug-in with Internet Explorer 10.
Workaround: None
Full Disk Encryption is now supported on Windows 8 devices that use traditional (non-UEFI) BIOS but is not supported on Windows 8 devices that use UEFI BIOS.
Full Disk Encryption is not installed to existing managed devices during upgrade (system update) if the devices did not previously have Full Disk Encryption installed. The primary scenario affected by this is when you update a non-UEFI Windows 8 device. Full Disk Encryption is not installed because it was not supported on Windows 8 devices in previous releases, so there is no software to update.
Workaround: This issue will be fixed in the final SP3 release product. For this beta, you must uninstall the ZEnworks Adaptive Agent on the device and perform a new installation.
Location-based security policies that include non-default locations are not replicated correctly to subscribers. Depending on the policy, the loss of the location information might not be reported after the replication, or the policy might not be created.
Workaround: None. Replication of security policies to subscribers is not supported in this beta.
A Group Policy cannot be edited if Firefox 20.0, 21.0, and 22.0 is used to launch ZENworks Control Center.
Workaround: To edit the Group Policy follow the instructions provided in the ZENworks11SP3_Beta_Patch_827920.zip file present in the current download location.
A Group Policy cannot be created if Firefox 22.0 is used to launch ZENworks Control Center, as it does not launch the Group Policy Helper tool to configure the settings.
Workaround: To create a Group Policy, Firefox 22.0 should be opened in the Administrator mode to launch ZENworks Control Center.
ZENworks Endpoint Security Management and User Management-related events are only applicable for Windows devices, not for Linux or Mac devices. Hence, they should not be displayed in the audit tree. However, they are displayed in the audit tree of Linux and Mac devices.
Workaround: None. Ignore these events.
This section includes the following:
For detailed information about the new features or enhancements in ZENworks 11 SP3 Beta, see Whats New in ZENworks 11 SP3 Beta
.
The platforms that are supported in ZENworks Reporting v5.0.1 Beta include the following:
Operating System Support
Windows 8 x86 and x86_64
Windows Server 2003 SP2 x86_64 (Enterprise and Standard editions)
Windows Server 2003 R2 SP2 x86_64 (Enterprise and Standard editions)
Windows Server 2008 SP2 x86_64 (Enterprise and Standard editions)
Windows Server 2008 R2 x86_64 (Enterprise and Standard editions)
Windows Server 2008 R2 SP1 x86_64 (Enterprise and Standard editions)
Windows Server 2012 Server Standard x86_64 (Foundation, Essential, Standard edition, and Datacenter)
SUSE Linux Enterprise Server 10 (SLES 10) SP3/SP4 x86-_64 (Intel and AMD Opteron processors)
SLES 11 SP1/SP2/SP3 x86_64 (Intel and AMD Opteron processors)
SLES 11 SP2 and SP3 for VMware X86_64
Red Hat Enterprise Linux 5.8, 5.9, 6.3, and 6.4 x86_64
Red Hat Enterprise Linux 6.0/6.1/6.2 x86, x86_64
Browser Support
Firefox ESR version 10 and 17
Firefox version 20, 22, and 23
Internet Explorer versions 8, 9, and 10
For information on the System Requirements and for installation instructions, see ZENworks Reporting 5.0.1 Installation Guide.
For all ZENworks 11 SP3 Beta documentation, see Novell ZENworks 11 SP3 documentation Web site.
This section contains information about issues that might occur while you work with ZENworks Reporting v.5.0.1 Beta:
Section 2.4.1, Installing ZENworks Reporting on Redhat the SELinux status sets to Premissive
Section 2.4.2, When you log into ZENworks Reporting an error message is displayed
Section 2.4.3, Unable to log in as e-directory user in ZENworks Reporting
Section 2.4.4, An error message is displayed if you filter the Input Control with the All option
Section 2.4.6, ZENworks Reporting installer does not list LDAP group(s) from the LDAP tree
Section 2.4.7, ZENworks Reporting permissions must be provided at role level only
Section 2.4.9, ZENworks Reporting administrator role not mapped to the nested groups
Section 2.4.10, The Patch Cached option on the Input Control is not functioning correctly
Section 2.4.11, The Patch Cached option displays an error message occasionally
Section 2.4.12, Custom patches are not displayed correctly in the report
Section 2.4.13, The Patch Cached field in the report is not displayed correctly
Section 2.4.14, The old and new XML values display incorrect data
Section 2.4.15, The same Data Count is dispayed for Informational and Critical events
NOTE:In the ZENworks Reporting Solution, some strings are not localized.
If you install ZENworks Reporting on Redhat, then the SELinux status gets set to premissive (disabled). You can reset the SELinux status to enable (enforce) after installing the ZEnworks Reporting.
Workaround: Change the service status to the previously set value after restarting a device. This can also be enabled (enforcing) by manually running the setenforce 1 command as a root user.
After log into ZENworks Reporting, if your login session is timed out, and again if you try to log into ZENworks Reporting, then the java.lang.IllegalArgumentException error message is displayed.
Workaround: Ignore the error message and again log into ZENworks Reporting.
You cannot log in as an e-directory user in ZENworks Reporting when there are multiple instances of the same user name in the e-directory.
Workaround: None
In ZENworks Reporting, if you filter the Input Control, by using the
option, then an error message is displayed and a blank report is generated.Workaround: Filter the Input Control, using the
option.After installing ZENworks Reporting, if you launch the ZENworks Reporting Configuration Tool, without restarting a device, then the ZENworks Reporting is not installed error message is displayed, and the ZENworks Reporting Configuration Tool will exit. This is applicable only for Windows operating system.
Workaround: Restart the device after installing ZENworks Reporting, then launch the ZENworks Reporting Configuration Tool.
If you do not specify root context, then LDAP should consider the root of the LDAP tree as the root context. However, in this current ZENworks Reporting Beta release its not functuning as per requirement due to limitations of the Jaspersoft Reporting Engine.
Workaround: None.
ZENworks Reporting permissions must be provided at role level only and not at user level.
Workaround: None.
While passing the parameters to query from a report to another tab report these parameters pass through URL. If the length of the URL with these passed parameters exceeds the recommended length of corresponding browsers, then tab report fails.
Workaround: While launching a report do not select any option in the Input Control or select less number of parameters, which has the recommended length of URL supported by browsers.
In the ZENworks Reporting installer or ZENworks Reporting Configuration Tool, in the Configure User Source panel, if you map the parent group with administrator rights then nested groups which are under the parent group are not getting mapped with administrator rights.
Workaround: Map the sub-groups with administrator rights.
The
option in the Input Control window is not functioning correctly.Workaround: For the
option, select and .The
option displays an error message occasionally.Workaround: Select more patches by adding more patch impact fields.
Custom patches created from a bundle in the ZPM folder are not displaying correctly in the report. The original patch bundle gets associated with the bundle and not the custom patch.
Workaround: None.
The
option in the report is not displayed correctly. You can ignore the value.Workaround: None.
The
field and the field display incorrect data for the event.Workaround: None.
If you select
, and choose and from the Measures panel, then the same data count is displayed for both events.Workaround: None.
When you choose the
option, then an incorrect data count is displayed.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 © 2013 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.