Problem:
I'm working a lot with the ENGL Imaging Toolkit and to be able to not force run a bundle or apply a policy to a device when the device is being imaged and the ENGL build process is active on the device installing bundles from ZCM one has to configure a Requirement on those Bundles to either run or not.

Bundles and policies that NOT need to run need a Requirement 'Registry key exists' '\HKEY_LOCAL_MACHINE\Software\ENGL\ztoolkit' 'NO'

The Bundles that DO need to run (and is connected to the user that logs into ZCM during build) need a Requirement 'Registry key value' '\HKEY_LOCAL_MACHINE\Software\ENGL\ztoolkit\' 'RestartPhase' = '3'.

To make sure bundles do not run in phase 3 during desktop build one has to remember to always punt in those keys. Customers do easily forget this.

Solution:
I would like to have a zone system setting that configures a Bundle Default Requirement setting. This way I could define any bundle created to have this setting. As this may have undesired impact on (some) system bundles while others do should have this (like the PRU update bundles, see https://www.engl.co.uk/kb/tid-2009004.htm) a good solution would be to be able to define at system zone level:
- Force PRU bundles to have predefined requirement
Example: 'Registry key exists' '\HKEY_LOCAL_MACHINE\Software\ENGL\ztoolkit' 'NO'
-Option to Enable the 'New Bundle Wizard' to default show a Requirements screen using a (optional) custom defined requirement. Combined with my Idea for the 'Ability to pre define custom requirements at the zone level using a nice name' that will force a user to think about selecting a Requirement in this stage by either leaving the predefined default or just removing it.
This goes beyond creating bundle templates (which still would be great to have in ZCM).

Benefit:
Be less prone to user mistakes, especially case using tools like ENGL

by: Sebastiaan V. | over a year ago | Application Mgmt