F.0 Troubleshooting

The following sections explains the scenarios that you might encounter while using the Bundles component of Novell ZENworks 11.

Unable to locate the active text box in the user interface of ZENWorks Control Center

Source: ZENworks 11; Software Distribution.
Explanation: If you use Firefox 2.0 to open ZENworks Control Center, the cursor might fail to appear in the active text box.
Action: Use Internet Explorer.

Uploading content from a text file that contains extended characters corrupts the content

Source: ZENworks 11; Software Distribution.
Explanation: If you use the Edit Text File action to upload a text file containing extended characters, the content is corrupted.
Action: Open the text file, save it as UTF-8, then upload the file.

While launching applications, the window prompting for user input might not be displayed

Source: ZENworks 11; Software Distribution.
Explanation: If you use bundles to launch applications that require user input, the window prompting for the input might be hidden behind the application. This problem might occur if the applications are launched for the first time for each user login.
Action: If you want to immediately view the window, minimize the application. To fix the problem, restart the system.

Unable to select a large number of files to upload to the content server while performing the Install Directory or Install Files action with the Firefox browser

Source: ZENworks 11; Software Distribution.
Explanation: You cannot select a large number of files to upload to the content server while performing the Install Directory or Install Files action with the Firefox browser.
Action: Upload a smaller number of files with the Firefox browser, or use the Internet Explorer browser to perform the action.

Unable to execute the Install MSI action on a Windows 2000 device

Source: ZENworks 11; Software Distribution.
Explanation: If Grant administrator privilege to user during installation is selected in the Install MSI dialog box to provide administrator privileges to the logged in user, the user is prompted to provide the log in credentials when the Install MSI action is executed on the device. The action fails to execute even if the user has provided the correct password.
Action: Add the user as a part of the operating system as follows:

  1. Run MMC.

  2. Click File > Add/Remove Snap-in, click Add.

  3. In the Add Standalone Snap-in dialog box, select Group Policy Object Editor, click Add > Finish.

  4. Click Close to close the Add Standalone Snap-in dialog box.

  5. Click OK.

  6. In the Console Root window, double-click Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Act as part of the operating system

  7. Click Add User or Group.

  8. In Enter the object names to select, specify the user name. Click OK.

  9. Click OK.

Cannot back up the registry and edit the HKEY_CURRENT_USER by using a single registry action on a Windows Vista device

Source: ZENworks 11; Software Distribution.
Explanation: If you set up an action to both back up the registry and edit the HKEY_CURRENT_USER registry entry on Windows Vista*, the action fails because all user-initiated processes in Vista run as the lowest privileged user.
Action: Use two different registry actions, one to back up the registry in the system context, and another to edit HKEY_CURRENT_USER in the user context.

The Undo Install Actions fails to uninstall a directory

Source: ZENworks 11; Software Distribution.
Explanation: When you create an Install Directory File bundle, the directory is installed even if its name contains spaces; however, it cannot currently be uninstalled by using the Undo Install Actions action.
Action: Avoid spaces in directory names if you want to enable the uninstallation of that directory.

Unable to launch a RDP session from a 64-bit device

Source: ZENworks 11; Software Distribution.
Explanation: If you launch a Launch Windows Thin Client Application action configured with the RDP Session on a 64-bit managed device, the action might fail.
Action: Apply the KB925876 patch (http://support.microsoft.com/kb/925876).

Unable to select an icon with the 64-bit Internet Explorer

Source: ZENworks 11; Software Distribution.
Explanation: If you use the 64-bit Internet Explorer to launch ZENworks Control Center, then click the browse icon to browse to and select an icon from the icon resources such as an .exe, .dll, or .ico file, one of the icons from the resource file is selected by default. You cannot select any other icon.
Action: Use the 32-bit Internet Explorer to launch ZENworks Control Center.

If the Wake-on-LAN schedule on the managed device is behind the server’s time zone, the device fails to wake up

Source: ZENworks 11; Software Distribution.
Explanation: If a bundle having the distribution schedule configured is assigned to a managed device such that the Wake-on-LAN schedule is behind the server’s time zone, the device fails to wake up.
Action: Ensure that the Wake-on-LAN schedule on the managed device is not behind the server’s time zone.

Bundle shortcut icon is not visible in the Quick Launch area of a Windows 7 device taskbar

Source: ZENworks 11; Software Distribution.
Explanation: If you assign a bundle to a Windows 7 managed device and choose to place the bundle shortcut icon in the Quick Launch area of the device, the bundle shortcut icon is not visible because Quick Launch is disabled by default on a Windows 7 device.
Action: To enable Quick Launch on a Windows 7 device taskbar:

  1. Right-click the taskbar and click Toolbars.

  2. Click New Toolbar to open the New Toolbar window.

  3. In the Folder option, specify the following: %UserProfile%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch.

  4. Click Select Folder.

To customize Quick Launch on a Windows 7 device taskbar:

  1. Right-click the taskbar and deselect Lock the Taskbar.

  2. (Optional) Click and drag the Quick Launch to the desired position on the taskbar.

  3. Right-click Quick Launch and deselect Show Title and Show Text to disable title or text display.

  4. Right-click Quick Launch. Click View > Small Icons to enable small icons.

Repairing an MSI that is installed on a device might reboot the device even if the norestart parameter is specified

Source: ZENworks 11; Software Distribution.
Explanation: If you run the Install MSI action to repair an MSI that has already been installed on a device, the device might reboot. This is because /f option that repairs a product can reboot the device. For more information, see Microsoft Support Site.
Action: Perform the following steps to repair a package without a reboot:

  1. In ZENworks Control Center, click the MSI Application Bundle you want to repair.

  2. Click Actions > Install.

  3. Click the Install MSI action to display the Edit Action - Install MSI dialog box.

  4. In the Repair Parameters option, Click to display the Repair Parameters dialog box.

  5. In the Command Line Parameters option, specify /i instead of /f, then click OK.

  6. In the MSI Properties panel, add the following properties:

    • Name = REINSTALLMODE ; Value = omus

    • Name = REBOOT ; Value = ReallySupress

  7. Click OK.

Unable to install or launch a bundle on a Linux or Macintosh device

Source: ZENworks 11; Software Distribution.
Explanation: On a Linux or Macintosh device, if you choose to run the zac command to install or launch a bundle that has special characters such as @ or $ in its name, the bundle fails to install or launch on the device.
Action: Run the zac command and use \\ to escape the special characters in the bundle name. For example, to install a bundle named mac@, run the command as follows:

zac bin mac\\@

Unable to import an exported registry file into the Windows registry

Source: ZENworks 11; Software Distribution.
Explanation: On platforms that use non-Western European languages, a registry file exported by using the ZENworks Registry Edit action might contain values that prevent the registry file from being imported into the Windows registry.
Action: To export the registry file:

  1. In ZENworks Control Center, click a bundle.

  2. Click Actions > Registry Edit.

  3. Click Export to export the registry file.

To import the registry file into the Windows registry:

  1. Edit the exported registry file to remove values such as ffffffffffffffb0 from the file.

  2. Import the file into the Windows registry.

  3. Use the Windows Regedit utility to reenter the values that you removed in Step 1.

    For more information on reentering the values, refer to the Registry Edit Action page of ZENworks Control Center.

The File Upload plug-in does not upload all of the selected files in Internet Explorer, or the browser is not responsive after files are uploaded in Firefox

Source: ZENworks 11; Software Distribution.
Explanation: When you use the Novell File Upload plug-in to upload multiple files, if a file name exceeds the maximum limit supported by the browser or the operating system, the following issues might arise:

  • Internet Explorer: The long filenames are truncated and some of the files are not uploaded.

  • Firefox: The browser becomes un-responsive.

Action: Upload the files in smaller batches using the Novell File Upload plugin.

Bundle Actions fail to launch due to XML file corruption in the local file system

Source: ZENworks 11; Software Distribution.
Explanation: ZENworks stores the bundle metadata in XML files in the local file system. Sometimes an attempt to launch a bundle on a managed device might fail if the Java XML library throws an exception.
Possible Cause: The XML file is corrupt in the local file system.
Action: Delete the cached metadata:

  1. Stop the ZENworks agent.

  2. Delete the Bundle Guid folder from the following path:

    /var/opt/novell/zenworks/apps/metadata/<Bundle Guid> folder

  3. Restart the agent.

After the upgrade, unable to uninstall a bundle that is set to uninstall prior to upgrade

Source: ZENworks 11; Software Distribution.
Explanation: Before upgrading a device if you have set a bundle to uninstall on that device, the bundle might not get uninstalled after you have upgraded the device.
Possible Cause: After the upgrade only the new cache entries are referenced and the old cache entries of the unassigned items are not referenced. Thus the old and the new cache entries are not synchronized.
Action: Won’t fix.