Wsus not updating windows 7 clients

Rated 3.82/5 based on 530 customer reviews

The new server is a 64-bit 2008 R2 server and the old one was a 32-bit 2008 server, but the clients don't care about that, do they?

The new clients that work correctly are all 64-bit, but some of the older clients that are not working are 64-bit and some are 32-bit.

2014-10-22 :448 972 fb0 AU AU setting next detection timeout to 2014-10-23 2014-10-22 :448 972 fb0 AU Setting AU scheduled install time to 2014-10-22 2014-10-22 :448 972 fb0 AU Successfully wrote event for AU health state:0 2014-10-22 :449 972 fb0 AU Successfully wrote event for AU health state:0 2014-10-22 :450 972 10a4 Report CWERReporter finishing event handling.

(00000000) 2014-10-22 :435 972 10a4 Report REPORT EVENT: 2014-10-22 :436-0400 1 147 101 0 0 Automatic Updates Success Software Synchronization Windows Update Client successfully detected 0 updates.

The new server has a different name, but I updated the GPO to reflect the new server name but the existing clients are not reporting.I have also tried manually replacing all the files from the windows update agent 7.4.7600.226 onto a windows 7 system suffering the problem.If I look at the WSUS console it does get change from version 7.3.7600.16385 to 7.4.7600.226 but it doesnt help me fix the problem.I have included an abstract of a file from one of the affect machines.------------ 2010-07-07 :862 900 b60 Misc =========== Logging initialized (build: 7.3.7600.16385, tz: 0930) =========== 2010-07-07 :880 900 b60 Misc = Process: C:\Windows\system3210-07-07 :880 900 b60 Misc = Module: c:\windows\system3210-07-07 :862 900 b60 Service ************* 2010-07-07 :880 900 b60 Service ** START ** Service: Service startup 2010-07-07 :880 900 b60 Service ********* 2010-07-07 :956 900 b60 Agent * WU client version 7.3.7600.16385 2010-07-07 :956 900 b60 Agent * Base directory: C:\Windows\Software Distribution 2010-07-07 :957 900 b60 Agent * Access type: No proxy 2010-07-07 :957 900 b60 Agent * Network state: Connected 2010-07-07 :111 900 b60 Report CWERReporter:: Init succeeded 2010-07-07 :112 900 b60 Agent *********** Agent: Initializing Windows Update Agent *********** 2010-07-07 :112 900 b60 Agent *********** Agent: Initializing global settings cache *********** 2010-07-07 :112 900 b60 Agent * WSUS server: 2010-07-07 :112 900 b60 Agent * WSUS status server: 2010-07-07 :112 900 b60 Agent * Target group: (Unassigned Computers) 2010-07-07 :112 900 b60 Agent * Windows Update access disabled: No 2010-07-07 :122 900 b60 Dnld Mgr Download manager restoring 0 downloads 2010-07-07 :123 900 b60 AU ########### AU: Initializing Automatic Updates ########### 2010-07-07 :124 900 b60 AU AU setting next detection timeout to 2010-07-07 2010-07-07 :124 900 b60 AU # WSUS server: 2010-07-07 :124 900 b60 AU # Detection frequency: 22 2010-07-07 :124 900 b60 AU # Approval type: Scheduled (Policy) 2010-07-07 :124 900 b60 AU # Scheduled install day/time: Every day at 2010-07-07 :124 900 b60 AU # Auto-install minor updates: Yes (User preference) 2010-07-07 :125 900 b60 AU Setting AU scheduled install time to 2010-07-07 2010-07-07 :553 900 b60 Report *********** Report: Initializing static reporting data *********** 2010-07-07 :553 900 b60 Report * OS Version = 6.1.7600.0.0.65792 2010-07-07 :553 900 b60 Report * OS Product Type = 0x00000004 2010-07-07 :590 900 b60 Report * Computer Brand = Gigabyte Technology Co., Ltd.

Leave a Reply