System Update (11.4.1) for ZENworks 11 SP4 Readme

2.1 Updating from Java Runtime 7 to Java Runtime 8

Java Runtime 7 Public Updates are no longer supported by Oracle. For information, see the Java website. ZENworks 11.4.1 updates Java Runtime from version 7 to version 8 on supported platforms.

ZENworks 11.4.1 will not update Java Runtime to version 8 on the following platforms:

Novell recommends that you update the above devices to versions supported by Java 8. This will ensure that you receive Critical Security Updates for Java 8 that are released by Oracle periodically.

2.2 Support for New Platforms

In ZENworks 11.4.1, the following platforms are supported:

For more information about the system requirements, see ZENworks 11 SP4 System Requirements.

2.3 Administration Browser Support

In ZENworks 11.4.1, the following web browsers are supported:

7.1 The Zicon Properties page appears blank on a ZENworks 11.4.1 device, when the operating system is upgraded to SLES or SLED 11 SP4

When you upgrade the operating system from SLES 11 SP3 to SLES or SLED 11 SP4 on a ZENworks 11.4.1 device, the Zicon Properties page appears blank.

Workaround: After upgrading the operating system from SLES or SLED 11 SP3 to SLES or SLED11 SP4, you need to stop and restart the agent with the osgiclean parameter:

7.2 When you are connected remotely on the SLES 10 SP3 or SP4 32-bit agent the INVALID PROTOCOL message is displayed

When you are connected remotely on the SLES 10 SP3 or SP4 32-bit agent, it displays the "INVALID PROTOCOL" message and the action fails.

Workaround: Deploy the zrmservice binary or novell-zenworks-xplat-zmd-rmagent-native-11.4.1-0.i586.rpm of 11.4.1 through a bundle on the SLES 10 SP3 or SP4 32-bit agents.

7.3 Migration from Windows 7 to Windows 10 fails when the User Management feature is enabled

Migration of Windows 7 to Windows 10 fails when the User Management feature is enabled in the ZENworks Management Zone prior to migration. Migration results in a blue screen.

Workaround: Perform the following:

7.4 Migration from Windows 7, 8, or 8.1 to Windows 10 fails when a Disk Encryption policy is enforced

Migration of Windows 7, 8, or 8.1 to Windows 10 fails when a Full Disk Encryption policy is enforced on the device. The migration results in a blue screen, at which point the only option is to roll back the migration to the Windows 7, 8, or 8.1 operating system.

Workaround: Prior to performing the migration, remove the Disk Encryption policy from the device and ensure that the device’s drives are decrypted.

7.5 After migrating from Windows 7 to Windows 10 a few ZENworks Services might not start automatically

After migrating from Windows 7 to Windows 10 a few ZENworks services such as Novell ZENworks Agent Service and ZES Service might not start automatically.

Workaround: When migrating from Windows 7 to Windows 10, use the latest version of Windows 10 (version 1511 and build 10586 or later).

7.6 Location created with the DHCP network parameter will not get enforced on SLES 12 devices

Location created with the DHCP network parameter will not get enforced on SLES 12 devices.

Workaround: None

7.7 SNMP discovery detects the operating system as Windows 8.1 instead of Windows 10

SNMP discovery detects the operating system as Windows 8.1 instead of Windows 10.

Workaround: None

7.8 The Min and Max Permanent Generation sizes are not updated in ZENworks Appliance

ZENworks 11.4.1 upgrades Java Runtime from version 7 to version 8 on supported platforms. The PermSize and MaxPermSize properties are not supported in Java 8 runtime. These properties are replaced with the MetaspaceSize and MaxMetaspaceSize properties respectively. However, the Appliance Configuration (Basic tab) continues to display the Min and Max Permanent Generation sizes (MB) and does not update the MetaspaceSize and MaxMetaspaceSize properties.

Workaround: Edit the MetaspaceSize and MaxMetaspaceSize property sizes (in MB):

7.9 A Remote Management operation will fail on a Windows managed device if the HTTP Proxy setting is configured without the port number

On a Windows managed device, the HTTP proxy setting can be configured by running the zac sp <ip_addr:port_number> command. If you perform a Remote Management operation without specifying the port number, the Remote Management service will not function properly.

Workaround: Run the zac sp <ip_addr:port_number> command and ensure that you specify the port number, then restart the Remote Management service.

7.10 Inventory Only Agent does not get updated from ZENworks 11.4 to ZENworks 11.4.1

When you upgrade the ZENworks 11 SP4 server to 11.4.1 and then you try to perform a system update of the Inventory only agent from 11.4 to 11.4.1, the agent does not get updated.

Workaround: Perform the following steps before applying the system update to ZENworks 11 SP4 Inventory only agents:

On Linux:

On Mac:

7.11 ZENworks Adaptive Agents are not able to install downloaded patches on SLED 12 machines

ZENworks Adaptive Agents are not able to install downloaded patches on SUSE Linux Enterprise Desktop (SLED) 12 machines because SLED 12 is not installed with the rpm-python.rpm file.

Workaround: Install the rpm-python.rpm file:

7.12 Applying the MDT Deployment bundle to re-install the operating system on a device that already has an operating system results in an infinite loop

When you apply the MDT Deployment bundle to re-install the operating system on a device that already has an operating system, it results in an infinite loop. On PXE boot, the device picks up the same MDT bundle every time. This issue occurs because the Microsoft Deployment Toolkit (MDT) wipes out the ZENworks Image Safe Data (ZISD) when preparing the disk to re-install the operating system on the device. Hence, the Imaging Server does not know the status of the imaging work assigned to the device and it is never cleared.

Workaround: Perform either of the following methods:

Method 1

When the device boots the MDT WIM and contacts the above customized MDT Deployment Share, the script prevents MDT from wiping out the ZISD data,

Method 2

7.13 Device will behave inconsistently if the MDT task state is specified as any value other than 4

In the ISDTool, if you specify any number other than 4 as the task state of the Microsoft Deployment Task (MDT), the device will behave inconsistently.

Workaround: None. You need to ensure that you specify 4 as the task state of MDT in the ISDTool.

7.14 On Windows 10 devices, when you perform an image restore and reboot the device, some Windows features might not work

On Windows 10 devices, without performing a Sysprep, when you restore an image and then reboot the device, the Windows start menu and few other Windows features like Cortana and Metro applications might not work.

Workaround: None. If you are taking an image without Sysprep, refer the Prerequisites for taking an Image on Windows 10 without Sysprep section in the ZENworks 11 SP4 Preboot Services and Imaging Reference.

7.15 ZENworks Imaging using Tuxera is not supported on Windows 10 with Sysprep

(Fixed in v11.4.2) If the Tuxera driver is used to take an image of a Windows 10 device with Sysperp, then the restored device will not boot.

Workaround: None

7.16 Remote Management operations fail when performed from a 11.4.1 Primary Server on a 11.4 agent using a 11.4 Join Proxy Satellite Server

When you try to remote control a 11.4 agent from a 11.4.1 Primary Server, using a 11.4 Join Proxy Satellite Server, the operation fails. Remote control does not work using Join Proxy if the Join Proxy version is 11.4 and the Remote Management viewer version is 11.4.1.

Workaround: Update the Join Proxy Satellite Server.

7.17 Mac OS X 10.10 and 10.11 managed devices cannot be used as Satellite Servers

Mac OS X 10.10 and 10.11 managed devices cannot be used as Satellite Servers because the agent is unable to open the configured Satellite Server port in the OS X firewall. This issue occurs because the ZENworks agent depends on the ipfw utility for opening ports in the OS X firewall. Since OS X 10.10, the ipfw utility has been discontinued. Apple suggests the use of the pfctl utility for this purpose.

Workaround: None

7.18 For the first time when you assign ZENworks 11.4.1 to the Primary Server that is newly added to the zone an error message is displayed

For the first time when you assign ZENworks 11.4.1 to a Primary Server that is newly added to the zone an error message is displayed.

Workaround: Click the Cancel button in the error message and then reassign the update.

7.19 Man pages are not working on Mac agents

Man pages are not working on Mac agents.

Workaround: You can unset the MANPATH variable to use the general Mac commands. However, the ZENworks-specific commands will still not work.

7.20 The agent will not be functional on a SLES 11 SP3 VMware platform if the RAM size is less than or equal to 1 GB

If the RAM size is less than or equal to 1 GB on the SLES 11 SP3 for VMware platform, the agent will not function properly.

Workaround: You need to increase the RAM size to more than 1 GB on the SLES 11 SP3 VMware platform.

7.21 SLES 10 SP3 or SP4 Imaging Servers fail to communicate with ZENworks 11.4.1 Primary Servers

The default version of openssl in SLES 10 SP3 or SP4 servers breaks the communication with the 11.4.1 Primary Servers.

Workaround: Apply the required FTF (https://bugzilla.novell.com/show_bug.cgi?id=958701).

7.22 Query group not created for Open Enterprise Server 2015

Unable to create query groups that will help in creating dynamic workstation groups for Open Enterprise Server (OES) 2015 devices.

Workaround: Apply the required SQL scripts. For more information, see TID 7017341 in the Novell Support Knowledgebase.