Microsoft released an out-of-band updated today with the bulletin ID of MS08-067. We are currently working on making the Fixlets and we should have them available soon. As soon as we release the Fixlets, you should see them updated in your Console within an hour and you can deploy them immediately.
I just pushed the patch via the BF console to a machine to test… The action showed “Pending Restart” but when I did a send refresh on the server and it updated in the console the item does not show as relevant…
Can anyone confirm that you do or do not have to reboot for this to be applied completely?
At 1:45pm Pacific Time, BigFix has released all the Fixlets for MS08-067 for English OSes (Microsoft released the patches at 11:45pm Pacific Time). The Fixlets should update in all BigFix Servers automatically within 1 hour or you can use “Tools > Manage Sites > Gather All Sites” to force your BigFix Server to update immediately.
All Non-English Fixlet messages are expected to be released before the end of the day.
All non-English Fixlets were released around 6pm Pacific Time. So by now everyone should have all the Fixlets… If people want to post their experiences with the patch, please do… Our tests here went very smoothly…
Are you aware of machine with a higher version of the netapi32.dll on XP machines? The fixlets are showing as relevant on less than 50% of our windows XPSP2 desktop population.
I just pushed the patch via the BF console to a machine to test… The action showed “Pending Restart” but when I did a send refresh on the server and it updated in the console the item does not show as relevant…
Can anyone confirm that you do or do not have to reboot for this to be applied completely?
Still looking for an answer here.
Is a system protected when you patch and do not reboot it?
If you patch it and do not reboot it, BigFix shows it as not relevant any longer.
I don’t know about anything about this particular patch, but generally speaking it’s common for the Fixlet relevance to become false after running the patch even when a reboot is still required. Note that the action won’t say ‘completed’ or ‘fixed’ until the issue is fully resolved, including a reboot. However, the Fixlet is no longer relevant before reboot because it doesn’t need to be applied again, even though a reboot may be required to complete the process.