The information in this Readme pertains to the 11.3.1 system update for ZENworks 11 SP3.
This update fixes some of the issues discovered in previous ZENworks releases and also includes new features.
Version 11.3.1 includes the following new features:
This feature allows you to copy the relationships of one device (Policies, Bundles, Device Group Membership) to another target device or set of target devices. The target could be devices, device groups, and device folders.
In this release, the IP Address is included as a new filter condition to the
under in order to allow subnet comparison. This is available for both the Windows Bundles and Policies.This is a new check box included in the Restrict IP Addresses page. Check this box if you want the newly added IP addresses of the server to be moved to the
list automatically, so that they are not visible to the ZENworks agent.If there is only one IP Address in the visible IP addresses list, do not move it to the
list. This is because the ZENworks agent must be able to see at least one IP address of the server.In the absence of Z-icon, you can now use the zac rrs or zac request-remote-session command to request a remote management session from the managed device. This command is available on Windows managed devices with ZENworks 11.3.1 and later.
An administrator can use the zac command to assign rights to other administrators (users) to register, re-register, or un-register a device from the Management Zone.
ZENworks imaging now supports 32-bit UEFI device imaging through Third-Party Imaging.
ZENworks Imaging also includes the following performance improvements:
The Multicast Imaging performance has been enhanced.
Imaging with the legacy NTFS driver has been improved to make the process faster.
Use the following guidelines to plan for the deployment of ZENworks 11.3.1 in your Management Zone:
Prior to installing the System Update, ensure that you have adequate free disk space in the following locations:
Location |
Description |
Disk Space |
---|---|---|
Windows: %zenworks_home%\install\downloads Linux: opt/novell/zenworks/install/downloads |
In the Downloads folder to maintain agent packages. |
3 GB |
Windows: %zenworks_home%\work\content-repo Linux: /var/opt/novell/zenworks/content-repo |
In the content-repo folder to import the zip file to the content system. |
3 GB |
Agent Cache |
To download the applicable System Update contents that are required to update the ZENworks server. |
1.5 GB |
Location where the System Update file is copied. NOTE:This is only applicable for the ZENworks Server that is used to import the System Update zip file. |
To store the downloaded System Update zip file. |
3 GB |
You must deploy version 11.3.1 first to the Primary Servers, then to Satellites, and finally to managed devices. Do not deploy this update to managed devices and Satellites (or deploy new 11.3.1 Agents in the zone) until all Primary Servers in the zone have been upgraded to 11.3.1.
NOTE:When the agents start communicating with the ZENworks servers before the Primary Servers are upgraded, the agents receive inconsistent data that might impact the zone. Therefore the Primary Servers should be upgraded within a short duration, ideally within few minutes of each other.
You can directly deploy version 11.3.1 to Primary Servers that have ZENworks 11.3.0, 11.3.0a, Win 8.1 for 11.3.0, Win 8.1 for 11.3.0a or 11.3.0 FRU1 installed.
The system reboots once after you upgrade to ZENworks 11.3.1. The reboot is applicable only for Windows devices. However, a double reboot is required in the following scenarios:
The Update For ZENworks 11 SP3 (11.3.1) supercedes Windows 8.1 Update for ZENworks (11 SP3) and FTF Roll Up 1 for ZENworks 11 (SP3).
Table 1 Double Reboot Scenarios
Scenario |
ZENworks Endpoint Security |
Full Disk Encryption |
Location Services |
Client Self Defence |
---|---|---|---|---|
Upgrade from 10.3.4 or above to 11.3.1 |
Disabled |
Disabled |
Lite |
Enabled |
Fresh Install of 11.3.1 |
Disabled |
Disabled |
Lite |
Enabled |
Fresh Install of 11.3.1 |
Disabled |
Disabled |
Full |
Enabled |
IMPORTANT:: Any managed device running versions prior to 10.3.4 must first be upgraded to at least ZENworks 10.3.4. The system reboots after the upgrade to ZENworks 10.3.4 and then reboots again when the 11.3.1 update is deployed.
Table 2 ZENworks Cumulative Agent Update to 11.3.1: Supported Paths
Managed Device Type |
Operating System |
Supported Versions |
Unsupported Versions |
---|---|---|---|
Primary Server |
Windows/Linux |
v11.3.x and later versions |
Any version prior to 11.3.x |
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 |
You can directly deploy ZENworks 11.3.1 to Satellites and Managed devices that have ZENworks 10.3.4, 11.0.0, 11.1.0, 11.2.0, 11.2.0 MU1, 11.2.0 MU2, 11.2.1, 11.2.1 MU1, 11.2.1 MU2, 11.2.2, 11.2.2 MU1, 11.2.2 MU2, 11.2.3a, 11.2.3a MU1, 11.2.4, 11.2.4 MU1, 11.3.0, 11.3.0a, Win 8.1 for 11.3.0, Win 8.1 for 11.3.0a or 11.3.0 FRU1 installed.
For instructions on downloading and deploying version 11.3.1 as an update, see ZENworks 11 SP3 System Updates Reference.
If your Management Zone consists of Primary Servers with a version prior to ZENworks 11 SP3, you can deploy version 11.3.1 to these Primary Servers only after all of them have been upgraded to ZENworks 11 SP3. For instructions, see the ZENworks 11 SP3 Upgrade Guide.
For administrative tasks, see the Novell ZENworks documentation website.
NOTE:Ensure that you read Section 2.0, Planning to Deploy Version 11.3.1 before you download and deploy the 11.3.1update.
For the list of supported Managed Device and Satellite Server versions in a Management Zone with 11.3.1, see the following ZENworks support matrix table.
Table 3 ZENworks Support Matrix
Managed Device |
Satellite Servers |
Primary Servers |
---|---|---|
v10.3.4 |
v10.3.4, v11.0, v11.1, v11.2,v11.2 MU1, v11.2 MU2, v11.2.1, v11.2.1 MU1, v 11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4, v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1, 11.3.1 |
v11.3.1 |
v11.0 |
v11.0, v11.1, v11.2, v11.2 MU1, v11.2 MU2, v11.2.1, v11.2.1 MU1, v 11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4, v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.1 |
v11.1, v11.2,v11.2 MU1, v11.2 MU2, v11.2.1, v11.2.1 MU1, v 11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2 |
v11.2, v11.2 MU1, v11.2 MU2, v11.2.1, v11.2.1 MU1, v 11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2 MU1 |
v11.2 MU1, v11.2 MU2, v11.2.1, v11.2.1 MU1, v 11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2 MU2 |
v11.2 MU2, v11.2.1, v11.2.1 MU1, v 11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2.1 |
v11.2.1, v11.2.1 MU1, v 11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a,11.3.0 FRU1, 11.3.1 |
v11.3.1 |
v11.2.1 MU1 |
v11.2.1 MU1, v 11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2.1 MU2 |
v11.2.1 MU2, v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2.2 |
v11.2.2, v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2.2 MU1 |
v11.2.2 MU1, v11.2.2 MU2, v11.2.3a, v11.2.3a MU1, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2.2 MU2 |
v11.2.2 MU2, v11.2.3a, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2.3a MU1 |
v11.2.3a MU1, v11.2.3a, v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2.4 |
v11.2.4,v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.2.4 MU1 |
v11.2.4 MU1,v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.3.0 |
v11.3.0a, Windows 8.1 Update for v11.3.0a, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.3.0 Windows 8.1 Update |
v11.3.0a Windows 8.1 Update, 11.3.0 FRU1,11.3.1 |
v11.3.1 |
v11.3.0 FRU1 |
11.3.0 FRU1,11.3.1 |
v11.3.1 |
ZENworks 11.3.1 includes the following:
In version 11.3.1, the following platforms are supported:
Apple OS X 10.9.0 (Mavericks)
Apple OS X 10.9.1
Apple OS X 10.9.2
RHEL 6.5
This is supported only as a managed device and as a satellite, but not as a Primary Server.
Scientific Linux 6.5
This is supported only as a managed device and as a satellite, but not as a Primary Server
Windows 2012 Server R2 Update 1
Windows 8.1 Update 1 (Professional and Enterprise editions)
In version 11.3.1, the following web browsers are supported:
Internet Explorer 11
Firefox 28, 29, and 30
This version supports Novell Client 2 SP3 IR7a for Windows 7 and Windows 8
Some of the issues identified in the initial release of ZENworks 11SP3 have been resolved with this release. For a list of the resolved issues, see TID 7015288 in the Novell Support Knowledgebase
Some of the issues that were discovered in the original shipping version of ZENworks 11 SP3 have not yet been resolved. Review the following Readme documents for more information:
When updating the ZENworks Adaptive Agent on a Windows managed device, the percentage complete reaches 92% and might not change for a significant amount of time (20 minutes or more). At this point, the update program is attempting to shut down ZENworks services running on the device, which can take some time. Let the update continue to run and it will complete.
The time-out duration for starting a multicast imaging session is calculated from the time the last client joins the multicast session. Ideally, the start time-out duration should be calculated from the time the first client joins the session.If the specified number of clients have not joined the session, wait for the specified time-out duration to start the multicast imaging session.
On Linux devices, the upgraded Novell ZENworks fileupload plug-in (from 11.3 to 11.3.1) will not work if you do not uninstall the existing version of Novell ZENworks fileupload plug-in (11.3) before installing or upgrading to the latest version (11.3.1).
ZENworks Configuration Management 11.3 media upgrade on a Linux Primary Server fails if the ISO is mounted to any directory under the /root path or if it is mounted to a path named Upgrade.
Workaround: For more information see, TID 7014693.
If the icon of a demoted satellite with the imaging role does not change, refresh the device.
The Data Encryption driver causes Windows 8.x devices that use English (India) for the Region Format setting to crash.
Workaround: This issue will be fixed in a future release. In the meantime, modify the device’s registry as explained in the following steps:
Access the device’s Windows registry.
If the device has crashed and the operating system will not boot, use a boot disk utility to access the registry.
Locate the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ZesOCC
If the ZesOCC key has a ReparseExclusions value, double-click the value, add \WINDOWS\SYSTEM32\KBDINEN.DLL as a new line in the field, then click to save the value.
or
If the ReparseExclusions value does not exist, right-click the ZesOCC key, click > , then use the following information to create the value:
Value Name: ReparseExclusions
Value Data: \WINDOWS\SYSTEM32\KBDINEN.DLL
Save the registry changes.
Apply a Data Encryption policy to the device.
or
If a policy is already applied, reboot the device to its operating system.
If you remote control a managed device from a 64-bit Windows 8 device that has the Internet Explorer 10 browser, the remote control dialog appears several times.
The activation of System Update Entitlement in the background will fail abruptly if the ZENworks Primary Server is shut down or if ZENworks services are stopped or restarted while the background activation is in progress. The activation will not automatically restart after the ZENworks Primary Server is up and the ZENworks Services are restored. Even if the retry is initiated again, the background activation will not start.
When you try to restore an image locally from a mounted partition, it hangs indefinitely under the following conditions:
If the image is created using the Tuxera driver
If the image includes files that are larger than 3 GB
Workaround: Use the legacy driver for creating and restoring the local image.
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 © 2014 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.