The Summary page of a bundle displays the following panels:
The General panel provides a summary of the bundle’s general settings.
Displays the type of bundle.
Clickto display the size of the content associated with the bundle. To view the correct size of the bundle, check for the bundle size information in the bundle summary page after the content import is complete.
When you create a bundle, the bundle's files are imported to the ZENworks content repository. The import is a server process that can take a while. Until the import is complete, the size of the bundle is displayed as 0 (zero).
Displays the latest published version of the bundle. However, if the bundle is a sandbox-only bundle or has a sandbox, it displays.
Displays whether or not the bundle can be deployed to managed devices. If a bundle is enabled, it can be deployed to managed devices.
When you disable a bundle that has already been deployed to a managed device, the bundle icon is removed from all the shortcut locations of the device. However, all the actions performed on the device prior to the disabling of the bundle remain unchanged. If this bundle is assigned to a new device, the bundle shortcut icons are not placed in the device's shortcut locations.
If the bundle is disabled, clickto allow it to be deployed.
An error is anything that causes the deployment or installation of the bundle to fail. The number displayed indicates the number of unacknowledged errors, which are any errors that you have not specifically marked as acknowledged. Unacknowledged errors are displayed in the Message Log section.
A warning is anything that does not cause the deployment or installation of the bundle to fail, but indicates minor problems with the bundle. The number displayed indicates the number of unacknowledged warnings, which are any warnings that you have not specifically marked as acknowledged. Unacknowledged warnings are displayed in the Message Log section.
Displays the bundle’s GUID (global unique identifier), a randomly generated string that provides a unique identifier for the bundle. You cannot edit the GUID.
Displays the bundle’s name as it appears in ZENworks Control Center (ZCC) and the ZENworks Agent (on managed devices). Clickto change the name. Changing the name does not cause the bundle to be redeployed.
Displays the bundle’s description, if one was provided when the bundle was created. The description appears in ZCC and the ZENworks Agent (on managed devices). Clickto change the description.
Determines the shortcut icon that ZENworks Agent displays on managed devices. During creation of the bundle, if you specified a custom icon rather than using the standard ZENworks bundle icon, this field displays the image and name of the custom icon. If you did not specify a custom icon, this field is empty and the standard icon is used.
Clickto change the icon, delete the icon, or add an icon if one is not specified.
To select an icon, click , allow browser to launch ZCC Helper, and then browse to and select the icon you want to display on managed devices.
If you do not specify an icon, a default icon is used.
NOTE:For Linux bundles, only the PNG and JPEG formats are supported.
Displays the contact information (names, phone numbers, and e-mail addresses) of the people who you want users to contact with problems or questions about the bundle. The contact information is displayed by ZENworks Agent on managed devices.
Clickto change the contact information, delete contact information, or add contact information.
Displays any information that has been added specifically for ZENworks administrators to view. The notes are displayed only in ZCC.
Clickto change the notes, add notes, or delete notes. Editing the note does not create a sandbox. You can edit the administrator notes for any version of a bundle.
Displays the folder path used by ZENworks Agent when displaying the bundle on themenu.
For example, if you specify Applications/Accounting as the path and choose to display the bundle on the menu, ZENworks Agent creates an Applications/Accounting folder on the menu and adds the bundle to it.
You can place multiple bundles in a single folder by specifying the same folder path for each of the bundles.
Clickto change the folder path, add a folder path, or delete the folder path.
You can create an image file for the bundle to use as an add-on image to a base image. If you have already created an image file for the bundle, this field displays the name of the image file. Otherwise, clickto create the image file and assign it to image servers.
If the bundle includes any dependent bundles, you can also create and assign an add-on image for the dependent bundles.
Clickto display the bundle activity indicator window during the distribution, installation, verification, and uninstallation of a bundle on the managed device. The user on the managed device cannot close this bundle activity indicator window.
On Windows 2000 devices, the control that indicates the progress of the bundle execution on the managed device is not displayed in the bundle activity indicator window.
Displaysif there are no bundle dependencies for this bundle. If there are dependencies for this bundle, click to display a list of additional bundles that are required by this bundle.
The list is for viewing only. To change a bundle dependency, switch to thetab, click the appropriate action (for example, or ), then locate the or . Select the entry and perform the action you want (for example, edit or delete it).
For more information, see Dependency Bundles.
This field is available only for Linux bundles. It indicates the severity, such as Security, Recommended or Optional.
This field is available only for Linux bundles and Linux Dependency bundles.
Clickto create a YUM service and assign it to ZENworks Servers in a Management Zone. You can create a YUM service for a bundle and use it on devices that are not managed by ZENworks. Click for more information on how to create a YUM service.
When you create the YUM service, the bundle’s Summary page is displayed. Thefield displays the relative path of the repository. The In-Progress icon indicates the progress. Click the tab to refresh the page. The icon indicates that the service is hosted on the Primary Server. The relative path of the YUM repository is displayed in the field.
A yellow icon is displayed when the repository is not updated with the packages in the bundle.
Clickto edit the YUM service details. You can edit the YUM service to add or remove Primary Servers.
The Bundle Status panel displays a summary of the bundle’s assignment, deployment, and launch status. Therow displays the status of the bundle through assignment to users; the row displays the status of the bundle through assignment to devices. A bundle can be directly assigned or assigned through membership in a folder or group. You can click an underlined link in any column to view the status of the individual users and devices to which the bundle is assigned, retry a failed bundle, or export the data to a CSV file.
A bundle’s status is calculated using the status of many events. For example, a device might indicate that the bundle failed when the distribution was successful, but the installation failed. The numbers in the various columns represent an overall view of the bundle’s status.
NOTE:The Bundle Status panel on the bundle’s sandbox or the older versions page does not display the status. However, the Bundle Status panel on the bundle’s published version page displays the status of the bundle’s published version, sandbox, and the older versions.
The bundle status information is separated into the follow groups listed below, which are independent of each other. For example, it is possible for an installation to be successful, but the launch to be unsuccessful.
The following status information is available:
Targeted: Displays the number of users and devices to which the bundle is assigned.
Devices Effective: Displays the number of devices on which the bundle is effective through a user or device assignment. A bundle is effective for a device if the device meets the system requirements of the bundle. The number of users or devices in thecolumn might be less than the number in the column because the bundle might be assigned to a device that does not meet the bundle’s system requirements. For example, you might have a Windows bundle assigned to a Linux device, but the bundle is not effective for that device.
Devices Not Effective: Displays the number of devices on which the bundle is not effective through a user or device assignment. If a bundle is not effective for the device, it means that the device does not meet the bundle’s system requirements.
Pending: The pending status for the device displays the number of devices on which the bundle is not yet distributed or executed, such as devices that are switched off. Click the underlined link to display the list of such devices.
Blocked/Targeted: Displays the number of users or devices on which the bundle is blocked from being used out of the targeted number of the users or devices. Click the underlined link to display the list of such users or devices.
The following status information is available:
Devices Pending: Displays the number of devices on which the bundle is pending. A bundle’s status is pending if the bundle has met the device’s system requirements, but the bundle has not been distributed to the device or the bundle has been distributed to the device but the bundle has not been installed.
Devices Succeeded: Displays the number of devices on which the bundle was successfully distributed and installed.
Devices Failed: Displays the number of devices on which the bundle’s distribution or installation failed.
The following status information is available:
Succeeded: Displays the number of devices on which the application in the bundle was successfully launched.
Failed: Displays the number of devices on which the application in the bundle was not successfully launched.
The Message Log panel displays all unacknowledged messages generated for the object. An unacknowledged message is one that you have not yet reviewed and marked as acknowledged.
Status: Displays an icon indicating the type of message: critical, warning, and normal.
Message: Displays a brief description of the event that occurred.
Date: Displays the date and time the event occurred.
NOTE:The Message Log panel on the bundle’s sandbox or the older versions page does not display any messages. However, the Message Log panel on the bundle’s published version page displays the messages of the bundle’s published version, sandbox, and the older versions.
A message remains in the Message Log list until you acknowledge it. You can acknowledge individual messages, acknowledge all messages at one time, or view more information about both acknowledged and unacknowledged messages. The following table explains how to do these tasks:
Acknowledge a message
If you decide that you don’t want to acknowledge the message, clickto dismiss the dialog box. This causes the message to remain in the Message Log list.
Acknowledge all messages
View all acknowledged or unacknowledged messages
In addition to viewing all acknowledged and unacknowledged messages, you can also view only those messages with a specific status or date, view more details about messages, and acknowledge messages.
Click thebutton on the Edit Message Log page for specific information about performing tasks on that page.
Delete a message
Deleting a message completely removes the message from your ZENworks system.
The Upcoming Events panel lists all bundles d to deploy or launch today on all managed devices in your ZENworks Management Zone. To view the events for another day, click the icon to select a specific day or use the 1, 7, and 31 arrows to view events for the previous or next day, week, or month.
Click a bundle to display or edit its details such as summary, relationship, requirement, actions, or settings.
Click a time to view the bundle’s details, including the time the event is d to fire, its type (Date Specific, Event, Recurring, etc.), the dates on which the event is d to be performed, and the event’s start and end time.
Click to view the bundle’s assignment details, including the bundle’s folder and its assignments (devices or workstations).