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 images 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 DOES 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'.

Other examples of settings I use frequently for requirements are
-'Environment Variable Value' 'DeviceType' = 'MyType'
-'Environment Variable Value' 'DeviceType A and B ' = 'DeviceType A' or 'DeviceType B'
-Multiple other environment or registry settings.

Solution:
As it's easy to forget to set needed requirements for an non-day-to-day-zcm-admin or make a typo in those as they do, It would be helpfull if we could configure these Requirements at the ZCM zone level. Here we could give those requirements a helpfull Name, which can be selected at the Policy/Bundle requirements tab as the would shows in the Add Requirement drop down menu.
Not only would these allow us to create a global set of requirements (MyRequirementSet as for 'Var X' = X OR 'Var Y' =Y) at once, but these could be inherited by multiple bundles and policies being updated as the global requirement gets modified itself. These Requirement sets need to be synced to the device as ZCM System Variables do (and need to be available on Device Startup events)

Benefit:
Less prone to making typo's or defining the wrong key or value that is needed in that situation. Time saver case requirements need to be modified for some reason.

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