4.0 Novell Application Launcher Troubleshooting Strategies

The following section explains the scenarios that you might encounter using the Novell Application Launcher component of Novell® ZENworks® 7 Desktop Management:

Novell Application Launcher constantly refreshes on the device that is connected to the network using a Virtual Private Network connection

Source: ZENworks Desktop Management; Novell Application Launcher.
Possible Cause: ICMP ping protocol is disabled on the Virtual Private Network (VPN) connection.
Action: Do the following:

  1. In ConsoleOne®, right-click the User object, then click Properties.

  2. Click the ZENworks tab, then click Launcher Configuration to display the Launcher Configuration page.

  3. Click Add. In the Launcher Configuration dialog box, select Configure remote access detection method.

  4. Set the value to either User will always be local, User will always be remote, or Prompt because Auto detect using max interface speed fails to function on networks on which ICMP ping is disabled.

On refreshing the Novell Application Launcher on a device that is not connected to the internet, the device takes some time to respond

Source: ZENworks Desktop Management; Novell Application Launcher.
Explanantion: When the Novell Application Launcher is refreshed on a device that is not connected to the internet, the CPU utilization of the device becomes very high and the device takes some time to respond.This is because the Update Root Certificates component on the device is turned on and the device is unable to connect to the Windows* Update server on the Internet. The Update Root Certificates component automatically updates trusted root-certificate authorities from the Microsoft* Update server at regular intervals.
Action: Do one of the following:

  • Connect the device to the internet

  • Disable the update of Root certificates. For more information on disabling the Update Root Certificates component, see Microsoft Support Site.

The job that is assigned to a workstation through BITS fails to resume after a system reboot

Source: ZENworks Desktop Management; Novell Application Launcher.
Explanantion: If a job is assigned to a workstation through BITS and the workstation reboots during the execution of the job, the job might fail to resume after the system reboots. If you want the job to resume after the sytem reboot, then ensure to set the startup type of BITS service to manual when you assign the job to the workstation.
Action: Set the startup type of BITS service to manual:

  1. Run services.msc to open the Services window.

  2. Right-click Background Intelligent Transfer Service and click Properties.

  3. Set the Startup type option to Manual.

  4. Click OK.