ZENworks 11 SP3 Beta

1.5.1 Unable to use the uninstall option for ZENworks bundle in the Start screen on a Windows 8 machine

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

1.5.2 The System Update progress is not visible on Windows 8 and Windows 2012 devices

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

1.5.3 ZENworks Control Center notification message for System Upgrade status shows incorrect list of Primary Servers

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.

1.5.4 On a server where .NET 4.5 is enabled, the ZENworks Installer tries to enable .NET 3.5 and the installation completes with warnings

While installing a Primary Server on a Windows Server 2012 machine, a Windows pop-up displays this error message on the Post Installation page: .NET Framework 3.5 (includes .NET 2.0 and 3.0) could not be installed.

Workaround: Enable .Net 3.5 on the machine before installing the ZENworks Primary Server.

1.5.5 Replicating bundles with a large number of content files by using ZENworks subscription fails

Workaround: Create multiple bundles with a smaller number of content files at the Publisher zone before starting the replication session.

1.5.6 Unable to share Preboot and Patch bundles with Subscribers

The following types of bundles cannot be shared with subscribers:

Workaround: None.

1.5.7 The PXE menu for both 64-bit and 32-bit devices gets updated when you upload either a 32-bit or a 64-bit .wim file on a server

If you upload a 32-bit.wim file on a server and boot a 64-bit device into the PXE, you can see the WinPE Maintenance mode 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.

1.5.8 Restoring an Image by using the Tuxera driver fails while Imaging is performed from an older version of an Imaging Satellite Server

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.

1.5.9 Scrolling through the logged audit events or the audit event configuration settings tree takes longer using a Firefox browser

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:

1.5.10 The bootcd_tntfs.iso file creation fails on RHEL Servers that have the tntfs.zip file

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.

1.5.11 Windows 8 login screen fails to appear after the restoration of Windows 8 images from a Virtual Machine on VMwareESX 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.

1.5.12 The Duration to honor for a Startup Location is not effective on an agent for the time defined in ZENworks Control Center

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 Duration to honor startup location 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.

1.5.13 Audit Role is displayed in the agent Closest Server Roles list even though it is not used to upload audit events

The Collection role is used to upload all Audit events from the agent to the server. However, the Audit role is displayed in the Agent Closest Server for Roles 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.

1.5.14 Audit events are not generated when more than five administrators are imported at a time

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.

1.5.15 Novell ZENworks File Upload plug-in will not work with Internet Explorer 10.

You cannot use the Novell ZENworks File Upload plug-in with Internet Explorer 10.

Workaround: None

1.5.16 Full Disk Encryption is not supported on Windows 8 devices that use UEFI BIOS

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.

1.5.17 Full Disk Encryption is not installed on upgraded devices

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.

1.5.18 ZENworks Endpoint Security policies with non-default locations fail to replicate to subscribers

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.

1.5.19 A Group Policy cannot be edited if Firefox 20.0, 21.0, and 22.0 is used to launch ZENworks Control Center

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.

1.5.20 A Group Policy cannot be created if Firefox 22.0 is used to launch ZENworks Control Center

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.

1.5.21 The Audit log tab shows events that are not applicable for Linux and Mac devices

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.

2.4.1 Installing ZENworks Reporting on Redhat the SELinux status sets to Premissive

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.

2.4.2 When you log into ZENworks Reporting an error message is displayed

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.

2.4.3 Unable to log in as e-directory user in 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

2.4.4 An error message is displayed if you filter the Input Control with the All option

In ZENworks Reporting, if you filter the Input Control, by using the All option, then an error message is displayed and a blank report is generated.

Workaround: Filter the Input Control, using the None option.

2.4.5 An error message is displayed if you launch ZENworks Reporting Configuration Tool without restarting a device

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.

2.4.6 ZENworks Reporting installer does not list LDAP group(s) from the LDAP tree

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.

2.4.7 ZENworks Reporting permissions must be provided at role level only

ZENworks Reporting permissions must be provided at role level only and not at user level.

Workaround: None.

2.4.8 Tabs report fails

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.

2.4.9 ZENworks Reporting administrator role not mapped to the nested groups

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.

2.4.10 The Patch Cached option on the Input Control is not functioning correctly

The Patch Cached option in the Input Control window is not functioning correctly.

Workaround: For the Patch Cached option, select Yes and No.

2.4.11 The Patch Cached option displays an error message occasionally

The Patch Cached option displays an error message occasionally.

Workaround: Select more patches by adding more patch impact fields.

2.4.12 Custom patches are not displayed correctly in the report

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.

2.4.13 The Patch Cached field in the report is not displayed correctly

The Patch Cached option in the report is not displayed correctly. You can ignore the value.

Workaround: None.

2.4.14 The old and new XML values display incorrect data

The Event Detail New XML Value field and the Event Detail Old XML Value field display incorrect data for the Policy Modified event.

Workaround: None.

2.4.15 The same Data Count is dispayed for Informational and Critical events

If you select Crosstab View, and choose Count of Critical Events and Count of Information Events from the Measures panel, then the same data count is displayed for both events.

Workaround: None.

2.4.16 Incorrect Data Count is displayed

When you choose the Details and Total Data option, then an incorrect data count is displayed.

Workaround: None.