2.1 Installing ZCC Helper

ZENworks ZCC Helper is a standalone application which provides a browser independent way to perform various actions such as:

  • On Windows:

    • Icon Extractor

    • Remote Management

    • Uploading Imaging Files

    • Windows Group Policy

    • File and Directory Upload

  • On Linux:

    • Remote Management

    • File and Directory Upload

To install ZCC Helper:

  1. In ZENworks Control Center, click Configuration.

  2. In the left navigation pane, click Download ZENworks Tools.

  3. In the left navigation pane of the ZENworks Download page, click Administrative Tools.

  4. Click the Configuration tab.

  5. Depending on the device architecture (32-bit or 64-bit), download the appropriate RPM or MSI.

    novell-zenworks-zcc-helper-<version>.msi for Windows devices

    novell-zenworks-zcc-helper-<version>.rpm for Linux devices

  6. Save and install the ZCC Helper.

NOTE:

  • Windows:

    • For 64-bit operating system, no need to install the JRE, as JRE is included with ZCC Helper.

    • For 32-bit operating system, the 3rd party JRE (8.x or higher version) should be manually installed.

  • Linux:

    • For 64-bit operating system, no need to install the JRE, as JRE is included with ZCC Helper. However, on 64-bit SLES 11 devices, the 3rd party JRE (8.x or higher version) should be installed and then set the ZCC_JAVA_HOME environment variable.

    • For 32-bit operating system, the 3rd party JRE (8.x or higher version) should be manually installed, and then set the ZCC_JAVA_HOME environment variable.

IMPORTANT:If you are facing any issues while installing ZCC Helper, see the Troubleshooting ZCC Helper section.

2.1.1 Troubleshooting ZCC Helper

  • While installing ZCC Helper on Linux devices, if any of the following error message is displayed, then perform the steps mentioned in the Workaround section:

    Error setting value: Client failed to connect to the D-BUS daemon:
    Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    
    Error setting value: Client failed to connect to the D-BUS daemon:
    Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    
    Error setting value: Client failed to connect to the D-BUS daemon:
    Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

    Workaround: Run the following commands:

    /usr/bin/gconftool-2 -s /desktop/gnome/url-handlers/zcclaunch/command '/opt/novell/zenworks/zcchelper/bin/zcchelper "%s"' -t string
    
    /usr/bin/gconftool-2 -s /desktop/gnome/url-handlers/zcclaunch/needs_terminal false -t bool
    
    /usr/bin/gconftool-2 -s /desktop/gnome/url-handlers/zcclaunch/enabled true -t bool
    
    /usr/bin/gconftool-rebuild
  • While installing ZCC Helper on Linux devices, if any of the following error message is displayed, then perform the steps mentioned in the Workaround section:

    /usr/bin/xdg-mime: line 545: /root/.local/share/applications/defaults.list.new: No such file or directory
    
    grep: /root/.local/share/applications/defaults.list.new: No such file or directory
    
    /usr/bin/xdg-mime: line 547: /root/.local/share/applications/defaults.list.new: No such file or directory
    
    /usr/bin/xdg-mime: line 549: /root/.local/share/applications/defaults.list.new: No such file or directory
    
    mv: cannot stat `/root/.local/share/applications/defaults.list.new': No such file or directory

    Workaround: Run the following commands:

    mkdir .local/share/applications
    
    xdg-mime default zcchelper.desktop x-scheme-handler/zcclaunch || true
    
    update-desktop-database
  • After installing ZCC Helper on 64-bit SLES 11 devices, ZCC Helper might not launch.

    Workaround: Install 3rd party JRE (8.x or higher version) manually, and then set the ZCC_JAVA_HOME path variable.

  • If you are using wayland display manager, ZCC Helper might not launch.

    Workaround: Logout and log into the device using the x11 display manager.