Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 948
  • Last Modified:

WSUS clients not receiving updates

We have recently set up a new WSUS server on windows 2008.  Clients have registered on the new server via group policy and are appearing in their correct groups.  However the clients refuse to detect any updates.  For example in the WSUS console machines show as requiring updates however the clients don't receive them.  In the clients windowsupdate.log are the following errors:

2011-10-18      11:38:49:549      1200      910      PT      +++++++++++  PT: Synchronizing server updates  +++++++++++
2011-10-18      11:38:49:549      1200      910      PT        + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://XX.XX.0.26:80/ClientWebService/client.asmx
2011-10-18      11:38:49:564      1200      910      PT      Initializing simple targeting cookie, clientId = 5e4a866c-ee37-44c1-b3fe-2ac03535334d, target group = WSUS Test Group, DNS name = ws-93fnv3j.companyname.local
2011-10-18      11:38:49:564      1200      910      PT        Server URL = http://XX.XX.0.26:80/SimpleAuthWebService/SimpleAuth.asmx
2011-10-18      11:38:49:580      1200      910      PT      WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2011-10-18      11:38:49:580      1200      910      PT      WARNING: SOAP Fault: 0x00012c
2011-10-18      11:38:49:580      1200      910      PT      WARNING:     faultstring:Fault occurred
2011-10-18      11:38:49:580      1200      910      PT      WARNING:     ErrorCode:ServerChanged(4)
2011-10-18      11:38:49:580      1200      910      PT      WARNING:     Message:Server rolled back since last call to GetCookie
2011-10-18      11:38:49:580      1200      910      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2011-10-18      11:38:49:580      1200      910      PT      WARNING:     ID:c262e598-4d08-42a1-9055-02701ed99f78
2011-10-18      11:38:49:580      1200      910      PT      WARNING: PTError: 0x80244015
2011-10-18      11:38:49:580      1200      910      PT      WARNING: GetCookie_WithRecovery failed : 0x80244015
2011-10-18      11:38:49:580      1200      910      PT      WARNING: RefreshCookie failed: 0x80244015
2011-10-18      11:38:49:580      1200      910      PT      WARNING: RefreshPTState failed: 0x80244015
2011-10-18      11:38:49:580      1200      910      PT      WARNING: Sync of Updates: 0x80244015
2011-10-18      11:38:49:596      1200      910      PT      WARNING: Cached cookie has expired or new PID is available
2011-10-18      11:38:49:596      1200      910      PT      Initializing simple targeting cookie, clientId = 5e4a866c-ee37-44c1-b3fe-2ac03535334d, target group = WSUS Test Group, DNS name = ws-93fnv3j.companyname.local
2011-10-18      11:38:49:596      1200      910      PT        Server URL = http://XX.XX.0.26:80/SimpleAuthWebService/SimpleAuth.asmx
2011-10-18      11:38:51:783      1200      910      Agent        * WARNING: Failed to synchronize, error = 0x80244015
2011-10-18      11:38:51:783      1200      910      DnldMgr      File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
2011-10-18      11:38:51:783      1200      910      Agent      Server changed and need resyncing with server
2011-10-18      11:38:52:674      1200      910      PT      +++++++++++  PT: Synchronizing server updates  +++++++++++
2011-10-18      11:38:52:674      1200      910      PT        + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://XX.XX.0.26:80/ClientWebService/client.asmx
2011-10-18      11:39:12:704      1200      910      PT      +++++++++++  PT: Synchronizing extended update info  +++++++++++
2011-10-18      11:39:12:704      1200      910      PT        + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://XX.XX.0.26:80/ClientWebService/client.asmx
2011-10-18      11:39:13:048      1200      910      Agent        * Found 0 updates and 62 categories in search; evaluated appl. rules of 738 out of 1538 deployed entities
2011-10-18      11:39:13:048      1200      910      Agent      *********
2011-10-18      11:39:13:048      1200      910      Agent      **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2011-10-18      11:39:13:048      1200      910      Agent      *************
2011-10-18      11:39:13:064      1200      11d8      AU      >>##  RESUMED  ## AU: Search for updates [CallId = {2C4C96D2-FA31-4DB3-8478-938C2EF006E6}]
2011-10-18      11:39:13:064      1200      11d8      AU        # 0 updates detected
2011-10-18      11:39:13:064      1200      11d8      AU      #########
2011-10-18      11:39:13:064      1200      11d8      AU      ##  END  ##  AU: Search for updates [CallId = {2C4C96D2-FA31-4DB3-8478-938C2EF006E6}]
2011-10-18      11:39:13:064      1200      11d8      AU      #############
2011-10-18      11:39:13:064      1200      11d8      AU      Featured notifications is disabled.

I have tried running the following script below on an affected PC to no avail, anyone have any ideas how to resolve this problem?

@Echo off
if exist %systemdrive%\SUSClientID.log goto end
net stop wuauserv
net stop bits
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f  > %systemdrive%\SUSClientID.log 2>&1
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f  >> %systemdrive%\SUSClientID.log 2>&1
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f  >> %systemdrive%\SUSClientID.log 2>&1
net start wuauserv
wuauclt.exe /resetauthorization /detectnow          
:end
exit
0
Riana
Asked:
Riana
  • 3
  • 2
1 Solution
 
AcklesCommented:
Can you please clear something, is there any client which is getting updates?
I mean do you have a good scenario as well?

A
0
 
AcklesCommented:
Also, is it possible to have complete environment?
Service Pack of Server
OS & SP of Client
What other software you are running with WSUS? Is there  SCM in the environment or not?

A
0
 
AcklesCommented:
Please have a look at this, it addresses one of the error from your log: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

http://www.wsus.info/index.php?showtopic=9246

To get the updates, the cookies have to be registered properly, try this it might be a quick fix & maybe fixes it fast.

A
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
Donald StewartNetwork AdministratorCommented:
First it is not necessary to add ":80" in your GPO

Secondly verify that your new WSUS server is indeed using port 80 and not 8530

If the latter change your GPO to match.

What version of WSUS did your previous WSUS server have?

You might need to ensure the clients have the latest windows update agent installed

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

http://technet.microsoft.com/en-us/library/bb932139.aspx

0
 
RianaAuthor Commented:
Hi,

First of all thanks for you suggests.  In the end I ran a revised batch file on the clients and this fixed the problem.  The batch file script I ran was:

rem Fixes problem with client machines not showing up on the server due to imaging method
cd c:
rmdir "C:\Batch\WSUS\"
rmdir "C:\Batch\WSUS2\"
rmdir "C:\Batch\WSUS3\"
IF EXIST "C:\Batch\WSUSID\" GOTO :END
@echo on
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f

@echo Triggering detection after resetting WSUS client identity
net stop wuauserv
net start wuauserv
wuauclt /resetauthorization /detectnow
mkdir "C:\Batch\WSUSID\"
END

So it was a problem to do with the WSUS ID of the image PC being used on more than one machine.  The machines are now picking up updates again.
0
 
RianaAuthor Commented:
It fixed my specific problem.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now