New Office 2007 Install - Policy Action To Quick to Remediate

Usage and Config Platform
1

(imported topic written by SystemAdmin)

Has anyone run into the issue? We have a BigFix Baseline for Office 2007 that includes Service Pack 2 and the Baseline is deployed as a Policy Action. We deploy Office 2007 with SP2 in the build, but since SP2 is no longer slipstreamed, it installs the non-service pack version first and then attempts to apply the service pack.

Here is where the problem(funny that being to quick to remediate is the problem here!) BigFix has already detected the unpatched Office 2007 version is is attempting to remediate via the policy action.

So the question is how to build in relevance so that the policy action only kicks in after Office has had time to fully install. Perhaps a reg key date / time stamp somewhere or a file / fodler date / time stamp? Does anyone have any experience with this? I image Office 2010 will have the same issue.

John

2

(imported comment written by BenKus)

Hey John,

Does this actually disturb the SP install? I thought the SP would apply successfully even if a few patches were thrown in between the original install and SP upgrade.

Ben

3

(imported comment written by SystemAdmin)

ben, it does seem to cause problems. fyi, we have sp2 as part of the baseline as well. seems to be a timing issue, but we will test some more and confirm.