Approved Security Update Compliance Report

This SQL script shows compliance deviations for approved security updates. The script looks at all security updates that have been approved to a specific target group (or a parent

 
 
 
 
 
(0)
Add to favorites
Windows Update
8/10/2009
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • No results
    1 Posts | Last post October 19, 2017
    • When I run the script as a query from SQL Server 2008 R2 Management Studio against WSUS 3.2.7600.226 I don't get any errors but I also don't get any data in either Results... I just see the headers Computer Name... Missing Updates.... and a second window Update Title... Update ID... Number computers. 
  • Running Query on Server 2012
    1 Posts | Last post May 06, 2016
    • I just wanted to share the command for Server 2012.
      Note, the -i is lowercase.
      sqlcmd -S np:\\.\pipe\MICROSOFT##WID\tsql\query -i name_of_script.vbs
      
  • Approved Update Report WSUS 3.0 / SQL 2014
    1 Posts | Last post September 03, 2015
    • Has anyone got this to work on a SQL 2014 server with the SUSDB running as a SQL 2008 db, reporting on a WSUS 3.0 installation? I have it generating an e-mail, but no output at all. No errors either. I am not really a SQL guy or a scripter, but I hold my own at times. It used to work on the SQL 2008 server with a WSUS 2.0 db. 
      
      I added this to the end of the script.
      
      EXEC msdb.dbo.sp_send_dbmail @profile_name='SQL2014_JRP',@recipients='XXXXXX@XXXXXX.com',@subject='WSUS Computer Status Summary for Approved Updates',@body_format='HTML',@body=@HTML
      
      Thanks in advance.
      
  • Relevant Security Update Compliance Report?
    2 Posts | Last post November 05, 2010
    • Instead of reporting on the approved security updates, I would like to create a query that reports on the relevant security updates. Ideally the report would be based upon the creation date of the patch metadata on the WSUS server in order to track compliance with installing patches within a specific patch timeframe (e.g. 30 days). The current report is dependent upon the approval of a security update, which could be delayed for whatever reason.
      
      Any suggestions?
    • I get an error when running this unless I define the updates table without a primary key.  I get a duplicate key error.
      
      DECLARE @updates AS TABLE (Id uniqueidentifier NOT NULL) --PRIMARY KEY)
      
      Is there a problem in my DB or does this script have an issue?