This is the Windows Server Update Services support team blog. We cover all things relating to WSUS and Windows Update.
We’ve had a few questions regarding critical updates and WSUSSCN2.CAB so I thought I’d publish a quick explainer in case you were wondering the same.
Question: Is security advisory KB2719615 going to be added for Microsoft Update Catalog in the near future?
Answer: KB2719615 is a critical update, so like all other MSRC security advisories that are released as a Critical Update, it will not currently be in the WSUSSCN2.CAB. This MSXML advisory is also unique in that it is not available on Microsoft Update, which means it cannot be obtained via Automatic Updates, Windows Update, Microsoft Update, or any enterprise management tool (WSUS Server, SMS/SCCM, Intune) or the MU Catalog.
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
The above seems to be incorrect. It is not availible via WSUS. See social.technet.microsoft.com/.../92af870b-7ba1-41fb-bf2c-ebb3cd4e2e18
Please note that this answer is posted in two locations. The other location has not been updated to reflect the conclusion provided here on 6/26/2012.
The opposite conclusion (to paraphrase; Windows and Automatic updates address this issue for consumers) is still posted here:
Is it possible to link to the two posts to better reflect updates?
Would it be possible to get an update from MS on the consumer front? It seems there have been reports in several places that Automatic Update will resolve this issue. Apparently this is not actually the case. And, if users consulted any source but this page they may have an unwarranted sense of safety assuming that Auto Update will protect them.
A followup to the early June press releases indicating that this continues to be an outstanding issue also seems warranted; along with a more user friendly process for end users accustomed to using Automatic Updates.
This issue is also mentioned on the social technet here:
Would it be possible to post a definitive comment or link there as well?