Patch cannot download, so hang the entire action?

Usage and Config Platform
1

(imported topic written by comjb)

What is the thought process behind allowing BigFix to hold up an entire baseline action when a single component fails to download and cache for one reason or another? Wouldn’t it make more sense to timeout on the failing component, and continue on with the rest of the baseline? This issue has bitten us more than once and it ends up throwing off our entire patch schedule and process. In a large IT department, it has a larger impact than you might think.

2

(imported comment written by jgstew)

I agree, we have this same issue. We would much prefer that the baseline continue instead of stalling out because of a single item.

There is an RFE related to this somewhere to vote on I believe. I don’t have a link handy.

3

(imported comment written by gearoid)

In the meantime - take a look at the features of Automation Plans in server automation which have the ability to specify what to do if a step fails.

4

(imported comment written by comjb)

We don’t own the server automation module. I also would not purchase a module to resolve a functional problem that should come standard with the patching module, but thank you for the information nonetheless.

5

(imported comment written by comjb)

Here is the RFE for this enhancement. Please visit the link and vote for it so we can prioritize the fix:

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&SELECTED_SEARCH_TAB=TAB1&BRAND_ID=90&PROD_FAM_ID=182&CREATED_BY=&KEYWORDS=skip&CR_ID=54195&COMPANY=&rfenumber=id&PAGE=1&ITEMS_PER_PAGE=20&SORT_BY=CREATE_DATE&SORT_ORDER=DESC&HIDE_DESCRIPTIONS=true&is_javascript_enabled=false