Monday, April 19, 2010 6:13 AM
The above mentioned update is reported as installed on every windows xp client. We do not deploy this patch and the smtp service is not installed on our clients. So i expected that i get "not applicable" reported.
Does anybody have the same "problem"/behaviour an maybe have a solution for this.
Tuesday, April 20, 2010 8:56 AMIt's recommended to check windowsupdate.log to find out how this update installed.
Tuesday, April 20, 2010 9:42 AM
As we do not deploy this update and not all of our 2800 users/clients have admin rights i do not think, that this update is really installed. I checked some clients which reported this update as "installed". None of them have an entry in the registry, filesystem or windowsupdate.log.
The file smtpsvc.dll only exists in the system32\dllcache folder. This file have the old version (6.0.2600.5512) and not the patched one (6.0.2600.5949). Therefore i think that the clients are not patched.
As mentioned in my first post i think that the clients do not need the patch and schould report as "not applicable" but all clients reports this patch as "installed" which i think is wrong because the patch is not installed.
I found other users (other site: http://marc.info/?l=patchmanagement&m=127135960313702&w=2) having the same "problem".
Wednesday, April 21, 2010 2:39 AM
Thank you for pointing it. According to our colleagues' feedback, some customer encountered same issue. We marked this issue as KNOWN ISSUE. And KB976323 have been updated today .
This security update may be reported as Installed by Microsoft Baseline Security Analyzer (MBSA) scans or Microsoft Windows Server Update Services (WSUS) server reports for some Windows XP or Windows Server 2003-based systems that do not have the SMTP service enabled. This problem occurs because of an error in the Windows update detection logic metadata. The MBSA scan or WSUS report should report Not Applicable when the SMTP service is not installed on these platforms. This is a reporting issue only. Customers who have successfully installed this update do not have to take action.
I think this issue should be fixed soon.
Thank you for your understanding.
- Marked As Answer by Cyberspace19 Wednesday, April 21, 2010 5:14 AM
Friday, May 04, 2012 6:25 PM
"I think this issue should be fixed soon."
How "soon" is this going to be "fixed".
The environment that I monitor has been affected by this to the tune of thousands of hosts, and I certainly would like to get it reporting properly so that our field administrators are not having to ignore this "missing" patch where it is not applicable.
Appreciate any update or pointer to where such update might exist.