WSUS

Reviewed: ClientReportingLevel (Jan 18, 2013)

Panatus — Fri, 18 Jan 2013 09:20:07 GMT

Rated 4 Stars (out of 5) - i try this software

Source code checked in, #69709

Project Collection Service Accounts — Mon, 01 Oct 2012 22:10:56 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69708

Project Collection Service Accounts — Mon, 01 Oct 2012 22:06:45 GMT

Checked in by server upgrade

New Post: unhandled exception from command line--requires "run as administrator"!

dotnetnoob — Fri, 13 Jul 2012 18:23:40 GMT

Hi All: Just thought I'd pass along a tip if anyone runs into this.

I logged on to an SBS 2008 sp2 server using my domain admin login, and tried to run the cleanup tool from the command line and received the following error:

d:\tools\WSUS>wsus_cleanup_cl localhost f 8530Running with the following parameters:Server Name: localhostUsing SSL: fUsing Port: 8530The type initializer for 'Microsoft.UpdateServices.Internal.Constants' threw anexception.

Unhandled Exception: System.Security.SecurityException: The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security. at System.Diagnostics.EventLog.FindSourceRegistration(String source, String machineName, Boolean readOnly) at System.Diagnostics.EventLog.SourceExists(String source, String machineName) at WSUS_Cleanup_CL.Class1.Main(String[] args)The Zone of the assembly that failed was:MyComputer

I was able to run it without errors when I chose "run as administrator" when starting the command window.

HTH

Reviewed: WSUS Cleanup (Aug 31, 2011)

smahanes — Wed, 31 Aug 2011 14:55:50 GMT

Rated 5 Stars (out of 5) - Seems to work wonderfully. Per the author's recommendation, I am running it as a Task Sequence. No errors reported, and the WSUS DB seems a little snappier. thanks joseti!

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

New Post: "Timeout expired" every time I try to run the tool

joseti — Tue, 23 Aug 2011 18:11:24 GMT

I would recommend trying to run the cleanup 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.

New Post: WSUS_Cleanup_LC.exe

joseti — Tue, 23 Aug 2011 18:10:42 GMT

I would recommend trying to run the cleanup 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.

Source code checked in, #52373

_TFSSERVICE — Wed, 28 Jul 2010 17:08:20 GMT

Checked in by server upgrade

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

Reviewed: WSUS Cleanup (jan 18, 2010)

PeterisE — Tue, 19 Jan 2010 06:45:25 GMT

Rated 5 Stars (out of 5) - What are the permissions required for the executing user account, if I want to schedule cleanup task? By the way the tool works great! Thanks

Reviewed: WSUS Cleanup (Jan 16, 2010)

oltconsulting — Sat, 16 Jan 2010 11:44:19 GMT

Rated 3 Stars (out of 5) - Useful tool but I'm also getting the database timeout error on all the servers I try it on. Is it working properly for anyone? Does anyone have a way to can work round this?

Reviewed: WSUS Cleanup (Dec 13, 2009)

FusionMaster — Mon, 14 Dec 2009 04:20:01 GMT

Rated 1 Stars (out of 5) - I have been using this for quite some time now, in the eventlog for the application I too get the "timeout" error, so it doesn't actually maintain the SQL database. many many subsequent runs still produce the error... is there a fix for this?

New Post: Error: could not connect to the WSUS server

breaker19 — Tue, 24 Nov 2009 23:16:52 GMT

User error -- I was specifying SSL, when it wasn't SSL. Now it's working.

New Post: Error: could not connect to the WSUS server

breaker19 — Tue, 24 Nov 2009 21:49:07 GMT

When I run the tool, I'm getting Could not connect to the WSUS server in the history log file. The cmd prompt shows: The underlying connection was closed: An unexpected error occurred on a send. Any ideas. Does the tool require a certain version of WSUS -- I'm running 3.0.6000.374. Thx.

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).