Can a fixlet be provided for Microsoft Security Advisory 2736233? This patch was released (9/11/2012).
An update (KB2736233) for Microsoft Security Advisory: Update Rollup for ActiveX Kill Bits
Affected Software:
• Microsoft Windows XP
• Windows Server 2003
• Windows Vista
• Windows Server 2008
• Windows 7
• Windows Server 2008 R2
Summary:
This update sets the kill bits for the following third-party software:
Cisco Secure Desktop. The following Class Identifier relates to a request by Cisco to set a kill bit for an ActiveX control that is vulnerable. For more information regarding security issues in the Cisco Secure Desktop ActiveX control, please see the Cisco Security Advisory, Multiple Vulnerabilities in Cisco AnyConnect Secure Mobility Client. The class identifiers (CLSIDs) for this ActiveX control are as listed in the Third-Party Kill Bits section of this advisory.
Cisco Hostscan. The following Class Identifier relates to a request by Cisco to set a kill bit for an ActiveX control that is vulnerable. For more information regarding security issues in the Cisco Hostscan ActiveX control, please see the Cisco Security Advisory, Multiple Vulnerabilities in Cisco AnyConnect Secure Mobility Client. The class identifiers (CLSIDs) for this ActiveX control are as listed in the Third-Party Kill Bits section of this advisory.
Cisco AnyConnect Secure Mobility Client. The following Class Identifier relates to a request by Cisco to set a kill bit for an ActiveX control that is vulnerable. For more information regarding security issues in the Cisco AnyConnect Secure Mobility Client ActiveX control, please see the Cisco Security Advisory, Multiple Vulnerabilities in Cisco AnyConnect Secure Mobility Client. The class identifiers (CLSIDs) for this ActiveX control are as listed in the Third-Party Kill Bits section of this advisory.
I am having trouble with this patch. I am getting a Failed status on most of my Windows 7 machines. I manually installed it on one Win7 computer that failed in Bigfix, and it said it was already installed. Then when I run the fixlet through Bigfix, it goes to pending restart when it should have been not relevant. Then when I restart, I get a failed status. I get the same result if I run it multiple times even though the log says not relevant. It seems that the relevance check is not correct.
Thanks for the information. The patch itself will update several registry keys in the target platform. I am thinking the fixlet detect something missing in the registry. It would be great if you can contact our support and we can do further checking on your system.