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: 222
  • Last Modified:

Clients not reporting

I'm running WSUS to update ten Windows 2003 servers and ninety Windows XP clients.  Three of the servers are not reporting.  I have run cliendiag.exe on these three servers, and they all pass.  However, when looking at the WindowsUpdate.log files on these servers, they wrongly point to an old decommissioned WSUS server -

2008-06-10      14:12:57:688       828      4b4      PT        Server URL = http://fhserver05/SimpleAuthWebService/SimpleAuth.asmx

instead of the current WSUS server which is fhserver08.

The WSUS server is correctly shown as fhserver08 in the registry of each of these servers, and I can find no trace in the registry of the old server, fhserver05.

Can anyone help please?
0
vphul
Asked:
vphul
  • 2
1 Solution
 
John Gates, CISSPSecurity ProfessionalCommented:
There is a GPO object associated with the WSUS update location in domains..  Maybe te old server is referenced there?

http://www.microsoft.com/technet/community/columns/sectip/st0506.mspx

-D-
0
 
vphulAuthor Commented:
A Group Policy does point the servers correctly to fhserver08, but when I run rsop.msc on one of the affected servers, it shows the WSUS server incorrectly as fhserver05.
0
 
vphulAuthor Commented:
I finally found the answer to this issue. There was a problem with Group Policy/SysVol replication between the domain controllers, which meant that some servers and clients were not getting the current GPOs.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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