Link to home
Start Free TrialLog in
Avatar of Jamie McCarthy
Jamie McCarthyFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Windows 2003 R2 wont update from WSUS

Hi Experts,

Ive got a WSUS infrastructure which has been working fine until I added a WIndows 2003 R2 machine as a client.

The machine is registered with WSUS, it has been set up via GPO to point to the WSUS server for updates. All my other clients are working fine, these include Windows 2008R2, 2008R1, Vista and XP. (They all share the same GPO Setting)

I notice on the Windows 2003 box the update program still points you to a Microsoft Internet Website.

I am confident (at the moment) that WSUS is working correctly, its even reporting that it needs to apply updates to the windows 2003 machine. I feel like I am missing a simple step that is specific to windows 2003.

Any Ideas ????

PS - WSUS is ver 3 running on Windows 2008 R2
Avatar of rizla7
rizla7

is the wsus policy being applied to the client machine? rsop, gpresult, etc..
Avatar of Jamie McCarthy

ASKER

Yes it is being applied
SOLUTION
Avatar of rizla7
rizla7

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Don
Does clientdiag come up all passes?
Does the following command from command prompt show you are pointed to the correct WSUS server?
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"
Are there any errors in your windowsupdate.log?
Hi dstewartjr,

The registry entry looks correct. I checked the log and I see various errors.

I've attached the log file. Note I have had redact names etc.
WSUSLOG.txt
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
looking at the logs, the client looks fine.

Setup        * IsUpdateRequired = No

its detectin the update, but your log ends here

AU client got new directive = 'Install Approval', serviceId

which means it's impossible to tell what happened when it went into 'install' mode
"looking at the logs, the client looks fine."



GetCookie failure, error = 0x8024400D and  hr = 8024E001
that could indeed be a client issue, or an iis issue. probably client tho, didnt see that.
doesn't break after that point, strange. i wonder if we could get the rest of the log ;o
That is why I suggested ID:28464446  :)
in that case, check this out:

http://www.winserverkb.com/Uwe/Forum.aspx/wsus/769/0x8024400D
http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/901ad7af-bfc2-4a21-9409-2977a087cd1e

something to do with sus clientid .. although this issue has 20,000 possible causes form the looks of it. so good luck ;p
Duplicate Susclientid is old news,


http://support.microsoft.com/kb/903262 

We have added an automatic feature to the Windows Update Agent that is  installed on WSUS client computers. This feature can help address this  duplicate-SusClientID issue. The feature provides a solution that is  added to the client-side Windows Update Agent starting with version  7.0.6000.374. (This version is the client version that was included with  WSUS 3.0.)


The latest version is 7.4.7600.226
and this is assuming 2003 r2 includes the updated client out of the box. might also try downloading the update client from ms directly.

http://technet.microsoft.com/en-us/library/bb932139.aspx
already been mentioned, well excuse me. i cant think of anything else. ;p
Good Morning all,

Well I don't know whats happened but 3 days later without making any changes to anything the updates have now started working. Thank you all for you comments and suggestions. I am now going to try and find out what has changed. If I find anything I post a comment here.

Thanks All
Was there a reboot in the interim?
No.
well it was most likely the reinstall, if not that then the cache clear. those 2 cause most of the issues i've seen with wuauclt.
Jamiemc,
 
You never said whether you reinstalled the "Windows Update Agent" or not
Sorry your right I didn't elaborate.

I logged onto the server this morning after downloading the agent last night to install it, and thats when I found the updates had taken.