We’ve done some investigation and it seems like it’s hit or miss which version you get. Likely it’s a cache synching prooblem on Microsofts side.
We are trying to figure out which sha1 is correct and we may or may not update the Fixlet. In the meantime, if you would like to push the patch, you can modify the Fixlet to use the sha1 of the file you are getting. Alternatively, if you just re-push the action, there is some chance you will get the file with the matching sha1.
// If the line below fails, please use the “Office 2003 Deployment Control – Initial Assignment” Fixlet message in the BES Support site to configure your Office deployment and then redeploy this action
continue if {(exists key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Office2003Control” whose (exists value “DeploymentType” whose (it=2 OR it=3) of it) of registry)
continue if {(size of it = 5193624 AND sha1 of it = “4f8289407d89d54d01d532275d4882e422dd521f”) of file “office2003-KB982133-FullFile-ENU.exe” of folder “__Download”}
sphear’s original problem with the Office 2007 Compatibility Pack version of MS10-038 got resolved about a month ago. You look like you’re having an issue with a different piece of MS10-038 content.
Is it failing on the continue if {(exists key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Office2003Control” whose (exists value “DeploymentType” whose (it=2 OR it=3) of it) of registry) statement? If it is, that seems to indicate that maybe the office2003 control registry key hasn’t been set.
If it’s failing somewhere else then something else is going on.