Why Microsoft Security Bulletins MS15-049 and MS15-051 are listed as MS15-044 in Configuration Manager and WSUS

~ Meghan Stewart | Support Escalation Engineer

If you’ve reviewed the Security Bulletin Summary for May 2015, you may have noticed that some security bulletins appear to be missing from your WSUS or Configuration Manager console. If you open the Microsoft Update Catalog and put in all of the KB numbers that were published under those three bulletins, you will notice that they are all listed with MSRC Number MS15-044.

Example 1

3045171 is listed under both MS15-051 and MS15-044 but when you look the it in the Update Catalog you can see it was published under MS15-044.

Below is what you would see in your Configuration Manager console. WSUS would look similar as long as you added the MSRC Number column.

Example 2

3056819 is listed both under MS15-044 and MS15-049 but comes in as MS15-044, not MS15-049.

Why the overlap

There is a reason for this overlap. Basically, the fix was consolidated, and if you read the FAQ about the updates on each of the bulletins themselves you’ll see that they do state this:

https://technet.microsoft.com/library/security/MS15-044

Why some updates are also denoted in other bulletins released in May

Several of the update files listed in this bulletin are also denoted in other bulletins being released in May due to an overlap in the affected software. Although the different bulletins address separate security vulnerabilities, the security updates have been consolidated where possible and appropriate, hence the occurrence of some identical update files being present in multiple bulletins.

Note that identical update files shipping with multiple bulletins do not need to be installed more than once.

This update FAQ is also listed on https://technet.microsoft.com/library/security/MS15-051 and a similar one is noted in the FAQ here: https://technet.microsoft.com/en-us/library/security/ms15-049

The bottom line

So what’s the bottom line for all this? Deploy all of MS15-044 to be compliant for MS15-049 & MS15-051.

Meghan Stewart | Support Escalation Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on FacebookandTwitter :

Main System Center blog: https://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: https://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: https://blogs.technet.com/dpm/
Orchestrator Team blog: https://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: https://blogs.technet.com/momteam/
Service Manager Team blog: https://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: https://blogs.technet.com/scvmm

Microsoft Intune: https://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: https://blogs.technet.com/sus/
RMS blog: https://blogs.technet.com/b/rms/
App-V Team blog: https://blogs.technet.com/appv/
MED-V Team blog: https://blogs.technet.com/medv/
Server App-V Team blog: https://blogs.technet.com/b/serverappv

Forefront Endpoint Protection blog: https://blogs.technet.com/b/clientsecurity/
Forefront Identity Manager blog: https://blogs.msdn.com/b/ms-identity-support/
Forefront TMG blog: https://blogs.technet.com/b/isablog/
Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/
Application Proxy blog: https://blogs.technet.com/b/applicationproxyblog/
The Surface Team blog: https://blogs.technet.com/b/surface/

System Center 2012 Configuration Manager System Center 2012 R2 Configuration Manager ConfigMgr 2012 R2