A.0 Troubleshooting

The following sections explain the issues that you might encounter on a managed device.

The ZENworks Agent UI shows both English and the local language chosen for viewing

Source: ZENworks; ZENworks Agent.
Explanation: ZENworks resources are loaded according to the locale of the process that retrieves them. When using regional settings, the ZENworks Windows service might be configured to use a different language than the user is configured to use. The result is that the strings from both languages are displayed.
Action: Do one of the following:
  • Install the native language operating system

  • Change the default user language to match the language displayed by the user

Standalone install or uninstall of individual components does not work on Windows managed devices

Source: Zenworks; ZENworks Agent.
Explanation: Standalone install or uninstall of individual components do not work on the ZENworks Agent. When you enable or disable individual components, the settings might not be applied and the following message is logged:
[CompMgmt] [] [Aborting InstallAndUninstallComponents because of a pending reboot]

For example, if a bundle or policy component is disabled, you might continue seeing the bundle or policy component in effect on the ZENworks Agent.

Possible Cause: The Windows system might not be updated with the latest patches.
Action: Do the following:
  • Apply the latest patches for Windows.

  • Delete the registry key HKEY_Local_Machine/Software/Novell/ZCM/volatile.

  • Reboot the system.

For more information, see TID 7006485 in the .

Unable to start zmd in debug mode on a RHEL 4 b4-bit managed device

Source: Zenworks; ZENworks Agent.
Explanation: When you try to run zmd in the debug mode on a RHEL 4 64-bit managed device, you might encounter the following error:
Native library not loaded
Possible Cause: The GLIBC version on the managed device is not 2.4 or later.
Action: On the managed device, upgrade the GLIBC version to 2.4 or later.

Locations configured in ZENworks Control Center may not apply to RHEL 5 devices

Source: Zenworks; ZENworks Agent.
Explanation: The Network Manager may not be running as a daemon on the RHEL 5 device. So, the nm-tool command output will be empty.
Action: Do one of the following:
  • Run the Network Manager by using the NetworkManager command.

  • Run the Network Manager as a daemon by using the chkconfig command.

    For example, chkconfig --level 35 NetworkManager on command runs the Network Manager as a daemon for levels 3 and 5.

On a Windows XP device, the installation of ZENworks Agent with the Remote Management component through Remote Desktop Connection fails

Source: Zenworks; ZENworks Agent.
Explanation: If you remotely connect to a managed device through Remote Desktop Connection (RDP), then download and install the ZENworks Agent, the installation does not complete and the Remote Desktop Connection program stops working.
Action: To fix the issue, download the patch from the Microsoft Support Web site (http://support.microsoft.com/kb/952132) and install it on the managed device..

ZEN CASA not storing Groupwise credentials

Source: Zenworks, ZENworks Agent.
Explanation: If the managed device is running with ZENworks Agent and Groupwise client, in which Groupwise client is enabled with single-sign-on (CASA) and remember password options. After closing and reopening of Groupwise client, it again prompts for password.
Action: Specify the password for Groupwise client and reboot the managed device.