Results 1 to 2 of 2

Thread: Dependent Bundles

Threaded View

  1. #1

    Dependent Bundles

    Hey Guys,

    Thought I'd throw this one out there for some opinions.

    I've got an application with multiple entrypoints akin to an office suite.

    There's a single installer for the application, but no main application (it's got about 5 components that could be launched, depending on what the user wants to do).

    I've created a single bundle which installs the application, and then a number of separate bundles that point to each of the entrypoints for the application (each is a different executable).

    Each of these "Launch" bundles calls the "main" bundle in its "Install" actions, and then moves on to launch the appropriate executable in the "Launch" actions.

    This works great - the first time the user launches any of the "Launch" bundles, if the main installer bundle hasn't been run, then the "Install" action runs the installer, and if the installer has already been run then it simply moves on.

    My problem is that if a user has already installed the application and we then make a change to the "Install" bundle, the "launch" bundles do not pick up on the fact that we've made this change, so therefore the user does not receive the new version of the application.

    I've ensured that the new version of the "main" bundle has indeed been published.

    The following runs under the assumption that the ZENworks agent has been refreshed on the device AFTER I published the new "main" bundle.

    If I have the user run one of the "Launch" icons for the application that they've already launched, the install actions are skipped.

    If I have the user run one of the "Launch" icons for the application that they've NOT already launched, the new version I've published is installed.

    If I have the user "Verify" one of the "Launch" icons for the application that they've already launched, the new version of the "Install" bundle I've published is installed.

    In ZENworks 10.x, prior to the introduction of Bundle Change Management, I could increment the version of a bundle whether I'd made any changes or not, so I would simply select all of the "Launch" bundles and increment their versions along with the new "Main" bundle.

    The problem in ZENworks 11.x with Bundle Change Management is that in order to increment the versions of these "Launch" bundles which depend on the "Main" bundle in their install actions is that I cannot simply increment the version of the "Launch" bundles.

    I have to make some kind of trivial change like toggling "Show Bundle Activity" off and back on again, and then publish the new version of each of the "Launch" bundles.

    Is this working as designed, or am I missing something here?

    I would think there should be a way for me to publish a new version of a bundle without fiddling around with toggling a setting, especially if the bundle has dependencies and those dependent bundles run the "main" bundle I just made a change to.

    In ZENworks 10.x, if I made a change to a bundle which other bundles depended upon, I would simply increment the version of the "main" bundle, and then I would be prompted to increment the version of any bundles that depended upon the "main" one.


    P.S. I would leave the standard Windows shortcuts that the application creates on its own, but the purpose of the ZENworks shortcuts I created (the "launch" bundles for the multiple entrypoints) is to ensure that some special HKCU registry entries get applied to the currently logged in user's profile prior to launching the application).
    Last edited by pitcherj; 06-Dec-2012 at 06:37 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts