WSUS Release Rss Feed

Updated Release: WSUS Cleanup (Sep 23, 2008)

joseti — Tue, 23 Aug 2011 18:13:53 GMT

This tool can automate the cleanup process within WSUS.

The zip contains three files. The exe that performs the cleanup, an optional sql file that can be used to run the WSUS database maintenance script and a small help file. Just extract the files to a single directory and run the exe from a command line. The exe will then look for the sql file and if present run the SQL maintenance script.

Once the tool is complete it will create a log file within the same directory as the tool with the cleanup results but it will also log cleanup results to the application event log.

Create a scheduled task to run this tool monthly.

==========================================

C:\>WSUSCleanupCL.exe /?
Help menu.

WSUSCleanupCL.exe Server SSL Port Parameter List

server = WSUS server name.
SSL = 't' if using SSL otherwise 'f'.
Port = port number WSUS is listening on. Default is '80' otherwise '8530'.

Parameters:
superseded = cleanup all superseded updates that are no longer needed.
expired = cleanup all expired unapproved updates.
obsolete = cleanup all expired updates regardless of their approval.
compress = cleanup previous revision of updates that are no longer deployable.
computers = cleanup computers that have not contacted the server in over 30 days.
files = cleanup unneeded content files.
DB = runs the database maintenance script (make sure the DB_maint.sql file is present).

all = if all is used all cleanup options above will be run.

Sample commands:
WSUSCleanupCL.exe
The above command will prompt you to input the server name, SSL configuration and port number WSUS is listening on. This can be run against a local or a remote server and runs ALL cleanup options.

WSUSCleanupCL.exe SomeServer t 8530 all
The above command will connect to SomeServer on port 8530, use SSL and cleanup with all options.

WSUSCleanupCL.exe SomeServer f 80 computers superseded
The above command will connect to SomeServer on port 80, it will not use SSL and cleanup will only run the computers and superseded options (no other cleanup options will run).

==================================

If you get a SQL timeout while running the tool I would recommend trying to run the cleanup initially from management studio or use sqlcmd as described here:
http://technet.microsoft.com/en-us/library/cc708594(WS.10).aspx

The timeout in studio manager or sqlcmd should allow for longer execution time. Once you run it initially and get the database cleaned up the subsequent runs with this tool should work.

Released: WSUS Cleanup (Sep 23, 2008)

Tue, 23 Aug 2011 18:13:53 GMT

Updated Release: SQLInjectionFinder.exe (2010) (May 14, 2008)

gctech — Tue, 08 Jun 2010 19:41:23 GMT

SQLInjectionFinder.exe (v2010)
Tool to help determine .asp pages targeted by SQL Injection attacks

Usage:
1. Launch SQLInjectionFinder.exe on the IIS machine where the suspected SQL Injection occurred.
2. The tool looks for the location of the IIS Logs (as it may or may not be in system32\Logfiles)
3. It then navigates through each subfolder and parses each IIS log... looking for “CAST(“ statements
4. If suspicious entries are found, CSV output files are created at the following location:
%Systemdrive%\CSSSEC_SQLInJectFinder\DATA

Released: SQLInjectionFinder.exe (2010) (May 14, 2008)

Tue, 08 Jun 2010 19:41:23 GMT

Updated Release: WSUS Cleanup (Sep 23, 2008)

joseti — Thu, 25 Jun 2009 18:14:29 GMT

Released: WSUS Cleanup (Sep 23, 2008)

Thu, 25 Jun 2009 18:14:29 GMT

Updated Release: WSUS Cleanup (Sep 23, 2008)

joseti — Thu, 25 Jun 2009 14:29:04 GMT

This tool can automate the cleanup process within WSUS.

The zip contains three files. The exe that performs the cleanup, an optional sql file that can be used to run the WSUS database maintenance script and a small help file. Just extract the files to a single directory and run the exe from a command line. The exe will then look for the sql file and if present run the SQL maintenance script.

Once the tool is complete it will create a log file within the same directory as the tool with the cleanup results but it will also log cleanup results to the application event log.

Create a scheduled task to run this tool monthly.

==========================================

C:\>WSUSCleanupCL.exe /?
Help menu.

WSUSCleanupCL.exe Server SSL Port Parameter List

server = WSUS server name.
SSL = 't' if using SSL otherwise 'f'.
Port = port number WSUS is listening on. Default is '80' otherwise '8530'.

Parameters:
superseded = cleanup all superseded updates that are no longer needed.
expired = cleanup all expired unapproved updates.
obsolete = cleanup all expired updates regardless of their approval.
compress = cleanup previous revision of updates that are no longer deployable.
computers = cleanup computers that have not contacted the server in over 30 days.
files = cleanup unneeded content files.
DB = runs the database maintenance script (make sure the DB_maint.sql file is present).

all = if all is used all cleanup options above will be run.

Sample commands:
WSUSCleanupCL.exe
The above command will prompt you to input the server name, SSL configuration and port number WSUS is listening on. This can be run against a local or a remote server and runs ALL cleanup options.

WSUSCleanupCL.exe SomeServer True 8530 all
The above command will connect to SomeServer on port 8530, use SSL and cleanup with all options.

WSUSCleanupCL.exe SomeServer False 80 computers superseded
The above command will connect to SomeServer on port 80, it will not use SSL and cleanup will only run the computers and superseded options (no other cleanup options will run).

Released: WSUS Cleanup (Sep 23, 2008)

Thu, 25 Jun 2009 14:29:04 GMT

This tool can automate the cleanup process within WSUS.

The zip contains three files. The exe that performs the cleanup, an optional sql file that can be used to run the WSUS database maintenance script and a small help file. Just extract the files to a single directory and run the exe from a command line. The exe will then look for the sql file and if present run the SQL maintenance script.

Once the tool is complete it will create a log file within the same directory as the tool with the cleanup results but it will also log cleanup results to the application event log.

Create a scheduled task to run this tool monthly.

==========================================

C:\>WSUSCleanupCL.exe /?
Help menu.

WSUSCleanupCL.exe Server SSL Port Parameter List

server = WSUS server name.
SSL = 't' if using SSL otherwise 'f'.
Port = port number WSUS is listening on. Default is '80' otherwise '8530'.

Parameters:
superseded = cleanup all superseded updates that are no longer needed.
expired = cleanup all expired unapproved updates.
obsolete = cleanup all expired updates regardless of their approval.
compress = cleanup previous revision of updates that are no longer deployable.
computers = cleanup computers that have not contacted the server in over 30 days.
files = cleanup unneeded content files.
DB = runs the database maintenance script (make sure the DB_maint.sql file is present).

all = if all is used all cleanup options above will be run.

Sample commands:
WSUSCleanupCL.exe
The above command will prompt you to input the server name, SSL configuration and port number WSUS is listening on. This can be run against a local or a remote server and runs ALL cleanup options.

WSUSCleanupCL.exe SomeServer True 8530 all
The above command will connect to SomeServer on port 8530, use SSL and cleanup with all options.

WSUSCleanupCL.exe SomeServer False 80 computers superseded
The above command will connect to SomeServer on port 80, it will not use SSL and cleanup will only run the computers and superseded options (no other cleanup options will run).

Updated Release: WSUS Cleanup (Sep 23, 2008)

joseti — Thu, 25 Jun 2009 14:28:01 GMT

Updated Release: SQLInjectionFinder.exe (1.7.0) (May 14, 2008)

gctech — Thu, 11 Jun 2009 23:20:17 GMT

SQLInjectionFinder.exe (v1.7.0)
Tool to help determine .asp pages targeted by SQL Injection attacks

Usage:
1. Launch SQLInjectionFinder.exe on the IIS machine where the suspected SQL Injection occurred.
2. The tool looks for the location of the IIS Logs (as it may or may not be in system32\Logfiles)
3. It then navigates through each subfolder and parses each IIS log... looking for “CAST(“ statements
4. If suspicious entries are found, CSV output files are created at the following location:
%Systemdrive%\CSSSEC_SQLInJectFinder\DATA

Released: SQLInjectionFinder.exe (1.7.0) (May 14, 2008)

Thu, 11 Jun 2009 23:20:17 GMT

Updated Release: SQLInjectionFinder.exe (1.7.0) (May 14, 2008)

gctech — Thu, 11 Jun 2009 23:15:29 GMT

Updated Release: SQLInjectionFinder.exe (1.6.0) (May 14, 2008)

gctech — Thu, 11 Jun 2009 22:50:34 GMT

SQLInjectionFinder.exe (v1.6.0)
Tool to help determine .asp pages targeted by SQL Injection attacks

Usage:
1. Launch SQLInjectionFinder.exe on the IIS machine where the suspected SQL Injection occurred.
2. The tool looks for the location of the IIS Logs (as it may or may not be in system32\Logfiles)
3. It then navigates through each subfolder and parses each IIS log... looking for “CAST(“ statements
4. If suspicious entries are found, CSV output files are created at the following location:
%Systemdrive%\CSSSEC_SQLInJectFinder\DATA

Reviewed: WSUS Cleanup (Jan 26, 2009)

DLKirchmer — Mon, 26 Jan 2009 11:31:52 GMT

Rated 5 Stars (out of 5) - This should be part of the product and not an after the fact add-on.

Updated Release: SQLInjectionFinder.exe (1.6.0) (May 14, 2008)

gctech — Tue, 20 Jan 2009 19:18:41 GMT

SQLInjectionFinder.exe (v1.5.0)
Tool to help determine .asp pages targeted by recent SQL Injection attacks

Usage:
1. Launch SQLInjectionFinder.exe on the IIS machine where the suspected SQL Injection occurred.
2. The tool looks for the location of the IIS Logs (as it may or may not be in system32\Logfiles)
3. It then navigates through each subfolder and parses each IIS log... looking for “CAST(“ statements
4. If suspicious entries are found, CSV output files are created at the following location:
%Systemdrive%\CSSSEC_SQLInJectFinder\DATA

Released: SQLInjectionFinder.exe (1.6.0) (May 14, 2008)

Tue, 20 Jan 2009 19:18:41 GMT

Updated Release: SQLInjectionFinder.exe (1.5.0) (May 14, 2008)

gctech — Sun, 18 Jan 2009 17:38:42 GMT

Released: SQLInjectionFinder.exe (1.5.0) (May 14, 2008)

Sun, 18 Jan 2009 17:38:40 GMT

Reviewed: WSUS Cleanup (Nov 24, 2008)

tdghia — Mon, 24 Nov 2008 16:04:13 GMT

Rated 5 Stars (out of 5) - Great tool! I have been running it for over a month now without a problem and it works great. I actually run it every week since most of my wsus servers have more than 10000 clients.

Created Release: ClientReportingLevel (Nov 10, 2008)

joseti — Mon, 10 Nov 2008 22:04:20 GMT

This tool controls the client reporting level property for WSUS. When someone installs SCCM, reporting for WSUS may inadvertently get disabled thus preventing all clients to stop sending status reports. As long as SCCM is still installed and the WSUS server in question is still controlled by SCCM the reporting level should be configured via SCCM.

If SCCM gets removed or the Software Update Role for the WSUS server in question is removed you can use this utility to control the WSUS reporting level. Run it from a command line on the WSUS server in question.

=========

C:\Users\Administrator\Desktop>WSUSReportingLevel.exe /?

Current Reporting Level: All

Please enter a numeric option:
Press '1' to set the client reporting level to 'ALL'.
Press '2' to set the client reporting level to 'NONE'.
Press '3' to set the client reporting level to 'STATUS ONLY'.
Press '4' to exit.