It would really be nice if there is a simple bündle task to increase the version number of a bundle without having to modify some aspect of the bundle.

Currently to get a new version number it is necessary to make a sufficiently large Change to the bundle.

Sometimes there are no changes to the bundle itself, but e.g. to some indirect data (files on unc path, variables, etc.) which require a new version number.

Comments

  • Hi Georg,

    You could use zman command (zman biv) to increment the version of the bundle/policy. Beware if a bundle has sandbox, then sandbox gets published instead.

    There is no way from ZCC you could do this operation nor a real use case to just increment the version without any changes to the bundle. Let me know if you have any specific scenario that forces you to increment the version without any change.

  • @Sudheer the specific scenario has already been stated in the original request:
    You're doing a "Network MSI" installation in a bundle and have swapped out the MSI with a newer version under the same UNC location. If the bundle is assigned to devices with a schedule, it will not reinstall on the next scheduled event unless you've bumped up the version.