none
Patching the Windows Internal Database used by WSUS

    Question

  • Hi,

    We have WSUS installed on a server which uses the Windows Internal Database. A vulnerability scanner we use has identified the Windows Internal Database as SQL 2005 SP3 and indicates it needs to have MS11-049 installed, I've downloaded the SQL 2005 patch for MS11=049 and tried to install it but I get the message that no instances needing the patch can be found. Anyone know how I can install this patch.

    jeudi 28 février 2013 20:02

Réponses

  • We have WSUS installed on a server which uses the Windows Internal Database. A vulnerability scanner we use has identified the Windows Internal Database as SQL 2005 SP3 and indicates it needs to have MS11-049 installed, I've downloaded the SQL 2005 patch for MS11=049 and tried to install it but I get the message that no instances needing the patch can be found. Anyone know how I can install this patch.

    You have WSUS.... i would suggest starting by approving and installing Service Pack 4 for the Windows Internal Database (KB2463332), since SP4 does supersede the MS11-049 update for WID SP3. However, MS11-049 for SP4 is also superseded by MS12-070 (Oct 2012), so your vulnerability scanner would seem to need a much newer database than it currently has. MS11-049 is only a current update for SQL Server 2008 R2 and the Visual Studio 2005 SP1 or Visual Studio 2008 SP1 XML Editor.

    Regarding your immediate issue, though, your specific message of non-applicability may also relate to which package of MS11-049 you downloaded.

    • KB2494113 is the package for SQL Server 2005 Service Pack 3 (which would include the WID with SP3 applied).
    • KB2494120 is the package for SQL Server 2005 Service Pack 4 (which would include the WID with SP4 applied).

    There are also a dozen other packages, none of which would apply to WID-with-SP3.

    If you're trying to install anything except KB2494113, then the non-applicable message is correct.

    That's also based on the presumption that MS11-049 actually does apply explicitly to the Windows Internal Database. I note that the MS11-049 article does not expressly list the Windows Internal Database in the affected software list, but unfortunately that's not conclusive evidence of anything since the WID quite often is overlooked or considered "just another edition" of SQL Server 2005.

    On a WSUS v3 SP2 server on Win2008R2 that I just scanned, running WID SP4, MS12-070 is reported as Not Applicable for that system which suggests that MS11-049 might also be Not Applicable for Windows Internal Database installations.

    You have a WSUS server .... Use IT! :-)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    jeudi 28 février 2013 21:53
    Modérateur