Patch Management Solution

Hello,

we have problems with reporting patch in title. When we can check Resource summary on some PC we can see that this patch is installed. In WindowsUpdate log we can see that the patch was installed. SMA don't have information (it is not in Software updates tab) that this patch needs to be installed but according report we can see that some computers don't have this patch installed - see screen shot.

Can you please check it? SMP version 7.1 MP1.1 Roll up5.

When you take a look at the computer itself that's missing the update do you see any indication in the SMA of why it's not installed?  Also, what happens when you run the update manually on one of these computers?

Hello Kada,

Keep in mind that once the Software Update is installed, and the IsInstalled=TRUE is processed by the SMP to the database; the client is pulled from the Patch Intersect Filter for that update and is no longer targeted by the Software Update Policy. This is why the InstallLog.csv file was created.

When you check the InstallLog.csv file on the client; do you see that KB2862330 is installed with the v2 in the name?

It may be that the update was revised, the settings on the PMImport do not have the 'Enable distribution of newly added Software Updates' enabled, and therefore the Software Update Policy is not deploying the revised update v2.

Confirm the affected clients are targeted by the Software Update Policy for MS13-081 and that the Advanced Tab displays the Software Update Advertisement is enabled for KB2862330v2. 

If the v2 update is present with the Exit Code 0 or 3010 (client rebooted); you may want to troubleshoot why the client's Patch Inventory is failing to be delivered / processed by the SMP as outlined on KM: HOWTO60750 

If the update was trying to retarget then I would suspect a rules issue would be at play here, but where the Software Updates Tab is blank; it appears to be a problem with missing events data (Step 6 in the above mentioned KM article) or Patch Inventories failing to be processed.

Hope this helps,

Joshua

Joshua,

here is the record from Installlog.csv

Yes, I think the problem is with the reboot event.

http://www.symantec.com/business/support/index?page=content&id=TECH167291

We did change the value in the registry for affected PC and now waiting for reboot.

Please keep in mind that the reboot required is only a part of the event. If the client's registry key displays 'Reboot Required' then a reboot will resolve the reporting issue; however, if the registry key is set back, and the Compliance Reports still fail to display accurately, the work around to implement the Updated Views in SQL will be the resolution until the next Software Update Cycle can be ran and the event re-processed.

The KM: TECH167291 will detail the checks to make to see if this is needed and holds the updated Views to run in SQL Management Studio.