IF you have facing the problem like the log shows

2008-03-28 12:10:24:947 1152 274 AU ## START ## AU: Search for updates
2008-03-28 12:10:24:947 1152 274 AU #########
2008-03-28 12:10:24:947 1152 274 AU <<## SUBMITTED ## AU: Search for updates [CallId = {C98707A2-D7AF-4D38-A4D5-BAA0482F53E3}]
2008-03-28 12:10:24:947 1152 864 Agent *************
2008-03-28 12:10:24:947 1152 864 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-03-28 12:10:24:947 1152 864 Agent *********...
Continue reading ...

Reconnect the Wsus...
you need to delete the identification info from the registry and reboot the PC in order for it to report properly. Here is the relevant information:

HKLM\Software\Microsoft\Windows\CurrentVersion\Windowsupdate
Delete the following entries, if present:
AccountDomainSID
SusClientID
PingID

Reboot.

The appropriate entries will be recreated when the PC reconnects to WUS.
Continue reading ...

The following events are occured while updating wsus 2.0 to wsus 3.0

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12012
Description:
The API Remoting Web Service is not working.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12032
Description:
The Server Synchronization Web Service is not working.


Event Type: Error
Event Source: Windows Server Update Services
Event Category: W...
Continue reading ...

Configuring Automatic Updates by using Group Policy

The easiest way to configure automatic updates is through the group policy, in environments where this is possible. If group policies (AD) are not available, you can use the registry file which has to be deployed to every machine. This registry file, or group policy template if you're using Active Directory, enables advanced features available with the new WSUS client.

In order to configure client machines using group policy it is ...
Continue reading ...

Check in the IIS Manager to see what authentication type is enabled on the directories that are part of the WSUS Server. Windows Integrated Authentication needs to be enabled on the "SimpleAuthWebService", "Content", "ClientWebService", "ReportingWebService" and the "SelfUpdate" folders. After correcting this, all my clients are making successful connections and downloading approved updates, as well as reporting to the server that the client exists and is using the Windows Server Upda...
Continue reading ...

You see the following errors in "%Windir%\WindowsUpdate.log".

FATAL: Failed to get session from datastore, error = 0x80004002
FATAL: Failed to Unserialize from data store, error = 0x80004002
WARNING: Exit code = 0x80004002
WARNING: InitAUComponents Failed, will restart AU in 30 mins, error = 0x80004002
DnldMgr FATAL: DM:CAgentDownloadManager::CheckAllCallDownloadStates: GetSession failed with 0x80004002.

1. If you have a proxy server -

Stop Automatic Update Service - "Net stop wuauserv".
Run the fol...
Continue reading ...

It looks like the client datastore failed to initialize.
1. Open a CMD prompt on the client.
2. Type "net stop wuauserv" (without quotes) .
3. Type "cd %Windir%\SoftwareDistribution".
4. Type "RD /s /q Datastore" (this will remove the client datastore).
5. Type "net start wuauserv" (without quotes) .
6. Type "wuauclt /detectnow" then check %Windir%\WindowsUpdate.log if it is successful.
OR, just stop the Automatic Updates Service and delete "%Windir%\SoftwareDistribution\DataStore" folder and ...
Continue reading ...

DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.

"%Windir%\WindowsUpdate.log" shows - AU AU Restart required

Restart the service and forced update detection and the error is gone.

DnldMgr Download manager restoring 2 downloads
Agent * Succeeded to load 2 persisted download calls
DnldMgr Retrieved 2 persisted download jobs
DnldMgr * Restored download job.

The computer succesfully updated.
Continue reading ...

The 0x8024402C or 0x8024502D error codes typically occur because an incorrect character exists in the proxy override settings
To resolve these errors, remove characters from the proxy exception list, and then clear the proxy cache. To do this, follow these steps:
1. Open Internet Explorer.
2. On the Tools menu, click Internet Options.
3. Click the Connections tab, click LAN Settings, and then click Advance.
4. Delete any entry in the Exceptions section.
5. Quit Internet Explorer.
6. Click St...
Continue reading ...