|Bypassing ‘Update Collection OS X’ for Helix 6.2|
Helix 6.2 features built-in structure checking, making Update Collection OS X obsolete. Furthermore, certain situations that are legal in Helix 6.2 are flagged by Update Collection OS X and reported as damage.
For these reasons it is preferable to bypass Update Collection OS X altogether when using Helix Maintenance Manager with Helix 6.2. This technote explains how.
One limitation of Helix Maintenance Manager is that it requires that both Update Collection and Helix Utility be run as part of any plan. This presents a dilemma, since Update Collection OS X is obsolete in Helix 6.2.
The answer is in recognizing that, because HMM was created to work with more than one version of Helix, it is necessary to specify the exact copy of Update Collection OS X to be used to check the collection. By supplying our own ‘Update Collection simulator’ we can tell HMM that a successful structure check has been done, allowing it to go on to the next step in the plan.
Follow these steps to set up an Update Collection OS X simulator in Helix Maintenance Manager…
Helix Maintenance Manager will now use this AppleScript applet in place of Update Collection OS X, bypassing the obsolete program.
It is important to note that although it appears that you can select any application in the ‘Choose a File’ dialog, HMM expects that the selected application is named Update Collection OS X and may hang if the selected application has a different name.
|About Helix Utility||
Although Update Collection OS X can be bypassed, it appears there is no way to bypass Helix Utility OS X. The interactive nature of Helix Utility can not be simulated, it seems.
This issue affects all users who use Helix Maintenance Manager with Helix 6.2 or later.