ZENworks 11 SP3 Beta Refresh Readme

October 16, 2013

The information in this Readme file pertains to Novell ZENworks 11 SP3 Beta Refresh.

1.0 What’s New

The ZENworks 11 SP3 Beta Refresh includes the following new features:

1.1 ZENworks Configuration Management

1.1.1 System Update

The following new features are available as part of the System Update feature:

1.1.1.1 Standalone Agent Updater

The Standalone Agent Updater is an independent executable to update Windows managed devices and Windows Satellite Servers. Even if the device is unable to connect to the server, it will be updated to the latest version of the agent. The executable can be generated from any ZENworks Primary Server in the zone by using the zman system-update-create-package (sucp) command for the update that is imported into the zone.

1.1.1.2 System Update Rights

The Approve Updates and Apply Updates rights are now included as a part of the System Update Rights feature. Any downloaded update must be approved by the administrator before being deployed to a device.

Approve Updates: Administrators with Approve Updates rights can approve an update. The deploy options are available only after the approval.

Apply Updates: Administrators with Apply Updates rights can deploy the updates to those devices for which they have View Leaf rights. Administrators have the option of deploying to all devices and stages only if they have Apply Updates and View Leaf rights for all devices in the zone.

1.1.2 Data Pruning

In the Upgrade wizard, you can now opt for database pruning before upgrading the ZENworks server to ZENworks 11 SP3. After the successful pruning, you need to relaunch the Upgrade wizard to complete the Upgrade process. Pruning of inventory records prevents high utilization of the database and reduces the duration of the upgrade process.

1.1.3 Imaging

You can now create a bootable USB drive to boot systems with BIOS and UEFI firmware to perform imaging operations.

1.2 Patch Management

Patch Policy is a new feature that enables the user to set up automated and targeted patch downloads and remediation. This feature provides multiple variables and combinations to select from. After a policy is created, it will search for, download, and deliver patches to the appropriate systems (as defined by the users’ requirements), and can be scheduled to deploy at any time. For example, they can be scheduled when network traffic is quieter. This feature further streamlines the Patch Download process by greatly reducing administration time and saving on storage space.

NOTE:For more information about these features, see the ZENworks 11 SP3 Beta Refresh Scenarios.

2.0 Supported Platforms and Installation Instructions

The new platforms that are supported in ZENworks 11 SP3 Beta Refresh include the following:

  • Managed Device Support

    • Windows 7 Thin PC (32-bit)

    • Scientific Linux 6.4 (32 and 64-bit)

      NOTE:Imaging capability and ZENworks Patch Management is not supported on both these platforms.

For additional information about the System Requirements and for instructions on how to install ZENworks 11 SP3 Beta, see the ZENworks 11 SP3 Server Installation Guide.

3.0 Planning to upgrade to ZENworks 11.3

Use the following guidelines to plan for the upgrade to ZENworks 11.3 in your Management Zone:

  • You must first upgrade the Primary Servers, then update the Satellite Servers, and finally the managed devices to ZENworks 11 SP3. Do not upgrade the managed devices and Satellite Servers (or add new 11 SP3 Agents in the zone) until all Primary Servers in the zone have been upgraded to 11.SP3.

    NOTE:Agents might receive inconsistent data from the zone until all Primary Servers are upgraded. Hence, this part of the process should take place in as short a time as possible, ideally, immediately after the first Primary Server is upgraded.

  • You can directly update the managed devices in the zone to ZENworks 11 SP3, only if the managed devices have been updated to ZENworks 10.3.4 or later.

    The system reboots once after you upgrade to ZENworks 11 SP3. However, a double reboot will be required in the following scenarios:

    Table 1 Double Reboot Scenarios

    Scenario

    ZENworks Endpoint Security

    Full Disk Encryption

    Location Services

    Client Self Defence

    Upgrade from 10.3.4 to 11 SP3

    Disabled

    Disabled

    Lite

    Enabled

    Fresh Install of 11 SP3

    Disabled

    Disabled

    Lite

    Enabled

    Fresh Install of 11 SP3

    Disabled

    Disabled

    Full

    Enabled

    IMPORTANT:: All Primary Servers running ZENworks 11.1.0a or earlier versions, should first be upgraded to ZENworks 11.2.0 before upgrading them to ZENworks 11.3. Satellite Servers and managed devices should be updated to 10.3.4 before updating them to ZENworks 11 SP3.

Table 2 ZENworks Cumulative Agent Update to 11 SP3: Supported Paths

Managed Device Type

Operating System

Supported Versions

Unsupported Versions

Primary Server

Windows/Linux

v11.2 and later versions

Any version prior to 11.2

Satellite Server

Windows/Linux/Mac

v10.3.4 and later versions

Any version prior to 10.3.4

Managed Device

Windows

v10.3.4 and later versions

Any version prior to 10.3.4

Linux

v11.0 and later versions

NA

Mac

v11.2 and later versions

NA

4.0 Upgrade Prerequisites and Instructions

For detailed information about the prerequisites and for instructions to upgrade Primary Servers, Satellites, and managed devices to ZENworks 11 SP3 Beta Refresh, see the ZENworks 11 SP3 Upgrade Guide.

5.0 Additional Product Documentation

This Readme lists issues that are specific to ZENworks 11 SP3 Beta Refresh. For all other ZENworks 11 SP3 Beta documentation, see the Novell ZENworks 11 SP3 documentation website.

6.0 Known Issues in ZENworks 11 SP3 Beta Refresh

This section contains information about issues that might occur while you work with ZENworks 11 SP3 Beta Refresh:

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

6.2 Unable to share Preboot and Patch bundles with Subscribers

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.

6.3 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. In the Firefox browser, click Tools > Options > Advanced.

  2. Click the General tab.

  3. Under Browsing, uncheck the smooth scrolling option.

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

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

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

6.7 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

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

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

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

6.11 An error occurs while creating Subscriber keys that have long names on an MS SQL database

If you provide a long Subscriber key name, when the MS SQL database converts the name into bytes, the index created from this name might exceed the database limitation for the index length (900 characters). In this case, the Subscriber key creation fails.

Workaround: None.

6.12 Operating System on UEFI devices loses mount points on image restoration

For volume junction points, the GUID of the volume is used to refer to the target volume. For UEFI devices, the GUID is changed to maintain uniqueness of the partition. As a result, the references in the junction points will not work.

Workaround: Remount the volumes after image restoration.

6.13 Snooze prompt has not been implemented for Windows 8 metro view

The Snooze prompt has not been implemented for the Windows 8 metro view.

Workaround: None

6.14 In a bundle with multiple bundle locks, deleting one lock results in deletion of both locks on an Xplat- Linux device

On an Xplat-Linux device, if you create a bundle and add multiple bundle locks for the same bundle with different configurations and then delete a bundle lock, the other bundle lock for the same bundle is deleted. For example, this could happen if you add one bundle lock with the Deny Install option and add another bundle without the Deny Install option.

Workaround: None

6.15 Warning message is displayed during agent installation through YaST2 Add-on in SLED or SLES machine

When a ZENworks 11SP3 server is added as a YaST2 repository in a SLED or SLES machine, you will see a warning message: Cannot assess installation media. Check whether the server is accessible.

Workaround: Ignore the warning and proceed with adding the repository.

6.16 Deleting extended partitions by using the img command corrupts existing partitions

Workaround:

  1. Check to see the list of partitions on all the disks by running the following command:

    # parted -l

  2. To delete the required extended partition run the following command:

    # parted /dev/sdX rm n

    /dev/sdX is the disk and n is the number of the partition that is to be deleted.

    For example: To delete the seventh partition from the /dev/sda disk, run the following command:

    # parted /dev/sda rm 7

6.17 The Audit tab displays event types that are not applicable for Linux and Mac devices

ZENworks Agent audit events are only applicable for Windows devices, and not for Linux or Mac devices. Therefore, the audit event types should not be displayed in the Audit tab for these devices.

Workaround: None. Ignore the Agent events in the Audit tab for Linux and Mac devices.

6.18 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 because the old entries on the servers are not deleted automatically.

Workaround: After a successful migration, delete the old entries on the Primary Servers manually.

6.19 Incorrect values displayed for the inventory records to be pruned

When you opt for pruning in the Upgrade wizard, the number of records specified for deletion is displayed in the Pre-prune summary screen.

For example, if you have marked 8,000,000 records out of the total 10,000,000 records for pruning, then 8,000,000 of 10,000,000 is displayed in the number of records specified for deletion field.

After successful pruning, when you relaunch the Upgrade wizard for pruning, the Database Pruning screen displays an incorrect value in the Total number of records found to be deleted field.

For example, if 8,000,000 inventory records have been deleted out of 10,000,000 inventory records, then the ideal value to be displayed in the Total number of records found to be deleted field is 2,000,000.

Currently an incorrect value is displayed. As a result, there is a mismatch in the values displayed for deleted Inventory records and for Inventory records that are yet to be deleted.

Workaround: None

6.20 The About ZENworks Window help page is not displayed on a ZENworks Agent

In the ZENworks application window of a ZENworks Agent, if you click About ZENworks Window from the Help menu then the relavant help page is not displayed.

Workaround: None.

6.21 The Tuxera Boot CD creation fails when uploading the Tuxera.zip file on a server installed on a non-default location.

The boot cd creation fails and the Replication Status is not available. The Tuxera.zip file is replicated in the tftp home folder.

Workaround: Create the boot cd manually. For more information, see Creating a Tuxera Boot CD in the ZENworks 11 SP3 Preboot Services and Imaging Reference.

6.22 Monitoring the usage of Web applications on 64-bit devices from Windows 7 onwards might be difficult

On 64 -bit devices from Windows 7 onwards, it might be difficult to collect or monitor the usage of the Web-based applications or pages.

Workaround: None

6.23 Switch User option might not work in a remote session on some of the tablet devices

The Switch User option on some of the Windows tablet devices such as Windows8 Surface Pro, Dell Latitude might not work in a remote session.

Workaround: None

6.24 The inventory report displays two entries of the IOA when the IOA is upgraded to 11.3

The Inventory Only agent (IOA) updates or upgrades itself as soon as the Primary server is upgraded from 11.2 to 11.3. The inventory report displays two entries of the IOA i.e both 11.2 and 11.3, instead of only 11.3.

Workaround: None

7.0 ZENworks Reporting

The information in this Readme includes the following:

7.1 Supported Platforms

The platforms that are supported in ZENworks Reporting v5.0.1 Beta include the following:

  • Operating System Support

    • 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, and Standard edition)

    • 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_64

  • Browser Support

    • Firefox ESR version 10 and 17

    • Firefox version 20, 22, and 23

    • Internet Explorer versions 8, 9, and 10

7.2 Download Information

The following installation builds are available for download on the ZENworks 11 SP3 Beta website:

  • ZENworks_Reporting_5_Beta_Refresh.iso: Download the ZENworks Reporting installer and other ZRS resource files from the Novell website, and extract them to where you want to install ZENworks Reporting.

7.3 Installation Instructions

For installation information, see the ZENworks Reporting 5 Installation Guide.

7.4 Additional Product Documentation

For all ZENworks 11 SP3 documentation, see the Novell ZENworks 11 SP3 documentation website.

7.5 Known Issues

This section contains information about issues that might occur while you work with ZENworks Reporting v.5.0.1 Beta:

NOTE:In the ZENworks Reporting Solution, some strings are not localized.

7.5.1 Unable to log in as an edirectory user in ZENworks Reporting

You cannot log in as an edirectory user in ZENworks Reporting when eDirectory contains are multiple instances of the same user name.

Workaround: None

7.5.2 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, an error message is displayed and a blank report is generated.

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

7.5.3 ZENworks Reporting administrator role not mapped to the nested groups

In the ZENworks Reporting installer or theZENworks Reporting Configuration Tool, if you navigate to the Configure User Source wizard and map the parent group with administrator rights, nested groups that are under the parent group will not be mapped with administrator rights.

For example, a Finance group has the sub-groups, finance_account, finance_purchase, finance_administration and a finance_manager user. If the Finance group is selected, only the finance_manager user will have the mapped rights; none of the sub-groups will have these rights. The rights will not flow to the nested groups.

If you want to specify rights to nested groups, you must map these groups (finance_account, finance_purchase, and finance_administration) separately.

Workaround: Map the sub-groups separately.

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

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

7.5.6 Custom patches are not displayed correctly in the report

Custom patches created from a bundle in the ZPM folder do not display correctly in the report. The original patch bundle gets associated with the bundle and instead of with the custom patch.

Workaround: None.

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

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

7.5.9 Incorrect Data Count is displayed

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

Workaround: None.

7.5.10 An error appears when running some of the Predefined reports for Patch Management

An error appears when running some of the predefined reports for Patch Management.

Workaround: None.

7.5.11 Unable to import resources

Unable to import resources in ZENworks Reporting, by using the Import option (Manage > Server Settings > Import).

Workaround: Use the CLI mode to import resources.

To import Schedule jobs, specify the following --everything in the import command:

  1. Open a command prompt.

  2. Go to the following path:

    • For Windows: %ZRS_HOME%\js\buildomatic

    • For Linux: /opt/novell/zenworks-reporting/js/buildomatic

  3. Run the following js-import –-input-zip “path” command.

    Where “path” is the path of the exported zip file. You can use the following js-import –-input-zip “path” --update command to update your repository.

7.5.12 Measures does not provide the correct value in the Crosstab report

When you create a Crosstab report by using ZENworks Audit Domain, some measures do not provide the correct value.

Workaround: None.

7.5.13 Some of the Field data might not appear in the Crosstab report

When you create a Crosstab report by using ZENworks Audit Domain, some of the field data might not appear.

Workaround: None.

7.5.14 Unable to create or run the RSD File Copy Events report in the ZENworks Audit domain

In ZENworks Reporting, you might not be able to create or run the RDS File Copy Events report (View > Repository > ZENworks Audit > Predefined Reports > RSD File Copy Events).

Workaround: None.

8.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

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