Hi guys, First question from an altiris newbie.
Guys,we are using NS 6.2 with Patch Management, and having a big problem with Office 2003 patches.
Problem:
Altiris NS Server reports that most our workstations are vulnerable, but the patch is actually installed on them.
Bulletin/Patch in question:
MS08-052/KB954478
The patch exe is as follows:
Office2003-kb954478-fullfile-enu.exe
What we have done:
The patch was released over a month ago, and if we remote on locally to the workstations, and go to Add/Remove programs, we see an entry in there for the patch: Security Update for Office 2003 (KB954478)
Looking at the Altiris Agent, we find that the patch is continually trying to download and we dont know why.
If we go into the Reports section of the NS server, most systems are reporting that they are vulnerable with respect to this patch, even though they have the patch installed.
The machines have been rebooted since the patch was deployed.
Ive used the remote altiris agent diagnositcs tool.
Ive tried to run an update inventory using the agent, but the reporting ns server is not updating.
Inventory collection is set at an interval every 6 hours.
Because my knowledge of altiris is really limited, im stumped and would love your guys seasoned expertise.
I spose the concern here is how do we get the ns server to report that systems that have actually been patched, dont show as vulnerable when doing the report on the ns server.
Q: How can you force an inventory update, including entries seen in Add/Remove programs, from the client? How and where then do you check on the ns server that this machine will show the patch has been installed?
We have over 3000 machines reporting that this patch has not been installed, when in reality, it is.
Any help greatly appreciated.
by: bbaoPosted on 2009-07-06 at 14:57:08ID: 24789547
according to KB954478, if the patch has been deployed successfully, the following DLL should be updated as follows:
File name, File version, File size, Date, Time
GDIPlus.dll , 11.0.8230.0, 1,693,184, 26-Jul-2008, 00:15
so have you actually checked the file on a managed PC having the problem?