WSUS Server Cleanup Wizard... to run or not to run?

Hi,
Sometimes on my server, the WSUS synchronization fails (operation timed out) and I heard that running the Server Cleanup Wizard could help. I also heard that nothing should be done in the WSUS console because it's managed by SCCM.
For SCCM, is it a good or bad practice to run Server Cleanup Wizard from WSUS console and why? SCCM isn't cleaning stuff already? I don't want to mess things up.
Thanks for your help!

Hi,
In addition, you can run the PowerShell Script in Scheduled Tasks.
http://gallery.technet.microsoft.com/ScriptCenter/en-us/fd39c7d4-05bb-4c2d-8a99-f92ca8d08218
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

False positive KB2478662 after Server Cleanup Wizard

This morning WSUS gave me false positives for several clients. I've seen FPs before, but I've never discovered what causes them. In fact, I'm finding it hard to even ask a useful question.
On Friday I ran the WSUS Cleanup Wizard. On Monday I found that our Server 2008 R2 box and all but two of our Windows 7 boxes report as needing .NET update KB2478662 - a long-superseded update from 2011.
I ran "wmic qfe list" to learn that neither KB2478662 nor its two superseding patches (KB2633873 and KB2539635) were installed on any of the unhappy clients. However, KB2972100 supersedes KB2633873 and KB2539635 (but not the earlier KB2478662),
and is installed on all the clients involved. KB2972100 is not listed as superseding KB2478662, the earliest in the chain, so it appears this sort of leapfrogging supersession may not be detected well by WSUS.
However: KB2972100 was installed two months ago, and KB2478662 didn't show before Friday; according to the Microsoft Catalog, none of the update packages has been updated recently; and I'm not finding reports from other admins of the ghost of KB2478662 emerging
from the shadows. I can only assume that running the Cleanup Wizard Friday somehow left WSUS in a state where this false positive could result.
Like I said, I can't decide what question to ask. Am I likely correct in blaming the Cleanup Wizard? If so, is there some way of cleaning up after the wizard? Or of preventing this sort of false positive in the first place? Or is there
some other common cause for this sort of FP?
I seem to get two or three of these FPs a year, and I always end up researching the chain of superseding updates, manually scanning clients until I'm sure the latest update is really in place - and then I decline the false positive. But I'd love to know
a better way to handle these, or to avoid them.

so I don't have a years-long database of approved updates.
That remains to be seen. It only takes one hour of overambitious update approvals to generate five years of content on a WSUS server. :-)
KB2478662 has never appeared before
KB2478662 is an update contained in MS11-039 and has existed since June, 2011. If your WSUS server is only a couple of months old, I'm pretty confident in stating that KB2478662 was part of your original synchronization. KB247862 (MS11-039) is not a superseded
update.
It's much more likely that you just did not notice it before.. but it's always been there.
(as I noted, KB2972100 was broadly installed in October) and has never had any approvals at all.
I can't speak to the question of approvals, but if it was broadly installed, then I'd guess that happened before you deployed this WSUS server and those updates were installed as a result of Automatic Updates. Given that it was released on Oct 14th,
that makes perfect sense.
I've never had the opportunity to decline it, because it's never appeared as "needed".
Those two statements are totally noncongruent. You don't decline an update because it is or is not needed, or was or was not ever reported as needed, you decline an update because it will **NEVER** be needed again at all.
None of the four updates I mention came out since I installed WSUS.
Correct, but not really relevant.
KB2478662 (MS11-039, Jun 2011) - already explained. NOT superseded, except for ITANIUM systems, which was superseded by MS11-069.
KB2539635 (MS11-069, Aug 2011) - SUPERSEDED by KB2633873 (MS12-016, Feb 2012), KB2604115 (MS12-035, May 2012), KB2729452 (MS12-074, Nov 2012), KB2742599 (MS13-004, Jan 2013), and KB2972100 (MS14-057, Oct 2014).
KB2633873 (MS12-016, Feb 2012) - SUPERSEDED by KB2604115 (MS12-035, May 2012), KB2729452 (MS12-074, Nov 2012), KB2742599 (MS13-004, Jan 2013), and KB2972100 (MS14-057, Oct 2014).
KB2972100 (MS14-057, Oct 2014) - The *CURRENT* update.
So since they all came out before you installed WSUS that means that ALL of them were ON your server the day you installed it, and TWO of them were relevant from Day One. The other two should have been immediately declined if KB2972100 was reported as 100%
NotApplicable.
If WSUS thinks KB2478662 is superseded, I have no idea why the Cleanup Wizard hasn't already handled it.
There's no "think" about it. Either the update is superseded, or it is not, and whether it's superseded and what supersedes it and what it supersedes is displayed in the Update Details in the WSUS console. One need only read the screen to get the
facts. In this case KB2478662 is NOT superseded (unless you have an Itanium server), and nothing "thinks" that it is (except you).
As for why the Server Cleanup Wizard hasn't dealt with it, one need only understand what the Server Cleanup Wizard DOES do with superseded updates. Superseded updates are declined *IF* (and only IF):
The update is superseded and has not been approved for at least 30 days.
The update is superseded and not needed by any client systems or downstream servers.
The update is superseded and the superseding update is APPROVED.
So... the ITANIUM instance of KB2478662 will not be handled by the Server Cleanup Wizard, because you have likely not approved any ITANIUM updates that supersede it. And the other instances of KB2478662 will not be handled by the Server Cleanup Wizard because
they are not superseded.
So, back to your original message.
KB2478662 WILL be "Needed" on any system where it is NOT installed, because this update is NOT superseded. Your original premise that this update is superseded is the root of all confusion.
Furthermore, neither KB2633873 nor KB2539635 superseded that package, but they are superseded by a newer update (KB2972100) which predates the existence of your WSUS server, so the presence of KB2972100 and the absence of BK2633873 and KB2539635 is 100%
normal and expected.
You were correct in noting that KB2972100 does not supersede KB2478662, but that's the point at which your logic broke down and asking yourself how 'D' supersedes 'C' and 'B', and 'C' and 'B' supersede 'A', but 'D' does not supersede 'A' might have led to
a re-evaluation of your conclusions.
Ergo... there are *NO* false positives. What is reported is FACTUAL.
HINT: (I've written this over a hundred times in the past five years).... The question you should be asking in such situations is NOT "What's wrong with the update?", but rather "What's wrong with the client?" or "What's wrong with
my analysis?" The WUA evaluates applicability based on a defined set of rules, and reports the update status to the WSUS server based on the evaluation of those rules. If the update is more than a week old.. I absolutely PROMISE you that there is *NOTHING*
wrong with the detection logic in that update and you need to focus your investigation on things other than the updates.
As for how to handle superseded updates and update approvals, you may find some benefit from this article:
Removing unneeded update approvals
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Server cleanup wizard problem - unable to connect to the WSUS Server Database.

I'm trying to run server cleanup wizard.. it starts to run and then after a while it gives me this error:
The WSUS administration console was unable to connect to the WSUS Server Database.
Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.
System.Data.SqlClient.SqlException -- Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Source
.Net SqlClient Data Provider
Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
   at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.InitializeDerivedProperties()
   at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.get_NewUpdatesCount()
   at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetSyncInfoRow(WsusSynchronizationInfo syncInfo)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetListRows()
Thanks

Some questions:
Are there any other databases running on this Std Edition SQL service?
[a] Yes there are, we have Kaspersky enterprise DB, Report Server DB and local application DB.
Are there any other services running on this WSUS Server?
[b] Yes there are, we have Active Directory, Kaspersky enterprise, SQL Server 2005, and WSUS all on the same server.
How many days since your WSUS server was first installed?
[c] It's been about a year now.
What is the physical size of the SUSDB.mdf file?
[d] 9,666,752 KB
What is the hardware configuration of this machine, including disk drives?
[e] Intel Xeon 1.86, 2GB Ram, HD C: 39GB - E: 25.2, running Windows Server 2003 R2 SP2.
How many client systems are you servicing from this WSUS Server?
[f] Around 40.
What products/classifications are you synchronizing.
[g] Windows XP-vista, Windows Server 2003, Office 2003-2007, SQL Server 2005.
Okay, for starters, you have an underpowered/overextended machine running Active Directory, ASP.NET, and a database server, all on a sub 2GHz CPU with 2GB RAM, and not enough disk spindles. The machine has had WSUS running for about a year and is 9GB in size.
There's no doubt in my mind that some of your performance issues are directly related to disk and database fragmentation.
There's also no doubt that some of your performance issues are directly related to memory starvation.
I'd suggest the following long-term fixes:
1. Get a second machine. Make it a dedicated database server. Provision it accordingly to support servicing multiple database applications.
2. Lacking #1, this machine needs more memory. It also needs more disk spindles. At a minimum the databases being serviced should be on a dedicated physical drive; ideally there would be two dedicated drives allocated for supporting database services. The
For the short-term fixes, do this:
1. During after-hours time, if you don't already have one, build a temporary machine that can act as a DC/GC, while you take this machine temporarily offline.
1. Shutdown the Update Services service, SQL Server database engine, and any other services dependent on the SQL Server database engine (Kapersky, and other reporting applications). Disconnect from the network to temporarly eliminate DC traffic. (You could also shutdown the AD services, but disconnecting the network cable is ever-so-much easier.) Defragment ALL drives.
2. Restart ONLY the SQL Server service. Obtain this SQL script to Reindex the WSUS Databases.
3. Restart ONLY the Update Services service. Attempt the Server Cleanup Wizard again. Run it in two passes. Pass 1 performing everything except remove unused updates. Pass 2 running only remove unused updates.
4. After completion of the Server Cleanup Wizard, reconnect the machine to the network and resume all other services.
5. If you're able to complete #3, secure the services of a well-qualified DBA to determine if there are any misconfigurations in your SQL Server setup that would account for why your WSUS database is 9GB in size -- such as improperly configured autogrowth parameters. Based on the products you're updating and only forty clients, 9GB is about 3x the maximum size I would expect to see in a WSUS database. It's possible this is simply caused by excess unused updates, it's possible it's caused by fragmentation, it's probable it was caused by unnecessary autogrowth of the database due to insufficient update maintenance. You'll want a DBA to assist you in shrinking that database after you successfully run the Database Maintenance and Server Cleanup Wizard.
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

Simulating the server cleanup wizard from the command line

We have several servers that run WSUS 3.0 SP2. Are there command line equivalents (wsusutil, etc.) that perform the same tasks as the server cleanup wizard? The objective is to set up a scheduled task so that the server cleanup wizard does not have to be run manually.
Thanks in advance,
Sergio

Hi Sergio,
By default, there is no command line to run server cleanup wizard.
But you can run this wizard by writing a command-line tool (VB, WSUS SDK)that calls WSUS API.
Windows Server Update Services API Samples and Tools
http://download.microsoft.com/download/8/d/0/8d068114-bd66-4fde-a04c-aeaa9d1fe640/Update%20Services%20API%20Samples%20and%20Tools.EXE
Also, I found an article which provide a solution to run server cleanup wizard via powershell:
Perform WSUS 3.0 Cleanup Manager via Powershell
http://pulsarit.net/cs/blogs/claudiog/archive/2007/05/16/eseguire-wsus-3-0-cleanup-manager-via-powershell.aspx

Downstream WSUS server without internet connection, license terms not being downloaded

We have 2 WSUS servers.
ServerA is the upstream server and has access to the internet
ServerB is configured as Autonomous downstream and has no internet access.
Synchronisation between the two servers works fine, with the exception of updates that have license terms. As part of the synchronisation, the downstream server attempts to download the license terms directly from Microsoft but fails, since there is no internet
connection.
Is there a way of configuring it so that the license terms are download from the upstream server or something similar?

with the exception of updates that have license terms. As part of the synchronisation, the downstream server attempts to download the license terms directly from Microsoft
This is not how it works. If the downstream server is correctly configured as a downstream server, it downloads
everything from the upstream server.
How did you determine that your downstream server was attempting to download direct from Microsoft, or that it was directly related to anything being synchronized from the upstream server.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WSUS Server 3.2 wsuscontents folder size is taking away all the disk space(75GB)

Hi ,
We have Windows server 2008R2 X64. server and we have configured WSUS Server 3.2. The WSUSContents folder is taking away all the disk space and there is no space left . As a result WSUS stopped working.
We used WSUS Server cleanup Wizard, but it is not able to reduce the size of this folder.
Is there anyway we can purge the WSUS database? is there any script to run?
Thanks a ton in advance for the help.
Pro1962
India1947

The WSUSContents folder is taking away all the disk space and there is no space left . As a result WSUS stopped working.
We used WSUS Server cleanup Wizard, but it is not able to reduce the size of this folder.
Start here:
Removing unneeded update approvals.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WSUS Cleanup Wizard

Running SBS2011 as a VM using VMWare. I want to clean up WSUS (or get rid of it altogether) but when I run the Server Cleanup Wizard and select Unused updates and update revisions, it stops after a couple minutes with Error: Database Error.
I am able to reset the server node but never get through the cleanup.
Any suggestions are welcome.
Barry

Hi Barry,
Would you please let us know current situation of this issue? Just check if above suggestions can help you.
If any update, please feel free to let us know.
Just addition, please also refer to Lawrence’s suggestion in following similar thread and check if can help
you.
WSUS
Server Cleanup Wizard says: Database Error...
Hope this helps.
Best regards,
Justin Gu

WSUS Server Database maintenance--WSUSCOntents Folder size is taking all the disk space (75GB)

Hi ,
We have set up WSUS Server 3.2 on Windows server 2008 R2 and set the Disk size as 80 GB. The WSUSContents folder is taking away all the disk space and as a result WSUS Server stopped working.
Details:
1. There are no other languages selected other than English.
2.There are no Downstream servers configured.
3.Server cleanup wizard runs for 10 seconds and it shows the below report .
4. Is there any script available to purge the WSUS database?
India1947

The WSUSContents folder is taking away all the disk space and as a result WSUS Server stopped working.
You need to perform additional administration on the server other than just running the Server Cleanup Wizard. Running the wizard with no other administration will accomplish nothing of significance.
Removing unneeded update approvals
Of course, running out of room on the disk drive may well have corrupted the database, at which point the only reliable means of recovery is to install a NEW instance of WSUS with a fresh database.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Host update information not same between WSUS server(Up/Downstream)

Hi,
I have two WSUS server (in win server 2012).
HOST connect to WSUS1, WSUS1 sync WSUS2, WSUS2 sync Microsoft update server(internet).
In WSUS1, Host update states is 100% and last report at 2014/05/28 AM 10:00.
In WSUS2, Host update states is 95% and last report at 2014/05/28 AM 10:00.
WSUS sync at 2014/05/28 AM 17:00
What is the problem?
Kevin

Am 29.05.2014 schrieb kevinbolton:
I have two WSUS server (in win server 2012).
HOST connect to WSUS1, WSUS1 sync WSUS2, WSUS2 sync Microsoft update server(internet).
In WSUS1, Host update states is 100% and last report at 2014/05/28 AM 10:00.
In WSUS2, Host update states is 95% and last report at 2014/05/28 AM 10:00.
WSUS sync at 2014/05/28 AM 17:00
Pls run Server Cleanup Wizard in Options on both WSUS-Servers.
Servus
Winfried
Gruppenrichtlinien
WSUS Package Publisher
HowTos zum WSUS Package Publisher
NNTP-Bridge für MS-Foren

WSUS Cleanup script: cannot connect to WSUS Server

Hi guys,
I'm trying to apply a script (already posted) which allows to perform the WSUS server cleanup with an unattended way.
The script begins as follow:
[reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration") | out-null
#...Get hostname...
$sysinfo = Get-WmiObject -Class Win32_ComputerSystem
$fullname = “{0}.{1}” -f $sysinfo.Name, $sysinfo.Domain
#...Connection to WSUS...
$wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer($fullname,$false,8530)
The $fullname variable returns the expected info, but $wsus doesn't. It displays the following:
Exception calling "GetUpdateServer" with "3" argument(s): "Request for principal permission failed."
At C:\Users\*******\Desktop\WSUS_Server_Cleanup.ps1:7 char:1
+ $wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer($f ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : SecurityException
Please could anybody tell me what am I doing wrong???
Thanks a lot in advance!
Best Regards.

Thank you!
Monday's mistakes... :(
Best Regards.

Clients cannot update from WSUS server - error 8024400E

Alright, so I'm troubleshooting our WSUS server and seem to be stuck. I am running WSUS 3.2.7600.226 on Server 2003. The client I have been using for testing is Windows 7 x64, but we have this issue on all clients (XP, 7 x86, and 7 x64). I started
with an error of 800B0001 and after googling installed KB2720211 to fix it. Now I am getting error 8024400E on clients when I attempt to update. I followed a technet walkthrough and verified that my WSUS settings are all correct (at least regarding iis,
registry, gpo settings, and file system permissions). I am able to download CAB files from the WSUS server by going to the proper address in a browser. Here is a snippet from my WindowsUpdate log on my client:
2013-12-20 10:27:29:784 972 23ac AU #############
2013-12-20 10:27:29:784 972 23ac AU ## START ## AU: Search for updates
2013-12-20 10:27:29:784 972 23ac AU #########
2013-12-20 10:27:29:785 972 23ac AU <<## SUBMITTED ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:785 972 2bcc Agent *************
2013-12-20 10:27:29:785 972 2bcc Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-12-20 10:27:29:785 972 2bcc Agent *********
2013-12-20 10:27:29:785 972 2bcc Agent * Online = Yes; Ignore download priority = No
2013-12-20 10:27:29:785 972 2bcc Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation'
and RebootRequired=1"
2013-12-20 10:27:29:785 972 2bcc Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-12-20 10:27:29:785 972 2bcc Agent * Search Scope = {Machine}
2013-12-20 10:27:29:785 972 2bcc Setup Checking for agent SelfUpdate
2013-12-20 10:27:29:785 972 2bcc Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2013-12-20 10:27:29:785 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-12-20 10:27:29:789 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:794 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-12-20 10:27:29:797 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:799 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-12-20 10:27:29:803 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:808 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-12-20 10:27:29:812 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:821 972 2bcc Setup Determining whether a new setup handler needs to be downloaded
2013-12-20 10:27:29:821 972 2bcc Setup SelfUpdate handler is not found. It will be downloaded
2013-12-20 10:27:29:821 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:823 972 2bcc Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:823 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:835 972 2bcc Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:835 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:852 972 2bcc Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:852 972 2bcc Setup SelfUpdate check completed. SelfUpdate is NOT required.
2013-12-20 10:27:29:884 972 2bcc PT +++++++++++ PT: Synchronizing server updates +++++++++++
2013-12-20 10:27:29:884 972 2bcc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusservername/ClientWebService/client.asmx
2013-12-20 10:27:29:896 972 2bcc PT WARNING: Cached cookie has expired or new PID is available
2013-12-20 10:27:29:896 972 2bcc PT Initializing simple targeting cookie, clientId = 488f3922-1a4e-4921-b015-25957eeb6500, target group = http://wsusservername, DNS name = mycomputer.domain.local
2013-12-20 10:27:29:896 972 2bcc PT Server URL = http://wsusservername/SimpleAuthWebService/SimpleAuth.asmx
2013-12-20 10:27:29:902 972 2bcc PT WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
2013-12-20 10:27:29:902 972 2bcc PT WARNING: SOAP Fault: 0x000190
2013-12-20 10:27:29:902 972 2bcc PT WARNING: faultstring:Fault occurred
2013-12-20 10:27:29:902 972 2bcc PT WARNING: ErrorCode:InternalServerError(5)
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Message:(null)
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie";
2013-12-20 10:27:29:902 972 2bcc PT WARNING: ID:9d989bf6-04e3-44a9-8ffd-f20bb997b3f0
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: PopulateAuthCookies failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: RefreshCookie failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: RefreshPTState failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Sync of Updates: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc Agent * WARNING: Failed to synchronize, error = 0x8024400E
2013-12-20 10:27:29:902 972 2bcc Agent * WARNING: Exit code = 0x8024400E
2013-12-20 10:27:29:902 972 2bcc Agent *********
2013-12-20 10:27:29:902 972 2bcc Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-12-20 10:27:29:902 972 2bcc Agent *************
2013-12-20 10:27:29:902 972 2bcc Agent WARNING: WU client failed Searching for update with error 0x8024400e
2013-12-20 10:27:29:902 972 1bc8 AU >>## RESUMED ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:902 972 1bc8 AU # WARNING: Search callback failed, result = 0x8024400E
2013-12-20 10:27:29:902 972 1bc8 AU # WARNING: Failed to find updates with error code 8024400E
2013-12-20 10:27:29:902 972 1bc8 AU #########
2013-12-20 10:27:29:902 972 1bc8 AU ## END ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:902 972 1bc8 AU #############
2013-12-20 10:27:29:903 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:29:903 972 1bc8 AU AU setting next detection timeout to 2013-12-20 21:27:29
2013-12-20 10:27:29:903 972 1bc8 AU Setting AU scheduled install time to 2013-12-21 10:00:00
2013-12-20 10:27:29:903 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:29:904 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:34:498 972 2bcc Report REPORT EVENT: {2519DC64-E7F9-499B-A2F8-B58DA4A0C08A} 2013-12-20 10:27:29:902-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software Synchronization Windows Update Client failed
to detect with error 0x8024400e.
2013-12-20 10:27:34:502 972 2bcc Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2013-12-20 10:27:34:502 972 2bcc Report WER Report sent: 7.6.7600.256 0x8024400e 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2013-12-20 10:27:34:502 972 2bcc Report CWERReporter finishing event handling. (00000000)
I focused in on "GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200" and did some googling which all points at Microsoft Office 2003 SP1 update as being the culprit, and I followed
the instructions on a technet site to disable the update and am still getting the same error. I'm stumped at this point, and I thought I would post here in the hope that someone can help me before I end up just wiping it out and reinstalling (which I'm worried
won't even solve it).

I focused in on "GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200" and did some googling which all points at Microsoft Office 2003 SP1 update as being the culprit, and I followed
the instructions on a technet site to disable the update and am still getting the same error.
While you're definitely on the right track, the Office2003SP1 update really has not been an issue since WSUS Service Pack 2 was released in October 2009 (and really, the Office2003SP1 update that was the cause of this was replaced long before that even,
so you probably don't even have the defective update on your server).
However, the error is generally associated with the presence of defective update(s) on the WSUS server, so the first thing to do is address any potential issues caused by a failed install of KB2720211.
If the error still persists after verifying that all other aspects of the server are fully operational, review the list of not-Declined updates on your WSUS server and make sure that:
All Expired updates are Declined (and then run the Server Cleanup Wizard and let it delete the expired updates).
All approvals for older revisions have been removed (and then run the Server Cleanup Wizard and let it delete the older revisions).
All approvals for superseded updates have been removed. (And then, when they report as 100% Not Applicable, decline them, and then run the Server Cleanup Wizard so that it can delete the files associated with those updates).
Once all of the potentially problematic updates have been removed from the view of the Windows Update Agent, and if this error then persists, we can evaluate it from a more focused perspective.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Two WSUS server, both have information of imaged computers

Hi
I have SCCM 2012 R2 and MDT 2013 and WSUS on one server. And other server with just WSUS for update installation in MDT Build and Capture.
All deployments go via SCCM.
1. Is it normal behavior? After Capture, I imported image into SCCM and deployed via SCCM pxe boot and after that I can see that this new deployed computer is visible in both WSUS server under All computers?
I thought that 2nd WSUS is just for build and capture.
2. Do I need restore MDT on SCCM server how it was before installing 2nd WSUS and install separate MDT on that 2nd WSUS server for build and capture purposes only?

1. Is it normal behavior? After Capture, I imported image into SCCM and deployed via SCCM pxe boot and after that I can see that this new deployed computer is visible in both WSUS server under All computers?
Yes, this is normal.
I thought that 2nd WSUS is just for build and capture.
That may well be, but once a computer is registered with that server, it will stay registered until somebody or something (read: Server Cleanup Wizard) DELETES old computers from the database.
2. Do I need restore MDT on SCCM server how it was before installing 2nd WSUS and install separate MDT on that 2nd WSUS server for build and capture purposes only?
No, and you *cannot* use a Software Update Point for supporting your MDT activities. You just need to either remove those computers regularly (read: manually) from the standalone WSUS, or run the Server Cleanup Wizard once a month and they'll be removed them
automagically 30 days after they're done with that WSUS server.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Remove the updates Installed to the client from WSUS SERVER

WSUS Server running on the Windows Server 2008 R2. Is there a way to get rid of updates that have been pushed out and installed on all client computers? because currently I am running out of disk space and I really don't want to increase the disk space
further more.
I tried the Server Cleanup Wizard but it didn't help much as it only cleans out unnecessary and declined updates.

Hi,
On current situation, please refer to the following article and check if can help you.
What
to do when your WSUSContent folder grows too large
Based on your description, I understand that you know which updates had been installed. In other words, you
know which updates will never be used. In WSUS server, please navigate to those updates and right click them, then select
Decline. (Please note: if have downstream replica servers,
please don’t Decline these updates directly). Then please run the Server Cleanup Wizard again and monitor the result. If anything I misunderstand, please don’t hesitate to let me know.
In addition, this issue seems to be more related to WSUS configuration. As Dave suggested, posting this question
in
WSUS Forum will be better. I believe we will get a better assistance there.
If any update, please feel free to let us know.
Hope this helps.
Best regards,
Justin Gu

The WSUS administration console was unable to connect to the WSUS Server via the remote API. (Server 2k8)

I have installed a new server for WSUS on Server 2k8, This is a stand alone server on Internet No client system is connected on this server as I have to copy these updates to my LAN which never connects to internet. (Previously I was using server 2k3. for
online & server 2008 on my LAN , now I have changed the server for Online)
Wsus has finished the synchronization & downloaded updates of around 67GB & its downloading more updates. The server shows me some updates are waiting to approved. but when I click the link for those updates I get following error message.
error code is as follows -
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.WebException -- The operation has timed out
Source
System.Web.Services
Stack Trace:
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetAndCacheUpdates(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.UpdatesListPage.GetListRows()
I Have tried desabling the firewall,disabling the antivirus protection. Tried by changing the default rule Please Help.

Hi Sagar,
First, please check if the RAM is exhausted. When there is not enough RAM, this issue may occurs.
Please try to run iisreset on the WSUS server, then try to reconnect.
Also, please try to run the server cleanup wizard to remove the unused update.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

WSUS server clean up

Hi I am new in WSUS, recently on the remote dedicated WSUS server when selecting option "Server Cleanup Wizard" to clean machines which have been replaced and no more on the network I get the error " An error occured when trying to perform a database operation.
This can happen if the database is very busy, if the database service is stopped, or if the connection to the database is lost. Please contact your system Administrator if the problem persists."
This problem comes just in the process to complete the task. I have restarted the server several times and I could not get solution.
what is wrong with this server.

Hi I am new in WSUS, recently on the remote dedicated WSUS server when selecting option "Server Cleanup Wizard" to clean machines which have been replaced and no more on the network I get the error " An error occured when trying to perform a database
operation. This can happen if the database is very busy, if the database service is stopped, or if the connection to the database is lost. Please contact your system Administrator if the problem persists."
This issue is most likely occuring as a result of the "Delete unneeded updates" step, and not while trying to delete old computer entries. Typically it occurs on long-standing systems where the SCW has not been previously used, or on systems with large database
sizes with higher-than-optimal disk defragmentation issues.
Please do the following:
Run the Server Cleanup Wizard with only the option Delete computers selected. By removing dead computers from the database, it significantly reduces the work required by the update scans because approval state and installation
status no longer need to be checked for those systems.
Decline ALL superseded updates reported as 100% Not Applicable.
Run the Server Cleanup Wizard with the Decline expired updates and
Decline superseded updates options selected. This task only changes data in the database and is rarely impacted by fragmentation issues. It will pick up any eligible stragglers that you may have missed in Step 2.
Run the Server Cleanup Wizard with the Delete unused files option selected. While deleting unused files will not help with the database issues while deleting updates, it will help with the disk defragmentation you will be doing
in the next steps.
Stop the database service. Most likely this is the Windows Internal Database service.
Defragment the volume containing the SUSDB.MDF file. If you chose the installation defaults, this file is contained in C:\WSUS\UpdateServicesDBFiles. Most likely defragmentation will also require you to reboot the server, unless the \WSUS folder is on a
different volume.
Restart the database service (unless you had to reboot to defragment drive C:, in which case the database service should already be running).
Obtain the WSUS Database Maintenance script described in the section Reindex the WSUS Database found in the WSUS Operations Guide. Run
the script.
Run the Server Cleanup Wizard with the Delete unneeded updates option. This task should now complete with a defragmented and reindexed database.
Repeat steps 4 through 8 a second time to ensure optimal performance of the database after removal of these unneeded updates.
Continue to use the Server Cleanup Wizard monthly, in combination with removals of approvals from unneeded superseded updates to maintain optimal performance of your WSUS server.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2011)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com

WSUS Server Cleanup Wizard... to run or not to run?

Similar Messages

Maybe you are looking for