This document provides troubleshooting guidelines for common problems related to deployment of bundles in a ZENworks 11 SP3 system. If, after completing the troubleshooting steps, the problem is not resolved, please contact Novell Technical Support for additional help.
If the bundle is displayed in the ZENworks Adaptive Agent properties but not in the NAL window, verify that Debug logging is not enabled (ZENworks Adaptive Agent properties >> ).
Debug logging considerably increases the amount of time required to display bundles in the NAL window.
If the bundle is user assigned, check the following:
Is the user logged in to ZENworks on the device?
Has the device been refreshed (ZENworks icon >) since the bundle assignment was made and the user logged in?
Is user authentication configured correctly? For troubleshooting help, see ZENworks 11 SP3 Troubleshooting Authentication.
If the bundle is device assigned, check the following:
Has the device been refreshed (ZENworks icon >) since the bundle assignment was made?
Verify that the bundle is published:
In ZENworks Control Center, clickto display the list.
Locate the bundle in thelist:
If thecolumn displays a version number (for example, 0), the bundle is published. If it displays , the bundle is not published. Click the bundle to display its properties, then click the button next to the field.
NOTE: If the bundle is not showing up on a test device or for a test user, make sure that the Sandbox version is the active version. Only Sandbox bundles can be deployed to test devices and users.
Verify that the bundle assignment is not blocked:
Open the properties for the device, user, group, or folder to which the bundle is assigned.
In thelist, makes sure the bundle’s is not . If it is, select the check box in front of the bundle’s name, then click .
If the bundle assignment is through a device group or folder, check the following:
Is the device is a member of the group or folder?
If the bundle assignment is to a dynamic device group, has the group refreshed after the device was added to the group? To refresh a dynamic device group, select the check box in front of the group in thelist, then click > .
If the bundle assignment is through a user group or folder, make sure that the user is a member of the group or folder.
Click the bundle to display its properties, then check the following:
Enabled: Is the bundle enabled? Disabled bundles are not applied to devices. To check, click thetab and verify that the setting is .
Availability schedule: Has an Availability schedule been set that restricts when the bundle is available. To check, click thetab, locate the device in the list or the user in the list, then click the link to display the Availability schedule.
System requirements: Have system requirements been defined that cause the bundle to not show up on the device. To check, click thetab and compare the defined system requirements against the device.
Run once: Is the Run Once option enabled on the bundle. To check, click thetab, click the tab, then click .
Ensure that DNS is working correctly by performing an nslookup (on the device) of the IP address or DNS name of the Primary or Satellite Server from which the device receives its bundle content. You can run zac zc -l on the device to see the IP addresses and DNS names of the content servers.
On the device, run the zac zetr command at a console prompt to reestablish trust between the device and the ZENworks servers:
If the installation or launch error states that the device can’t download the bundle content because the ZENworks server is not available, the problem is the result of a content replication issue among the ZENworks servers. See ZENworks 11 SP3 Troubleshooting Content Replication.
Has the bundle ever worked on the device? If yes, what changed? If you have Auditing enabled to track bundle modifications, click the bundle to display its properties, click thetab, then see if any modifications have been made to the bundle recently.
If the bundle runs a script or executable, can the script or executable run on the device independent of the bundle?
Click the bundle to display its properties, then check the following:
Rights for bundle actions: Click thetab, then review the , , and action sets. Does the device’s user have the rights needed to perform the actions? If a Dynamic Administrator User is being used, are the appropriate credentials being used, especially to access any network files?
Requirements for bundle actions: Do any of the, , and actions have requirements that are not met by the device? To see an action’s requirements, click the action to display the Edit Action dialog box, then click the tab.
Success return codes: If the bundle uses an action such asor , does that action include the correct return codes for successful completion of the action? Scripts need to return a success code of 0. To see an action’s return codes, click the action to display the Edit Action dialog box, then look on the tab for the field.
Continue on failure: Is thesetting for each action correct? Click an action set tab ( , , or ) to view this setting for each configured action.
Published or Sandbox: If the bundle is published, is the device or user (if user assigned) not configured as a test device or user? If the bundle is sandbox, is the device or user configured as a test device or user?
Undefined system variables: Does the bundle use any variables that are not defined in the bundle? Click thetab > . The and lists contain the only system variables that can be used to define information (paths, names, and so forth) in the bundle.
Bundle chaining: Does the bundle have dependencies on other bundles that are causing the install or launch to fail? To check bundle dependencies, click the Getting Bundle Chaining to work the way it did in ZENworks 7, for help understanding how to correctly use bundle chaining.tab. If the field shows a link, the bundle has dependencies. See the Novell Cool Solutions article,
Launch the Windows Event Viewer and examine the ZENworks-related messages for any indication of why the bundle failed to install or launch.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2015 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.