20.5 Editing Bundles

You can edit an existing bundle to change its description, add or remove assignments, add or remove the bundle from existing catalogs or bundle groups, add or remove packages from the bundle, deploy a different version of the bundle, and more.

You can use the ZENworks Control Center or the zlman command line utility to edit bundles. The following procedure explains how to edit a bundle by using the ZENworks Control Center. If you prefer the zlman command line utility, see the Bundle Commands section of zlman (1).

To edit a bundle:

  1. In the ZENworks Control Center, click the Bundles tab.

    Bundles tab

  2. Click the bundle's name to display the Summary page, then make the desired configuration changes as explained below.

    Use the Summary page to view detailed information about the selected bundle. This page provides general information about the bundle, lists the individual devices that are assigned to the bundle, displays an event log, shows upcoming events, and lists the catalogs or groups that the bundle belongs to.

    You can also use this page to edit the bundle group's description, add or remove assignments for the bundle, and change other configuration settings, as described below.

    1. Review the information in the General section, then make the desired configuration changes (you can edit only the Description in this section).

      Size: Displays the number of packages that make up the bundle.

      Version: Displays the bundle's version number. You can have multiple versions of the same bundle. If you click the Details tab on this page and make any configuration changes, the version number increments.

      Number of errors not acknowledged: 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 display in the Event Log section below.

      Number of warnings not acknowledged: A warning is anything that does not cause the deployment or installation of the bundle to fail, but indicates minor problems with the packages or bundle. The number displayed indicates the number of unacknowledged warnings, which display in the Event Log section below.

      GUID: Lists the selected object's GUID (global unique identifier), a randomly generated string that provides a unique identifier for the bundle. You cannot edit the object's GUID.

      Description: Displays the selected object's description, if one was provided when the bundle was created. The description provides a short description of the bundle's contents. This description displays in the ZENworks Control Center interface and in the user interface.

      Click Edit to change the bundle group's description, if necessary.

    2. Review the information in the Assignments section, then make the desired configuration changes.

      The Assignments section lists the devices that are assigned to the selected bundle. You can click the device name to view information about each device that is directly assigned to the bundle, including its schedule and other options.

      You can also use the following options:

      Advanced: Click Advanced to display the Edit Assignments page, which includes a list of the devices that are assigned to the selected bundle, the folder that contains each device, each device's deployment and installation schedule, and whether the Allow remove and Dry run options are enabled. You can use the Edit Assignments page to edit certain settings, such as the deployment and installation schedules as well as the Allow remove and Dry run options .

      Add: Click Add to launch the Assign Bundle Wizard to select the devices to be assigned to the selected bundle. For more information, see Section 20.4, Assigning Bundles.

      Remove: Select the device by clicking the check box next to the appropriate device name, then click Remove to remove the device's assignment from this bundle.

      Action > Deploy and Install Now: Click Action > Deploy and Install Now to immediately deploy and install the bundle on the selected device (without regard to its schedule or waiting for a device refresh). To access the Action menu, you must select a device or device folder by clicking the check box next to its name.

    3. Review the information in the Event Log section, then make the desired changes.

      The Event Log section lists all unacknowledged errors and warnings.

      The Status column displays an icon indicating each item's status. Position the mouse pointer over each icon to display a short message describing the status of the item.

      To acknowledge an error or warning, click its name in the Event column, then click Acknowledged in the Message Detail Information dialog box that displays. You can also click Advanced, select the check box next to the appropriate event, then click Acknowledge (a check mark displays on the right side of the Date column to indicate that the item has been acknowledged).

    4. Review the information in the Upcoming Events section.

      The Upcoming Events section lists events scheduled for the selected bundle. You can click the calendar icon to display a calendar to view events for the desired date. You can also use the arrows to view events for the previous or next day, week, or month. Click Refresh to see upcoming events for the selected bundle.

    5. Review the information in the Catalogs/Groups sections, then make the desired configuration changes.

      The Catalogs/Groups sections list the catalogs and groups that contain the selected bundle.

      You can also use the following options:

      Advanced: Click Advanced to display the Edit Catalogs/Groups page to display a list of the catalogs and groups that contain the selected bundle. You can click Add to open the Select Groups dialog box to add the selected bundle to existing catalogs or groups. You can also remove a bundle or group by clicking the check box next to the Name column, then clicking Remove to remove the bundle from that catalog or group.

      Add: Click Add to open the Select Groups dialog box, then click the blue arrow in the Select column to select the desired catalog or group and display its name in the Selected list box.

      Remove: Select the device by clicking the check box next to the appropriate catalog or bundle name, then click Remove to remove the selected bundle from the catalog or group.

  3. Click the Details tab, then make the desired configuration changes.

    Use the Details page to view detailed information about the selected bundle, such as the bundle's version number, name and display name, folder, description, a list of the individual RPM packages that make up the bundle, and the distribution/installation/uninstallation scripts that the bundle will use.

    You can also use the options on this page to deploy a different version of the selected bundle to assigned devices, delete a particular version of the bundle, add or remove packages from the bundle, and change the script engine and scripts that you want to use for the bundle.

    1. Review the information in the RPM Package Bundle Settings section, then make the desired configuration changes.

      Version: Displays the selected bundle's version number. You can have multiple versions of the same bundle. If you make any configuration changes on this page (changing the display name or description, adding a package to or removing a package from the bundle, or adding or modifying a script), the version number increments. You can use the Version drop-down list to view the details of each version of the selected bundle. Text below the Version box informs you which version of the bundle is deployed on assigned devices.

      Deploy: Lets you deploy a different version of the currently deployed bundle. Use the Version drop-down list to select the desired version number, then click Deploy.

      Only one version of a bundle can be deployed at any given time. For example, suppose a bundle has multiple versions: 1, 2, and 3. If version 1 is currently deployed, all associated devices have version 1 of the bundle deployed. If you then make version 3 the deployed version, all devices with version 1 deployed and still associated to that bundle will be automatically upgraded to version 3.

      Delete: Lets you delete a version of the currently deployed bundle. Use the Version drop-down list to select the desired version number, then click Delete.

      Copy: Lets you copy a version of the selected bundle. Use the Version drop-down list to select the desired version number, then click Copy. You can then alter the settings of the copied version to create a new version of the bundle.

      If you create a copy of the YOU patch bundle, the copied version is converted to the RPM package bundle type. Before deploying the RPM package bundle to the device, you must remove the patch RPMs from the bundle. However, you cannot install the copied version of the YOU patch bundle if it contains only scripts.

      Display name: Displays the name that displays for users when they update software. The display name, which can be more intuitive for users, was provided when the bundle was created. You can edit the display name.

      Description: Displays a short description of the bundle's contents. This description displays in the ZENworks Control Center interface and in the ZENworks Linux Management Update Client, which is the user interface. You can edit the description.

      Enforce Persistence: (Selected by default.) If this option is selected, the packages inside the RPM bundle are initially installed according to the bundle's schedule and the packages are reinstalled on assigned devices if they are removed in the future. If this option is not selected, the packages are installed initially according to schedule, but the packages are not checked to see if they have been removed from assigned devices and the packages are never reinstalled. This option applies to RPM bundles only; it does not apply to preboot, file, or Dell Update Package (DUP) bundles.

    2. Review the information in the Packages section, then make the desired configuration changes.

      The Packages section displays the RPM packages contained in the selected bundle. Use the Packages section to upload RPM packages to the bundle, to import RPM packages contained in the ZENworks Linux Management package repository, or to remove packages from a bundle. The packages that you upload to a bundle must already exist on the local device on which you are running the ZENworks Control Center, or you can import packages from the package repository.

      You can use the following options:

      Upload RPM: Click Add > Upload RPM to open the RPM File Upload dialog box. For more information, see Step 6.a.

      Import from repository: Click Add > Import from repository to open the Package Import dialog box. For more information, see Step 6.b.

      Remove: Click Remove to remove the selected packages from the bundle, as needed. The packages removed from the deployed version of the bundle are uninstalled from the managed devices only when a new version of the bundle is deployed.

      To remove the patch RPMs from the YOU patch bundle, you must first create a copy of the YOU patch bundle, then remove the patches from the copied version of the bundle.

      To create a copy of the YOU patch bundle:

      1. Click the Copy button located at the top of the page.

      2. In the Copy dialog box, specify a name for the copy version.

      3. Click OK.

      You cannot install the copied version of the YOU patch bundle if it contains only scripts.

      Set Freshen: Click Action > Set Freshen to transact a package only if a previous version of the package is already installed on the device. You can use the Freshen option in conjunction with the Auto-Detect, Update, or Install options available in Edit.

      Unset Freshen: Click Action > Unset Freshen to turn off Freshen; the package is transacted regardless if the package is already installed on the device or not.

      Edit: Click Action > Edit to display the RPM File Upload dialog box where you can change the selected package's install type and Freshen option.

      Install type: Click Action > Edit > Install Type to use the Install type drop-down list to choose from the following installation options:

      • Auto-detect: Automatically detects whether the bundle is already installed on assigned devices and either installs the bundle or updates an existing bundle, if necessary. Basically, the Auto-detect option determines whether the Update or the Install option functionality (explained below) is best, and then performs that operation. Any kernel packages are installed using the Install option functionality; other packages are installed using the Update option functionality. This is the default option and should be used in most situations.

      • Update: Updates the packages on assigned devices if the packages in the bundle are newer than what is installed on the devices. If the packages are not installed on the assigned devices, ZENworks Linux Management installs them. With the Update option, you don't need to worry whether a package is already installed because the package is either updated (if needed) or installed on the device. Parallel installation of a package is not possible with the Update option.

      • Install: Installs the bundle on all assigned devices. If previous versions of the packages exist on the devices, ZENworks Linux Management does not update the existing packages. As a result, packages can be installed multiple times (parallel installations), which might cause overlap issues. This option is rarely used; you should use the default option, Auto-detect, under most circumstances. You should use this option almost exclusively to install kernel packages.

      Freshen (upgrade only if installed): Use this option to transact a package only if a previous version of the package is already installed on the device. You can use the Freshen option in conjunction with the Auto-detect, Update, or Install options.

      NOTE:To view details about each package, click the desired package in the Name column.

    3. Review the information in the Scriptable Actions section, then make the desired configuration changes.

      As part of the process of distributing a bundle, ZENworks Linux Management can launch scriptable actions that will be executed before and after the bundle is distributed, installed, and uninstalled. For example, you can get data files from a Web server before installing an application that uses them, run applications, and so forth.

      Each action displays the script engine that was specified when the bundle was created. To create a new action, click New to display the Scriptable Action dialog box. For detailed instructions, see Step 9.

  4. Click Apply to save any changes you have made.