Just seen this blog to clear it up.

http://blogs.technet.com/b/configurationmgr/archive/2015/05/14/why-microsoft-security-bulletins-ms15-049-and-ms15-051-are-listed-as-ms15-044-in-wsus-and-configuration-manager.aspx

On Thursday, 14 May 2015, Gushue, William <[email protected]> wrote:

>  Good.  Thank you.
>
>
>
> *From:* [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');> [mailto:
> [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>] *On
> Behalf Of *Jason Wallace
> *Sent:* Thursday, May 14, 2015 6:51 AM
> *To:* [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>
> *Subject:* RE: [mssms] MS15-044 and MS15-051
>
>
>
> Hi there
>
>
>
> Yes, I believe that is correct
>
>
>
> *From:* [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');> [
> mailto:[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>] *On
> Behalf Of *Gushue, William
> *Sent:* 13 May 2015 18:20
> *To:* myITforum SMS List ([email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>)
> *Subject:* [mssms] MS15-044 and MS15-051
>
>
>
> MS15-051 is not showing up in the SCCM console under All Software Updates
> after I sync this month’s security updates.
>
>
>
> After doing some digging it seems MS15-044 and MS15-051 point to the same
> update (3045171).
>
>
>
> I found this in the wsyncmgr.log:
>
>
>
> “Skipped update aa0289a0-34fa-4b84-b307-7dd4a2806e5b - Security Update for
> Windows 8.1 for x64-based Systems (KB3045171) because it is up to date.”
>
>
>
> So MS15-044 shows up and in the reports it shows as “Installed”, but no
> sign of MS11-051.  Is this expected behaviour?
>
>
>
> Thanks.
>
>
>  ------------------------------
>
>
> ********************************************************************
>
> This e-mail message is privileged, confidential and subject to
> copyright. Any unauthorized use or disclosure is prohibited.
>
> Le contenu du présent courriel est privilégié, confidentiel et
> soumis à des droits d'auteur. Il est interdit de l'utiliser ou
> de le divulguer sans autorisation.
>
> ********************************************************************
>
>
>
>
>
>



Reply via email to